SIST EN 300 392-11-18 V1.1.1:2003

Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 18: Barring of Outgoing Calls (BOC)

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 08.60 to 08.85

Prizemni snopovni radio (TETRA) - Govor in podatki (V+D) - 11. del: Dopolnilne storitve stopnje 2 - 11-18. del: Zapora odhodnih klicev (BOC)

General Information

• Status: Published
• Publication Date: 30-Nov-2003
• Withdrawal Date: 30-Jun-1999
• ICS: 33.070.10 - Terrestrial Trunked Radio (TETRA)
• Technical Committee: RES - Radio equipment and systems
• 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 EN 300 392-11-18 V1.1.1 (2001-08) - Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 18: Barring of Outgoing Calls (BOC)

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 300 392-11-18
01-MXOLM
Prizemni snopovni radio (TETRA) - Govor in podatki (V+D) - 11. del: Dopolnilne
storitve stopnje 2 - 11-18. del: Zapora odhodnih klicev (BOC)
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary
services stage 2; Sub-part 18: Barring of Outgoing Calls (BOC)
Ta slovenski standard je istoveten z: EN 300 392-11-18 (
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST EN 300 392-11-18 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST EN 300 392-11-18 V1.1.1:2003

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

SIST EN 300 392-11-18 V1.1.1:2003
DRAFT
EUROPEAN pr ETS 300 392-11-18
TELECOMMUNICATION October 1996
STANDARD
Source: ETSI TC-RES Reference: DE/RES-06001-11-18
ICS: 33.020, 33.060, 33.060.50
Key words: TETRA, Supplementary S
Radio Equipment and Systems (RES);
Trans-European Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 11: Supplementary Services (SS) Stage 2;
Part 11-18: Barring of Outgoing Calls (BOC)
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: [e-mail]
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 1996. All rights reserved.

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

SIST EN 300 392-11-18 V1.1.1:2003
Page 2
Draft prETS 300 392-11-18: October 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-11-18 V1.1.1:2003
Page 3
Draft prETS 300 392-11-18: October 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .8
3.1 Definitions .8
3.2 Abbreviations .8
4 SS-BOC stage 2 specification.9
4.1 Functional model.9
4.1.1 Functional model description.9
4.1.2 Description of FEs.10
4.1.2.1 Affected user's FE, FE1.10
4.1.2.2 SS-BOC FE in the SwMI, FE2.10
4.1.2.3 Authorized user's FE, FE3.11
4.1.2.4 SS-BOC generic FE in SwMI, FE4 .11
4.1.2.5 Called party's FE, FE5.11
4.2 Relationship with a basic and packet data service .11
4.3 Definition of information flows.12
4.3.1 Definition .12
4.3.1.1 DEFINE.13
4.3.1.2 DEFINE-ACK.14
4.3.1.3 INFORM-USER .14
4.3.1.4 INFORM-USER-ACK.15
4.3.2 Interrogation .15
4.3.2.1 INTERROGATE.16
4.3.2.2 INTERROGATE-ACK.16
4.3.3 Operation.17
4.3.3.1 CALL-BARRED.18
4.4 Information flow sequences.18
4.4.1 Definition .19
4.4.2 Definition over ISI .19
4.4.3 Interrogation .20
4.4.4 Interrogation over ISI.20
4.4.5 Operation.21
4.4.6 Operation over ISI .21
4.5 FE actions.21
4.5.1 FE actions of FE1.21
4.5.2 FE actions of FE2.22
4.5.3 FE actions of FE3.22
4.5.4 FE actions of FE4.22
4.5.5 FE actions of FE5.22
4.6 Allocation of FEs to physical equipment .22
4.7 Inter-working considerations.23
History.24

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

SIST EN 300 392-11-18 V1.1.1:2003
Page 4
Draft prETS 300 392-11-18: October 1996
Blank page

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

SIST EN 300 392-11-18 V1.1.1:2003
Page 5
Draft prETS 300 392-11-18: October 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 9: DE/RES-06001-9, work item stopped.
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", (DE/RES-06001-14).
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-11-18 V1.1.1:2003
Page 6
Draft prETS 300 392-11-18: October 1996
Blank page

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

SIST EN 300 392-11-18 V1.1.1:2003
Page 7
Draft prETS 300 392-11-18: October 1996
1 Scope
This European Telecommunication Standard (ETS) defines the stage 2 specification of the
Supplementary Service Barring of Outgoing Calls (SS-BOC) for the Trans-European Trunked Radio
(TETRA) as provided by European operators.
SS-BOC enables barring restriction for outgoing calls to be set. SS-BOC specifies the definition,
interrogation and operation of the supplementary service. The Switching and Management Infrastructure
(SwMI) applies the SS-BOC definitions when the restricted user requests an outgoing service.
The SS-BOC actions are defined for the SwMI, for the Mobile Station (MS) and for the Line Station (LS).
The SS-BOC information flows may be delivered over the Inter-System Interface (ISI). SS-BOC may also
be invoked for services, e.g. calls, within one TETRA system or for services that extend over the ISI to
several TETRA systems.
Man-Machine Interface (MMI) and charging principles are outside the scope of this ETS.
Stage 2 describes the functional capabilities of the Supplementary Service introduced in stage 1
description. Stage 2 identifies the functional capabilities for the management and operation of the service
in the SwMI, in the MS and in the LS. Stage 2 describes also the information flows exchanged between
these entities and the flows sent over the ISI.
NOTE: The stage 2 description is followed by the stage 3 description, which specifies
the encoding rules for the information flows and process behaviour for the different
entities in the SwMI, in the MS and in the LS.
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-12-18: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA); Voice plus Data (V+D); Part: 12: Supplementary
services stage 2; Part 12-18: Barring of Outgoing Calls (BOC)".
[3] ETS 300 392-11-19: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA); Voice plus Data (V+D); Part: 11: Supplementary
services stage 2; Part 11-19: Barring of Incoming Calls (BIC)".
[4] 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".
[5] 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 authorized by dispatcher".

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

