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

• Abstract:

  To define the Stage 2 requirements for TETRA SS Area Selection

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.070.10 - Terrestrial Trunked Radio (TETRA)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Mandate: BC-T-344
• Ref Project: ETSI EN 300 392-11-8 V1.1.1 (2000-12) - Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 8: Area Selection (AS)

SIST EN 300 392-11-8 V1.1.1:2003 is the Slovenian adoption of ETSI EN 300 392-11-8 V1.1.1 for Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D). It specifies the stage 2 requirements for the TETRA supplementary service Area Selection (SS-AS), for terminal equipment and networks that need to control where a call may be set up.

What does SIST EN 300 392-11-8 V1.1.1:2003 specify?

SIST EN 300 392-11-8 V1.1.1:2003 specifies the stage 2 functional description of SS-AS in TETRA. It explains what the service does, which functional entities participate, and which information flows support definition, interrogation, invocation, operation, and failure handling.

The scope states that SS-AS lets a user select an area where a call will be set up. It also states that Man-Machine Interface (MMI) and charging principles are outside the document’s scope.

The document is organized into these main clauses:

• Clause 1 - Scope
• Clause 2 - References
• Clause 3 - Definitions and abbreviations
• Clause 4 - Functional model
• Clause 5 - Information flows
• Clause 6 - FE actions
• Clause 7 - Allocation of functional entities to physical equipment
• Clause 8 - Interworking considerations

What are the key requirements of SIST EN 300 392-11-8 V1.1.1:2003?

SIST EN 300 392-11-8 V1.1.1:2003 defines SS-AS as a stage 2 supplementary service, so it stops at functional behavior and information flows. In practice, that means the standard tells implementers what the service must do in the network and what messages must exist, while the stage 3 protocol details are left to the companion specification.

Clause 4 sets out the functional model with these entities: FE1, FE21, FE221, FE222, FE25, FE20 and FE3. The model matters because it shows where area definition is mapped, where call control checks the selected area, and where the service is enforced during call setup and, for group calls, during later call operation.

Clause 5 defines the core SS-AS information flows:

• ASSIGN and ASSIGN ACK
• DEFINE and DEFINE ACK
• INTERROGATE and INTERROGATE ACK
• INVOKE
• INVOKE CONFIRM
• INVOKE EXT
• NOT DEFINED
• NOT SUBSCRIBED
• NOT SUPPORTED

These flows matter because they separate management of area definitions from call-time use of those definitions. For a buyer or integrator, this shows that SS-AS is not only a call feature - it also has an administration side for defining and querying selectable areas.

Clause 5 also distinguishes call-independent management from call-related invocation. DEFINE and INTERROGATE are used by an authorized user to manage selectable areas, while INVOKE is used by the served user when setting up a call. That separation matters in implementation because the service has both provisioning behavior and real-time call-control behavior.

The call control behavior depends on the selected area definition and on where the relevant Switching and Management Infrastructure (SwMI) is located. The document describes cases for individual calls and group calls, including situations where the originating SwMI, called user home SwMI, group home SwMI, or participating SwMIs are wholly inside, partly inside, or outside the selected area. In practice, this is what makes SS-AS suitable for location-bounded call setup across different network topologies.

Clause 6 assigns actions to each functional entity. FE21 checks whether SS-AS is subscribed, FE221 resolves an area number to its selected area definition, FE222 decides where FE25 instances are needed, and FE25 enforces the area limit on call establishment and call continuation. For implementers, these actions are the clearest description of what each node must do when a user invokes SS-AS.

The document also defines failure handling. If the area number is not defined, the service returns NOT DEFINED. If SS-AS is not subscribed, it returns NOT SUBSCRIBED. If another SwMI on the call path does not support the service or the selected area type, it returns NOT SUPPORTED. That is important in practice because it tells an implementation how to fail cleanly instead of attempting an unsupported call setup.

Clause 8 adds interworking considerations for multi-network situations. It describes how SS-AS profile information is exchanged when an individual subscriber migrates or when a SwMI attaches to a group, and it states that SS-AS invocation for an external outgoing call is ignored. This matters for operators because the service must remain consistent when subscribers move between SwMIs.

What terms does SIST EN 300 392-11-8 V1.1.1:2003 define?

Supplementary Service Area Selection (SS-AS) - The supplementary service that lets a user choose an area in which a call is allowed to be set up.

served user - The calling party that invokes SS-AS when setting up an individual call or a group call.

authorized user - An identified user who is allowed to define SS-AS areas and/or interrogate the infrastructure about areas defined for a subscriber or group.

