SIST ETS 300 392-11-11 E1:2003

Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 11: Call Waiting (CW)

To define the Stage 2 requirements for TETRA SS Call Waiting

Prizemni snopovni radio (TETRA) – Govor in podatki (V+D) – 11. del: Dopolnilne storitve stopnje 2 – 11. poglavje: Čakajoči klic (CW)

General Information

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.070.10 - Terrestrial Trunked Radio (TETRA)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 392-11-11 ed.1 (2000-09) - Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 11: Call Waiting (CW)

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 392-11-11 E1:2003
01-december-2003
3UL]HPQLVQRSRYQLUDGLR7(75$±*RYRULQSRGDWNL9'±GHO'RSROQLOQH
VWRULWYHVWRSQMH±SRJODYMHýDNDMRþLNOLF&:
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary
services stage 2; Sub-part 11: Call Waiting (CW)
Ta slovenski standard je istoveten z: ETS 300 392-11-11 Edition 1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST ETS 300 392-11-11 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST ETS 300 392-11-11 E1:2003

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

SIST ETS 300 392-11-11 E1:2003
EUROPEAN ETS 300 392-11-11
TELECOMMUNICATION September 2000
STANDARD
Source: TETRA Reference: DE/TETRA-03001-11-11
ICS: 33.020
Key words: Data, radio, speech, stage 2, supplementary service, TETRA
Terrestrial Trunked Radio (TETRA);
VoiceplusData (V+D);
Part 11: Supplementary services stage 2;
Sub-part 11: Call Waiting (CW)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: [e-mail] - http://www.etsi.org
Tel.:[phone]- Fax:[phone]
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.

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

SIST ETS 300 392-11-11 E1:2003
Page 2
ETS 300 392-11-11: September 2000
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Standards Making Support Dept." at the address shown on the title page.

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

SIST ETS 300 392-11-11 E1:2003
Page 3
ETS 300 392-11-11: September 2000
Contents
Foreword.5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .8
3.1 Definitions .8
3.2 Abbreviations .8
4 Functional model.8
4.1 Functional model description .8
4.2 Description of functional entities .10
4.2.1 Served user functional entity, FE1 .10
4.2.2 Served user SwMI functional entity, FE21 .10
4.2.3 Served user new SwMI functional entity, FE21'.10
4.2.4 Affected user SwMI functional entity, FE25 .10
4.2.5 Served user home SwMI FE, FE20.11
4.2.6 Affected user functional entity, FE5 .11
4.3 Relationship of functional model to basic call functional model .11
5 Information flows .12
5.1 Definition of information flows.12
5.1.1 ACTIVATE.12
5.1.2 ACTIVATE ACK .12
5.1.3 DEACTIVATE.12
5.1.4 DEACTIVATE ACK .12
5.1.5 INFORM 1 .13
5.1.6 INFORM 2 .13
5.1.7 INVOKE.13
5.1.8 INVOCATION FAILURE.13
5.1.9 rd_LOCATION CHANGE .14
5.1.10 re_LOCATION CHANGE .15
5.2 Relationship of information flows to basic individual call information flows.15
5.3 Service primitives.16
5.4 Examples of information flow sequences .17
5.4.1 Activation.17
5.4.2 Deactivation.18
5.4.3 Invocation and operation.18
5.4.3.1 Successful invocation .18
5.4.3.2 Successful acceptance of a waiting call .19
5.4.3.3 Unsuccessful invocation .20
5.4.3.4 Migration of served user with waiting calls .21
6 FE actions .21
6.1 Functional Entity actions of FE1 .21
6.2 Functional Entity actions of FE20 .22
6.3 Functional Entity actions of FE21 .22
6.4 Functional Entity actions of FE21' .23
6.5 Functional Entity actions of FE25 .23
6.6 Functional Entity actions of FE5 .23
7 Allocation of functional entities to physical equipment.24
8 Interworking considerations .24

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

SIST ETS 300 392-11-11 E1:2003
Page 4
ETS 300 392-11-11: September 2000
Annex A (informative): Bibliography . 26
History. 27

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

SIST ETS 300 392-11-11 E1:2003
Page 5
ETS 300 392-11-11: September 2000
Foreword
This European Telecommunication Standard (ETS) has been produced by the Terrestrial Trunked Radio
(TETRA) Project of the European Telecommunications Standards Institute (ETSI).
This ETS is a multi-part standard and will consist of the following parts:
Part 1: "General network design";
Part 2: "Air Interface (AI)";
Part 3: "Interworking at the Inter-System Interface (ISI)";
Part 4: "Gateways basic operation";
Part 5: "Peripheral Equipment Interface (PEI)";
Part 6: "Line connected Station (LS)";
Part 7: "Security";
Part 9: "General requirements for supplementary services";
Part 10: "Supplementary services stage 1";
Part 11: "Supplementary services stage 2";
Part 12: "Supplementary services stage 3";
Part 13: "SDL model of the Air Interface (AI)";
Part 14: "Protocol Implementation Conformance Statement (PICS) proforma specification".
Transposition dates
Date of adoption of this ETS: 7 July 2000
Date of latest announcement of this ETS (doa):
31 October 2000
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 April 2001
Date of withdrawal of any conflicting National Standard (dow): 30 April 2001

---------------------- Page: 7 ----------------------

SIST ETS 300 392-11-11 E1:2003
Page 6
ETS 300 392-11-11: September 2000
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 392-11-11 E1:2003
Page 7
ETS 300 392-11-11: September 2000
1 Scope
The present ETS specifies the stage 2 description of the Supplementary Service Call Waiting (SS-CW)
for the Terrestrial Trunked Radio (TETRA).
SS-CW permits a called user to acknowledge an incoming individual call while he is already busy.
Subsequently that user shall have the choice to accept, reject or ignore that incoming call.
Man-Machine Interface (MMI) and charging principles are outside of the scope of this ETS.
Supplementary service specifications are produced in three stages according to the method defined in
CCITT Recommendation I.130 [1]. The stage 2 description identifies the functional capabilities and the
information flows needed to support the supplementary service as specified in its stage 1 description (see
ETS 300 392-10-11 [6]). The stage 2 description is followed by the stage 3 description, which specifies
the protocols at the air interface and at the various Inter-System Interfaces (ISI) to support the service.
This document is applicable to TETRA Voice plus Data terminal equipment and networks.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the
latest edition of the publication referred to applies.
[1] CCITT Recommendation I.130 (1988): "Method for the characterization of
telecommunication services supported by an ISDN and network capabilities of
an ISDN".
[2] ETSI ETS 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 2: Air Interface (AI)".
[3] ETSI ETS 300 392-3-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 2:
Additional Network Feature Individual Call (ANF-ISIIC)".
[4] ETSI ETS 300 392-3-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 5:
Additional Network Feature for Mobility Management (ANF-ISIMM)".
[5] ETSI ETS 300 392-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 9: General requirements for supplementary services".
[6] ETSI ETS 300 392-10-11: "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 10: Supplementary services stage 1; Sub-part 11: Call Waiting
(CW)".
[7] ETSI ETS 300 392-12-11: "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 12: Supplementary services stage 3; Sub-part 11: Call Waiting
(CW)".
[8] ISO/IEC 11574: "Information technology - Telecommunications and information
exchange between systems - Private Integrated Services Network -
Circuit-mode 64 kbit/s bearer services - Service description, functional
capabilities and information flows".

---------------------- Page: 9 ----------------------

SIST ETS 300 392-11-11 E1:2003
Page 8
ETS 300 392-11-11: September 2000
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the definitions of ETS 300 392-9 [5] apply with the following modifications:
affected user: callinguser inanindividual call.
affected user SwMI: SwMI where the affected user is currently registered. The affected user SwMI is the
originating SwMI in an individual call.
served user: individual user for whom SS-CW supplementary service has been subscribed. When
SS-CW has been activated for him, that user can thus successfully invoke the supplementary service for
a new incoming individual call while he is already busy.
served user SwMI: SwMI where the served user is currently registered. In an individual call, the served
user SwMI is the terminating SwMI.
timer T2: measures the waiting time for the offered call from user C to be either accepted or cleared by
the served user B after SS-CW has been invoked. This timer is a network basic call timer. It corresponds
to the basic call timer T304 on the called user side (see clause 14 of ETS 300 392-2 [2]).
3.2 Abbreviations
For the purposes of this ETS, the following general abbreviations apply:
ANF-ISIIC Additional Network Feature - Inter-System Interface Individual Call
ANF-ISIMM Additional Network Feature - Inter-System Interface Mobility Management
CC Basic Service Call Control functional entity
CCA Basic Service Call Control functional entity agent
NOTE 1: CC and CCA are applied as defined in ISO/IEC 11574 [8].
CW Call Waiting
FE Functional Entity
ISI Inter-System Interface
LS Line Station
MS Mobile Station
SDL Specification an Description Language
SS Supplementary Service
NOTE 2: The abbreviation SS is only used when referring to a specific supplementary service
(e.g. SS-CW).
SwMI Switching and Management Infrastructure
4 Functional model
4.1 Functional model description
The functional model shall comprise the following Functional Entities (FEs):
FE1 Served user functional entity
FE21 Served user SwMI FE
FE21' Served user new SwMI FE
FE25 Affected user SwMI FE
FE20 Served user home SwMI FE
FE5 Affected user FE

---------------------- Page: 10 ----------------------

SIST ETS 300 392-11-11 E1:2003
Page 9
ETS 300 392-11-11: September 2000
The following relationships shall exist:
ra between FE1 and FE21
rb between FE21 and FE5
rc between FE21 and FE25
rd between FE1 and FE21'
re between FE21 and FE21'
rf between FE1 and FE20
Figure 1 shows these FEs and relationships for the basic operational part of SS-CW, when the served
user does not change location after he has invoked SS-CW for a (individual) call.
rb
ra
rc
FE1
FE21 FE25 FE5
Figure 1: Functional model for the basic operational part of SS-CW
Figure 2 shows these FEs and relationships for the operational part of SS-CW when the served user
changes location after he has invoked SS-CW for a (individual) call.
rb
ra rc
FE25
FE1 FE21 FE5
rd re
FE21'
Figure 2: Functional model for the operational part of SS-CW
with location change of the served user
NOTE: Both figures 1 and 2 apply only in the case of individual call since SS-CW does not
apply to group call.

---------------------- Page: 11 ----------------------

SIST ETS 300 392-11-11 E1:2003
Page 10
ETS 300 392-11-11: September 2000
Figure 3 shows these FEs and relationships for the management part of SS-CW.
rf
FE1
FE20
(note 1)
r
anf-isimm
(note 2)
FE21
NOTE 1: All requests issued by the served user are to be addressed to his home SwMI.
NOTE 2: The relationship between FE20 and FE21 is an ANF-ISIMM relationship, across which the
SS-CW profile is exchanged.
Figure 3: Functional model for the management part of SS-CW
4.2 Description of functional entities
4.2.1 Served user functional entity, FE1
FE1 is the functional entity that serves the called user for the invocation of SS-CW.
If the served user changes location with one or more individual call still waiting, FE1 requests FE21' about
possible changes for those calls. It will process the corresponding response (from FE21') according to its
contents: notably if that response indicates a call reference change for some calls still waiting, it will
update accordingly its call references for those calls.
FE1 may also relay the activation and deactivation requests received from the served user to FE20, and
the corresponding responses from FE20 to the served user (as indication primitives).
4.2.2 Served user SwMI functional entity, FE21
When it receives a SS-CW invocation from FE1, FE21 checks whether SS-CW has been activated and, if
so, takes note that the call is waiting, in informing FE5 and FE25.
If the served user changes location with an individual call still waiting, FE21 may attempt to create FE21'.
If that attempt is successful, FE21 passes the data about that call to FE21'. If not, it informs the collocated
individual call control entity about the situation.
4.2.3 Served user new SwMI functional entity, FE21'
If the served user changes location with a call still waiting, FE21' may be created.
FE21' then receives the data about that call and replaces FE21 after it has answered FE1 request about
possible changes for those calls (due to the location change).
4.2.4 Affected user SwMI functional entity, FE25
FE25 receives from FE21 the information that SS-CW has been invoked (by the called user) for the call
and passes it to the collocated individual call control entity.

---------------------- Page: 12 ----------------------

SIST ETS 300 392-11-11 E1:2003
Page 11
ETS 300 392-11-11: September 2000
4.2.5 Served user home SwMI FE, FE20
FE20 processes the optional activation requests received from FE1.
NOTE: When the served user has migrated and is registered in a visited SwMI, the
informationabout SS-CW activationstoredby FE20willbepassedtoFE21by
ANF-ISIMM (see ETS 300 392-3-5 [4]).
4.2.6 Affected user functional entity, FE5
FE5 is the functional entity that serves the affected user (i.e. the calling user) to inform him that SS-CW
has been invoked (by the called user) for his call.
4.3 Relationship of functional model to basic call functional model
Although no formal model has been defined for basic individual call, that model can be readily derived
from the PISN model for basic call, in ISO/IEC 11574 [8].
FE1 shall be collocated with the CCA of the called user in an individual call.
FE21 shall be collocated with the CC functional entity in the terminating SwMI.
Depending on whether the served user has roamed or migrated (with one or more individual calls still
waiting), FE21' shall be collocated with the CC functional entity: either
- in the same terminating SwMI if the served user has roamed; or
- in the new terminating SwMI if the served user has migrated.
FE25 shall be collocated with the CC functional entity in the originating SwMI.
FE5 shall be collocated with the CCA of the calling user in an individual call.
Figure 4 shows the relationship between the models for SS-CW and for the basic individual call.
rb
rc
ra
FE5 FE25 FE21 FE1
r1 r2 r2 r3
C
C A CC CC CCA
CC
(note)
NOTE: It is possible that no intermediate CC be present (i.e. when the called user is registered in his
home SwMI and when no transit Private Integrated (services) Network Exchanges -PINXs- are
present).
Figure 4: Relationship between models for SS-CW and basic individual call

---------------------- Page: 13 ----------------------

SIST ETS 300 392-11-11 E1:2003
Page 12
ETS 300 392-11-11: September 2000
5 Information flows
5.1 Definition of information flows
In the tables listing the information elements in information flows, the column headed "Type" indicates
which of these elements are Mandatory (M), which are Optional (O) and which are Conditional (C).
5.1.1 ACTIVATE
ACTIVATE is an unconfirmed information flow across relationship rf from FE1 to FE20 which is used to
activate SS-CW.
NOTE: The response/confirmation information flow corresponding to the ACTIVATE
request/indication information flow is ACTIVATE ACK (see subclause 5.1.2).
There are no elements in that information flow.
5.1.2 ACTIVATE ACK
ACTIVATE ACK is actually the response/confirmation information flow corresponding to the ACTIVATE
request/indication information flow. It is thus across relationship rf from FE20 to FE1. It is used to respond
to the corresponding activation request.
Table 1 lists the elements within the ACTIVATE ACK information flow.
Table 1: Contents of ACTIVATE ACK
Element Type
Activation result M
Activation failure cause C (note)
NOTE: Conditional on the activation result being negative.
The element activation result shall indicate whether the corresponding activation request has been
successful or not.
The element activation failure cause shall indicate the reason why the activation request by the served
user has failed. That reason may be because SS-CW has not been subscribed to for the user or because
FE20 does not support the activation procedure.
5.1.3 DEACTIVATE
DEACTIVATE is an unconfirmed information flow across relationship rf from FE1 to FE20 which is used
to deactivate SS-CW.
NOTE: The response/confirmation information flow corresponding to the DEACTIVATE
request/indication information flow is DEACTIVATE ACK (see subclause 5.1.4).
There are no elements in that information flow.
5.1.4 DEACTIVATE ACK
DEACTIVATE ACK is actually the response/confirmation information flow corresponding to the
DEACTIVATE request/indication information flow. It is thus across relationship rf from FE20 to FE1. It is
used to respond to the corresponding deactivation request.

---------------------- Page: 14 ----------------------

SIST ETS 300 392-11-11 E1:2003
Page 13
ETS 300 392-11-11: September 2000
Table 2 lists the elements within the DEACTIVATE ACK information flow.
Table 2: Contents of DEACTIVATE ACK
Element Type
Deactivation result M
Deactivation failure cause C (note)
NOTE: Conditional on the deactivation result being negative.
The element deactivation result shall indicate whether the corresponding deactivation request has been
successful or not.
The element deactivation failure cause shall indicate the reason why the deactivation request by the
served user has failed. That reason may be because SS-CW has not been subscribed to for the user or
because FE20 does not support the activation procedure.
5.1.5 INFORM 1
INFORM 1 is an unconfirmed information flow:
- across relationship rb from FE21 to FE5 to inform the affected user about the successful result of
SS-CW invocation;
- across relationship rc from FE21 to FE25 to inform the originating SwMI about the successful result
of SS-CW invocation.
There are no elements in that information flow.
5.1.6 INFORM 2
INFORM 2 is an unconfirmed information flow across relationship rb from FE21 to FE5 to inform the
affected user that the waiting call is being cleared because the served user has changed location and
either the FE21' functional entity cannot be created (e.g. case of migration into a new SwMI that does not
support SS-CW) or the call control entity collocated with FE21' cannot keep "alive" the waiting call.
There are no elements in that information flow.
5.1.7 INVOKE
INVOKE is an unconfirmed information flow across relationship ra from FE1 to FE21 to invoke SS-CW.
There are no elements in that information flow.
5.1.8 INVOCATION FAILURE
INVOCATION FAILURE is an unconfirmed information flow across relationship ra from FE21 to FE1 to
inform the called user who has invoked SS-CW that that invocation has failed.
Table 3 defines the content of the INVOCATION FAILURE information flow.
Table 3: Content of INVOCATION FAILURE
Element Type
Failure cause M

---------------------- Page: 15 ----------------------

SIST ETS 300 392-11-11 E1:2003
Page 14
ETS 300 392-11-11: September 2000
The element failure cause indicates why SS-CW failed. That cause may be that SS-CW: either
- has not been subscribed for that user; or
- has not been activated for that user.
NOTE: The above provision implies that there is a FE21 functional entity. Otherwise by
definition there is no information flow INVOCATION FAILURE (since the terminating
SwMI does not support SS-CW). In such a case, the called user who has invoked
SS-CW will be informed about the invocation failure by the generic failure case
defined in subclause 11.2.1 of ETS 300 392-9 [5].
5.1.9 rd_LOCATION CHANGE
rd_LOCATION CHANGE is a confirmed information flow across relationship rd from FE1 to FE21' in the
case of location change of the served user to allow the later acceptance of the calls still waiting. The
support of that information flow is optional for FE21' but mandatory for FE1 (i.e. first FE1 has to send it in
case of location change of the served user with one or more calls still waiting, second if FE21' sends the
corresponding response/confirmation information flow, FE1 has to receive it and act according to its
information).
There are no elements in the rd_LOCATION CHANGE request/indication information flow.
Table 4 lists the elements within the rd_LOCATION CHANGE response/confirmation information flow.
Table 4: Contents of rd_LOCATION CHANGE response/confirmation
Element Type
Location change procedure support M
Call reference update O (note 1)
Calls lost O (note 2)
NOTE 1: If the location change procedure is supported (information given by the element
location change procedure support):
- may be present in the case of roaming (i.e. FE21' located in the same
SwMI as FE21);
- shall be present in the case of migration (i.e. FE21' located in another
SwMI than FE21).
NOTE 2: Shall be present if the location change procedure is supported and if calls have
been lost during that procedure (e.g. by lack of resources).
The element location change procedure support shall indicate whether or not the call control entity
collocated with FE21' supports the procedure for keeping "alive" calls still waiting when the served user
has changed location.
NOTE: If the call control entity collocated with FE21' can keep "alive" a waiting call when the
served user changes location, it will then necessarily be able to accept the later
request by the served user to accept that waiting call: since the support of such
request is part of TETRA basic call (the corresponding primitive is the basic service
TNCC-COMPLETE request, which results in the U CONNECT PDU being sent by the
served user MS).
The element call reference update shall indicate the new call references when they have changed due to
the location change.
The element calls lost shall indicate the waiting calls which have been cleared during the location change
procedure.