SIST EN 300 392-11-18 V1.1.1:2003
Page 8
Draft prETS 300 392-11-18: October 1996
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
affected user: The user who has outgoing calls barred.
authorized user: The user who is permitted to bar outgoing calls on affected user's behalf.
basic service: Circuit mode speech service and circuit mode data service, see ETS 300 392-2 [1]
clause 11.
Functional Entity (FE): Functional Entity performs the SS-BOC specific tasks in the MS, the LS or
the SwMI.
NOTE: In stage 2 specification the FE functionality is not restricted to SS sub-entity within
layer 3.
home system: The TETRA network which Mobile Network Identity (MNI) is equal to the user's MNI.
The SS-BOC definition is saved in the home system and home system is responsible for transporting
the SS-BOC definition to visited system(s).
Inter-System Interface (ISI): The interface between two TETRA networks, that supports 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.
SS-BOC definition indication: The SS-BOC definition indication may be sent to the affected user(s)
to inform him about the definition made on his behalf.
SS-BOC operation: The barring of a call in accordance with the SS-BOC definition.
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 functional entity
CCA Call Control functional entity Agent
FE Functional Entity
ISI Inter-System Interface
LS Line Station
MCC Mobile Country Code
MNC Mobile Network Code
MNI Mobile Network Identity
MS Mobile Station
SDL (Functional) Specification and Description Language
SS-BOC Supplementary Service Barring of Outgoing Calls

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

SIST EN 300 392-11-18 V1.1.1:2003
Page 9
Draft prETS 300 392-11-18: October 1996
SwMI Switching and Management Infrastructure
TETRA Trans-European Trunked RAdio
TSI TETRA Subscriber Identity
V+D Voice plus Data
4 SS-BOC stage 2 specification
4.1 Functional model
4.1.1 Functional model description
The functional model shall comprise the following Functional Entities (FEs):
FE1 affected user's (calling party's) FE for SS-BOC in MS/LS;
FE2 SS-BOC FE in SwMI;
FE3 authorized party's FE for SS-BOC in MS/LS;
FE4 SS-BOC generic FE in SwMI in visited system;
FE5 called party's FE for SS-BOC in MS/LS;
CC call control functional entity in SwMI;
CCA call
control functional entity agent in MS/LS.
NOTE: CC/CCA refers to any basic service sub-entity or packet mode data service entity,
which shall be used in conjunction with SS-BIC.
The following relationships shall exist between these FEs:
ra between FE1 and FE2;
rb between FE2 and FE2 in different TETRA systems;
rc between FE2 and FE3;
rd between FE2 and FE4 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
authorized SS-BOC FE SS-BOC FE authorized
user  ra  re user
FE1 FE1
affected affected
user user
Figure 1: Functional model for the management part

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

SIST EN 300 392-11-18 V1.1.1:2003
Page 10
Draft prETS 300 392-11-18: October 1996
home system visited system
ra rd ra
FE1 FE2 FE2 FE1
affected SS-BOC FE SS-BOC FE affected
user  rg  rg user
FE5 FE5
called called
party party
NOTE: FE5 does not receive any indication of the barred service.
Figure 2: Functional model for the operational part
4.1.2 Description of FEs
4.1.2.1 Affected user's FE, FE1
The functional tasks of FE1 shall be the following:
- upon reception of an SS-BOC definition indication from the SwMI, FE1 shall inform the user of
the indication;
- upon reception of an SS-BOC interrogation request from the user, FE1 shall send the interrogation
request to the SwMI;
- upon reception of an SS-BOC interrogation response from the SwMI, FE1 shall inform the user of
the response;
- upon reception of a barring indication from the SwMI, FE1 shall inform the user of the barring of
the basic or packet data service.
4.1.2.2 SS-BOC FE in the SwMI, FE2
The functional tasks of FE2 shall be the following in the home system of the affected user:
- upon reception of an SS-BOC definition request from FE3, FE2 shall save the definition in the SwMI
and acknowledge the request to FE3. FE2 shall send the SS-BOC definition indication(s) to FE1(s),
if requested by FE3 in the definition request;
- upon reception of an SS-BOC interrogation request from FE1 or FE3, FE2 shall send
the interrogation response to FE1 or FE3 respectively;
- upon reception of an outgoing basic or packet data service request from FE1, for which
the SS-BOC restrictions apply, FE2 shall bar the request and inform FE1 about the barring.
The functional tasks of FE2 shall be the following in the visited system of the affected user:
- upon reception of an SS-BOC interrogation request from FE1 or FE3, FE2 shall send
the interrogation response to FE1 or FE3 respectively, if the visited system knows the SS-BOC
definition;
- upon reception of an outgoing basic or packet data service request from FE1, for which
the SS-BOC restrictions apply, FE2 shall bar the request and inform FE1 about the barring, if the
visited system knows the SS-BOC definition;

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

