«Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 10: Priority Call (PC) 2 Final draft ETSI ...»
ETSI EN 300 392-11-10 V1.1.1 (2001-03)
European Standard (Telecommunications series)
Terrestrial Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 11: Supplementary services stage 2;
Sub-part 10: Priority Call (PC)
2 Final draft ETSI EN 300 392-11-10 V1.1.1 (2001-03)
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://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
email@example.com 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 2001.
All rights reserved.
Contents Intellectual Property Rights
3 Definitions and abbreviations
4 Functional model
4.1 Functional model description
4.2 Description of functional entities
4.2.1 User A's functional entity, FE1
4.2.2 SS-PC functional entity in the individual or group home SwMI, FE21
4.2.3 SS-PC FE in the controlling SwMI, FE21
4.2.4 SS-PC FE in called user visited SwMI or participating SwMI, FE25
4.2.5 Authorized user's FE, FE3
4.2.6 User B's (called party) FE, FE5
4.3 Relationship of functional model to basic call functional model
5 Information flows
5.1 Definition of information flows
5.1.4 Operation and invocation
5.1.5 Information flows between different TETRA systems
5.2 Relationship of SS-PC information flows to other information flows
5.3 Service primitives
5.4 Information flow sequences
188.8.131.52 Definition of SS-PC when definition is sent to user A
184.108.40.206 Definition when the authorized user is in a visited system
220.127.116.11 Definition when user A is in a visited system
5.4.5 Functional entity actions
18.104.22.168 Functional entity actions of FE1
22.214.171.124 Functional entity actions of FE21
126.96.36.199 Functional entity actions of FE3
188.8.131.52 ISI Functional entity actions of FE25
5.4.6 Operation for call within one TETRA system
5.4.7 Operation for call initiated over Inter-System Interface (ISI)
ETSI 4 Final draft ETSI EN 300 392-11-10 V1.1.1 (2001-03) 5.4.8 Functional entity actions
184.108.40.206 Functional entity actions of FE1
220.127.116.11 Functional entity actions of FE21
18.104.22.168 Functional entity actions of FE25
22.214.171.124 Functional entity actions of FE5
6 Allocation of FEs to physical equipment
7 Inter-working considerations
7.1 Management and operation
ETSI 5 Final draft ETSI EN 300 392-11-10 V1.1.1 (2001-03) 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), and is now submitted for the Vote phase of the ETSI standards Two-step Approval Procedure.
The present document had been submitted to Public Enquiry as ETS 300 392-11-10. During the processing for Vote, it was converted into an EN.
The present document is part 11 of a multi-part deliverable covering Voice plus Data (V+D), as identified below:
Part 14: "Protocol Implementation Conformance Statement (PICS) proforma specification;
TS 100 392-15: "TETRA frequency bands, duplex spacings and channel numbering".
1 Scope The present document defines the stage 2 specifications of the Supplementary Service Priority Call (SS-PC) for the Terrestrial Trunked RAdio (TETRA).
The SS-PC is defined to enable a user to have preferential access to the network resources in a TETRA system in times of congestion. The SS-PC applies for the basic services: circuit mode calls (speech or data). The SS-PC specifies the definition, activation, deactivation and interrogation for the usage of low and high call priorities in the TETRA system.
The SS-PC operations are defined for Switching and Management Infrastructure (SwMI), for the Mobile Station (MS) and for the Line Station (LS). SS-PC is defined for subscribers of one TETRA system, but the subscribers may be located in several TETRA systems and the information flows may be delivered over the Inter System Interface (ISI).
SS-PC may also be invoked for basic services within one TETRA system or for basic services that extend over ISI to several TETRA systems.
The pre-emptive priorities, Man-Machine Interface (MMI) and charging principles are outside of 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 and operation of the service in the SwMI, in the MS and in the LS. Stage 2 describes also the information flows exchanged between these entities and the flows sent over the ISI.
NOTE: The stage 2 description is followed by the stage 3 description, which specifies the encoding rules for the information flows and process behaviour for the different entities in the SwMI, the MS and LS.
Aspects relating to all supplementary services are detailed in ETS 300 392-9 .
2 ReferencesThe 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.
 ISO/IEC 11574 (2000): "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".
