ETSI EN 300 392-11-14 V1.1.1 (2002-07)
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 14: Late Entry (LE)
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 14: Late Entry (LE)
DEN/TETRA-03001-11-14
Prizemni snopovni radio (TETRA) - Govor in podatki (V+D) - 11. del: Dopolnilne storitve stopnje 2 - 11.-14. del: Poznejši vstop (LE)
General Information
Buy Standard
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 300 392-11-14
01-MXOLM
Prizemni snopovni radio (TETRA) - Govor in podatki (V+D) - 11. del: Dopolnilne
storitve stopnje 2 - 11.-14. del: Poznejši vstop (LE)
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary
services stage 2; Sub-part 14: Late Entry (LE)
Ta slovenski standard je istoveten z: EN 300 392-11-14 (
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST EN 300 392-11-14 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 300 392-11-14 V1.1.1:2003
---------------------- Page: 2 ----------------------
SIST EN 300 392-11-14 V1.1.1:2003
DRAFT
EUROPEAN pr ETS 300 392-11-14
TELECOMMUNICATION September 1996
STANDARD
Source: ETSI TC-RES Reference: DE/RES-06001-11-14
ICS: 33.060, 33.060.50
Key words: TETRA, V+D, LE
Radio Equipment and Systems (RES);
Trans-European Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 11: Supplementary Services (SS) Stage 2;
Part 11-14: Late Entry (LE)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1996. All rights reserved.
---------------------- Page: 3 ----------------------
SIST EN 300 392-11-14 V1.1.1:2003
Page 2
Draft prETS 300 392-11-14: September 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-14 V1.1.1:2003
Page 3
Draft prETS 300 392-11-14: September 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .8
4 Supplementary Service Late Entry (SS-LE) stage 2 specification .8
4.1 Functional model.8
4.1.1 Functional model description.8
4.1.2 Description of FEs.9
4.1.2.1 User B's functional entity, FE1.9
4.1.2.2 SS-LE functional entity, FE2.9
4.1.2.3 Authorized user's functional entity, FE3.9
4.1.2.4 LE functional entity in system 2, FE4.10
4.1.3 Relationship with a basic service .10
4.1.3.1 LE broadcast.10
4.1.3.2 LE acknowledgement .10
4.1.3.3 LE paging.10
4.1.3.4 The relationships with basic service .10
4.2 Information flows.11
4.2.1 Definition of information flows .11
4.2.1.1 Definition.11
4.2.1.1.1 DEFINE request.11
4.2.1.1.2 DEFINE-ACK .11
4.2.1.2 Operation.12
4.2.1.2.1 INFORM1 for LE broadcast .12
4.2.1.2.2 INFORM2 for LE acknowledgement.13
4.2.1.2.3 INFORM2-ACK for LE
acknowledgement.13
4.2.1.2.4 INFORM3 for LE paging .14
4.2.1.2.5 INFORM3-ACK for LE paging.14
4.2.1.3 Routing between different TETRA systems.14
4.2.1.3.1 INFORM4.14
4.2.1.4 Interrogation.15
4.2.1.4.1 INTERROGATE.15
4.2.1.4.2 INTERROGATE-ACK .15
4.2.2 Relationship of information flows to basic call information flows.16
4.2.3 Information flow sequences .16
4.2.3.1 Definition.16
4.2.3.2 Normal definition of LE when FE3 in system 2.17
4.2.3.3 Operation of LE broadcast.17
4.2.3.4 Operation of LE acknowledgement .18
4.2.3.5 Operation of LE paging.19
4.2.3.6 Operation of LE broadcast when user A (calling party) is
in system 2.20
4.2.3.7 Interrogation of SS-LE .20
4.2.3.8 Interrogation of SS-LE when FE3 in system 2.21
4.2.4 FE actions .21
4.2.4.1 FE actions of FE1 .21
4.2.4.2 FE actions of FE2 .21
4.2.4.3 FE actions of FE3 .22
4.2.4.4 FE actions of FE4 .22
4.2.4.5 FE actions of FE5 .22
---------------------- Page: 5 ----------------------
SIST EN 300 392-11-14 V1.1.1:2003
Page 4
Draft prETS 300 392-11-14: September 1996
4.3 Allocation of FEs to physical equipment. 23
4.4 Inter-working considerations . 23
History. 24
---------------------- Page: 6 ----------------------
SIST EN 300 392-11-14 V1.1.1:2003
Page 5
Draft prETS 300 392-11-14: September 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", (DE/RES-06001-7).
Part 8: "Management services", (DE/RES-06001-8).
Part 9: "Performance objectives", (DE/RES-06001-9).
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).
Part 15: "Inter-working - Extended Operations", (DE/RES-06001-15).
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-14 V1.1.1:2003
Page 6
Draft prETS 300 392-11-14: September 1996
Blank page
---------------------- Page: 8 ----------------------
SIST EN 300 392-11-14 V1.1.1:2003
Page 7
Draft prETS 300 392-11-14: September 1996
1 Scope
This European Telecommunication Standard (ETS) defines the stage 2 specifications of the
Supplementary Service Late Entry (SS-LE) for the Trans-European Trunked Radio (TETRA).
The SS-LE allows radio users to be informed of and, if they are concerned, to join an already existing
point-to-multipoint speech call.
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 of the service in the
Switching and Management Infrastructure (SwMI), in the Mobile Station (MS) and in the Line Station (LS).
Stage 2 also describes the information flows between these entities and also the flows sent over the
Inter-System Interface (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 SwMI, MS and LS of the service.
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] prETS 300 392-11-16: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA); Part 11: Supplementary Services (SS) Stage 2;
Part 11-16: Pre-emptive Priority Call (PPC)".
[2] prETS 300 392-12-16: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA), Part 12: Supplementary Services (SS) Stage 3;
Part 12-16: Pre-emptive Priority Call (PPC)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
authorized user: An identified user who is able to define and interrogate the SS-LE parameters.
The definition procedure and principles for authorized user are outside the scope of SS-LE.
forced LE: The user should join the ongoing multipoint call as soon as he receives a late entry indication.
If the user is already engaged in another communication, the user has to join the highest priority call.
LE acknowledgement: Indication sent in LE messages by a SwMI to inform a member who would like to
join the call that he has to inform the SwMI of his entering the call.
LE broadcast: Indication sent by a SwMI to inform members of a multipoint call which are currently not
already involved in this call that they can join directly an existing communication (a channel is already
allocated in this cell).
LE paging: Indication sent by a SwMI to inform members of a multipoint call which are currently not
already involved in this call that they need to ask for a communication channel for that call if they wish to
participate the call (a channel is not yet allocated in this cell).
---------------------- Page: 9 ----------------------
SIST EN 300 392-11-14 V1.1.1:2003
Page 8
Draft prETS 300 392-11-14: September 1996
system 1: A TETRA system in which SS-LE can be defined and invoked. System 1 is the TETRA system
which has same Mobile Network Identity (MNI) as the TETRA group identity to which SS-LE is defined.
system 2: A TETRA system to which SS-LE can be extended and invoked. System 2 is a TETRA system
which has a different MNI as the TETRA group identity to which SS-LE is defined.
user A: Calling party in a call.
user B: In a group call a party that receives the SS-LE indications about an ongoing call.
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
FE Functional Entity
ISI Inter-System Interface
LE Late Entry
SS Supplementary Service
NOTE: The abbreviation SS is only used when referring to a specific supplementary service.
SwMI Switching and Management Infrastructure
(V)GTSI Visiting TETRA Subscriber Group Identity
4 Supplementary Service Late Entry (SS-LE) stage 2 specification
4.1 Functional model
4.1.1 Functional model description
The functional model shall comprise the following Functional Entities (FEs):
- FE1 user B's functional entity;
- FE2 SS-LE functional entity in system 1;
- FE3 authorized user's functional entity;
- FE4 SS-LE functional entity in system 2;
- FE5 user A's (calling party's) functional entity.
The following relationships shall exist between these FEs:
- ra between FE1 and FE2;
- rb between FE2 and FE4 in different TETRA systems;
- rc between FE2 and FE3;
- rd between FE2 and FE5;
- re between FE1 and FE4;
- rf between FE3 and FE4.
Figure 1 shows these FEs and relationships for the operational part, and Figure 2 for the management
part.
---------------------- Page: 10 ----------------------
SIST EN 300 392-11-14 V1.1.1:2003
Page 9
Draft prETS 300 392-11-14: September 1996
SYSTEM 1 SYSTEM 2
ra rb re
FE1 FE2 FE4 FE1
user B SS-LE FE SS-LE FE user B
Figure 1: Functional model for the operational part of SS-LE
SYSTEM 1 SYSTEM 2
rc rb rf
FE3 FE2 FE4 FE3
authorised SS-LE FE SS-LE FE authorised
user user
Figure 2: Functional model for the management part of SS-LE
4.1.2 Description of FEs
4.1.2.1 User B's functional entity, FE1
FE1 shall receive notifications of SS-LE from FE2 when SS-LE is invoked for a call. In case of LE
acknowledgement, FE1 shall send the acknowledgement when it participates in an ongoing call. In case
of LE paging, FE1 shall send the paging response when it aims to participate in an ongoing call. If FE1 is
in system 2 FE1 shall send the messages to FE4.
4.1.2.2 SS-LE functional entity, FE2
At the reception of call invocation request from FE5, FE2 shall determine if the SS-LE is invoked. If so,
FE1 shall determine the applied SS-LE type, the area etc. and shall invoke the SS-LE. FE2 sends the
notifications of SS-LE to FE1s.
FE2 shall receive SS-LE definition requests from FE3s. FE2 shall analyse the requests and if they are
found authorized and correct, FE2 shall make the definitions to the system and shall acknowledge to FE3.
If not, FE2 shall reject the request and send a negative acknowledgement to FE3.
FE2 shall also receive SS-LE interrogation requests from FE3 about availability or state of a SS-LE
service. FE2 shall fetch the response for the interrogation and if FE2 finds the request authorized it shall
send the response to FE3.
If any FE1s or FE3s are in system 2 FE2 shall send and receive the messages from them via FE4. If the
basic service to which SS-LE is defined, extends to another TETRA system (system 2), FE2 shall send a
SS-LE information flow to system 2 to indicate if SS-LE should or should not be invoked in system 2.
4.1.2.3 Authorized user's functional entity, FE3
At the receipt of a request from service user, FE3 shall send SS-LE definition and interrogation requests
to FE2. FE3 may perform local checks for the requests and if it finds them valid, FE3 shall send the
requests to FE2. If FE3 rejects a request, if shall give an indication to the service user. At the reception of
the responses, FE3 shall indicate the result to the service user.
If FE3 is in system 2, it shall send the messages to FE2 via FE4.
---------------------- Page: 11 ----------------------
SIST EN 300 392-11-14 V1.1.1:2003
Page 10
Draft prETS 300 392-11-14: September 1996
4.1.2.4 LE functional entity in system 2, FE4
FE4 shall deliver the different SS-LE related messages between FE2 and FE3. FE4 shall determine and
add the routing address to the messages and deliver the information flows to either FE2 or FE3.
If a basic service extends to system 2, FE4 should receive a SS-LE information flow which indicates if FE2
should or should not invoke SS-LE for the call in system 2. If SS-LE is invoked in system 2 for the call,
FE4 shall determine the SS-LE type for the call in system 2.
When the SS-LE service in invoked in the system 2, FE4 shall request assignment of (V)GTSI for the
group, add (V)GTSI to the SS-LE messages, determine the area where SS-LE is sent and request
allocation of traffic channels for the call.
4.1.3 Relationship with a basic service
In case of definition or interrogation of SS-LE the FEs shall not be collocated with CC or CCA.
4.1.3.1 LE broadcast
FE1 shall be collocated with CCA when FE1 receives the SS-LE indication included in the incoming call
invocation.
FE2 shall be collocated with CC when FE2 invokes the SS-LE to a call.
FE4 shall be collocated with CC, when the SS-LE is activated in system 2 for a call.
4.1.3.2 LE acknowledgement
FE1 shall be collocated with CCA when FE1 receives the SS-LE indication included in the incoming call
invocation.
FE2 shall be collocated with CC when FE2 invokes the SS-LE to a call.
FE4 shall be collocated with CC, when the SS-LE is activated in system 2 for a call.
4.1.3.3 LE paging
FE1 shall be collocated with CCA when FE1 receives the SS-LE indication included in the incoming call
invocation.
FE2 shall be collocated with CC when FE2 invokes the SS-LE to a call. FE2 shall send paging requests,
receive the responses to the requests and request call set-up for the FE1 that has sent the paging
response.
FE4 shall be collocated with CC, when the SS-LE is activated in system 2 for a call.
4.1.3.4 The relationships with basic service
Figure 3 shows the relationship of SS-LE with basic service.
---------------------- Page: 12 ----------------------
SIST EN 300 392-11-14 V1.1.1:2003
Page 11
Draft prETS 300 392-11-14: September 1996
ra rb re
FE1 FE2 FE4 FE1
CCA CC CC CCA
user B SS-LE FE SS-LE FE user B
Figure 3: The relationships with a basic service
4.2 Information flows
4.2.1 Definition of information flows
In the tables listing the elements in information flows, the column headed "Type" indicates which if these
elements are Conditional (C), Optional (O) and Mandatory (M).
4.2.1.1 Definition
Only authorized user (FE3) shall make SS-LE definitions. The definition can be to one group identity or a
list or range of group identities. FE2 shall acknowledge the definition request. FE2 shall save the SS-LE
definitions in SwMI in the system 1 for the defined group identity/identities, if the definition request was
accepted.
The LE type can be defined. The LE type can be defined either as LE paging applied or No LE paging
applied. If LE paging is applied only for cells in which a traffic channel has not been allocated for the call.
Once a traffic channel is allocated, SS-LE type shall be changed to LE Broadcast or LE Acknowledgement
depending on the basic service type. If the LE type is omitted in the definition, it is outside the scope of this
ETS, which LE type shall be applied and the decision can be made e.g. depending on the congestion in
the system.
SS-LE can be defined to be invoked over ISI to extend to several TETRA systems. Or, the SS-LE can be
defined not to extend over ISI.
4.2.1.1.1 DEFINE request
DEFINE shall be an information flow for the relationship rc, rb and rf, and from FE3 to FE2 or from FE3 to
FE4 and then to FE2. The flow shall be used to define SS-LE for one group or a list or range of groups.
Table 1 lists the elements within the DEFINE information flow.
Table 1: Contents of DEFINE
Element Type
Defining authorized user M
Defined group identity/identities M
LE Type O
LE used over ISI O
Basic service type(s) O
Repetition rate O
4.2.1.1.2 DEFINE-ACK
DEFINE-ACK shall be an information flow for the relationship rc, rb and rf, and from FE2 to FE3 or from
FE2 to FE4 and then to FE3. The flow shall be used in order to acknowledge a definition reques
...
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.-14. del: Poznejši vstop (LE)Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 14: Late Entry (LE)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:EN 300 392-11-14 (3SIST EN 300 392-11-14en01-PDM3SIST EN 300 392-11-14SLOVENSKI
STANDARD
SIST EN 300 392-11-14 V1.1.1:2003
DRAFTEUROPEANprETS 300 392-11-14TELECOMMUNICATIONSeptember 1996STANDARDSource: ETSI TC-RESReference: DE/RES-06001-11-14ICS:33.060, 33.060.50Key words:TETRA, V+D, LERadio Equipment and Systems (RES);Trans-European Trunked Radio (TETRA);Voice plus Data (V+D);Part 11: Supplementary Services (SS) Stage 2;Part 11-14: Late Entry (LE)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.SIST EN 300 392-11-14 V1.1.1:2003
Page 2Draft prETS 300 392-11-14: September 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-14 V1.1.1:2003
Page 3Draft prETS 300 392-11-14: September 1996ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.73.1Definitions.73.2Abbreviations.84Supplementary Service Late Entry (SS-LE) stage 2 specification.84.1Functional model.84.1.1Functional model description.84.1.2Description of FEs.94.1.2.1User B's functional entity, FE1.94.1.2.2SS-LE functional entity, FE2.94.1.2.3Authorized user's functional entity, FE3.94.1.2.4LE functional entity in system 2, FE4.104.1.3Relationship with a basic service.104.1.3.1LE broadcast.104.1.3.2LE acknowledgement.104.1.3.3LE paging.104.1.3.4The relationships with basic service.104.2Information flows.114.2.1Definition of information flows.114.2.1.1Definition.114.2.1.1.1DEFINE request.114.2.1.1.2DEFINE-ACK.114.2.1.2Operation.124.2.1.2.1INFORM1 for LE broadcast.124.2.1.2.2INFORM2 for LE acknowledgement.134.2.1.2.3INFORM2-ACK for LEacknowledgement.134.2.1.2.4INFORM3 for LE paging.144.2.1.2.5INFORM3-ACK for LE paging.144.2.1.3Routing between different TETRA systems.144.2.1.3.1INFORM4.144.2.1.4Interrogation.154.2.1.4.1INTERROGATE.154.2.1.4.2INTERROGATE-ACK.154.2.2Relationship of information flows to basic call information flows.164.2.3Information flow sequences.164.2.3.1Definition.164.2.3.2Normal definition of LE when FE3 in system 2.174.2.3.3Operation of LE broadcast.174.2.3.4Operation of LE acknowledgement.184.2.3.5Operation of LE paging.194.2.3.6Operation of LE broadcast when user A (calling party) isin system 2.204.2.3.7Interrogation of SS-LE.204.2.3.8Interrogation of SS-LE when FE3 in system 2.214.2.4FE actions.214.2.4.1FE actions of FE1.214.2.4.2FE actions of FE2.214.2.4.3FE actions of FE3.224.2.4.4FE actions of FE4.224.2.4.5FE actions of FE5.22SIST EN 300 392-11-14 V1.1.1:2003
Page 4Draft prETS 300 392-11-14: September 19964.3Allocation of FEs to physical equipment.234.4Inter-working considerations.23History.24SIST EN 300 392-11-14 V1.1.1:2003
Page 5Draft prETS 300 392-11-14: September 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", (DE/RES-06001-7).Part 8:"Management services", (DE/RES-06001-8).Part 9:"Performance objectives", (DE/RES-06001-9).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).Part 15:"Inter-working - Extended Operations", (DE/RES-06001-15).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-14 V1.1.1:2003
Page 6Draft prETS 300 392-11-14: September 1996Blank pageSIST EN 300 392-11-14 V1.1.1:2003
Page 7Draft prETS 300 392-11-14: September 19961ScopeThis European Telecommunication Standard (ETS) defines the stage 2 specifications of theSupplementary Service Late Entry (SS-LE) for the Trans-European Trunked Radio (TETRA).The SS-LE allows radio users to be informed of and, if they are concerned, to join an already existingpoint-to-multipoint speech call.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 of the service in theSwitching and Management Infrastructure (SwMI), in the Mobile Station (MS) and in the Line Station (LS).Stage 2 also describes the information flows between these entities and also the flows sent over theInter-System Interface (ISI).NOTE:The stage 2 description is followed by the stage 3 description, which specifies theencoding rules for the information flows and process behaviour for the different entitiesin SwMI, MS and LS of the service.2Normative referencesThis 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 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]prETS 300 392-11-16: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA); Part 11: Supplementary Services (SS) Stage 2;Part 11-16: Pre-emptive Priority Call (PPC)".[2]prETS 300 392-12-16: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA), Part 12: Supplementary Services (SS) Stage 3;Part 12-16: Pre-emptive Priority Call (PPC)".3Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply:authorized user: An identified user who is able to define and interrogate the SS-LE parameters.The definition procedure and principles for authorized user are outside the scope of SS-LE.forced LE: The user should join the ongoing multipoint call as soon as he receives a late entry indication.If the user is already engaged in another communication, the user has to join the highest priority call.LE acknowledgement: Indication sent in LE messages by a SwMI to inform a member who would like tojoin the call that he has to inform the SwMI of his entering the call.LE broadcast: Indication sent by a SwMI to inform members of a multipoint call which are currently notalready involved in this call that they can join directly an existing communication (a channel is alreadyallocated in this cell).LE paging: Indication sent by a SwMI to inform members of a multipoint call which are currently notalready involved in this call that they need to ask for a communication channel for that call if they wish toparticipate the call (a channel is not yet allocated in this cell).SIST EN 300 392-11-14 V1.1.1:2003
Page 8Draft prETS 300 392-11-14: September 1996system 1: A TETRA system in which SS-LE can be defined and invoked. System 1 is the TETRA systemwhich has same Mobile Network Identity (MNI) as the TETRA group identity to which SS-LE is defined.system 2: A TETRA system to which SS-LE can be extended and invoked. System 2 is a TETRA systemwhich has a different MNI as the TETRA group identity to which SS-LE is defined.user A: Calling party in a call.user B: In a group call a party that receives the SS-LE indications about an ongoing call.3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:FEFunctional EntityISIInter-System InterfaceLELate EntrySSSupplementary ServiceNOTE:The abbreviation SS is only used when referring to a specific supplementary service.SwMISwitching and Management Infrastructure(V)GTSIVisiting TETRA Subscriber Group Identity4Supplementary Service Late Entry (SS-LE) stage 2 specification4.1Functional model4.1.1Functional model descriptionThe functional model shall comprise the following Functional Entities (FEs):-FE1user B's functional entity;-FE2SS-LE functional entity in system 1;-FE3authorized user's functional entity;-FE4SS-LE functional entity in system 2;-FE5user A's (calling party's) functional entity.The following relationships shall exist between these FEs:-rabetween FE1 and FE2;-rbbetween FE2 and FE4 in different TETRA systems;-rcbetween FE2 and FE3;-rdbetween FE2 and FE5;-rebetween FE1 and FE4;-rfbetween FE3 and FE4.Figure 1 shows these FEs and relationships for the operational part, and Figure 2 for the managementpart.SIST EN 300 392-11-14 V1.1.1:2003
Page 9Draft prETS 300 392-11-14: September 1996SYSTEM 1SYSTEM 2rarbreFE1FE2 FE4FE1user BSS-LE FESS-LE FEuser B
Figure 1: Functional model for the operational part of SS-LESYSTEM 1SYSTEM 2rcrbrfFE3FE2 FE4FE3authorised SS-LE FE SS-LE FEauthorised user user
Figure 2: Functional model for the management part of SS-LE4.1.2Description of FEs4.1.2.1User B's functional entity, FE1FE1 shall receive notifications of SS-LE from FE2 when SS-LE is invoked for a call. In case of LEacknowledgement, FE1 shall send the acknowledgement when it participates in an ongoing call. In caseof LE paging, FE1 shall send the paging response when it aims to participate in an ongoing call. If FE1 isin system 2 FE1 shall send the messages to FE4.4.1.2.2SS-LE functional entity, FE2At the reception of call invocation request from FE5, FE2 shall determine if the SS-LE is invoked. If so,FE1 shall determine the applied SS-LE type, the area etc. and shall invoke the SS-LE. FE2 sends thenotifications of SS-LE to FE1s.FE2 shall receive SS-LE definition requests from FE3s. FE2 shall analyse the requests and if they arefound authorized and correct, FE2 shall make the definitions to the system and shall acknowledge to FE3.If not, FE2 shall reject the request and send a negative acknowledgement to FE3.FE2 shall also receive SS-LE interrogation requests from FE3 about availability or state of a SS-LEservice. FE2 shall fetch the response for the interrogation and if FE2 finds the request authorized it shallsend the response to FE3.If any FE1s or FE3s are in system 2 FE2 shall send and receive the messages from them via FE4. If thebasic service to which SS-LE is defined, extends to another TETRA system (system 2), FE2 shall send aSS-LE information flow to system 2 to indicate if SS-LE should or should not be invoked in system 2.4.1.2.3Authorized user's functional entity, FE3At the receipt of a request from service user, FE3 shall send SS-LE definition and interrogation requeststo FE2. FE3 may perform local checks for the requests and if it finds them valid, FE3 shall send therequests to FE2. If FE3 rejects a request, if shall give an indication to the service user. At the reception ofthe responses, FE3 shall indicate the result to the service user.If FE3 is in system 2, it shall send the messages to FE2 via FE4.SIST EN 300 392-11-14 V1.1.1:2003
Page 10Draft prETS 300 392-11-14: September 19964.1.2.4LE functional entity in system 2, FE4FE4 shall deliver the different SS-LE related messages between FE2 and FE3. FE4 shall determine andadd the routing address to the messages and deliver the information flows to either FE2 or FE3.If a basic service extends to system 2, FE4 should receive a SS-LE information flow which indicates if FE2should or should not invoke SS-LE for the call in system 2. If SS-LE is invoked in system 2 for the call,FE4 shall determine the SS-LE type for the call in system 2.When the SS-LE service in invoked in the system 2, FE4 shall request assignment of (V)GTSI for thegroup, add (V)GTSI to the SS-LE messages, determine the area where SS-LE is sent and requestallocation of traffic channels for the call.4.1.3Relationship with a basic serviceIn case of definition or interrogation of SS-LE the FEs shall not be collocated with CC or CCA.4.1.3.1LE broadcastFE1 shall be collocated with CCA when FE1 receives the SS-LE indication included in the incoming callinvocation.FE2 shall be collocated with CC when FE2 invokes the SS-LE to a call.FE4 shall be collocated with CC, when the SS-LE is activated in
system 2 for a call.4.1.3.2LE acknowledgementFE1 shall be collocated with CCA when FE1 receives the SS-LE indication included in the incoming callinvocation.FE2 shall be collocated with CC when FE2 invokes the SS-LE to a call.FE4 shall be collocated with CC, when the SS-LE is activated in system 2 for a call.4.1.3.3LE pagingFE1 shall be collocated with CCA when FE1 receives the SS-LE indication included in the incoming callinvocation.FE2 shall be collocated with CC when FE2 invokes the SS-LE to a call. FE2 shall send paging requests,receive the responses to the requests and request call set-up for the FE1 that has sent the pagingresponse.FE4 shall be collocated with CC, when the SS-LE is activated in system 2 for a call.4.1.3.4The relationships with basic serviceFigure 3 shows the relationship of SS-LE with basic service.SIST EN 300 392-11-14 V1.1.1:2003
Page 11Draft prETS 300 392-11-14: September 1996rarbreFE1FE2FE4FE1CCACCCCCCAuser BSS-LE FESS-LE FEuser B
Figure 3: The relationships with a basic service4.2Information flows4.2.1Definition of information flowsIn the tables listing the elements in information flows, the column headed "Type" indicates which if theseelements are Conditional (C), Optional (O) and Mandatory (M).4.2.1.1DefinitionOnly authorized user (FE3) shall make SS-LE definitions. The definition can be to one group identity or alist or range of group identities. FE2 shall acknowledge the definition request. FE2 shall save the SS-LEdefinitions in SwMI in the system 1 for the defined group identity/identities, if the definition request wasaccepted.The LE type can be defined. The LE type can be defined either as LE paging applied or No LE pagingapplied. If LE paging is applied only for cells in which a traffic channel has not been allocated for the call.Once a traffic channel is allocated, SS-LE type shall be changed to LE Broadcast or LE Acknowledgementdepending on the basic service type. If the LE type is omitted in the definition, it is outside the scope of thisETS, which LE type shall be applied and the decision can be made e.g. depending on the congestion inthe system.SS-LE can be defined to be invoked over ISI to extend to several TETRA systems. Or, the SS-LE can bedefined not to extend over ISI.4.2.1.1.1DEFINE requestDEFINE shall be an information flow for the relationship rc, rb and rf, and from FE3 to FE2 or from FE3 toFE4 and then to FE2. The flow shall be used to define SS-LE for one group or a list or range of groups.Table 1 lists the elements within the DEFINE information flow.Table 1: Contents of DEFINEElementTypeDefining authorized userMDefined group identity/identitiesMLE TypeOLE used over ISIOBasic service type(s)ORepetition rateO4.2.1.1.2DEFINE-ACKDEFINE-ACK shall be an information flow for the relationship rc, rb and rf, and from FE2 to F
...
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.-14. del: Poznejši vstop (LE)Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 14: Late Entry (LE)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:EN 300 392-11-14 Version 1.1.1SIST EN 300 392-11-14 V1.1.1:2003en01-december-2003SIST EN 300 392-11-14 V1.1.1:2003SLOVENSKI
STANDARD
SIST EN 300 392-11-14 V1.1.1:2003
ETSI EN 300 392-11-14 V1.1.1 (2002-07)European Standard (Telecommunications series) Terrestrial Trunked Radio (TETRA);Voice plus Data (V+D);Part 11: Supplementary services stage 2;Sub-part 14: Late Entry (LE)
SIST EN 300 392-11-14 V1.1.1:2003
ETSI ETSI EN 300 392-11-14 V1.1.1 (2002-07) 2
Reference DEN/TETRA-03001-11-14 Keywords LE, TETRA ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 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://portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editor@etsi.fr Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2002. All rights reserved.
DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTM and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. SIST EN 300 392-11-14 V1.1.1:2003
ETSI ETSI EN 300 392-11-14 V1.1.1 (2002-07) 3
Contents Intellectual Property Rights.4 Foreword.4 1 Scope.6 2 References.6 3 Definitions and abbreviations.7 3.1 Definitions.7 3.2 Abbreviations.7 4 Functional model.7 4.1 Functional model description.7 4.2 FE description.8 4.2.1 User B's functional entity, FE1.8 4.2.2 SS-LE functional entity, FE2.8 4.2.3 Authorized user's functional entity, FE3.9 4.2.4 LE functional entity FE2 in visited SwMI.9 4.3 Relationship with basic services.9 5 Information flows.9 5.1 Definition of information flows.9 5.1.1 Definition.9 5.1.1.1 DEFINE.10 5.1.1.2 DEFINE ACK.10 5.1.2 Operation.10 5.1.2.1 INFORM1 for LE broadcast.11 5.1.2.2 INFORM2 for LE acknowledgement.11 5.1.2.3 INFORM2 ACK for LE acknowledgement.11 5.1.2.4 INFORM3 for LE paging.12 5.1.2.5 INFORM3 ACK for LE paging.12 5.1.2.6 INFORM4.12 5.1.3 Interrogation.13 5.1.3.1 INTERROGATE.13 5.1.3.2 INTERROGATE ACK.13 5.2 Relationship of information flows to basic call information flows.13 5.3 SS-LE service primitives.14 5.4 Information flow sequences.14 5.4.1 General.14 5.4.2 Definition.15 5.4.3 Definition of LE when FE3 in visited SwMI.15 5.4.4 Operation of LE broadcast.16 5.4.5 Operation of LE broadcast when user A (calling party) is in visited SwMI.16 5.4.6 Operation of LE acknowledgement.17 5.4.7 Operation of LE paging.17 5.4.8 Interrogation of SS-LE.18 5.4.9 Interrogation of SS-LE when authorized user is in visited SwMI.19 5.4.10 FE actions.19 5.4.10.1 FE actions of FE1.19 5.4.10.2 FE actions of FE2.19 5.4.10.3 FE actions of FE3.20 5.4.10.4 FE ISI actions of FE2 in visited SwMI.20 6 Allocation of FEs to physical equipment.20 7 Interworking considerations.21 Annex A (informative): Bibliography.22 History.23
SIST EN 300 392-11-14 V1.1.1:2003
ETSI ETSI EN 300 392-11-14 V1.1.1 (2002-07) 4
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://webapp.etsi.org/IPR/home.asp). 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-14. During the processing for Vote it was converted into an EN. The present document is part 11, sub-part 14 of a multi-part deliverable covering Voice plus Data (V+D), as identified below: EN 300 392-1: "General network design"; EN 300 392-2: "Air Interface (AI)"; EN 300 392-3: "Interworking at the Inter-System Interface (ISI)"; ETS 300 392-4: "Gateways basic operation"; EN 300 392-5: "Peripheral Equipment Interface (PEI)"; EN 300 392-7: "Security"; EN 300 392-9: "General requirements for supplementary services"; EN 300 392-10: "Supplementary services stage 1"; EN 300 392-11: "Supplementary services stage 2"; Sub-part 1: "Call Identification (CI)"; Sub-part 2: "Call Report (CR)"; Sub-part 3: "Talking Party Identification (TPI)"; Sub-part 4: "Call Forwarding (CF)"; Sub-part 5: "List Search Call (LSC)"; Sub-part 6: "Call Authorized by Dispatcher (CAD)"; Sub-part 7: "Short Number Addressing (SNA)"; Sub-part 8: "Area Selection (AS)"; Sub-part 9: "Access Priority (AP)"; Sub-part 10: "Priority Call (PC)"; Sub-part 11: "Call Waiting (CW)"; SIST EN 300 392-11-14 V1.1.1:2003
ETSI ETSI EN 300 392-11-14 V1.1.1 (2002-07) 5
Sub-part 12: "Call Hold (CH)"; Sub-part 13: "Call Completion to Busy Subscriber (CCBS)"; Sub-part 14: "Late Entry (LE)"; Sub-part 16: "Pre-emptive Priority Call (PPC)"; Sub-part 17: "Include Call (IC)"; Sub-part 18: "Barring of Outgoing Calls (BOC)"; Sub-part 19: "Barring of Incoming Calls (BIC)"; Sub-part 20: "Discreet Listening (DL)"; Sub-part 21: "Ambience Listening (AL)"; Sub-part 22: "Dynamic Group Number Assignment (DGNA)"; Sub-part 23: "Call Completion on No Reply (CCNR)"; Sub-part 24: "Call ReTention (CRT)"; EN 300 392-12: "Supplementary services stage 3"; ETS 300 392-13: "SDL model of the Air Interface (AI)"; ETS 300 392-14: "Protocol Implementation Conformance Statement (PICS) proforma specification"; TS 100 392-15: "TETRA frequency bands, duplex spacings and channel numbering"; TS 100 392-16: "Network Performance Metrics"; TS 100 392-17: "TETRA V+D and DMO Release 1.1 specifications".
National transposition dates Date of adoption of this EN: 12 July 2002 Date of latest announcement of this EN (doa): 31 October 2002 Date of latest publication of new National Standard or endorsement of this EN (dop/e):
30 April 2003 Date of withdrawal of any conflicting National Standard (dow): 30 April 2003
SIST EN 300 392-11-14 V1.1.1:2003
ETSI ETSI EN 300 392-11-14 V1.1.1 (2002-07) 6
1 Scope The present document defines the stage 2 specifications of the Supplementary Service Late Entry (SS-LE) for the Trans-European Trunked Radio (TETRA). The SS-LE allows radio users to be informed of and, if they are concerned, to join an already existing point-to-multipoint speech or data call.
Man-Machine Interface (MMI) and charging principles are outside the scope of the present document. Stage 2 describes the functional capabilities of the supplementary service introduced in stage 1 description. Stage 2 identifies the functional capabilities for the management of the service in the Switching and Management Infrastructure (SwMI), in the Mobile Station (MS) and in the Line Station (LS). Stage 2 also describes the information flows between these entities and also the flows sent over the Inter-System Interface (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 SwMI, MS and LS of the service. Aspects relating to all supplementary services are detailed in EN 300 392-9 [4]. 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 and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. [1] ETSI ETS 300 392-11-16: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 11: Supplementary services stage 2; Sub-part 16: Pre-emptive Priority Call (PPC)". [2] ETSI ETS 300 392-12-16: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 12: Supplementary services stage 3; Sub-part 16: Pre-emptive Priority Call (PPC)". [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-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 9: General requirements for supplementary services". [5] 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)". SIST EN 300 392-11-14 V1.1.1:2003
ETSI ETSI EN 300 392-11-14 V1.1.1 (2002-07) 7
3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: authorized user: identified user who is able to define and interrogate the SS-LE parameters forced LE: User is forced to join to the indicated call. NOTE: The user should join the ongoing multipoint call as soon as he receives a late entry indication. If the user is already engaged in another communication, the user has to join the highest priority call. LE acknowledgement: indication sent in LE messages by a SwMI to inform a member who would like to join the call that he has to inform the SwMI of his entering the call LE broadcast: indication sent by a SwMI to inform members of a multipoint call which are currently not already involved in this call that they can join directly an existing communication (a channel is already allocated in this cell) LE paging: indication sent by a SwMI to inform members of a multipoint call which are currently not already involved in this call that they need to ask for a communication channel for that call if they wish to participate the call (a channel is not yet allocated in this cell) user A: calling party in a call user B: party that receives the SS-LE indications about an ongoing call server user: party that receives the SS-LE indications about an ongoing call and joins the call NOTE: Also known as user B. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: FE Functional Entity ISI Inter-System Interface LE Late Entry SS Supplementary Service NOTE: The abbreviation SS is only used when referring to a specific supplementary service. SwMI Switching and Management Infrastructure (V)GTSI Visiting TETRA Subscriber Group Identity 4 Functional model 4.1 Functional model description The functional model shall comprise the following Functional Entities (FEs): - FE1 user B's functional entity; - FE2 SS-LE functional entity; - FE3 authorized user's functional entity. SIST EN 300 392-11-14 V1.1.1:2003
ETSI ETSI EN 300 392-11-14 V1.1.1 (2002-07) 8
The following relationships shall exist between these FEs: - ra between FE1 and FE2; - rb between FE2s in different TETRA SwMIs; - rc between FE2 and FE3. Figure 1 shows these FEs and relationships for the operational part, and figure 2 for the management part. Refer to EN 300 392-9 [4] for further details on FE2 division into sub-entities. Home SwMIVisited SwMIrarbraFE1FE2 FE2FE1User BSS-LE FESS-LE FEUser B
Figure 1: Functional model for the operational part of SS-LE Home SwMIVisited SwMIrcrbrcFE3FE2 FE2FE3Authorised userSS-LE FEAuthorised user
Figure 2: Functional model for the management part of SS-LE 4.2 FE description 4.2.1 User B's functional entity, FE1 FE1 shall receive notifications of SS-LE from FE2 when SS-LE is invoked for a call. In case of LE acknowledgement, FE1 shall send the acknowledgement when it participates in an ongoing call. In case of LE paging, FE1 shall send the paging response when it aims to participate in an ongoing call. If FE1 is in visited SwMI FE1 shall send the messages to FE2 in visited SwMI. 4.2.2 SS-LE functional entity, FE2 At the reception of call invocation request from a calling user A, FE2 shall determine if the SS-LE is invoked. If so, FE1 shall determine the applied SS-LE type and shall start operation of the SS-LE. During operation FE2 shall send the notifications of SS-LE to FE1s. FE2 shall receive SS-LE definition requests from FE3s. FE2 shall analyse the requests and if they are found authorized and correct, FE2 shall make the definitions to the system and shall acknowledge to FE3. If not, FE2 shall reject the request and send a negative acknowledgement to FE3. FE2 shall also receive SS-LE interrogation requests from FE3 about availability or state of a SS-LE service. FE2 shall fetch the response for the interrogation and if FE2 finds the request authorized it shall send the response to FE3. If the basic service to which SS-LE is defined, extends to another TETRA system (visited SwMI), FE2 shall send a SS-LE information flow to visited SwMI FE2 to indicate if SS-LE should or should not be invoked in visited SwMI. SIST EN 300 392-11-14 V1.1.1:2003
ETSI ETSI EN 300 392-11-14 V1.1.1 (2002-07) 9
4.2.3 Authorized user's functional entity, FE3 At the receipt of a request from service user, FE3 shall send SS-LE definition and interrogation requests to FE2. At the reception of the responses, FE3 shall indicate the result to the service user. 4.2.4 LE functional entity FE2 in visited SwMI Refer EN 300 392-9 [4] for message routing services in a visited SwMI. If a basic service extends to visited SwMI, FE2 should receive a SS-LE information flow which indicates if it should or should not invoke SS-LE for the call in visited SwMI. If SS-LE is invoked in visited SwMI for the call, the visited SwMI FE2 shall determine the SS-LE type for the call in visited SwMI. When the SS-LE type is acknowledgement, then the visited SwMI FE 2 shall pass acknowledgement from FE1 to the home SwMI FE2. The group number shall be known in the visited SwMI either by migration or group linking, refer ETS 300 392-3-5 [5], when the SS-LE service in invoked in the visited SwMI, FE2.
4.3 Relationship with basic services Figure 3 shows the relationship of SS-LE with basic service. Home SwMIVisited SwMIrarbraFE1FE2FE2FE1CCACCCCCCAuser BSS-LE FESS-LE FEuser B
Figure 3: The relationships with a basic service 5 Information flows 5.1 Definition of information flows In the tables listing the elements in information flows, the column headed "Type" indicates which if these elements are Conditional (C), Optional (O) and Mandatory (M). 5.1.1 Definition Only authorized user (FE3) shall make SS-LE definitions. The definition can be to one group identity or a list or range of group identities. FE2 shall acknowledge the definition request. FE2 shall save the SS-LE definitions in the home SwMI for the defined group identity/identities, if the definition request was accepted.
The authorized user may define the LE type to be can be defined. If the LE type is omitted in the definition, it is outside the scope of the present document, which LE type shall be applied and the decision can be made e.g. depending on the congestion in the system. SS-LE can be defined to be invoked over ISI to extend to several TETRA systems or the SS-LE can be defined not to extend over ISI.
SIST EN 300 392-11-14 V1.1.1:2003
ETSI ETSI EN 300 392-11-14 V1.1.1 (2002-07) 10 5.1.1.1 DEFINE DEFINE shall be an information flow from FE3 to FE2 for the relationship rc and rb. The flow shall be used to define SS-LE for one group and may be used to define SS-LE for a list or range of groups. Table 1 lists the elements within the DEFINE information flow. Table 1: Contents of DEFINE
Element
Type Defined group identity/identities
M LE Type
O LE used over ISI
O Basic service type(s) O Repetition rate O
5.1.1.2 DEFINE ACK DEFINE ACK shall be an information flow from FE2 to FE3 for the relationship rc and rb. The flow shall be used in order to acknowledge a definition request made for one group or a list or range of groups. Table 2 lists the elements within the DEFINE ACK information flow. Table 2: Contents of DEFINE ACK Element
Type Defined group identity/identities
M Result for definition M
5.1.2 Operation A SwMI may be four different SS-LE types. These four types are LE broadcast, LE acknowledgement, LE paging and forced LE and they have the following characteristics: LE broadcast shall be used for unacknowledged group calls and it may be used for acknowledged group calls. It shall be used to inform users about an ongoing group call. The users may join the call immediately after the reception of LE broadcast information flow. If the user joins the call, it shall move to the traffic channel, if any allocated at that time. LE acknowledgement shall be used for acknowledged group calls. It shall be used to inform users about an ongoing group call and to request an acknowledgement from a user that joins the call. The users may join the call immediately after the reception of LE acknowledgement information flow. If the user joins the call, it shall move to the allocated traffic channel, if any, and it shall send the acknowledgement after moving to the traffic channel. If the traffic channel is not at that moment allocated for the indicated call, the user shall send the acknowledgement on the control channel.
LE paging shall be used to inform users about an ongoing group call. LE paging should be used when the traffic channel is not yet allocated for the call in a cell. So, LE paging should be used to request a paging response from users that wish to join the call, so that the SwMI can allocate the traffic channels after at least one user has indicated the need. FE2 shall start LE paging by sending the paging indication, to which FE1 shall send a response, if it wishes to join the call. When FE2 receives the paging response from FE1, FE2 shall send LE broadcast information flow to FE1. Or, if the applied LE type shall be LE acknowledgement, FE2 shall send LE acknowledgement information flow to FE1. The LE broadcast/LE acknowledgement information flow shall be sent in order to allow FE1 to participate the call. The paging response is considered also as an acknowledgement and the requesting FE1 need not response to the LE acknowledgement information flow to FE1 after sending the PE paging response. Forced LE may be used to force the user to join an ongoing multipoint call even if the user is engaged to another (lower priority) call. Forced LE is implemented by using the pre-emptive values of "Call priority" element within basic service information flow as described in ETS 300 392-11-16 [1] and ETS 300 392-12-16 [2]. If a call for which SS-LE has been defined extends to visited SwMI, FE2 in home SwMI shall indicate to FE2 in visited SwMI whether SS-LE should or should not be applied in visited SwMI. FE2 in visited SwMI should invoke the LE Broadcast or LE Acknowledgement depending on the call type. Whether FE2 in visited SwMI applies LE Paging first is up to visited SwMI and is outside the scope of the present document. SIST EN 300 392-11-14 V1.1.1:2003
ETSI ETSI EN 300 392-11-14 V1.1.1 (2002-07) 11 5.1.2.1 INFORM1 for LE broadcast INFORM1 shall be an information flow from FE2 to FE1 for LE broadcast over the relationship ra and the flow shall be sent by FE2 in visited SwMI if the user B is in visited SwMI. The flow shall inform the user B about an ongoing group call.
INFORM1 shall be used in case of LE broadcast; INFORM1 shall also be used when a user has responded to LE paging and when FE2 has changed the LE type to LE broadcast and FE2 informs FE1 about the allocated traffic channel and thus FE2 shall allow FE1 to participate the call. Table 3 lists the elements within the INFORM1 information flow. Table 3: Contents of INFORM1
Element
Type LE broadcast indication
M
5.1.2.2 INFORM2 for LE acknowledgement INFORM2 shall be an information flow and from FE2 to FE1 for LE acknowledgement over the relationship ra. The flow shall be sent from FE2 in visited SwMI to FE1 if the user B is in visited SwMI. It shall inform the user B about an ongoing group call and request an acknowledgement response, if the user B decides to join the call.
INFORM2 shall be used in case of LE acknowledgement; INFORM2 shall also be used when a user has responded to LE paging and when FE2 has consequently changed the LE type to LE acknowledgement and FE2 informs FE1 about the allocated traffic channel and thus FE2 invites FE1 to participate the call. NOTE: If LE type is changed from LE paging to LE acknowledgement, the traffic channel should be given in INFORM2 information flow. Table 4 lists the elements within the INFORM2 information flow. Table 4: Contents of INFORM2 Element
Type LE acknowledgement indication
M
5.1.2.3 INFORM2 ACK for LE acknowledgement INFORM2 ACK shall be an information flow from FE1 to FE2 for LE acknowledgement over the relationships ra and rb. The flow shall be sent from FE1 to FE2 via FE2 in visited SwMI if the user B is in visited SwMI. The flow shall inform the system about a user B that participates the call. If a user does not participate the call, the user shall not send LE acknowledgement message.
FE1 should only send one LE acknowledgement response per one call (one call item).
FE1 shall send the acknowledgement in INFORM2 information flow.
Table 5 lists the elements within the INFORM2 ACK information flow. Table 5: Contents of INFORM2 ACK Element
Type Call identifier M
SIST EN 300 392-11-14 V1.1.1:2003
ETSI ETSI EN 300 392-11-14 V1.1.1 (2002-07) 12 5.1.2.4 INFORM3 for LE paging INFORM3 shall be an information flow from FE2 to FE1 for LE paging over the relationship ra. The flow shall be sent from FE2 in visited SwMI to FE1 if the user B is in visited SwMI. The flow shall inform the user B about a group call and request a response, if the user B wishes to participate the call. As LE paging is used when the traffic channel has not been allocated for the call in the cell, there shall be no indication of an allocated traffic channel in INFORM3.
Table 6 lists the elements within the INFORM3 information flow. Table 6: Contents of INFORM3 Element
Type LE paging indication
M
5.1.2.5 INFORM3 ACK for LE paging INFORM3 ACK shall be an i
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.