SIST EN 300 392-11-18 V1.1.1:2003
Page 11
Draft prETS 300 392-11-18: October 1996
- upon reception of an outgoing basic or packet data service request from FE1, FE2 may send
the service request to the home system and bar the call, if indicated by the home system. FE2 shall
inform FE1 about the barring of the service.
4.1.2.3 Authorized user's FE, FE3
The functional tasks of FE3 shall be the following:
- upon reception of an SS-BOC definition request from the user, FE3 shall send the request to
the SwMI;
- upon reception of an SS-BOC definition acknowledgement from the SwMI, FE3 shall inform
the user of the acknowledgement;
- upon reception of an SS-BOC interrogation request from the user, FE3 shall send the request to
the SwMI;
- upon reception of an SS-BOC interrogation response from the SwMI, FE3 shall inform the user of
the response.
4.1.2.4 SS-BOC generic FE in SwMI, FE4
As a generic functional entity for transportation, FE4 shall have as it functional tasks the following tasks:
- upon reception of an SS-BOC information flow over the ISI from FE2 to FE1 or to FE3, FE4 shall
transport the flow to FE1 or to FE3 respectively;
- upon reception of an SS-BOC information flow from FE1 or FE3 to FE2, FE4 shall transport the flow
over the ISI to FE2.
4.1.2.5 Called party's FE, FE5
FE5 does not have any actions related to SS-BOC. The FE is only presented to clarify the service
behaviour.
4.2 Relationship with a basic and packet data service
FE2 shall be collocated to CC in the SwMI.
FE1 shall be collocated to CCA.
The relationship with basic and packet data service is shown in figure 3.

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