---------------------- Page: 16 ----------------------

SIST ETS 300 392-11-11 E1:2003
Page 15
ETS 300 392-11-11: September 2000
5.1.10 re_LOCATION CHANGE
re_LOCATION CHANGE is a confirmed information flow across relationship re from FE21 to FE21' in the
case of location change of the served user to keep "alive" the waiting call to which it refers (so that it may
be successfully accepted later). The support of that information flow is optional for both FE21 and FE21'.
NOTE 1: re_LOCATION CHANGE is over the Inter-System Interface (ISI) only when the served
user changes location in registering in a new SwMI (i.e. according to TETRA
terminology, the served user migrates). Otherwise, when the served user changes
location within the same SwMI (i.e. according to the TETRA terminology, the served
user roams), re_LOCATION CHANGE is internal to that SwMI.
Table 5 defines the content of the re_LOCATION CHANGE request/indication information flow and
table 6, that of the re_LOCATION CHANGE response/confirmation information flow.
Table 5: Content of re_LOCATION CHANGE request/indication
Element Type
Number of waiting calls M
The element number of waiting calls shall indicate how many calls the served user has still in the call
waiting state.
Table 6: Content of re_LOCATION CHANGE response/confirmation
Element Type
Location change support M
The element location change support shall indicate whether or not the call control entity collocated with
FE21' can keep "alive" the waiting call to which the re_LOCATION CHANGE response/confirmation
information flow refers.
NOTE 2: See note in subclause 5.1.9.
5.2 Relationship of information flows to basic individual call information flows
Table 7 shows the relationship of the SS-CW information flows to those of basic individual call over both
the air interface and the ISI.
NOTE: The basic individual call information flows are defined:
- for the air interface, if not explicitly in ETS 300 392-2 [2], at least implicitly
in clause 11 and 14 of that ETS; and
- for the ISI, in ETS 300 392-3-2 [3].

---------------------- Page: 17 ----------------------

SIST ETS 300 392-11-11 E1:2003
Page 16
ETS 300 392-11-11: September 2000
Table 7: Relationship of SS-CW information flows to basic call
Information flow Independent With basic Basic call flows:
of basic call? call?
INFORM 1 no yes D-ALERT (note 2)
INFORM 2 no yes D-RELEASE (note 3)
ACTIVATE yes (note 1) no
ACTIVATE ACK yes (note 1) no
DEACTIVATE yes (note 1) no
DEACTIV
...