SIST EN 300 392-12-19 V1.1.1:2003
(Main)Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary services stage 3; Sub-part 19: Barring of Incoming Calls (BIC)
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary services stage 3; Sub-part 19: Barring of Incoming Calls (BIC)
Analysis of predicted needs for digital trunked systems in Europe; definition of services to be provided; analysis of spectrum req ments; characteristics of relevant interfaces Contains: TETRA 14.60/85
Prizemni snopovni radio (TETRA) – Govor in podatki (V+D) – 12. del: Dopolnilne storitve stopnje 3 – 19. poglavje: Zapora dohodnih klicev (BIC)
General Information
Buy Standard
Standards Content (Sample)
SLOVENSKI STANDARD
SIST E76 300 392-12-19
01-MXOLM
Prizemni snopovni radio (TETRA) – Govor in podatki (V+D) – 12. del: Dopolnilne
storitve stopnje 3 – 19. poglavje: Zapora dohodnih klicev (BIC)
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary
services stage 3; Sub-part 19: Barring of Incoming Calls (BIC)
Ta slovenski standard je istoveten z: EN 300 392-12-19 (
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST E76 300 392-12-19 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
---------------------- Page: 2 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
DRAFT
EUROPEAN pr ETS 300 392-12-19
TELECOMMUNICATION December 1996
STANDARD
Source: ETSI TC-RES Reference: DE/RES-06001-12-19
ICS: 33.020
Key words: TETRA, V+D, BIC
Radio Equipment and Systems (RES);
Trans-European Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 12: Supplementary Services (SS) Stage 3;
Part 12-19: Barring of Incoming Calls (BIC)
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
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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 1996. All rights reserved.
---------------------- Page: 3 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 2
Draft prETS 300 392-12-19: December 1996
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.
---------------------- Page: 4 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 3
Draft prETS 300 392-12-19: December 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .8
4 SS-BIC stage 3 specification.9
4.1 Functional model description .9
4.2 Relationship with a basic and packet data service .10
5 SS-BIC service description.11
5.1 General .11
5.2 Offered services.11
5.3 TNSS-SAP.11
5.4 TNCC-SAP.12
5.5 TNSCLNS-SAP.12
5.6 TNCO-SAP .12
5.7 SS-BIC services offered over the TNSS-SAP .13
5.7.1 SS-BIC primitives .13
5.7.2 DEFINE request .13
5.7.3 DEFINE confirm .14
5.7.4 INFORM-USER indication.15
5.7.5 INFORM-USER response .15
5.7.6 INTERROGATE request .16
5.7.7 INTERROGATE confirm .16
5.7.8 CALL-BARRED indication .17
5.8 Parameter descriptions.17
5.9 Mapping of SS-BIC primitives to TNSS primitives.19
6 SS-BIC protocol description .20
6.1 General .20
6.2 SS-BIC protocol states.21
6.2.1 Protocol states of FE1.21
6.2.2 Protocol states of FE2.21
6.2.2.1 State IDLE .21
6.2.2.2 State WAIT-FOR-ACK.22
6.2.3 Protocol states of CC to which FE2 is collocated.22
6.2.4 Protocol states of FE3.22
6.2.5 Protocol states of FE4.22
6.2.6 Protocol states of FE5.23
6.2.7 Protocol states of CCA to which FE5 is collocated .23
6.2.7.1 State IDLE .23
6.2.7.2 State MO_CALL_SETUP.23
6.3 Procedures.23
6.3.1 Procedures for FE1 .23
6.3.2 Procedures for FE2 .23
6.3.2.1 Definition in FE2 .23
6.3.2.2 Distribution in FE2 .24
6.3.2.3 Interrogation in FE2 .24
6.3.3.3 Procedures for CC to which FE2 is collocated .24
6.3.3.4 Procedures for FE3 .25
6.3.3.5 Procedures for FE4 .25
6.3.3.6 Procedures for FE5 .25
---------------------- Page: 5 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 4
Draft prETS 300 392-12-19: December 1996
6.4 PDU Descriptions. 25
6.4.1 DEFINE. 26
6.4.2 DEFINE-ACK . 26
6.4.3 INFORM-USER . 27
6.4.4 INFORM-USER-ACK. 27
6.4.5 INTERROGATE. 28
6.4.6 INTERROGATE-ACK . 28
6.4.7 CALL-BARRED. 29
6.4.8 Element coding. 29
6.4.8.1 Action type . 29
6.4.8.2 Address string . 29
6.4.8.3 Definition result . 30
6.4.8.4 Definition type . 30
6.4.8.5 Digit. 30
6.4.8.6 Distribution result . 31
6.4.8.7 Exception to address string. 31
6.4.8.8 Interrogation result . 31
6.4.8.9 Length of address string . 31
6.4.8.10 Number of address strings. 32
6.4.8.11 Number of exceptions to address strings . 32
6.4.8.12 Number of service(s). 32
6.4.8.13 Number of subscriber identities . 32
6.4.8.14 Rejection cause . 33
6.4.8.15 Service . 33
6.4.8.16 Service type . 34
6.4.8.17 Subscriber identity. 34
7 SS-BIC FE behaviour . 34
7.1 Behaviour of FE1. 35
7.1.1 Service interaction for FE1 . 35
7.1.2 Process description for FE1 . 36
7.2 Behaviour of FE2. 37
7.2.1 Service interaction for FE2 . 37
7.2.2 Process description for FE2 . 38
7.3 Behaviour of CC to which FE2 is collocated . 40
7.3.1 Service interaction for CC to which FE2 is collocated . 40
7.3.2 Process description for CC to which FE2 is collocated . 41
7.4 Behaviour of FE3. 42
7.4.1 Service interaction for FE3 . 42
7.4.2 Process description for FE3 . 43
7.5 Behaviour of FE4. 44
7.5.1 Service interaction for FE4 . 44
7.5.2 Process description for FE4 . 45
7.6 Behaviour of FE5. 46
7.6.1 Service interaction for FE5 . 46
7.6.2 Process description for FE5 . 47
7.7 Behaviour of CCA to which FE5 is collocated. 48
7.7.1 Service interaction for CCA to which FE5 is collocated. 48
7.7.2 Process description for CCA collocated to FE5. 49
History. 50
---------------------- Page: 6 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 5
Draft prETS 300 392-12-19: December 1996
Foreword
This draft European Telecommunication Standard (ETS) has been produced by the Radio Equipment and
Systems (RES) Technical Committee of the European Telecommunications Standards Institute (ETSI),
and is now submitted for the Public Enquiry phase of the ETSI standards approval procedure.
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: "Inter-working", (DE/RES-06001-3).
Part 4: "Gateways", (DE/RES-06001-4).
Part 5: "Terminal equipment interface", (DE/RES-06001-5).
Part 6: "Line connected stations", (DE/RES-06001-6).
Part 7: "Security".
Part 8: "Management services", (DE/RES-06001-8).
Part 10: "Supplementary Services (SS) Stage 1".
Part 11: "Supplementary Services (SS) Stage 2".
Part 12: "Supplementary Services (SS) Stage 3".
Part 13: "SDL Model of the Air Interface".
Part 14: "PICS Proforma".
Proposed transposition dates
Date of latest announcement of this ETS (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa
---------------------- Page: 7 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 6
Draft prETS 300 392-12-19: December 1996
Blank page
---------------------- Page: 8 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 7
Draft prETS 300 392-12-19: December 1996
1 Scope
This European Telecommunication Standard (ETS) defines the stage 3 specification of the Barring of
Incoming Call (BIC) supplementary service for the Trans-European Trunked Radio (TETRA).
SS-BIC supplementary service enables barring restrictions for incoming services, e.g. calls, to be set.
SS-BIC specifies the definition, interrogation and operation of the supplementary service. The Switching
and Management Infrastructure (SwMI) applies the SS-BIC definitions when an incoming service is
requested for the restricted user. The SS-BIC actions are defined for the SwMI, for the Mobile Station
(MS) and for the Line Station (LS). The SS-BIC information flows may be delivered over the Inter System
Interface (ISI).
SS-BIC is invoked for incoming services within one TETRA system or for services that extend over ISI to
several TETRA systems.
Man-Machine Interface (MMI) and charging principles are outside the scope of this ETS.
Supplementary service stage 3 specification is preceded by the stage 1 and the stage 2 specifications of
the service. Stage 1 describes the functional capabilities from the user’s point of view. Stage 2 defines the
functional behaviour in terms of functional entities and information flows. Stage 3 gives a precise
description of the Supplementary Service from the implementational point of view. It defines the protocol
for the service and the encoding rules for the information flows. It defines the processes for the functional
entities and their behaviour. The described protocols and behaviour apply to the SwMI, for the MS and for
the LS and may be applied over the ISI between TETRA systems.
2 Normative references
This ETS incorporates, by dated or 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] ETS 300 392-2: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air Interface (AI)".
[2] ETS 300 392-1: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA); Voice plus Data (V+D), Part 1: General Network
Design".
[3] ETS 300 392-10-1: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA); Voice plus Data (V+D); Part: 10: Supplementary
services stage 1; Part 10-1: Call diversion".
[4] ETS 300 392-10-6: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA); Voice plus Data (V+D); Part: 10: Supplementary
services stage 1; Part 10-6: Call authorised by dispatcher".
[5] ITU-T Recommendation Z.100 (1993): "Specification and Description Language
(SDL)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
affected user: Functional Entity 1 (FE1), the user on whose behalf the incoming services are barred. The
SS-BIC is defined either for affected user’s individual subscriber identity or for a group identity of which the
affected user is member.
authorised user: FE3, the user who is permitted to define SS-BIC on affected user’s behalf.
---------------------- Page: 9 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 8
Draft prETS 300 392-12-19: December 1996
basic service: Circuit mode speech service or circuit mode data service, see ETS 300 392-2 [1] clause
11.
calling party: FE5, the party whose service request is barred due to SS-BIC.
Functional Entity (FE): An FE performs the SS-BIC specific tasks in the MS, in the LS or in the SwMI.
home system: The TETRA network which Mobile Network Identity (MNI) is equal to the user’s MNI. The
SS-BIC definition is saved in the home system and home system is responsible for transporting the
SS-BIC definition to visited system(s).
Inter System Interface (ISI): The interface between two TETRA networks, that enables the inter-working
of services between these two systems.
Mobile Network Identity (MNI): Mobile Country Code (MCC) and Mobile Network Code (MNC) of the
TETRA Subscriber Identity (TSI).
Mobile Station (MS): A physical grouping that contains all of the mobile equipment that is used to obtain
TETRA services. By definition, a mobile station contains at least one Mobile Radio Stack.
packet data service: Connection oriented packet mode data service and connectionless packet mode
data service, see ETS 300 392-2 [1] clauses 24 and 26.
operation: The act of performing a service, e.g. in case of SS-BIC the barring of a call.
Switching and Management Infrastructure (SwMI): All of the TETRA equipment for a Voice plus Data
(V+D) network except for subscriber terminals. The SwMI enables subscriber terminals to communicate
with each other via the SwMI.
visited system: The TETRA network which MNI is not equal to the user’s MNI.
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
CC Call Control sub-entity for SS-BIC in CMCE in SwMI
CCA Call Control sub-entity for SS-BIC in CMCE in MS/LS
CMCE Circuit Mode Control Entity
CONS Connection Oriented Network Service
FE Functional Entity
ISI Inter System Interface
LS Line Station
MCC Mobile Country Code
MLE Mobile Link Entity
MNC Mobile Network Code
MS Mobile Station
PDU Protocol Data Unit
SAP Service Access Point
SCLNS Specific ConnectionLess Network Service
SS Supplementary service sub-entity within CMCE
SS-BIC Supplementary Service Barring of Incoming Call
SSI Short Subscriber Identity
SwMI Switching and Management Infrastructure
TETRA Trans-European Trunked Radio
TNCC-SAP Call Control service access point
TNCO-SAP Connection Oriented network service Service Access Point
TNSCLNS-SAP Specific ConnectionLess Network Service Service Access Point
TNSS-SAP Supplementary Service Service Access Point
TSI TETRA Subscriber Identity
---------------------- Page: 10 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 9
Draft prETS 300 392-12-19: December 1996
4 SS-BIC stage 3 specification
4.1 Functional model description
The functional model shall comprise the following Functional Entities (FEs):
FE1: SS sub-entity in Circuit Mode Control Entity (CMCE) for SS-BIC in affected user’s MS/LS;
FE2: SS sub-entity in CMCE for SS-BIC in SwMI;
FE3: SS sub-entity in CMCE for SS-BIC in authorised user’s MS/LS;
FE4: generic SS sub-entity in CMCE for SS-BIC in SwMI;
FE5: SS sub-entity in CMCE for SS-BIC in calling party’s MS/LS;
CC: call control sub-entity for SS-BIC in CMCE in SwMI;
CCA: call control sub-entity for SS-BIC in CMCE in MS/LS.
NOTE: The SS-BIC functionality in CC/CCA is also applicable for packet data service, unless
otherwise mentioned.
The following relationships shall exist between these FEs:
ra between FE1 and FE2;
rb between FE2 and FE4 in different TETRA systems;
rc between FE2 and FE3;
rd between FE2 and FE2 in different TETRA systems;
re between FE1 and FE4;
rf between FE3 and FE4;
rg between FE2 and FE5.
Figures 1 and 2 show these FEs and their relationships. Figure 1 gives the functional model for the
management part and figure 2 gives the functional model for the operational part.
home system visited system
rc rb rf
FE3 FE2 FE4 FE3
authorised SS-BIC FE SS-BIC FE authorised
user ra re user
FE1 FE1
affected affected
user user
Figure 1: Functional model for the management part
---------------------- Page: 11 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 10
Draft prETS 300 392-12-19: December 1996
home system visited system
rg rd rg
FE5 FE2 FE2 FE5
calling SS-BIC FE SS-BIC FE calling
party ra ra party
FE1 FE1
affected affected
user user
NOTE: FE1 does not receive any information of the barring.
Figure 2: Functional model for the operational part
4.2 Relationship with a basic and packet data service
FE2 shall be collocated to CC in SwMI.
FE5 shall be collocated to CCA.
The relationship with basic and packet data service is shown in figure 3.
home system visited system
rg rd rg
FE5 FE2 FE2 FE5
CCA CC CC CCA
calling SS-BIC FE SS-BIC FE calling
party ra ra party
FE1 FE1
affected affected
user user
NOTE: FE1 does not receive any information of the barring.
Figure 3: Relationships with FEs and CCs/CCAs
---------------------- Page: 12 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 11
Draft prETS 300 392-12-19: December 1996
5 SS-BIC service description
5.1 General
This clause describes SS-BIC services offered by Supplementary Service (SS) and call control sub-
entities of CMCE, Connection Oriented Network Service (CONS) and Specific ConnectionLess Network
Service (SCLNS) of the TETRA voice plus data layer 3 service boundary in the MS/LS.
NOTE: The layer 3 services and service boundary for the SwMI is outside the scope of this
ETS.
The SS-BIC services shall be offered at:
- Supplementary Services Service Access Point (TNSS-SAP);
- Call Control Service Access Point (TNCC-SAP);
- Connection Oriented network service Service Access Point (TNCO-SAP);
- Specific ConnectionLess Network Service Service Access Point (TNSCLNS-SAP).
The SS-BIC services described in this clause shall complement the SS service, the call control service,
CONS and SCLNS specified in ETS 300 392-2 [1], clauses 12, 11, 24 and 26 respectively.
5.2 Offered services
SS-BIC is an optional supplementary service for TETRA voice plus data layer 3. If SS-BIC is supported,
this subclause shall specify the services and their availability.
The following SS-BIC services shall be provided:
- barring indication: barring indication for a basic service (call control service) or packet data service
(CONS, SCLNS) that the user has requested.
The following SS-BIC services may be provided:
- definition: a request to define SS-BIC into the SwMI;
- definition information: the reception of SS-BIC definition for information;
- interrogation: interrogation of SS-BIC definition.
5.3 TNSS-SAP
The SS-BIC definition, user definition and interrogation shall be provided at TNSS-SAP.
The SS-BIC service elements shall be carried as primitives within the following three general generic
supplementary services primitives over TNSS-SAP:
a) TNSS-SERVICE;
b) TNSS-INFO;
c) TNSS-ERROR.
Figure 4 illustrates the flow for generic SS primitives.
---------------------- Page: 13 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 12
Draft prETS 300 392-12-19: December 1996
TNSS-ERROR indication,
SIGNAL
TNSS-INFO indication,
TNSS-ERROR indication, TNSS-INFO confirm,
TNSS-INFO confirm,
TNSS-SERVICE indication,
TNSS-INFO indication,
TNSS-SERVICE confirm
TNSS-INFO request,
TNSS-INFO response,
TNSS-SERVICE confirm
TNSS-SERVICE indication,
TNSS-SERVICE request,
TNSS-SERVICE response TNSS-SAP
TNSS-INFO request,
TNSS-INFO response,
TNSS-SERVICE request,
TNSS-SERVICE response
SS SERVICE
MS
Figure 4: The flow for generic SS primitives
TNSS-SERVICE shall enable an invoking entity to request and to be informed about, an operation to be
performed by the performing entity.
TNSS-INFO shall enable an entity to be informed of ongoing transactions.
TNSS-ERROR shall enable a performing entity to return the negative reply of a unsuccessfully performed
operation to the invoking entity.
For a detailed description of the generic supplementary service primitives refer to ETS 300 392-2 [1],
subclause 12.3.
5.4 TNCC-SAP
The SS-BIC barring indication for call control service shall be provided at TNCC-SAP.
The SS-BIC service element shall be carried as an element within the TNCC-RELEASE indication
primitive over TNCC-SAP. The barring shall be indicated in TNCC-RELEASE primitive as Disconnect
cause parameter having the value Not allowed traffic case.
For a detailed description of the call control service primitives refer to ETS 300 392-2 [1], subclause 11.3.
5.5 TNSCLNS-SAP
The SS-BIC barring indication for SCLNS shall be provided at TNSCLNS-SAP.
The SS-BIC barring indication shall be carried within the TN-DELIVERY indication at TNSCLNS-SAP. The
parameter Disposition Report shall be mapped from Disposition element within DELIVERY PDU to
TN-DELIVERY indication, as defined in ETS 300 392-2 [1], clause 26.
5.6 TNCO-SAP
The SS-BIC barring indication for CONS shall be provided at TNCO-SAP.
---------------------- Page: 14 ----------------------
SIST EN 300 392-12-19 V1.1.1:2003
Page 13
Draft prETS 300 392-12-19: December 1996
The SS-BIC service elements shall be carried within the N-DISCONNECT indication primitives over
TNCO-SAP. The barring shall be indicated by mapping the Clearing cause and Diagnostic code from
CLEAR INDICATION packet to N-DISCONNECT indication, as defined in ETS 300 392-2 [1], clause 24.
5.7 SS-BIC services offered over the TNSS-SAP
5.7.1 SS-BIC primitives
The generic supplementary service primitives shall contain the following SS-BIC primitives.
a) DEFINE request;
b) DEFINE confirm;
c) INFORM-USER indication;
d) INFORM-USER response;
e) INTERROGATE request;
f) INTERROGATE confirm;
g) CALL-BARRED indication.
The information contained in the following primitive description tables correspond to the following key:
- Remark: comment;
- C: conditional;
- O: optional;
- M: mandatory.
5.7.2 DEFINE request
DEFINE request shall be offered from application to FE3 to define SS-BIC on affected user’s behalf. The
primitive shall contain the parameters listed in table 1.
Parameter definitions:
- Subscriber identity defines the restricted identity. If there are several subscriber identities given in
the primitive, the following definitions shall be requested to all the identities.
- Definition type indicates if the definition shall be an addition, replacement of removal of a previously
made definition.
NOTE: It is possible that there is no previous SS-BIC definition.
- Services outside closed user group causes barring of service requests received from a party
outside the given closed group. The closed user group definition is outside the scope of this ETS.
- Service causes barring of the given service.
- Address string causes barring of a service requested by a user whose identity is or starts with the
given string.
- Exception to address string allows services requested by a user whose identity is or starts with the
given string. The shall be used to enable exceptions to restricting Address string definitions and the
overrides these definition
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Prizemni snopovni radio (TETRA) – Govor in podatki (V+D) – 12. del: Dopolnilne storitve stopnje 3 – 19. poglavje: Zapora dohodnih klicev (BIC)Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary services stage 3; Sub-part 19: Barring of Incoming Calls (BIC)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:EN 300 392-12-19 (3SIST E76 300 392-12-19en01-PDM3SIST E76 300 392-12-19SLOVENSKI
STANDARD
SIST EN 300 392-12-19 V1.1.1:2003
DRAFTEUROPEANprETS 300 392-12-19TELECOMMUNICATIONDecember 1996STANDARDSource: ETSI TC-RESReference: DE/RES-06001-12-19ICS:33.020Key words:TETRA, V+D, BICRadio Equipment and Systems (RES);Trans-European Trunked Radio (TETRA);Voice plus Data (V+D);Part 12: Supplementary Services (SS) Stage 3;Part 12-19: Barring of Incoming Calls (BIC)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.SIST EN 300 392-12-19 V1.1.1:2003
Page 2Draft prETS 300 392-12-19: December 1996Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST EN 300 392-12-19 V1.1.1:2003
Page 3Draft prETS 300 392-12-19: December 1996ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.73.1Definitions.73.2Abbreviations.84SS-BIC stage 3 specification.94.1Functional model description.94.2Relationship with a basic and packet data service.105SS-BIC service description.115.1General.115.2Offered services.115.3TNSS-SAP.115.4TNCC-SAP.125.5TNSCLNS-SAP.125.6TNCO-SAP.125.7SS-BIC services offered over the TNSS-SAP.135.7.1SS-BIC primitives.135.7.2DEFINE request.135.7.3DEFINE confirm.145.7.4INFORM-USER indication.155.7.5INFORM-USER response.155.7.6INTERROGATE request.165.7.7INTERROGATE confirm.165.7.8CALL-BARRED indication.175.8Parameter descriptions.175.9Mapping of SS-BIC primitives to TNSS primitives.196SS-BIC protocol description.206.1General.206.2SS-BIC protocol states.216.2.1Protocol states of FE1.216.2.2Protocol states of FE2.216.2.2.1State IDLE.216.2.2.2State WAIT-FOR-ACK.226.2.3Protocol states of CC to which FE2 is collocated.226.2.4Protocol states of FE3.226.2.5Protocol states of FE4.226.2.6Protocol states of FE5.236.2.7Protocol states of CCA to which FE5 is collocated.236.2.7.1State IDLE.236.2.7.2State MO_CALL_SETUP.236.3Procedures.236.3.1Procedures for FE1.236.3.2Procedures for FE2.236.3.2.1Definition in FE2.236.3.2.2Distribution in FE2.246.3.2.3Interrogation in FE2.246.3.3.3Procedures for CC to which FE2 is collocated.246.3.3.4Procedures for FE3.256.3.3.5Procedures for FE4.256.3.3.6Procedures for FE5.25SIST EN 300 392-12-19 V1.1.1:2003
Page 4Draft prETS 300 392-12-19: December 19966.4PDU Descriptions.256.4.1DEFINE.266.4.2DEFINE-ACK.266.4.3INFORM-USER.276.4.4INFORM-USER-ACK.276.4.5INTERROGATE.286.4.6INTERROGATE-ACK.286.4.7CALL-BARRED.296.4.8Element coding.296.4.8.1Action type.296.4.8.2Address string.296.4.8.3Definition result.306.4.8.4Definition type.306.4.8.5Digit.306.4.8.6Distribution result.316.4.8.7Exception to address string.316.4.8.8Interrogation result.316.4.8.9Length of address string.316.4.8.10Number of address strings.326.4.8.11Number of exceptions to address strings.326.4.8.12Number of service(s).326.4.8.13Number of subscriber identities.326.4.8.14Rejection cause.336.4.8.15Service.336.4.8.16Service type.346.4.8.17Subscriber identity.347SS-BIC FE behaviour.347.1Behaviour of FE1.357.1.1Service interaction for FE1.357.1.2Process description for FE1.367.2Behaviour of FE2.377.2.1Service interaction for FE2.377.2.2Process description for FE2.387.3Behaviour of CC to which FE2 is collocated.407.3.1Service interaction for CC to which FE2 is collocated.407.3.2Process description for CC to which FE2 is collocated.417.4Behaviour of FE3.427.4.1Service interaction for FE3.427.4.2Process description for FE3.437.5Behaviour of FE4.447.5.1Service interaction for FE4.447.5.2Process description for FE4.457.6Behaviour of FE5.467.6.1Service interaction for FE5.467.6.2Process description for FE5.477.7Behaviour of CCA to which FE5 is collocated.487.7.1Service interaction for CCA to which FE5 is collocated.487.7.2Process description for CCA collocated to FE5.49History.50SIST EN 300 392-12-19 V1.1.1:2003
Page 5Draft prETS 300 392-12-19: December 1996ForewordThis draft European Telecommunication Standard (ETS) has been produced by the Radio Equipment andSystems (RES) Technical Committee of the European Telecommunications Standards Institute (ETSI),and is now submitted for the Public Enquiry phase of the ETSI standards approval procedure.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:"Inter-working", (DE/RES-06001-3).Part 4:"Gateways", (DE/RES-06001-4).Part 5:"Terminal equipment interface", (DE/RES-06001-5).Part 6:"Line connected stations", (DE/RES-06001-6).Part 7:"Security".Part 8:"Management services", (DE/RES-06001-8).Part 10:"Supplementary Services (SS) Stage 1".Part 11:"Supplementary Services (SS) Stage 2".Part 12:"Supplementary Services (SS) Stage 3".Part 13:"SDL Model of the Air Interface".Part 14:"PICS Proforma".Proposed transposition datesDate of latest announcement of this ETS (doa):3 months after ETSI publicationDate of latest publication of new National Standardor endorsement of this ETS (dop/e):6 months after doaDate of withdrawal of any conflicting National Standard (dow):6 months after doaSIST EN 300 392-12-19 V1.1.1:2003
Page 6Draft prETS 300 392-12-19: December 1996Blank pageSIST EN 300 392-12-19 V1.1.1:2003
Page 7Draft prETS 300 392-12-19: December 19961ScopeThis European Telecommunication Standard (ETS) defines the stage 3 specification of the Barring ofIncoming Call (BIC) supplementary service for the Trans-European Trunked Radio (TETRA).SS-BIC supplementary service enables barring restrictions for incoming services, e.g. calls, to be set.SS-BIC specifies the definition, interrogation and operation of the supplementary service. The Switchingand Management Infrastructure (SwMI) applies the SS-BIC definitions when an incoming service isrequested for the restricted user. The SS-BIC actions are defined for the SwMI, for the Mobile Station(MS) and for the Line Station (LS). The SS-BIC information flows may be delivered over the Inter SystemInterface (ISI).SS-BIC is invoked for incoming services within one TETRA system or for services that extend over ISI toseveral TETRA systems.Man-Machine Interface (MMI) and charging principles are outside the scope of this ETS.Supplementary service stage 3 specification is preceded by the stage 1 and the stage 2 specifications ofthe service. Stage 1 describes the functional capabilities from the user’s point of view. Stage 2 defines thefunctional behaviour in terms of functional entities and information flows. Stage 3 gives a precisedescription of the Supplementary Service from the implementational point of view. It defines the protocolfor the service and the encoding rules for the information flows. It defines the processes for the functionalentities and their behaviour. The described protocols and behaviour apply to the SwMI, for the MS and forthe LS and may be applied over the ISI between TETRA systems.2Normative referencesThis ETS incorporates, by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 392-2: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air Interface (AI)".[2]ETS 300 392-1: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA); Voice plus Data (V+D), Part 1: General NetworkDesign".[3]ETS 300 392-10-1: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA); Voice plus Data (V+D); Part: 10: Supplementaryservices stage 1; Part 10-1: Call diversion".[4]ETS 300 392-10-6: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA); Voice plus Data (V+D); Part: 10: Supplementaryservices stage 1; Part 10-6: Call authorised by dispatcher".[5]ITU-T Recommendation Z.100 (1993): "Specification and Description Language(SDL)".3Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply:affected user: Functional Entity 1 (FE1), the user on whose behalf the incoming services are barred. TheSS-BIC is defined either for affected user’s individual subscriber identity or for a group identity of which theaffected user is member.authorised user: FE3, the user who is permitted to define SS-BIC on affected user’s behalf.SIST EN 300 392-12-19 V1.1.1:2003
Page 8Draft prETS 300 392-12-19: December 1996basic service: Circuit mode speech service or circuit mode data service, see ETS 300 392-2 [1] clause11.calling party: FE5, the party whose service request is barred due to SS-BIC.Functional Entity (FE): An FE performs the SS-BIC specific tasks in the MS, in the LS or in the SwMI.home system: The TETRA network which Mobile Network Identity (MNI) is equal to the user’s MNI. TheSS-BIC definition is saved in the home system and home system is responsible for transporting theSS-BIC definition to visited system(s).Inter System Interface (ISI): The interface between two TETRA networks, that enables the inter-workingof services between these two systems.Mobile Network Identity (MNI): Mobile Country Code (MCC) and Mobile Network Code (MNC) of theTETRA Subscriber Identity (TSI).Mobile Station (MS): A physical grouping that contains all of the mobile equipment that is used to obtainTETRA services. By definition, a mobile station contains at least one Mobile Radio Stack.packet data service: Connection oriented packet mode data service and connectionless packet modedata service, see ETS 300 392-2 [1] clauses 24 and 26.operation: The act of performing a service, e.g. in case of SS-BIC the barring of a call.Switching and Management Infrastructure (SwMI): All of the TETRA equipment for a Voice plus Data(V+D) network except for subscriber terminals. The SwMI enables subscriber terminals to communicatewith each other via the SwMI.visited system: The TETRA network which MNI is not equal to the user’s MNI.3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:CCCall Control sub-entity for SS-BIC in CMCE in SwMICCACall Control sub-entity for SS-BIC in CMCE in MS/LSCMCECircuit Mode Control EntityCONSConnection Oriented Network ServiceFEFunctional EntityISIInter System InterfaceLSLine StationMCCMobile Country CodeMLEMobile Link EntityMNCMobile Network CodeMSMobile StationPDUProtocol Data UnitSAPService Access PointSCLNSSpecific ConnectionLess Network ServiceSSSupplementary service sub-entity within CMCESS-BICSupplementary Service Barring of Incoming CallSSIShort Subscriber IdentitySwMISwitching and Management InfrastructureTETRATrans-European Trunked RadioTNCC-SAPCall Control service access pointTNCO-SAPConnection Oriented network service Service Access PointTNSCLNS-SAPSpecific ConnectionLess Network Service Service Access PointTNSS-SAPSupplementary Service Service Access PointTSITETRA Subscriber IdentitySIST EN 300 392-12-19 V1.1.1:2003
Page 9Draft prETS 300 392-12-19: December 19964SS-BIC stage 3 specification4.1Functional model descriptionThe functional model shall comprise the following Functional Entities (FEs):FE1:SS sub-entity in Circuit Mode Control Entity (CMCE)
for SS-BIC in affected user’s MS/LS;FE2:SS sub-entity in CMCE for SS-BIC in SwMI;FE3:SS sub-entity in CMCE for SS-BIC in authorised user’s MS/LS;FE4:generic SS sub-entity in CMCE for SS-BIC in SwMI;FE5:SS sub-entity in CMCE for SS-BIC in calling party’s MS/LS;CC:call control sub-entity for SS-BIC in CMCE in SwMI;CCA:call control sub-entity for SS-BIC in CMCE in MS/LS.NOTE: The SS-BIC functionality in CC/CCA is also applicable for packet data service, unlessotherwise mentioned.The following relationships shall exist between these FEs:rabetween FE1 and FE2;rbbetween FE2 and FE4 in different TETRA systems;rcbetween FE2 and FE3;rdbetween FE2 and FE2 in different TETRA systems;rebetween FE1 and FE4;rfbetween FE3 and FE4;rgbetween FE2 and FE5.Figures 1 and 2 show these FEs and their relationships. Figure 1 gives the functional model for themanagement part and figure 2 gives the functional model for the operational part. home system visited systemrcrbrfFE3FE2FE4FE3authorisedSS-BIC FESS-BIC FEauthoriseduser
ra
reuserFE1FE1affectedaffecteduseruserFigure 1: Functional model for the management partSIST EN 300 392-12-19 V1.1.1:2003
Page 10Draft prETS 300 392-12-19: December 1996home systemvisited systemrgrdrgFE5FE2FE2FE5callingSS-BIC FESS-BIC FEcallingparty
ra
rapartyFE1FE1 affectedaffecteduseruserNOTE:FE1 does not receive any information of the barring.Figure 2: Functional model for the operational part4.2Relationship with a basic and packet data serviceFE2 shall be collocated to CC in SwMI.FE5 shall be collocated to CCA.The relationship with basic and packet data service is shown in figure 3.home system visited systemrgrdrgFE5FE2FE2FE5CCACCCCCCAcallingSS-BIC FESS-BIC FEcallingparty
ra
rapartyFE1FE1 affectedaffecteduseruserNOTE:FE1 does not receive any information of the barring.Figure 3: Relationships with FEs and CCs/CCAsSIST EN 300 392-12-19 V1.1.1:2003
Page 11Draft prETS 300 392-12-19: December 19965SS-BIC service description5.1GeneralThis clause describes SS-BIC services offered by Supplementary Service (SS) and call control sub-entities of CMCE, Connection Oriented Network Service (CONS) and Specific ConnectionLess NetworkService (SCLNS) of the TETRA voice plus data layer 3 service boundary in the MS/LS.NOTE:The layer 3 services and service boundary for the SwMI is outside the scope of thisETS.The SS-BIC services shall be offered at:-Supplementary Services Service Access Point (TNSS-SAP);-Call Control Service Access Point (TNCC-SAP);-Connection Oriented network service Service Access Point (TNCO-SAP);-Specific ConnectionLess Network Service Service Access Point (TNSCLNS-SAP).The SS-BIC services described in this clause shall complement the SS service, the call control service,CONS and SCLNS specified in ETS 300 392-2 [1], clauses 12, 11, 24 and 26 respectively.5.2Offered servicesSS-BIC is an optional supplementary service for TETRA voice plus data layer 3. If SS-BIC is supported,this subclause shall specify the services and their availability.The following SS-BIC services shall be provided:-barring indication: barring indication for a basic service (call control service) or packet data service(CONS, SCLNS) that the user has requested.The following SS-BIC services may be provided:-definition: a request to define SS-BIC into the SwMI;-definition information: the reception of SS-BIC definition for information;-interrogation: interrogation of SS-BIC definition.5.3TNSS-SAPThe SS-BIC definition, user definition and interrogation shall be provided at TNSS-SAP.The SS-BIC service elements shall be carried as primitives within the following three general genericsupplementary services primitives over TNSS-SAP:a)TNSS-SERVICE;b)TNSS-INFO;c)TNSS-ERROR.Figure 4 illustrates the flow for generic SS primitives.SIST EN 300 392-12-19 V1.1.1:2003
Page 12Draft prETS 300 392-12-19: December 1996SS SERVICEMSSIGNALTNSS-SAPTNSS-ERROR indication,TNSS-INFO indication,TNSS-INFO confirm,TNSS-SERVICE indication,TNSS-SERVICE confirmTNSS-INFO request,TNSS-INFO response,TNSS-SERVICE request,TNSS-SERVICE responseTNSS-ERROR indication,TNSS-INFO indication,TNSS-INFO confirm,TNSS-SERVICE indication,TNSS-SERVICE confirmTNSS-INFO request,TNSS-INFO response,TNSS-SERVICE request,TNSS-SERVICE responseFigure 4: The flow for generic SS primitivesTNSS-SERVICE shall enable an invoking entity to request and to be informed about, an operation to beperformed by the performing entity.TNSS-INFO shall enable an entity to be informed of ongoing transactions.TNSS-ERROR shall enable a performing entity to return the negative reply of a unsuccessfully performedoperation to the invoking entity.For a detailed description of the generic supplementary service primitives refer to ETS 300 392-2 [1],subclause 12.3.5.4TNCC-SAPThe SS-BIC barring indication for call control service shall be provided at TNCC-SAP.The SS-BIC service element shall be carried as an element within the TNCC-RELEASE indicationprimitive over TNCC-SAP. The barring shall be indicated in TNCC-RELEASE primitive as Disconnectcause parameter having the value Not allowed traffic case.For a detailed description of the call control service primitives refer to ETS 300 392-2 [1], subclause 11.3.5.5TNSCLNS-SAPThe SS-BIC barring indication for SCLNS shall be provided at TNSCLNS-SAP.The SS-BIC barring indication shall be carried within the TN-DELIVERY indication at TNSCLNS-SAP. Theparameter Disposition Report shall be mapped from Disposition element within DELIVERY PDU toTN-DELIVERY indication, as defined in ETS 300 392-2 [1], clause 26.5.6TNCO-SAPThe SS-BIC barring indication for CONS shall be provided at TNCO-SAP.SIST EN 300 392-12-19 V1.1.1:2003
Page 13Draft prETS 300 392-12-19: December 1996The SS-BIC service elements shall be carried within the N-DISCONNECT indication primitives overTNCO-SAP. The barring shall be indicated by mapping the Clearing cause and Diagnostic code fromCLEAR INDICATION packet to N-DISCONNECT indication, as defined in ETS 300 392-2 [1], clause 24.5.7SS-BIC services offered over the TNSS-SAP5.7.1SS-BIC primitivesThe generic supplementary service primitives shall contain the following SS-BIC primitives.a)DEFINE request;b)DEFINE confirm;c)INFORM-USER indication;d)INFORM-USER response;e)INTERROGATE request;f)INTERROGATE confirm;g)CALL-BARRED indication.The information contained in the following primitive description tables correspond to the following key:-Remark:comment;-C:conditional;-O:optional;-M:mandatory.5.7.2DEFINE requestDEFINE request shall be offered from application to FE3 to define SS-BIC on affected user’s behalf. Theprimitive shall contain the parameters listed in table 1.Parameter definitions:-Subscriber identity defines the restricted identity. If there are several subscriber identities given inthe primitive, the following definitions shall be requested to all the identities.-Definition type indicates if the definition shall be an addition, replacement of removal of a previouslymade definition.NOTE:It is possible that there is no previous SS-BIC definition.-Services outside closed user group causes barring of service requests received from a partyoutside the given closed group. The closed user group definition is outside the scope of this ETS.-Service causes barring of the given service.-Address string causes barring of a service requested by a user whose identity is or starts with thegiven string.-Exception to address string allows services requested by a user whose identity is or starts with thegiven string. The shall be used to enable exceptions to restricting Address string definitions and theoverrides these definitions, when the Exception to address string is longer than a Address stringelement.-Delivery to affected user(s) indicates that the SwMI shall send the definition to affected user for hisinformation. If the definition is made to a group, the definition shall be sent to all group members forinformation, if sent.SIST EN 300 392-12-19 V1.1.1:2003
Page 14Draft prETS 300 392-12-19: December 1996-Acknowledgement from affected user(s) indicates if the affected users shall acknowledge thereceived definition information.Table 1: DEFINE request contentsParameterReqRemarkSS TypeMSS-BICOperation typeMDefinitionNumber of subscriber identitiesMSubscriber identityMrepeatable (note 1)Definition typeMServices outside closed user groupC(note 2)Number of servicesC(note 2)ServiceCrepeatable (note 2)(note 3)Number of address stringsC(note 2) (note 3)Address stringCrepeatable (note 2)(note 4)Number of exceptions to address stringsC(note 2)Exception to address stringCrepeatable (note 2)(note 5)Delivery to affected user(s)MAcknowledgement requestedMNOTE 1:Element should be present and interpreted as indicated by the elementNumber of subscriber identity elements.NOTE 2:Element shall be present only if the Definition type is addition or replacement.NOTE 3:Service element should be repeated as many times as indicated in theelement Number of services elements.NOTE 4:Address string elements should be repeated as many times as indicated inthe element Number of address strings elements.NOTE 5:Exceptions to address string elements should be repeated as many times asindicated in the element Number of exceptions to address strings elements.5.7.3DEFINE confirmDEFINE confirm shall be offered from FE3
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Prizemni snopovni radio (TETRA) – Govor in podatki (V+D) – 12. del: Dopolnilne storitve stopnje 3 – 19. poglavje: Zapora dohodnih klicev (BIC)Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary services stage 3; Sub-part 19: Barring of Incoming Calls (BIC)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:EN 300 392-12-19 Version 1.1.1SIST EN 300 392-12-19 V1.1.1:2003en01-december-2003SIST EN 300 392-12-19 V1.1.1:2003SLOVENSKI
STANDARD
SIST EN 300 392-12-19 V1.1.1:2003
ETSIEN300392-12-19V1.1.1(2001-08)EuropeanStandard(Telecommunicationsseries)TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part12:Supplementaryservicesstage3;Sub-part19:BarringofIncomingCalls(BIC)SIST EN 300 392-12-19 V1.1.1:2003
ETSIETSIEN300392-12-19V1.1.1(2001-08)2ReferenceDEN/TETRA-03A-12-19Keywordsradio,TETRAETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 300 392-12-19 V1.1.1:2003
ETSIETSIEN300392-12-19V1.1.1(2001-08)3ContentsIntellectualPropertyRights.6Foreword.61Scope.82References.83Definitions,symbolsandabbreviations.93.1Definitions.93.2Symbols.93.3Abbreviations.93.3.1Generalabbreviations.93.3.2Supplementaryserviceabbreviations.104SS-BICservicedescription.104.1General.104.2SS-BICservices.104.3ServicesatTNSS-SAP.114.3.1Generalonservices.114.3.2CALLBARREDindication.114.3.3DEFINErequest.124.3.4DEFINEindication.124.3.5DEFINEEXTERNALrequest.124.3.6DEFINEEXTERNALindication.134.3.7DEFINEUSERindication.134.3.8DEFINEEXTERNALUSERindication.134.3.9INTERROGATErequest.144.3.10INTERROGATEindication.144.4ServicesattheTNCC-SAP.144.5Parameterdescription.145SignallingprotocolforsupportofSS-BIC.175.1General.175.2SS-BICOperationalrequirements.175.2.1RequirementsontheaffecteduserMS/LS.175.2.2RequirementsontheaffecteduserSwMI.175.2.3RequirementsonthecallinguserSwMI.175.2.4RequirementsonthecallinguserMS/LS.185.2.5RequirementsontheSS-BICRestricteduserhomeSwMI.185.3SS-BICCodingrequirements.185.3.1SS-BICPDUs.185.3.1.1DEFINEPDU.195.3.1.2DEFINEACKPDU.205.3.1.3DEFINEEXTERNALPDU.215.3.1.4DEFINEUSERPDU.225.3.1.5DEFINEUSERACKPDU.225.3.1.6DEFINEUSEREXTERNALPDU.235.3.1.7INTERROGATEPDU.235.3.1.8INTERROGATEACKPDU.245.3.1.9CALLBARREDPDU.255.3.1.10Notificationindicator.255.3.2TETRAPDUInformationElementCoding.265.3.2.1Acknowledgementfromaffecteduser(s).265.3.2.2Affecteduserextension.265.3.2.3Affecteduserextensionpresent.265.3.2.4AffecteduserSSI.265.3.2.5BICPDUtype.275.3.2.6Closedusergroupidentifier.27SIST EN 300 392-12-19 V1.1.1:2003
ETSIETSIEN300392-12-19V1.1.1(2001-08)45.3.2.7Definitionresult.285.3.2.8Definitiontype.285.3.2.9Deliverystatustoaffecteduser(s).285.3.2.10Deliverytoaffecteduser(s).295.3.2.11Distributionresult.295.3.2.12Exceptiontorestrictedextension.295.3.2.13Exceptiontorestrictedextensionpresent.295.3.2.14Exceptiontorestrictedexternalnumber.295.3.2.15Exceptiontorestrictedexternalnumberlengthindicator.305.3.2.16ExceptiontorestrictedSSI.305.3.2.17Interrogationresult.305.3.2.18Interrogationtype.305.3.2.19Numberofservice(s).315.3.2.20Rangetypeforaffecteduseridentities.315.3.2.21Rangetypeforclosedusergroups.315.3.2.22Rangetypeforexceptionstorestrictedexternalnumbers.315.3.2.23Rangetypeforrestrictedexternalnumbers.315.3.2.24Rangetypeforrestrictedidentities.315.3.2.25Rejectioncause.315.3.2.26Restrictedextension.325.3.2.27Restrictedextensionpresent.325.3.2.28Restrictedexternalnumber.325.3.2.29Restrictedexternalnumberlengthindicator.325.3.2.30RestrictedSSI.325.3.2.31Service.335.3.3AdditionalcodingrequirementsovertheISI.335.4SS-BICStateDefinitions.355.4.1StateatthecallinguserMS/LS.355.4.2StateatthecallinguserSwMI.355.4.3StateattheaffecteduserMS/LS.355.4.4StateattheaffecteduserSwMI.355.4.5StateattheauthorizeduserMS/LS.355.4.6StateattheSS-BICrestricteduserhomeSwMI.355.5SS-BICSignallingProcedures.355.5.1ActionsatCallingUserMS/LS.355.5.2ActionsatCallingUserSwMI.355.5.3ActionsattheauthorizeduserMS/LS.355.5.3.1NormalproceduresattheauthorizeduserMS/LS.365.5.3.2ExceptionalproceduresattheauthorizeduserMS/LS.365.5.4ActionsattheSS-BICcontrolentityattheSwMIwheretheauthorizeduserisregistered.365.5.4.1NormalproceduresattheSS-BICcontrolentityattheSwMIwheretheauthorizeduserisregistered.365.5.4.2ExceptionalproceduresattheSS-BICcontrolentityattheSwMIwheretheauthorizeduserisregistered.375.5.5ActionsattheSS-BICrestricteduserhomeSwMI.375.5.5.1Normalprocedures.375.5.5.2ExceptionalproceduresattheSS-BICcontrolentityattheSS-BICrestricteduserhomeSwMI.385.5.6Actionsattheaffected(called/barred)userSwMI.395.5.7Actionsattheaffected(called/barred)userMS/LS.395.6ImpactofInter-workingwithPublicISDN.395.6.1General.395.6.2SS-BICforIncomingCallfromPublicISDNtoTETRA.395.6.3SS-BICforIncomingCallfromTETRAtopublicISDN.395.7ProtocolinteractionsbetweenSS-BICandothersupplementaryservicesandANFs.395.7.1ProtocolinteractionsbetweenSS-BICandothersupplementaryservices.395.7.2ProtocolinteractionsbetweenSS-BICandISI-IC-ANF.40AnnexA(normative):SpecificationandDescriptionLanguage(SDL)representationofcallrelatedprocedures.41A.1SDLrepresentationsofSS-BICatcallinguserMS/LS.42SIST EN 300 392-12-19 V1.1.1:2003
ETSIETSIEN300392-12-19V1.1.1(2001-08)5A.2SDLrepresentationsofSS-BICatcallinguserSwMI.43A.3SDLrepresentationsofSS-BICatauthorizeduserMS/LS.44A.4SDLrepresentationsofSS-BICatSwMIwhereauthorizeduserisregistered.46A.5SDLrepresentationofSS-BICatSS-BICcalleduserhomeSwMI.48A.6SDLrepresentationofSS-BICatSS-BICcalleduserMS/LS.50AnnexB(informative):Bibliography.51History.52SIST EN 300 392-12-19 V1.1.1:2003
ETSIETSIEN300392-12-19V1.1.1(2001-08)6IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSIProjectTerrestrialTrunkedRadio(TETRA).ThepresentdocumenthadbeensubmittedtoPublicEnquiryasETS300392-12-19.DuringtheprocessingforVoteitwasconvertedintoanEN.Thepresentdocumentispart12,sub-part19ofamulti-partdeliverablecoveringVoiceplusData(V+D),asidentifiedbelow:Part1:"Generalnetworkdesign";Part2:"AirInterface(AI)";Part3:"InterworkingattheInter-SystemInterface(ISI)";Part4:"Gatewaysbasicoperation";Part5:"PeripheralEquipmentInterface(PEI)";Part7:"Security";Part9:"Generalrequirementsforsupplementaryservices";Part10:"Supplementaryservicesstage1";Part11:"Supplementaryservicesstage2";Part12:"Supplementaryservicesstage3";Part13:"SDLmodeloftheAirInterface(AI)";Part14:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part15:TETRAfrequencybands,duplexspacingsandchannelnumbering";Part16:"NetworkPerformanceMetrics";Part17:"TETRAV+DandDMORelease1.1specifications".SIST EN 300 392-12-19 V1.1.1:2003
ETSIETSIEN300392-12-19V1.1.1(2001-08)7NationaltranspositiondatesDateofadoptionofthisEN:3August2001DateoflatestannouncementofthisEN(doa):30November2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31May2002DateofwithdrawalofanyconflictingNationalStandard(dow):31May2002SIST EN 300 392-12-19 V1.1.1:2003
ETSIETSIEN300392-12-19V1.1.1(2001-08)81ScopeThepresentdocumentdefinesthestage3specificationoftheBarringofIncomingCall(BIC)supplementaryservicefortheTerrestrialTrunkedRadio(TETRA).SS-BICsupplementaryserviceenablesbarringrestrictionsforincomingservices,e.g.calls,tobeset.SS-BICspecifiesthedefinition,interrogationandoperationofthesupplementaryservice.TheSwitchingandManagementInfrastructure(SwMI)appliestheSS-BICdefinitionswhenanincomingserviceisrequestedfortherestricteduser.TheSS-BICactionsaredefinedfortheSwMI,fortheMobileStation(MS)andfortheLineStation(LS).TheSS-BICinformationflowsmaybedeliveredovertheInterSystemInterface(ISI).SS-BICisinvokedforincomingserviceswithinoneTETRAsystemorforservicesthatextendoverISItoseveralTETRAsystems.Man-MachineInterface(MMI)andchargingprinciplesareoutsidethescopeofthepresentdocument.Signallinginpacketdataserviceisoutsidethescopeofthepresentdocument.AccordingtoITU-TRecommendationI.130[7],supplementaryservicestage3specificationisprecededbythestage1andthestage2specificationsoftheservice.Stage1describesthefunctionalcapabilitiesfromtheuser'spointofview.Stage2definesthefunctionalbehaviourintermsoffunctionalentitiesandinformationflows.Stage3givesaprecisedescriptionoftheSupplementaryServicefromtheprotocolpointofview.Itdefinestheprotocolfortheserviceandtheencodingrulesfortheinformationflows.Itdefinestheprocessesforthefunctionalentitiesandtheirbehaviour.ThedescribedprotocolsandbehaviourapplytotheSwMI,fortheMSandfortheLSandmaybeappliedovertheISIbetweenTETRAsystems.AspectsrelatingtoallsupplementaryservicesaredetailedinEN300392-9[5].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublicationand/oreditionnumberorversionnumber)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.[1]ETSIEN300392-2:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part2:AirInterface(AI)".[2]ETSIETS300392-1:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part1:Generalnetworkdesign".[3]ETSIETS300392-10-1:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part10:Supplementaryservicesstage1;Sub-part1:Callidentification".[4]ETSIETS300392-10-6:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part10:Supplementaryservicesstage1;Sub-part6:CallAuthorizedbyDispatcher(CAD)".[5]ETSIEN300392-9:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part9:Generalrequirementsforsupplementaryservices".[6]ITU-TRecommendationZ.100(1993):"Specificationanddescriptionlanguage(SDL)".[7]ITU-TRecommendationI.130:"MethodforthecharacterizationoftelecommunicationservicessupportedbyanISDNandnetworkcapabilitiesofanISDN".[8]ETSIETS300392-3-1:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part3:InterworkingattheInter-SystemInterface(ISI);Sub-part1:Generaldesign".SIST EN 300 392-12-19 V1.1.1:2003
ETSIETSIEN300392-12-19V1.1.1(2001-08)9[9]ETSIEN300392-3-2:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part3:InterworkingattheInter-SystemInterface(ISI);Sub-part2:AdditionalNetworkFeatureIndividualCall(ANF-ISIIC)".[10]ITU-TRecommendationX.219:"RemoteOperations:Model,notationandservicedefinition".[11]ITU-TRecommendationX.229:"RemoteOperations:Protocolspecification".[12]ITU-TRecommendationX.217:"Informationtechnology-OpenSystemsInterconnection-ServicedefinitionfortheAssociationControlServiceElement".[13]ETSIETS300392-10-19:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part10:Supplementaryservicesstage1;Sub-part19:Barringofincomingcalls".3Definitions,symbolsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:affecteduser:userwhoseincomingserviceorservicesarebarredauthorizeduser:userwhoispermittedtodefineSS-BIConaffecteduser'sbehalfcallingparty:partywhoseoutgoingservicerequestisbarredduetoSS-BICNOTE:Alsodefinedasaffecteduser.packetdataservice:packetmodedataservice,seeEN300392-2,clause28restrictedparty:userwhoseoutgoingserviceorservicestotheaffecteduserarebarred3.2SymbolsForthepurposesofthepresentdocument,thesymbolsusedinSDLrepresentationsofproceduresaccordingtoITU-TRecommendationZ.100[6]apply.3.3Abbreviations3.3.1GeneralabbreviationsForthepurposesofthepresentdocument,thefollowinggeneralabbreviationsapply:CCCallControlsub-entityforSS-BICinCMCEinSwMICMCECircuitModeControlEntityISIInterSystemInterfaceLSLineStationMCCMobileCountryCodeMNCMobileNetworkCodeMSMobileStationPDUProtocolDataUnitSAPServiceAccessPointSSSupplementaryServiceSS-BICSupplementaryServiceBarringofIncomingCallSSIShortSubscriberIdentitySwMISwitchingandManagementInfrastructureTETRATerrestrialTrunkedRadioTNCC-SAPCallControlserviceaccesspointSIST EN 300 392-12-19 V1.1.1:2003
ETSIETSIEN300392-12-19V1.1.1(2001-08)10TNSS-SAPSupplementaryServiceServiceAccessPointTSITETRASubscriberIdentity3.3.2SupplementaryserviceabbreviationsForthepurposesofthepresentdocument,thefollowingsupplementaryserviceabbreviationsapply:BICBarringofIncomingCallsCADCallAuthorizedbyDispatcherSNAShortNumberAddressing4SS-BICservicedescription4.1GeneralSS-BICsupplementaryserviceenablesbarringrestrictionsforincomingservices,e.g.calls,tobeset.SS-BICspecifiesthedefinition,interrogationandoperationofthesupplementaryservice.TheSwitchingandManagementInfrastructure(SwMI)appliestheSS-BICdefinitionswhenanincomingserviceisrequestedfortherestricteduser.TheSS-BICactionsaredefinedfortheSwMI,fortheMobileStation(MS)andfortheLineStation(LS).TheSS-BICinformationflowsmaybedeliveredovertheInterSystemInterface(ISI).ThissupplementaryserviceisapplicabletoallbasiccircuitmodespeechanddataservicesdefinedinEN300392-2[1]aswellastoSDSmodeservices.4.2SS-BICservicesSS-BICisanoptionalsupplementaryserviceforTETRAvoiceplusdatalayer3.IfSS-BICissupported,thisclauseshallspecifytheservicesandtheiravailability.ThefollowingSS-BICservicesshallbeprovided:-barringindication:barringindicationforabasicservice(callcontrolservice).NOTE1:ThebarringindicationforSDSserviceisoutsidethescopeofthepresentdocument.ThefollowingSS-BICservicesmaybeprovided:-definition:arequesttodefineSS-BICintotheSwMI;-definitioninformation:thereceptionofSS-BICdefinitionforinformation;-interrogation:interrogationofSS-BICdefinition.TheSS-BICserviceaccesspointmaybeusedinconformancetestingasanormative(butpotentiallynotaccessible)boundaryinMSsandLSs.NOTE2:AsthepresentdocumentonlydealswiththeSS-BICalltheserviceprimitiveshavebeenshownwithoutaTNSS-BIC-prefixe.g.theTNSS-BICSERVICErequestisshortenintotheSERVICErequest.NOTE3:Asman-machineinterfaceorUserAMS/LSapplicationsareoutsidethescopeofthisstandardserviceprimitivesareusedtodefineinformationexchangetoandfromthestandardizedpartoftheMS/LS.Thoseprimitivesmaybeonlyindirectlyaccessible.NOTE4:Thelayer3servicesandserviceboundaryfortheSwMIareoutsidethescopeofthepresentdocument.TheSS-BICservicesdescribedinthisclauseshallcomplementthecallcontrolservicespecifiedinEN300392-2[1],clause11.SIST EN 300 392-12-19 V1.1.1:2003
ETSIETSIEN300392-12-19V1.1.1(2001-08)114.3ServicesatTNSS-SAP4.3.1GeneralonservicesTheSS-BICdefinition,userdefinitionandinterrogationshallbeprovidedatTNSS-SAP.TheSS-BICserviceprimitivesfortheauthorizeduserMS/LSattheTNSS-SAPmaybe:-DEFINErequest;-DEFINEindication;-DEFINEEXTERNALrequest;-DEFINEEXTERNALindication;-INTERROGATErequest;and-INTERROGATEindication.TheSS-BICserviceprimitivesfortheaffecteduserMS/LSattheTNSS-SAPmaybe:-DEFINEUSERindication;-DEFINEEXTERNALUSERindication;-INTERROGATErequest;and-INTERROGATEindication.TheSS-BICserviceprimitivesforthecallinguserMS/LSattheTNSS-SAPmaybe:-CALLBARREDindication;-NOTIFICATIONindication.NOTE:Inthepresentdocumentprimitivesrequestandindicationareusedinsteadofrequestandconfirmationastheremaynotbeaonetoonecorrespondencebetweenthoseprimitives,e.g.therecanbemultipleindicationsduetoasinglerequest.Theinformationcontainedinthefollowingprimitivedescriptiontablescorrespondtothefollowingkey:-Remark:comment;-C:conditional;-O:optional;-M:mandatory.4.3.2CALLBARREDindicationCALLBARREDindicationindicatestothecallinguserthatthebasicserviceinvocationhasbeenbarredduetoSS-BIC.TheCALLBARREDrequestprimitiveshallcontaintheSS-BICparameterslistedintable1.Table1:ParametersfortheprimitiveCALLBARREDindicationParameterIndicationRejectcauseMNOTE:AlsoNOTIFICATIONindicationisavailableforinformingthecallinguser,refertoEN300392-9[5],clauses5.2and7.2.2.SIST EN 300 392-12-19 V1.1.1:2003
ETSIETSIEN300392-12-19V1.1.1(2001-08)124.3.3DEFINErequestTheDEFINErequestprimitiveshallbesentbytheauthorizedusertotheSS-BICcontrollingentityoverTNSS-SAPtodefineBICsupplementaryserviceonaffecteduserbehalf.Ifthereareseveralsubscriberidentitiesgivenintheprimitive,thedefinitionresultshallbevalidtoallidentities.TheDEFINErequestprimitiveshallcontaintheSS-BICparameterslistedintable2.Table2:ParametersfortheprimitiveDEFINErequestParameterRequestAffecteduseridentityM,seenote1DefinitiontypeMServicesMClosedusergroupsC,seenote2RestrictedidentitiesC,seenote2ExceptionstorestrictedidentitiesM,seenote2Deliverytoaffecteduser(s)MAcknowledgementrequestedMNOTE1:Repeatable.NOTE2:Parametermaybepresentonlyifthedefinitiontypeisadditionorreplacement.4.3.4DEFINEindicationTheDEFINEindicationprimitiveshallbesenttotheauthorizeduserbytheSS-BICcontrollingentityoverTNSS-SAPtoconfirmtheSS-BICdefinition.Ifthereareseverals
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.