SIST EN 300 392-11-18 V1.1.1:2003
Page 12
Draft prETS 300 392-11-18: October 1996
home system visited system
ra rd ra
FE1 FE2 FE2 FE1
CCA CC CC CCA
affected SS-BOC FE SS-BOC FE affected
user  rg     rg user
FE5 FE5
called called
party party
NOTE: FE5 does not receive any indication of the barred service.
Figure 3: Relationships with FEs and CCs/CCAs
4.3 Definition of information flows
In the tables listing the service elements in information flows, the column header "Type" indicates which of
the service elements are Mandatory (M), Conditional (C) or Optional (O). If type is conditional,
the conditions are stated.
The listed service elements shall specify whether the information of each element is included in the flow.
NOTE: It is possible that there is not a one-to-one mapping between a service element and
Protocol Data Unit (PDU) or primitive elements described in ETS 300 392-12-18 [2].
4.3.1 Definition
The authorized user shall be able to define barring restrictions on affected user's behalf. The SS-BOC
definitions shall restrict outgoing services.
One restricted identity shall refer to an individual subscriber identity.
NOTE 1: Supplementary Service Barring of Incoming Calls (SS-BIC) is used to set restrictions
for group identities, see ETS 300 392-11-19 [3].
The authorized user shall only be allowed to define SS-BOC for subscriber identities which home system
is the same as the authorized user's home system.
One definition request shall be made to restrict:
- one subscriber identity;
- a range of subscriber identities; or,
- a list of subscriber identities.
The different barring restrict
...

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) - 11. del: Dopolnilne storitve stopnje 2 - 11-18. del: Zapora odhodnih klicev (BOC)Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 18: Barring of Outgoing Calls (BOC)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:EN 300 392-11-18 (3SIST EN 300 392-11-18en01-PDM3SIST EN 300 392-11-18SLOVENSKI
STANDARD



SIST EN 300 392-11-18 V1.1.1:2003



DRAFTEUROPEANprETS 300 392-11-18TELECOMMUNICATIONOctober 1996STANDARDSource: ETSI TC-RESReference: DE/RES-06001-11-18ICS:33.020, 33.060, 33.060.50Key words:TETRA, Supplementary SRadio Equipment and Systems (RES);Trans-European Trunked Radio (TETRA);Voice plus Data (V+D);Part 11: Supplementary Services (SS) Stage 2;Part 11-18: Barring of Outgoing Calls (BOC)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: [e-mail].: [phone] - Fax: [phone]Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.SIST EN 300 392-11-18 V1.1.1:2003



Page 2Draft prETS 300 392-11-18: October 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-11-18 V1.1.1:2003



Page 3Draft prETS 300 392-11-18: October 1996ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.83.1Definitions.83.2Abbreviations.84SS-BOC stage 2 specification.94.1Functional model.94.1.1Functional model description.94.1.2Description of FEs.104.1.2.1Affected user's FE, FE1.104.1.2.2SS-BOC FE in the SwMI, FE2.104.1.2.3Authorized user's FE, FE3.114.1.2.4SS-BOC generic FE in SwMI, FE4.114.1.2.5Called party's FE, FE5.114.2Relationship with a basic and packet data service.114.3Definition of information flows.124.3.1Definition.124.3.1.1DEFINE.134.3.1.2DEFINE-ACK.144.3.1.3INFORM-USER.144.3.1.4INFORM-USER-ACK.154.3.2Interrogation.154.3.2.1INTERROGATE.164.3.2.2INTERROGATE-ACK.164.3.3Operation.174.3.3.1CALL-BARRED.184.4Information flow sequences.184.4.1Definition.194.4.2Definition over ISI.194.4.3Interrogation.204.4.4Interrogation over ISI.204.4.5Operation.214.4.6Operation over ISI.214.5FE actions.214.5.1FE actions of FE1.214.5.2FE actions of FE2.224.5.3FE actions of FE3.224.5.4FE actions of FE4.224.5.5FE actions of FE5.224.6Allocation of FEs to physical equipment.224.7Inter-working considerations.23History.24SIST EN 300 392-11-18 V1.1.1:2003



Page 4Draft prETS 300 392-11-18: October 1996Blank pageSIST EN 300 392-11-18 V1.1.1:2003



Page 5Draft prETS 300 392-11-18: October 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 9:DE/RES-06001-9, work item stopped.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", (DE/RES-06001-14).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-11-18 V1.1.1:2003



Page 6Draft prETS 300 392-11-18: October 1996Blank pageSIST EN 300 392-11-18 V1.1.1:2003



Page 7Draft prETS 300 392-11-18: October 19961ScopeThis European Telecommunication Standard (ETS) defines the stage 2 specification of theSupplementary Service Barring of Outgoing Calls (SS-BOC) for the Trans-European Trunked Radio(TETRA) as provided by European operators.SS-BOC enables barring restriction for outgoing calls to be set. SS-BOC specifies the definition,interrogation and operation of the supplementary service. The Switching and Management Infrastructure(SwMI) applies the SS-BOC definitions when the restricted user requests an outgoing service.The SS-BOC actions are defined for the SwMI, for the Mobile Station (MS) and for the Line Station (LS).The SS-BOC information flows may be delivered over the Inter-System Interface (ISI). SS-BOC may alsobe invoked for services, e.g. calls, within one TETRA system or for services that extend over the ISI toseveral TETRA systems.Man-Machine Interface (MMI) and charging principles are outside the scope of this ETS.Stage 2 describes the functional capabilities of the Supplementary Service introduced in stage 1description. Stage 2 identifies the functional capabilities for the management and operation of the servicein the SwMI, in the MS and in the LS. Stage 2 describes also the information flows exchanged betweenthese entities and the flows sent over the ISI.NOTE:The stage 2 description is followed by the stage 3 description, which specifiesthe encoding rules for the information flows and process behaviour for the differententities in the SwMI, in the MS and in the LS.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-12-18: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA); Voice plus Data (V+D); Part: 12: Supplementaryservices stage 2; Part 12-18: Barring of Outgoing Calls (BOC)".[3]ETS 300 392-11-19: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA); Voice plus Data (V+D); Part: 11: Supplementaryservices stage 2; Part 11-19: Barring of Incoming Calls (BIC)".[4]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".[5]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 authorized by dispatcher".SIST EN 300 392-11-18 V1.1.1:2003



Page 8Draft prETS 300 392-11-18: October 19963Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply:affected user: The user who has outgoing calls barred.authorized user: The user who is permitted to bar outgoing calls on affected user's behalf.basic service: Circuit mode speech service and circuit mode data service, see ETS 300 392-2 [1]clause 11.Functional Entity (FE): Functional Entity performs the SS-BOC specific tasks in the MS, the LS orthe SwMI.NOTE:In stage 2 specification the FE functionality is not restricted to SS sub-entity withinlayer 3.home system: The TETRA network which Mobile Network Identity (MNI) is equal to the user's MNI.The SS-BOC definition is saved in the home system and home system is responsible for transportingthe SS-BOC definition to visited system(s).Inter-System Interface (ISI): The interface between two TETRA networks, that supports the inter-workingof services between these two systems.Mobile Network Identity (MNI): Mobile Country Code (MCC) and Mobile Network Code (MNC) ofthe TETRA 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.SS-BOC definition indication: The SS-BOC definition indication may be sent to the affected user(s)to inform him about the definition made on his behalf.SS-BOC operation: The barring of a call in accordance with the SS-BOC definition.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 functional entityCCACall Control functional entity AgentFEFunctional EntityISIInter-System InterfaceLSLine StationMCCMobile Country CodeMNCMobile Network CodeMNIMobile Network IdentityMSMobile StationSDL(Functional) Specification and Description LanguageSS-BOCSupplementary Service Barring of Outgoing CallsSIST EN 300 392-11-18 V1.1.1:2003