served user SwMI - The SwMI where the served user is currently registered; for a call, this is the originating SwMI.

geographical definition - A selected area definition based on map limits, such as a circle, a line-based area, or a rectangle.

site definition - A selected area definition expressed as a list of base stations within one or more SwMIs, sometimes implicitly as a whole home SwMI.

important user - In a group call, a user treated as important by the group controlling SwMI; for SS-AS, this also includes the calling user.

SwMI - Switching and Management Infrastructure, the network side entity that controls and manages TETRA service behavior.

Who uses SIST EN 300 392-11-8 V1.1.1:2003?

SIST EN 300 392-11-8 V1.1.1:2003 is used by TETRA network designers, SwMI implementers, and terminal equipment engineers who need to support area-based call setup control. It is also used by interoperability engineers, conformance test teams, and quality managers who need to check that SS-AS behavior matches the defined functional model and information flows.

Service planners and operators use it to understand how selectable areas are defined, assigned, interrogated, and enforced across home, originating, called-user-home, group-home, and participating SwMIs. Procurement and buyer teams can use it to judge whether a product supports the SS-AS behavior needed in their network topology.

What changed in SIST EN 300 392-11-8 V1.1.1:2003 from the previous edition?

The foreword and history show that the document was converted from ETS 300 392-11-8 to an EN during processing for Vote. The history also shows publication as V1.1.1 in December 2000.

Which standards are used with SIST EN 300 392-11-8 V1.1.1:2003?

• CCITT Recommendation I.130 - Provides the method used for the three-stage characterization of telecommunication services.
• ETSI ETS 300 392-1 - Gives the general TETRA network design framework.
• ETSI EN 300 392-2 - Covers the TETRA Air Interface (AI).
• ETSI EN 300 392-3-2 - Supports interworking at the Inter-System Interface (ISI) for Additional Network Feature Individual Call (ANF-ISIIC).
• ETSI ETS 300 392-3-3 - Supports ISI interworking for Additional Network Feature Group Call (ANF-ISIGC).
• ETSI ETS 300 392-3-5 - Covers ANF-ISIMM, which carries the SS-AS profile exchange used when users migrate or groups attach.
• ETSI EN 300 392-9 - Gives the general requirements for TETRA supplementary services.
• ETSI ETS 300 392-10-8 - Defines the stage 1 description of Area Selection.
• ETSI EN 300 392-12-8 - Gives the stage 3 protocol description for Area Selection.
• ISO/IEC 11574 - Provides the basic call service model and the CC/CCA terminology used in the functional model.

What does the SIST EN 300 392-11-8 V1.1.1:2003 document contain?

The document contains a functional model, detailed information flows, service primitives, worked signaling examples, allocation scenarios, and interworking guidance. It uses figures to show how SS-AS behaves in individual and group calls, including call setup success, call rejection, and call restoration.

The tables give the contents of the key information flows, including what data each flow carries and when a field is optional or conditional. They also show how functional entities can be allocated to MS/LSs and SwMIs, and how SS-AS profile information moves between SwMIs when users migrate or groups attach.

Clause 5.4 provides example sequences for definition, interrogation, and invocation. Clause 7 provides scenario tables for individual calls, group calls, and management cases, which helps implementers map the abstract functional entities to real network equipment. Clause 8 describes how SS-AS interacts with migration, group attachment, and external outgoing calls.

SLOVENSKI STANDARD
01-december-2003
3UL]HPQLVQRSRYQLUDGLR7(75$±*RYRULQSRGDWNL9'±GHO'RSROQLOQH
VWRULWYHVWRSQMH±SRJODYMH,]ELUDREPRþMD$6
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary
services stage 2; Sub-part 8: Area Selection (AS)
Ta slovenski standard je istoveten z: EN 300 392-11-8 Version 1.1.1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)
Terrestrial Trunked Radio (TETRA);
VoiceplusData(V+D);
Part 11: Supplementary services stage 2;
Sub-part 8: Area Selection (AS)