For the purposes of the present document, the following terms and definitions apply:
authorized user: user who is authorized to define, activate, deactivate and interrogate the SS-PC call controlling SwMI: in an individual call the call originating SwMI and in a group call the home SwMI of the group priority level: pre-agreed value allocated to each mobile ITSI or GTSI on a per call basis It is used to determine priority access to network resources in the event of network congestion.
user A: calling party, the party that invokes or generates invocation of SS-PC user B: called party in a call for which SS-PC is operated 3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
4.1 Functional model description The functional model describes the functional characteristics of the Functional Entities (FEs) involved in the management and operation of SS-PC.
The functional model shall comprise the following FEs:
• FE21 SS-PC FE in home SwMI or controlling SwMI;
NOTE 1: During definition, activation, deactivation and interrogation request, FE21 may either be user A's home SwMI or a group home SwMI.
NOTE 2: Called party in a call in which SS-PC is operated.
• FE25 SS-PC FE in user B's SwMI;
CC Call Control FE in SwMI.
CCA Call Control Agent FE in MS/LS.
The following relationships shall exist between these FEs:
4.2 Description of functional entities 4.2.1 User A's functional entity, FE1
The functional tasks of FE1 for definition and interrogation shall be the following:
- as an option, the MS/LS may support reception of SS-PC definition from FE21. Upon acceptance, FE1 shall pass the SS-PC definition request, to the user application and acknowledge the SS-PC definition, if FE21 has requested this;
- as an option, the MS/LS may supports SS-PC interrogation, FE1 shall pass the SS-PC interrogation request to FE21, when the user application issues it. Upon reception of the interrogation response from FE21, FE1 shall pass it to the user application.
The functional tasks for operation of FE1 for a priority individual or group call request shall be as follows:
- upon reception of the SS-PC invocation from the user application within a call set-up, FE1 shall send the SS-PC invocation to the SwMI (FE21) with the call set-up;
- upon reception of a SS-PC confirmation from FE21, FE1 shall pass the SS-PC confirmation to the user application;
- when migrated into a visited system the user application shall use "Priority not defined" in the call setup until a definition is provided e.g. by default or downloaded.
NOTE: It is outside of the present document how default values for the home system are allocated.
4.2.2 SS-PC functional entity in the individual or group home SwMI, FE21
The functional tasks of FE21 for definition, activation, deactivation and interrogation shall be the following:
- as an option, FE21 supports SS-PC definition, FE21 shall verify these request when received from FE3 and if found valid, save this information and acknowledge it to FE3;
- as an option, FE21 supports SS-PC activation or deactivation, FE21 shall verify these request when received from FE3 and if found valid, save this information and acknowledge it to FE3;
- as an option, if FE3 requested downloading of SS-PC definition to FE1(s), FE21 shall then send the corresponding requests to the concerned FE1s and may receive their acknowledgements;
- as an option, at the reception of an SS-PC interrogation request from either FE3 or FE1, FE21 should verify the request and send the response to FE3 or FE1. If FE21 does not support interrogation, an error indication shall be sent in response to the requesting entity.
4.2.3 SS-PC FE in the controlling SwMI, FE21
The functional tasks for operation of FE21 for a priority individual or group call shall be as follows:
- when FE21 receives a call set-up request with the SS-PC invocation, FE21 shall verify the received priority and change it, if needed;
- FE21 shall send the SS-PC call set-up, with its priority value to the called party/parties (FE5);
- if the SS-PC call attempt has been successful, FE21 should send the SS-PC priority to the calling party.
4.2.4 SS-PC FE in called user visited SwMI or participating SwMI, FE25 The are no functional tasks of FE25 for definition, activation, deactivation and interrogation.
NOTE: If authorised user (FE3) is migrated to a visited SwMI and makes a definition or interrogation request that applies to a subscriber identity belonging to another system, FE25 shall forward the request to FE21.
When FE25 receives a response to the request from FE21, it shall send the response to FE3, refer to ETS 300 392-9  for further details.
The functional tasks for operation of FE25 shall exist for both individual and group calls. These tasks shall then be the
- when FE25 receives a call set-up indication from FE21 with the SS-PC invocation, FE25 shall not change the received priority value. However, it may apply a different internal priority value for allocating its own resources for this call. FE25 shall send the SS-PC call set-up, with the priority value received from FE21, to the called party/parties.