Page 9Draft prETS 300 392-11-18: October 1996SwMISwitching and Management InfrastructureTETRATrans-European Trunked RAdioTSITETRA Subscriber IdentityV+DVoice plus Data4SS-BOC stage 2 specification4.1Functional model4.1.1Functional model descriptionThe functional model shall comprise the following Functional Entities (FEs):FE1affected user's (calling party's) FE for SS-BOC in MS/LS;FE2SS-BOC FE in SwMI;FE3authorized party's FE for SS-BOC in MS/LS;FE4SS-BOC generic FE in SwMI in visited system;FE5called party's FE for SS-BOC in MS/LS;CCcall control functional entity in SwMI;CCAcall control functional entity agent in MS/LS.NOTE:CC/CCA refers to any basic service sub-entity or packet mode data service entity,which shall be used in conjunction with SS-BIC.The following relationships shall exist between these FEs:rabetween FE1 and FE2;rbbetween FE2 and FE2 in different TETRA systems;rcbetween FE2 and FE3;rdbetween FE2 and FE4 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 forthe management part and figure 2 gives the functional model for the operational part. home system visited systemrcrbrfFE3FE2FE4FE3authorizedSS-BOC FESS-BOC FEauthorizeduser
ra
reuserFE1FE1affectedaffecteduseruserFigure 1: Functional model for the management partSIST EN 300 392-11-18 V1.1.1:2003



Page 10Draft prETS 300 392-11-18: October 1996home systemvisited systemrardraFE1FE2FE2FE1affectedSS-BOC FESS-BOC FEaffecteduser
rg
rguserFE5FE5calledcalledpartypartyNOTE:FE5 does not receive any indication of the barred service.Figure 2: Functional model for the operational part4.1.2Description of FEs4.1.2.1Affected user's FE, FE1The functional tasks of FE1 shall be the following:-upon reception of an SS-BOC definition indication from the SwMI, FE1 shall inform the user ofthe indication;-upon reception of an SS-BOC interrogation request from the user, FE1 shall send the interrogationrequest to the SwMI;-upon reception of an SS-BOC interrogation response from the SwMI, FE1 shall inform the user ofthe response;-upon reception of a barring indication from the SwMI, FE1 shall inform the user of the barring ofthe basic or packet data service.4.1.2.2SS-BOC FE in the SwMI, FE2The functional tasks of FE2 shall be the following in the home system of the affected user:-upon reception of an SS-BOC definition request from FE3, FE2 shall save the definition in the SwMIand acknowledge the request to FE3. FE2 shall send the SS-BOC definition indication(s) to FE1(s),if requested by FE3 in the definition request;-upon reception of an SS-BOC interrogation request from FE1 or FE3, FE2 shall sendthe interrogation response to FE1 or FE3 respectively;-upon reception of an outgoing basic or packet data service request from FE1, for whichthe SS-BOC restrictions apply, FE2 shall bar the request and inform FE1 about the barring.The functional tasks of FE2 shall be the following in the visited system of the affected user:-upon reception of an SS-BOC interrogation request from FE1 or FE3, FE2 shall sendthe interrogation response to FE1 or FE3 respectively, if the visited system knows the SS-BOCdefinition;-upon reception of an outgoing basic or packet data service request from FE1, for whichthe SS-BOC restrictions apply, FE2 shall bar the request and inform FE1 about the barring, if thevisited system knows the SS-BOC definition;SIST EN 300 392-11-18 V1.1.1:2003



Page 11Draft prETS 300 392-11-18: October 1996-upon reception of an outgoing basic or packet data service request from FE1, FE2 may sendthe service request to the home system and bar the call, if indicated by the home system. FE2 shallinform FE1 about the barring of the service.4.1.2.3Authorized user's FE, FE3The functional tasks of FE3 shall be the following:-upon reception of an SS-BOC definition request from the user, FE3 shall send the request tothe SwMI;-upon reception of an SS-BOC definition acknowledgement from the SwMI, FE3 shall informthe user of the acknowledgement;-upon reception of an SS-BOC interrogation request from the user, FE3 shall send the request tothe SwMI;-upon reception of an SS-BOC interrogation response from the SwMI, FE3 shall inform the user ofthe response.4.1.2.4SS-BOC generic FE in SwMI, FE4As a generic functional entity for transportation, FE4 shall have as it functional tasks the following tasks:-upon reception of an SS-BOC information flow over the ISI from FE2 to FE1 or to FE3, FE4 shalltransport the flow to FE1 or to FE3 respectively;-upon reception of an SS-BOC information flow from FE1 or FE3 to FE2, FE4 shall transport the flowover the ISI to FE2.4.1.2.5Called party's FE, FE5FE5 does not have any actions related to SS-BOC. The FE is only presented to clarify the servicebehaviour.4.2Relationship with a basic and packet data serviceFE2 shall be collocated to CC in the SwMI.FE1 shall be collocated to CCA.The relationship with basic and packet data service is shown in figure 3.SIST EN 300 392-11-18 V1.1.1:2003