2 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
Reference
DEN/TETRA-03A-11-08
Keywords
TETRA, V+D, data, radio, speech, stage 2,
supplementary service, area select
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: [phone] Fax: [phone]
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2000.
All rights reserved.
ETSI
3 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
Contents
Intellectual Property Rights .5
Foreword.5
1 Scope.6
2 References.6
3 Definitions and abbreviations.7
3.1 Definitions . 7
3.2 Abbreviations. 7
3.2.1 General abbreviations. 7
4 Functional model .8
4.1 Functional model description. 8
4.2 Description of functional entities . 10
4.2.1 Served user functional entity, FE1. 10
4.2.2 Served user current SwMI functional entity, FE21. 10
4.2.3 Area number mapping functional entity, FE221.10
4.2.4 SS-AS operation controlling functional entity, FE222. 10
4.2.5 SS-AS operating functional entity, FE25 . 10
4.2.6 Managed served user/group home SwMI FE, FE20. 11
4.2.7 Authorized user functional entity, FE3. 11
4.3 Relationship of functional model to basic call functional model. 11
5 Information flows .14
5.1 Definition of information flows . 14
5.1.1 ASSIGN . 14
5.1.2 ASSIGN ACK . 14
5.1.3 DEFINE . 15
5.1.4 DEFINE ACK. 15
5.1.5 INTERROGATE . 16
5.1.6 INTERROGATE ACK . 16
5.1.7 INVOKE . 17
5.1.8 INVOKE CONFIRM . 18
5.1.9 INVOKE EXT. 18
5.1.10 NOT DEFINED. 19
5.1.11 NOT SUBSCRIBED. 19
5.1.12 NOT SUPPORTED. 19
5.2 Relationship of information flows to basic call information flows. 20
5.3 Service primitives. 21
5.4 Examples of information flow sequences . 21
5.4.1 Definition . 22
5.4.1.1 Definition with no assignment. 22
5.4.1.2 Definition with assignment . 22
5.4.2 Interrogation . 23
5.4.3 Invocation and operation . 23
5.4.3.1 Invocation for individual call with successful operation. 23
5.4.3.1.1 Successful call establishment. 23
5.4.3.1.2 Call attempt cleared by SS-AS. 25
5.4.3.2 Invocation for group call with successful operation . 27
5.4.3.2.1 Successful call establishment. 27
5.4.3.2.2 Call attempt cleared by SS-AS. 30
5.4.3.3 Operation for call restoration . 31
5.4.3.4 SS-AS invocation failure . 31
5.4.3.4.1 Group call attempt by calling user outside the selected area with SS-AS inhibition for that
user. 31
5.4.3.4.2 Selected area not defined. 32
5.4.3.4.3 SS-AS not supported . 33
ETSI
4 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
5.4.3.4.4 SS-AS not subscribed to. 34
6 FE actions.34
6.1 Functional Entity actions of FE1. 34
6.2 Functional Entity actions of FE20. 34
6.3 Functional Entity actions of FE21. 35
6.4 Functional Entity actions of FE221. 35
6.5 Functional Entity actions of FE222. 35
6.6 Functional Entity actions of FE25. 37
6.7 Functional Entity actions of FE3. 38
7 Allocation of functional entities to physical equipment.38
8 Interworking considerations.39
History .42
ETSI
5 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Project Terrestrial Trunked Radio
(TETRA).
The present document had been submitted to Public Enquiry as ETS 300 392-11-8. During the processing for Vote it
was converted into an EN.
The present document is a multi-pert standard and will consist of the following parts:
Part 1: "General network design";
Part 2: "Air Interface (AI)";
Part 3: "Interworking at the Inter-System Interface (ISI)";
Part 4: "Gateways basic operation";
Part 5: "Peripheral Equipment Interface (PEI)";
Part 6: "Line connected Station (LS)";
Part 7: "Security";
Part 9: "General requirements for supplementary services";
Part 10: "Supplementary services stage 1";
Part 11: "Supplementary services stage 2";
Part 12: "Supplementary services stage 3";
Part 13: "SDL Model of the Air Interface (AI)";
Part 14: "Protocol Implementation Conformance Statement (PICS) proforma specification".
National transposition dates
Date of adoption of this EN: 1 December 2000
Date of latest announcement of this EN (doa): 31 March 2001
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 September 2001
Date of withdrawal of any conflicting National Standard (dow): 30 September 2001
ETSI
6 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
1 Scope
The present document specifies the stage 2 description of the Supplementary Service Area Selection (SS-AS) for the
Terrestrial Trunked Radio (TETRA).
SS-AS enables a user to select an area where a call will be set up.
Man-Machine Interface (MMI) and charging principles are outside of the scope of the present document.
Supplementary service specifications are produced in three stages according to the method defined in
CCITT Recommendation I.130 [1]. The stage 2 description identifies the functional capabilities and the information
flows needed to support the supplementary service as specified in its stage 1 description (see ETS 300 392-10-8 [8]).
The stage 2 description is followed by the stage 3 description, which specifies the protocols at the air interface and at
the various Inter-System Interfaces (ISI) to support the service.
The present document is applicable to TETRA Voice plus Data terminal equipment and networks.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
[1] CCITT Recommendation I.130 (1988): "Method for the characterization of telecommunication
services supported by an ISDN and network capabilities of an ISDN".
[2] ETSI ETS 300 392-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 1:
General network design".
[3] ETSI EN 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air
Interface (AI)".
[4] ETSI EN 300 392-3-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 3:
Interworking at the Inter-System Interface (ISI); Sub-part 2: Additional Network Feature
Individual Call (ANF-ISIIC)".
[5] ETSI ETS 300 392-3-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 3:
Interworking at the Inter-System Interface (ISI); Sub-part 3: Additional Network Feature Group
Call (ANF-ISIGC)".
[6] ETSI ETS 300 392-3-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 3:
Interworking at the Inter-System Interface (ISI); Sub-part 5: Additional Network Feature for
Mobility Management (ANF-ISIMM)".
[7] ETSI EN 300 392-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 9:
General requirements for supplementary services".
[8] ETSI ETS 300 392-10-8: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 10:
Supplementary services stage 1; Sub-part 8: Area selection".
[9] ETSI EN 300 392-12-8: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12:
Supplementary services stage 3; Sub-part 8: Area Selection (AS)".
ETSI
7 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
[10] ISO/IEC 11574: "Information technology; Telecommunications and information exchange
between systems; Private Integrated Services Network; Circuit-mode 64 kbit/s bearer services;
Service description, functional capabilities and information flows".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions of EN 300 392-9 [7] apply with the following
modifications:
authorized user: identified user who is allowed to define areas and/or interrogate the infrastructure about the SS-AS
areas defined for an individual subscriber or for a group
served user: calling party who invokes the supplementary service when setting up a group call or an individual call
served user SwMI: SwMI where the served user is currently registered. In a call (whether an individual or a group
call), the served user SwMI is the originating SwMI
In addition, the following terms and definitions shall apply:
geographical definition: definition of an SS-AS area given by limits on a map. In practice, due to the difficulty to
describe mathematically any area shape, only circles, areas along a line and rectangular areas are specified in
SS-AS protocol (see EN 300 392-12-8 [9])
important user: in a group call, a user considered by the group controlling SwMI as being important. In the case of
SS-AS, this definition applies also to the calling user of a group call (i.e. even if the group controlling SwMI does not
consider that user as being important)
site definition: definition of an SS-AS area given as a list of base stations within one or more SwMIs. Such list may be
implicit, e.g. area defined as a whole home SwMI with no visited SwMI (i.e. no participating SwMI in the case of a
group call, and no other terminating SwMI than such home SwMI in the case of an individual call)
3.2 Abbreviations
3.2.1 General abbreviations
For the purposes of the present document, the following general abbreviations apply:
ANF-ISIMM Additional Network Feature - Inter-System Interface Mobility Management
AS Area Selection
CC Basic Service Call Control functional entity
CCA Basic Service Call Control functional entity agent
NOTE 1: CC and CCA are applied as defined in ISO/IEC 11574 [10].
FE Functional Entity
GTSI Group TETRA Subscriber Identity
ISI Inter-System Interface
ITSI Individual TETRA Subscriber Identity
LS Line Station
MS Mobile Station
SS Supplementary Service
NOTE 2: The abbreviation SS is only used when referring to a specific supplementary service (e.g. SS-AS).
SwMI Switching and Management Infrastructure
ETSI
8 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
4 Functional model
4.1 Functional model description
The functional model shall comprise the following Functional Entities (FEs):
FE1 Served user functional entity;
FE21 Served user current SwMI FE;
FE221 Area number mapping FE;
FE222 SS-AS operation controlling FE;
FE25 SS-AS operating FE;
FE20 Managed served user/group home SwMI FE;
FE3 Authorized user functional entity.
The following relationships shall exist between these FEs:
ra between FE1 and FE21;
rb between FE21 and FE221;
rc between FE221 and FE222;
rd between FE222 and FE25;
re between FE1 and FE221;
rf between FE1 and FE222;
rg between FE3 and FE20.
Figure 1 shows these FEs and relationships for the basic operational part of SS-AS.
rc
FE222
FE221
rf rd
re rb
ra
FE1 FE21 FE25
Figure 1: Functional model for the operational part of SS-AS
NOTE: No functional entity is shown for the called users because the only SS-AS related action for users
participating in the group call is to inform them when they fail to restore their call (after having changed
location) because of SS-AS operation (i.e. they have moved outside the selected area and either they are
not important users for the call or SS-AS operation has not been inhibited for such users). Such
information being delivered to the user call control entity, the corresponding actions are to be considered
as basic call actions and not as SS-AS actions (hence the absence of SS-AS functional entity for the called
users).
ETSI
9 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
Explanation about figure 1
FE25 shall check whether it can establish the call within the selected area requested. It shall be located;
• in the case of an individual call, in the terminating SwMI;
• in the case of a group call, in:
- the group controlling SwMI (for the group members attached to the group in that SwMI or because it can
determine that some participating SwMIs -where group members are attached- are totally outside the selected
area);
- the participating SwMIs partly outside the selected area.
In the case of a group call, both FE221 and FE221 shall be located in the group controlling SwMI when the selected
area is one defined for the group - i.e. per GTSI. FE221 shall be located in the originating SwMI (assuming that the
latter is different from the former), for the determination of the area corresponding to the area number sent by FE1, and
FE222, in the group controlling SwMI for SS-AS operation control, when the selected area is one defined for the calling
user - i.e. per ITSI.
In the case of an individual call, FE221 shall be located in: either
- the originating SwMI (FE221 shall then be co-located with FE21, in which case the relationship rb will
"collapse"); or
- the called user home SwMI.
FE222 shall be located in the called user home SwMI. If the -individual- call is then established by rerouteing, the
protocol for sending the SS-AS information flow over relationship rc actually relays it through the originating SwMI -
but such relaying is a stage 3 description issue and not to be taken into account in the stage 2 description.
Figure 2 shows these FEs and relationships for the management part of SS-AS.
rg
FE3 FE20
(note 1)
r
anf-isimm
(note 2)
ra
FE21 FE1
(note 3)
NOTE 1: All requests issued by the authorized user for an SS-AS managed served user or group are to be
addressed to the home SwMI of this managed served user or group.
This holds even if the calling user is given a partial authorized user capability to define selectable areas
against his ITSI, or place interrogation about such definition.
NOTE 2: The relationship between FE20 and FE21 is an ANF-ISIMM relationship, across which flows the SS-AS
profile exchange.
NOTE 3: The relationship ra is shown on the figure in case the definition is assigned (i.e. downloaded) to the served
user.
Figure 2: Functional model for the management part of SS-AS
ETSI
10 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
4.2 Description of functional entities
4.2.1 Served user functional entity, FE1
FE1 is the functional entity that serves the calling user for the invocation of SS-AS.
In addition, FE1 handles the reception of the area definitions from FE21 and the possible sending of their
acknowledgement to FE21.
4.2.2 Served user current SwMI functional entity, FE21
When it receives an SS-AS invocation from FE1 (at call set-up time), FE21 determines if SS-AS has been activated
(i.e. subscribed) for the group, in the case of a group call, or for the served user, in the case of an individual call.
NOTE: Actually, there is one exception to the checking by FE21 of SS-AS subscription for the group: in the case
where the group is not attached. This is because the corresponding protocol would have slowed down the
establishment of the group call.
In addition in the case of group call, FE21 informs FE22 whether an FE25 collocated with it (see subclause 4.2.4)
would support the inhibition of SS-AS operation for the calling user at the establishment of the call (so that that user can
participate in the group call if he is outside the selected area).
In addition, if instructed by FE20, FE21 downloads the SS-AS definitions (received as part of ANF-ISIMM - see
ETS 300 392-3-5 [6])) and receives the possible corresponding acknowledgements from FE1.
4.2.3 Area number mapping functional entity, FE221
When it receives an SS-AS invocation from FE21, FE221 determines the selected area definition corresponding to the
area number invoked and passes it to FE222. It does not play any further role.
4.2.4 SS-AS operation controlling functional entity, FE222
When it receives an SS-AS invocation from FE221, FE222 determines the selected area definition corresponding to the
area number invoked. It subsequently creates FE25s in the appropriate SwMIs. FE222 created for an individual call is
cleared once that call has been established.
FE222 continues to exist during a group call. It creates FE25s in the new participating SwMIs if necessary for SS-AS
operation (i.e. when only part of the new SwMI is within the selected area). When important users, which were initially
participating in the call, change location during the call, FE222 may allow them to restore the call in inhibiting SS-AS
operation if they have moved outside the selected area.
NOTE 1: Reminder: according to the definition of important user in subclause 3.1, in the present document, the
calling user is defined as being an important user.
NOTE 2: If call restoration of an important user fails, especially if that user is the owner of the group call at that
time, the basic group call procedure will apply.
4.2.5 SS-AS operating functional entity, FE25
When it receives an SS-AS invocation with the selected area definition, from FE222, FE25 ensures that the call is not
established outside that area.
In the case of group call, FE25 can therefore be considered as a distributed functional entity, which bars the
establishment of the call in all cells outside the selected area, except possibly for the calling user if he is outside that
area. FE25 continues to operate during the call in ensuring that the group call is not extended beyond that area after it
has been established.
NOTE 1: The above paragraph means that FE25 will bar the group members outside the selected area who attempt
to join the group call later. It will also bar the operation of the supplementary service Late Entry (SS-LE)
outside the selected area.
ETSI
11 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
FE25 may support the inhibition of SS-AS operation for a group call (to be decided by FE222 for the call):
- at set-up time, for the calling user if he is outside the selected area; and
- during the call, when the calling user or other important users already participating in the call change location in
roaming or migrating outside the selected and FE25 support SS-AS inhibition, i.e. FE25 will then ensure that the
call restoration request from that user is not barred by SS-AS operation (although it takes place outside the
selected area).
NOTE 2: If it does not support the inhibition of SS-AS operation or if FE222 has not requested it, FE25 will ensure:
- that the calling user is not included in the call if he is outside the selected area. FE222 will then clear
that call (see subclause 6.4); or
- that, when any of the so-called important users, including the calling user, changes location to a cell
outside the selected area, the call restoration attempt of that user will fail. See note in subclause 4.2.3
if such user happens to be the owner of the group call at that time.
NOTE 3: Whether or not FE25 supports the inhibition of SS-AS operation, when any other initial participating user
than the important users including the calling user, has roamed or migrated outside the selected area, the
call restoration attempt of that user will fail.
In the case of individual call, FE25 is cleared once that call has been established, i.e. once the call has been established
the connected user may restore it when he changes location in roaming or migrating outside the selected area.
4.2.6 Managed served user/group home SwMI FE, FE20
FE20 receives and processes the optional definition requests received from FE3.
NOTE: When the served user has migrated and is registered in a visited SwMI, the SS-AS definition stored by
FE20 will be passed to FE21 in that SwMI by ANF-ISIMM (see ETS 300 392-3-5 [6]), possibly with the
request to download it to the served user (if the authorized user has requested that such definition be
assigned to the served user).
FE20 also receives and processes the optional interrogation requests received from FE3.
4.2.7 Authorized user functional entity, FE3
FE3 handles the sending the optional definition and/or interrogation requests passed by the authorized user application,
and the reception of the optional definition and/or interrogation responses from FE20, in passing them to the authorized
user application.
4.3 Relationship of functional model to basic call functional
model
Although no formal models have been defined for basic individual call or for basic group call, those models can be
readily derived from the PISN model for basic call, in ISO/IEC 11574 [10].
Being call unrelated the assignment, definition and interrogation procedures are independent of CC or CCA.
FE1 shall be collocated with the calling user CCA.
FE21 shall be collocated with the originating CC. Actually when the calling user invokes SS-AS for a group call in
using an area number defined against that group (which is the basic method for invoking SS-AS for a group call), the
SS-AS subscription function of FE21 shall be handled in the group controlling SwMI if at that time the originating
SwMI has not been attached to the group.
NOTE 1: If the originating SwMI has been attached, it means that it has received the information whether or not
SS-AS has been subscribed for the group (by the ANF-ISIMM group attachment service - see clause 8).
NOTE 2: Formally, FE21 should have been split into two functional entities to cater for the latter case. However it
was judged that such splitting would make the model unnecessarily complex for all other scenarios.
ETSI
12 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
In the case of a group call, FE222 shall be collocated with the transit CC in the group controlling SwMI, when that
SwMI is different from originating SwMI, or the originating CC in the originating SwMI when the originating SwMI
and the group controlling SwMI coincide, and FE221: either
- with the transit CC in the group controlling SwMI, when that SwMI is different from originating SwMI, or the
originating CC in the originating SwMI when the originating SwMI and the group controlling SwMI coincide.
This shall be the general case; or optionally
- with the originating CC in the originating SwMI when that SwMI is different from the group controlling SwMI.
In the case of an individual call, FE222 shall be collocated with the transit CC in the called user home SwMI when that
SwMI is different from the originating SwMI or the originating CC in the originating SwMI when the originating SwMI
and the called user home SwMI coincide, and FE221: either
- with the originating CC in the originating SwMI. This shall be the general case; or optionally
- with the transit CC in the called user home SwMI when that SwMI is different from the originating SwMI.
NOTE 3: When FE221 is collocated with the originating SwMI, the relationship rb becomes internal to that SwMI.
NOTE 4: When FE221 is collocated with the called user home SwMI, if the -individual- call is then established by
rerouteing, the protocol for sending the SS-AS information flow over relationship rd actually relays it
through the originating SwMI. However such relaying is a stage 3 description issue and not to be taken
into account in the stage 2 description.
FE25 shall be collocated:
- in the case of an individual call, with the terminating CC or with the transit CC in the called user home SwMI
when that SwMI is different from the terminating SwMI;
- in the case of a group call for which SS-AS is operated with no SS-AS inhibition for the calling user and other
important users:
- with the originating CC in the originating SwMI if it lies partly outside the selected area;
- with each terminating CCs in the SwMIs where group members are attached and which lie partly outside the
selected area (e.g. in the group controlling SwMI for the participants registered in that SwMI, or in the
participating SwMIs for the other participants);
- with the transit CC in the group controlling SwMI:
- for the originating SwMI if those two SwMIs are different and if the originating SwMI is totally outside
the selected area; and
- for the participating SwMIs totally outside the selected area.
- in the case of a group call for which SS-AS is operated with SS-AS inhibition for the calling user:
- with the same CCs as if SS-AS was operated with no SS-AS inhibition (i.e. originating CC if the originating
SwMI lies partly outside the selected area, terminating CCs in the SwMIs where group members are attached
and which lie partly outside the selected area, and transit CC in the group controlling SwMI when the latter
has determined that the originating SwMI or some participating SwMIs are totally outside the selected area);
- with the new terminating CCs in the new participating SwMIs which lie partly or totally outside the selected
area (for call restoration).
Figure 3 shows an example of the relationship between the models for SS-AS and:
- for the basic group call in the basic case where the definition of the selected area number is given in the group
home SwMI; and
- for the basic individual call in the optional case where the definition of the selected area number is given in the
called user home SwMI.
This example is used as the basis of most of information flow sequences in subclause 5.4.
ETSI
13 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
FE221/
FE222
re/rf rb CC rd
r2 r2
ra
FE21 FE25
FE1
r1 r3
CCA
CCA
CC CC
(note)
NOTE: The CC to which the called user CCA, on the right, is associated coincides with the transit CC shown in
the middle of the figure (with FE221 and FE222 collocated) when the called user is registered in his home
SwMI (whether for an individual call or for a group call).
Figure 3: Relationship between models for SS-AS and basic group call or basic individual call
in the case where FE221 is collocated with the called user/group home SwMI
Figure 4 shows another example of the relationship between the models for SS-AS and:
- for the basic individual call in the basic case where the definition of the selected area number is given in the
originating SwMI; and
- for the basic group call in the optional case where the definition of the selected area number is given in the
originating SwMI.
FE222
CC
rd
rf rc
r2 r2
ra/re
FE21/
FE25
FE1
FE221
r1
r3
CCA CCA
CC CC
(note)
NOTE: The CC the called user CCA, on the right, is associated coincides with the transit CC shown in the middle
of the figure (with FE222 collocated) when the called user is registered in his home SwMI (whether for an
individual call or for a group call).
Figure 4: Relationship between models for SS-AS and basic individual call or basic group call
in the case where FE221 is collocated with the originating SwMI
ETSI
14 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
5 Information flows
5.1 Definition of information flows
In the tables listing the information elements in information flows, the column headed "Type" indicates which of these
elements are Mandatory (M), which are Optional (O) and which are Conditional (C).
5.1.1 ASSIGN
ASSIGN an unconfirmed information flow across relationship ra from FE21 to FE1 which assigns to the SS-AS served
user MS/LS the selectable area definition corresponding to an area number.
NOTE 1: Subclause 5.1.3 provides that every member of a group is a served user to whom the selectable area
definitions for a group may be assigned. No SS-AS assignment for a group will be made to any other
user, not member of that group, although nothing will prevent such user from being SS-AS served user,
when setting up a call for that group (i.e. being the calling user for the group call).
Table 1 lists the elements within the ASSIGN information flow.
Table 1: Contents of ASSIGN
Element Type
Area number M (note 1)
Selectable area definition M (note 2)
O
Acknowledgement requested
NOTE 1: May be repeated.
NOTE 2: Shall be repeated as many times as the element area number.
The element area number shall be the indicator used to invoke SS-AS.
The element selectable area definition shall give the detailed definition corresponding to the preceding area number.
Such definition may be a "site" definition or a geographical definition.
When an acknowledgement is requested from the served user(s), it shall be sent by the ASSIGN ACK information flow
(see subclause 5.1.2), which may then be considered as a response/confirmation information flow corresponding to the
ASSIGN request/indication information flow.
NOTE 2: When the ASSIGN request/indication information flow corresponds to a definition made for an individual
user (see subclause 5.1.3), it will be sent to that user. When the ASSIGN request/indication information
flow corresponds to a definition made for a group (see subclause 5.1.3), it will either be broadcast to all
members of that group or sent individually to each.
5.1.2 ASSIGN ACK
ASSIGN ACK is actually the response/confirmation information flow corresponding to the ASSIGN request/indication
information flow. It is thus across relationship ra from FE1 to FE21. That flow is used to inform FE21 about the
completion of the corresponding assignment request.
NOTE 1: The definition of how a given ASSIGN ACK information flow relates to the corresponding ASSIGN
information flow is outside the scope of the stage 2 description.
Table 2 defines the content of the ASSIGN ACK information flow.
Table 2: Content of ASSIGN ACK
Element Type
Assignment result M
ETSI
15 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
The element assignment result shall indicate whether the assignment requested in the corresponding ASSIGN
request/indication information flow has been successful or not.
NOTE 2: In the case of assignment of area number definition for a group, when the corresponding ASSIGN
information flow broadcast to the group members included an assignment acknowledgement, the
ASSIGN ACK information flow will be sent by each member of the group - except those which did not
receive the ASSIGN information flow.
5.1.3 DEFINE
DEFINE is an unconfirmed information flow across relationship rg from FE3 to FE20, which defines the selectable area
corresponding to a SS-AS area number for individual subscriber(s) or group(s).
NOTE 1: The response/confirmation information flow corresponding to the DEFINE request/indication information
flow is DEFINE ACK (see subclause 5.1.4).
Table 3 lists the elements within the DEFINE information flow.
Table 3: Contents of DEFINE
Element Type
M (note 1)
Defined individual subscriber/group identity
Area number M (note 2)
Selectable area definition M (note 3)
M
Assignment requested
C (note 4)
Acknowledgement requested
NOTE 1: May be repeated.
NOTE 2: May be repeated.
NOTE 3: Shall be repeated as many times as the element area number.
NOTE 4: Such acknowledgement may be requested only together with the assignment of the
selectable area definition(s) (by the element "assignment requested").
The element defined individual subscriber/group identity shall contain the identity of the group or of the individual
subscriber being defined. When the DEFINE request/indication information flow is used with the element defined
individual subscriber/group identity having the value of a group identity, the area number shall apply to calls to this
group. When it is used with the element defined individual subscriber/group identity having the value of an individual
identity, the area number shall apply to individual calls made by the individual user. It may also apply to group calls
made by that user. An AS value defined for an individual user shall only be used when this user is notamember ofthe
called group. The originating SwMI will pass the definition of the user's AS value to the group controlling SwMI. The
group controlling SwMI then determines whether this value will be used.
See subclause 5.1.1 for the meaning of the elements area number and selectable area definition.
The element "assignment requested" shall indicate if the definition(s) of the area number(s) is (are) to be assigned to the
served user(s). If so, the value of the element "assignment requested" shall indicate whether or not such assignment is to
be acknowledged.
If the DEFINE request/indication information flow defines one or more area numbers for a group and requests such
definition to be assigned to the served user(s) (i.e. the value of its element individual subscriber/group identity
corresponds to a group identity, and that of its element assignment requested, to the request of such assignment), every
member of the group shall be a served user.
NOTE 2: Thus the value of the element "assignment requested" indicates whether or not one or more ASSIGN
request/indication information flow will be generated as a result of the DEFINE request/indication
information flow.
5.1.4 DEFINE ACK
DEFINE ACK is actually the response/confirmation information flow corresponding to the DEFINE request/indication
information flow. It is thus across relationship rg from FE20 to FE3. That flow is used to inform FE3 about the
completion of the corresponding definition request.
ETSI
16 ETSI EN 300 392-11-8 V1.1.1 (2000-12)
NOTE: The definition of how a given DEFINE ACK information flow relates to the corresponding DEFINE
information flow is outside the scope of the stage 2 description.
Table 4 lists the elements within the DEFINE ACK information flow.
Table 4: Contents of DEFINE ACK
Element Type
Definition result M (note 1)
Defined individual subscriber/group identity M (note 2)
Area number C (notes 3 and 4)
NOTE 1: There shall be only one definition result even if there are more than one
defined individual/group identity or more than one area number.
NOTE 2: May be repeated.
NOTE 3 Present if the definition result is positive.
NOTE 4: May be repeated.
The element definition result shall indicate if the DEFINE request/indication information flow has been successful or
not for the individual subscriber or group identified by the value of element defined individual subscriber/group
identity. Of course such value shall have to have been used in a previous DEFINE request/indication information flow.
If the definition has been successful, the element area number shall indicate which area number(s) has/have be
...