Page 12Draft prETS 300 392-11-18: October 1996home systemvisited systemrardraFE1FE2 FE2FE1CCACC CCCCAaffectedSS-BOC FESS-BOC FEaffecteduser
rg
rguserFE5FE5calledcalledpartypartyNOTE:FE5 does not receive any indication of the barred service.Figure 3: Relationships with FEs and CCs/CCAs4.3Definition of information flowsIn the tables listing the service elements in information flows, the column header "Type" indicates which ofthe service elements are Mandatory (M), Conditional (C) or Optional (O). If type is conditional,the conditions are stated.The listed service elements shall specify whether the information of each element is included in the flow.NOTE:It is possible that there is not a one-to-one mapping between a service element andProtocol Data Unit (PDU)
or primitive elements described in ETS 300 392-12-18 [2].4.3.1DefinitionThe authorized user shall be able to define barring restrictions on affected user's behalf. The SS-BOCdefinitions shall restrict outgoing services.One restricted identity shall refer to an individual subscriber identity.NOTE 1:Supplementary Service Barring of Incoming Calls (SS-BIC) is used to set restrictionsfor group identities, see ETS 300 392-11-19 [3].The authorized user shall only be allowed to define SS-BOC for subscriber identities which home systemis the same as the authorized user's home system.One definition request shall be made to restrict:-one subscriber identity;-a range of subscriber identities; or,-a list of subscriber identities.The different barr
...

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) - 11. del: Dopolnilne storitve stopnje 2 - 11-18. del: Zapora odhodnih klicev (BOC)Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 18: Barring of Outgoing Calls (BOC)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:EN 300 392-11-18 Version 1.1.1SIST EN 300 392-11-18 V1.1.1:2003en01-december-2003SIST EN 300 392-11-18 V1.1.1:2003SLOVENSKI
STANDARD



SIST EN 300 392-11-18 V1.1.1:2003



ETSIEN300392-11-18V1.1.1(2001-08)EuropeanStandard(Telecommunicationsseries)TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part11:Supplementaryservicesstage2;Sub-part18:BarringofOutgoingCalls(BOC)SIST EN 300 392-11-18 V1.1.1:2003



ETSIETSIEN300392-11-18V1.1.1(2001-08)2ReferenceDEN/TETRA-03A-11-18KeywordsTETRA,supplementaryserviceETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°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:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 300 392-11-18 V1.1.1:2003



ETSIETSIEN300392-11-18V1.1.1(2001-08)3ContentsIntellectualPropertyRights.4Foreword.41Scope.62References.63Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.74SS-BOCstage2specification.74.1Functionalmodel.74.1.1Functionalmodeldescription.74.1.2DescriptionofFEs.84.1.2.1Affecteduser'sFE,FE1.84.1.2.2SS-BOCFEintheSwMI,FE2.94.1.2.3Authorizeduser'sFE,FE3.94.1.2.4SS-BOCFE2invisitedSwMI.94.1.2.5Calledparty'sFE,FE5.94.2Relationshipwithabasicandpacketdataservice.104.3Definitionofinformationflows.104.3.1Definition.104.3.1.1DEFINE.114.3.1.2DEFINEandDEFINEEXTERNALACK.124.3.1.3DEFINEUSER.124.3.1.4DEFINEUSERACK.134.3.2Interrogation.134.3.2.1INTERROGATE.134.3.2.2INTERROGATEACK.144.3.3Operation.154.3.3.1CALLBARRED.154.4Serviceprimitives.164.5Informationflowsequences.164.5.1Definition.174.5.2DefinitionoverISI.174.5.3Interrogation.184.5.4InterrogationoverISI.194.5.5Operation.194.5.6OperationoverISI.194.6FEactions.204.6.1FEactionsofFE1.204.6.2FEactionsofFE2.204.6.3FEactionsofFE3.204.6.4FEactionsofvisitedSwMIFE2.204.6.5FEactionsofFE5.214.7AllocationofFEstophysicalequipment.214.8Inter-workingconsiderations.214.8.1Generalrequirements.214.8.2Managementandoperation.214.8.3Migration.22AnnexA(informative):Bibliography.23History.24SIST EN 300 392-11-18 V1.1.1:2003



ETSIETSIEN300392-11-18V1.1.1(2001-08)4IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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-11-18.DuringtheprocessingforVoteitwasconvertedintoanEN.Thepresentdocumentispart11,sub-part18ofamulti-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-11-18 V1.1.1:2003



ETSIETSIEN300392-11-18V1.1.1(2001-08)5NationaltranspositiondatesDateofadoptionofthisEN:3August2001DateoflatestannouncementofthisEN(doa):30November2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31May2002DateofwithdrawalofanyconflictingNationalStandard(dow):31May2002SIST EN 300 392-11-18 V1.1.1:2003



ETSIETSIEN300392-11-18V1.1.1(2001-08)61ScopeThepresentdocumentdefinesthestage2specificationoftheSupplementaryServiceBarringofOutgoingCalls(SS-BOC)fortheTerrestrialTrunkedRadio(TETRA)asprovidedbyEuropeanoperators.SS-BOCenablesbarringrestrictionforoutgoingcallstobeset.SS-BOCspecifiesthedefinition,interrogationandoperationofthesupplementaryservice.TheSwitchingandManagementInfrastructure(SwMI)appliestheSS-BOCdefinitionswhentherestricteduserrequestsanoutgoingservice.TheSS-BOCactionsaredefinedfortheSwMI,fortheMobileStation(MS)andfortheLineStation(LS).TheSS-BOCinformationflowsmaybedeliveredovertheInter-SystemInterface(ISI).SS-BOCmayalsobeinvokedforservices,e.g.calls,withinoneTETRAsystemorforservicesthatextendovertheISItoseveralTETRAsystems.Man-MachineInterface(MMI)andchargingprinciplesareoutsidethescopeofthepresentdocument.Stage2describesthefunctionalcapabilitiesoftheSupplementaryServiceintroducedinstage1description.Stage2identifiesthefunctionalcapabilitiesforthemanagementandoperationoftheserviceintheSwMI,intheMSandintheLS.Stage2describesalsotheinformationflowsexchangedbetweentheseentitiesandtheflowssentovertheISI.NOTE:Thestage2descriptionisfollowedbythestage3description,whichspecifiestheencodingrulesfortheinformationflowsandprocessbehaviourforthedifferententitiesintheSwMI,intheMSandintheLS.AspectsrelatingtoallsupplementaryservicesaredetailedinEN300392-9[6].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]ETSIEN300392-12-18:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part12:Supplementaryservicesstage3;Sub-part18:BarringofOutgoingCalls(BOC)".[3]ETSIEN300392-11-19:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part11:Supplementaryservicesstage2;Sub-part19:BarringofIncomingCalls(BIC)".[4]ETSIETS300392-10-1:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part10:Supplementaryservicesstage1;Sub-part1:Callidentification".[5]ETSIETS300392-10-6:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part10:Supplementaryservicesstage1;Sub-part6:CallAuthorizedbyDispatcher(CAD)".[6]ETSIEN300392-9:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part9:Generalrequirementsforsupplementaryservices".SIST EN 300 392-11-18 V1.1.1:2003



ETSIETSIEN300392-11-18V1.1.1(2001-08)73Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:affecteduser:userwhohasoutgoingcallsbarredauthorizeduser:userwhoispermittedtobaroutgoingcallsonaffecteduser'sbehalfpacketdataservice:packetmodedataservice,seeEN300392-2,clause283.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:CCCallControlfunctionalentityCCACallControlfunctionalentityAgentFEFunctionalEntityISIInter-SystemInterfaceLSLineStationMSMobileStationSDL(Functional)SpecificationandDescriptionLanguageSS-BOCSupplementaryServiceBarringofOutgoingCallsSwMISwitchingandManagementInfrastructureTETRATerrestrialTrunkedRadioV+DVoiceplusData4SS-BOCstage2specification4.1Functionalmodel4.1.1FunctionalmodeldescriptionThefunctionalmodelshallcomprisethefollowingFunctionalEntities(FEs):FE1affecteduser's(callingparty's)FEforSS-BOCinMS/LS;FE2SS-BOCFEinSwMIs;FE3authorizedparty'sFEforSS-BOCinMS/LS;FE5calledparty'sFEforSS-BOCinMS/LS;CCcallcontrolfunctionalentityinSwMI;CCAcallcontrolfunctionalentityagentinMS/LS.NOTE:CC/CCAreferstoanybasicservicesub-entityorpacketmodedataserviceentity,whichshallbeusedinconjunctionwithSS-BIC.SIST EN 300 392-11-18 V1.1.1:2003



ETSIETSIEN300392-11-18V1.1.1(2001-08)8ThefollowingrelationshipsshallexistbetweentheseFEs:rabetweenFE1andFE2;rbbetweenFE2sindifferentTETRAsystems;rcbetweenFE2andFE3;rdbetweenFE2sindifferentTETRAsystems;rebetweenFE1andvisitedSwMIFE2;rfbetweenFE3andvisitedSwMIFE2;rgbetweenFE2andFE5.Figures1and2showtheseFEsandtheirrelationships.Figure1givesthefunctionalmodelforthemanagementpartandfigure2givesthefunctionalmodelfortheoperationalpart.SS-BOChomeAnotherAuthorizeduserSwMISwMIAuthorizeduserrcrbrfFE3FE2FE2FE3AffecteduserrareAffecteduserFE1FE1Figure1:FunctionalmodelforthemanagementpartUserAAffecteduserhomeSwMIAnotherSwMIAffecteduserrardraFE5FE2FE2FE5NOTE:CalledpartyFE5doesnotreceiveanyindicationofthebarredservice.Figure2:Functionalmodelfortheoperationalpart4.1.2DescriptionofFEs4.1.2.1Affecteduser'sFE,FE1ThefunctionaltasksofFE1shallbethefollowing:-uponreceptionofanSS-BOCdefinitionindicationfromtheSwMI,ifFE1supportstheinformationprocedure,FE1shallinformtheuserapplication;-uponreceptionofanSS-BOCinterrogationrequestfromtheuserapplication,FE1shallsendtheinterrogationrequesttotheSwMI;-uponreceptionofanSS-BOCinterrogationresponsefromtheSwMI,FE1shallinformtheuserapplication;-uponreceptionofabarringindicationfromtheSwMI,FE1shallinformtheuserapplicationofthebarringofthebasicorpacketdataservice.SIST EN 300 392-11-18 V1.1.1:2003



ETSIETSIEN300392-11-18V1.1.1(2001-08)94.1.2.2SS-BOCFEintheSwMI,FE2ThefunctionaltasksofFE2shallbethefollowinginthehomesystemoftheaffecteduser:-uponreceptionofanSS-BOCdefinitionrequestfromFE3,FE2shallsavethedefinitionintheSwMIandacknowledgetherequesttoFE3.FE2shallsendtheSS-BOCdefinitionindication(s)toFE1(s),ifrequestedbyFE3inthedefinitionrequest;-uponreceptionofanSS-BOCinterrogationrequestfromFE1orFE3,FE2shallsendtheinterrogationresponsetoFE1orFE3respectively;-uponreceptionofanoutgoingbasicorpacketdataservicerequestfromFE1,forwhichtheSS-BOCrestrictionsapply,FE2shallbartherequestandinformFE1aboutthebarring.ThefunctionaltasksofFE2shallbethefollowinginthevisitedsystemoftheaffecteduser:-uponreceptionofanSS-BOCinterrogationrequestfromFE1orFE3,FE2shallsendtheinterrogationresponsetoFE1orFE3respectively,ifthevisitedsystemknowstheSS-BOCdefinition;-uponreceptionofanoutgoingbasicorpacketdataservicerequestfromFE1,forwhichtheSS-BOCrestrictionsapply,FE2shallbartherequestandinformFE1aboutthebarring,ifthevisitedsystemknowstheSS-BOCdefinition;-uponreceptionofanoutgoingbasicorpacketdataservicerequestfromFE1,FE2maysendtheservicerequesttothehomesystemandbarthecall,ifindicatedbythehomesystem.FE2shallinformFE1aboutthebarringoftheservice.4.1.2.3Authorizeduser'sFE,FE3ThefunctionaltasksofFE3shallbethefollowing:-uponreceptionofanSS-BOCdefinitionrequestfromtheuserapplication,FE3shallsendtherequesttotheSwMI;-uponreceptionofanSS-BOCdefinitionacknowledgementfromtheSwMI,FE3shallinformtheuserapplicationoftheacknowledgement;-uponreceptionofanSS-BOCinterrogationrequestfromtheuserapplication,FE3shallsendtherequesttotheSwMI;-uponreceptionofanSS-BOCinterrogationresponsefromtheSwMI,FE3shallinformtheuserapplicationoftheresponse.4.1.2.4SS-BOCFE2invisitedSwMIThevisitedSwMIFE2shallhaveasitfunctionaltasksthefollowingtasks,referEN300392-9[6]:-uponreceptionofanSS-BOCinformationflowovertheISIfromhomeSwMIFE2toFE1ortoFE3,thevisitedSwMIFE2shalltransporttheflowtoFE1ortoFE3respectively;-uponreceptionofanSS-BOCinformationflowfromFE1orFE3tohomeSwMIFE2,thevisitedSwMIFE2shalltransporttheflowovertheISItohomeSwMIFE2.4.1.2.5Calledparty'sFE,FE5FE5doesnothaveanyactionsrelatedtoSS-BOC.TheFEisonlypresentedtoclarifytheservicebehaviour.SIST EN 300 392-11-18 V1.1.1:2003



ETSIETSIEN300392-11-18V1.1.1(2001-08)104.2RelationshipwithabasicandpacketdataserviceFE2shallbecollocatedtoCCintheSwMI.FE1shallbecollocatedtoCCA.Therelationshipwithbasicandpacketdataserviceisshowninfigure3.AffecteduserAffecteduserhomeSwMIAnotherSwMIAffecteduserrardraFE1FE2FE2FE1CCACCCCCCANOTE:FE5doesnotreceiveanyindicationofthebarredservice.Figure3:RelationshipswithFEsandCCs/CCAs4.3DefinitionofinformationflowsInthetableslistingtheserviceelementsininformationflows,thecolumnheader"Type"indicateswhichoftheserviceelementsareMandatory(M),Conditional(C)orOptional(O).Iftypeisconditional,theconditionsarestated.Thelistedserviceelementsshallspecifywhethertheinformationofeachelementisincludedintheflow.NOTE:Itispossiblethatthereisnotaone-to-onemappingbetweenaserviceelementandProtocolDataUnit(PDU)orprimitiveelementsdescribedinEN300392-12-18[2].4.3.1DefinitionTheauthorizedusershallbeabletodefinebarringrestrictionsonaffecteduser'sbehalf.TheSS-BOCdefinitionsshallrestrictoutgoingservices.Onerestrictedidentityshallrefertoanindividualsubscriberidentity.NOTE1:SupplementaryServiceBarringofIncomingCalls(SS-BIC)isusedtosetrestrictionsforgroupidentities,seeEN300392-11-19[3].TheauthorizedusershallonlybeallowedtodefineSS-BOCforsubscriberidentitieswhichhomesystemisthesameastheauthorizeduser'shomesystem.Onedefinitionrequestshallbemadetorestrict:-onesubscriberidentity;-arangeofsubscriberidentities;or-alistofsubscriberidentities.Thedifferentbarringrestrictionsshallcompriseofoneormoreofthefollowing:-allorcertainoutgoingservicesoutsideclosedusergroups;-allorcertainoutgoingservicestypes;-restricteddestinationaddressesforoutgoingservices.Thedefinitionmaycontainexceptionstothebarreddestinationaddresses.Theauthorized
...