SIST EN 300 392-12-10 V1.2.1:2006
(Main)Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary services stage 3; Sub-part 10: Priority Call (PC)
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary services stage 3; Sub-part 10: Priority Call (PC)
The present document defines the stage 3 specifications of the Supplementary Service Priority Call (SS-PC) for the Terrestrial Trunked RAdio (TETRA). The SS-PC enables a user to have preferential access to the network resources in the 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 operations are defined for the Switching and Management Infrastructure (SwMI), for the Mobile Station (MS) and for the Line Station (LS). SS-PC can be defined to subscribers of one TETRA system, but the subscribers can be located in several TETRA systems and the information flows can be delivered over the Inter System Interface (ISI). SS-PC can 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 are outside of the scope of the present document.
Man-Machine Interface (MMI) and Charging principles are outside the scope of the present document.
Supplementary Service stage 3 specification is preceded by the stage 1 and the stage 2 specifications of the service. Stage 1 describes the functional capabilities from the user's point of view. Stage 2 defines the functional behaviour in terms of Functional Entities (FEs) and information flows. Stage 3 gives a precise description of the Supplementary Service from the implementation point of view. It defines the protocol for the service and the encoding rules for the information flows. It defines the processes for the functional entities and their behaviour. The described protocols and behaviour apply to the SwMI, for the MS and for the LS and can be applied over the ISI between TETRA systems. Aspects relating to all supplementary services are detailed in EN 300 392-9 [2].
Prizemni snopovni radio (TETRA) – Govor in podatki (V+D) – 12. del: Dopolnilne storitve stopnje 3 – 10. poddel: Prednostni klic (PC)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-april-2006
Prizemni snopovni radio (TETRA) – Govor in podatki (V+D) – 12. del: Dopolnilne
storitve stopnje 3 – 10. poddel: Prednostni klic (PC)
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary
services stage 3; Sub-part 10: Priority Call (PC)
Ta slovenski standard je istoveten z: EN 300 392-12-10 Version 1.2.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);
Voice plus Data (V+D);
Part 12: Supplementary services stage 3;
Sub-part 10: Priority Call (PC)
2 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
Reference
REN/TETRA-03122
Keywords
radio, 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.org
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 2004.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.7
2 References.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 SS-PC stage 3 specification.9
4.1 General.9
4.2 SS-PC services offered over the TNSS-SAP.9
4.2.1 DEFINE request.10
4.2.2 DEFINE indication.10
4.2.3 ASSIGN indication.11
4.2.4 ASSIGN response.11
4.2.5 INTERROGATE request.11
4.2.6 INTERROGATE indication.12
4.3 SS-PC services offered over the TNCC-SAP.12
4.3.1 PRIORITY1 request - SS-PC invocation.12
4.3.2 PRIORITY2 confirm/indication - SS-PC operation .12
4.4 Void.13
4.5 Parameter descriptions.13
5 SS-PC protocol description .14
5.1 General.14
5.2 SS-PC protocol states .14
5.2.1 Protocol states of FE1 .15
5.2.2 Protocol states of CCA to which FE1 is collocated .15
5.2.2.1 State IDLE.15
5.2.2.2 MO_CALL_SETUP.15
5.2.3 Protocol states of FE21.15
5.2.3.1 State IDLE.15
5.2.4 Protocol states of CC to which FE21 is collocated.16
5.2.4.1 State ANY-STATE.16
5.2.4.2 State SETUP-STARTED.16
5.2.5 Protocol states of FE3 .16
5.2.6 Protocol states of visited SwMI FE25.16
5.2.7 Protocol states of CC to which FE25 is collocated.17
5.2.7.1 State ANY-STATE.17
5.2.7.2 State SETUP-STARTED.17
5.2.8 Protocol states of CCA to which FE5 is collocated .17
5.2.8.1 ANY STATE.17
5.3 SS-PC Signalling Procedures.17
5.3.1 Procedures for FE1 .17
5.3.2 Procedures for FE21 .18
5.3.2.1 Definition in FE21 .18
5.3.2.2 Distribution in FE21.18
5.3.2.3 Interrogation in FE21 .18
5.3.3 Procedures for CC to which FE21 is collocated .19
5.3.3.1 Verification of priority in CC to which FE21 is collocated .19
5.3.4 Procedures for FE3 .19
5.3.4.1 Verification in FE3.19
5.3.5 Procedures for visited SwMI FE25.20
5.4 PDU Descriptions.20
5.4.1 ASSIGN PDU.20
ETSI
4 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
5.4.2 ASSIGN ACK PDU.21
5.4.3 DEFINE.21
5.4.4 DEFINE-ACK.22
5.4.5 INTERROGATE.22
5.4.6 INTERROGATE-ACK.23
5.4.7 Priority 1 and Priority 2 .23
5.4.7.1 D-CONNECT PDU.23
5.4.7.2 D-SETUP.23
5.4.7.3 U-SETUP.23
5.4.8 Void.23
5.5 Information element coding .23
5.5.1 Basic Service.24
5.5.2 Call priority.24
5.5.3 High priority value.24
5.5.4 Low priority value .25
5.5.5 Number of SS-PC definitions .25
5.5.6 Range type.25
5.5.7 Result for definition.25
5.5.8 Result for interrogation.26
5.5.9 SS-PC assignment.26
5.5.10 SS-PC definition.26
5.5.11 SS-PC PDU type.27
5.5.12 Subscriber extension present.27
5.5.13 Subscriber identity.27
6 SS-PC FE behaviour.28
6.1 Behaviour of FE1 (SS entity of user A) .29
6.1.1 Service interaction for FE1 .29
6.1.2 Process description for FE1 .30
6.2 Behaviour of CCA to which FE1 is collocated .31
6.2.1 Service interaction for CCA to which FE1 is collocated .31
6.2.2 Process description for CCA to which FE1 is collocated .32
6.3 Behaviour of FE21.33
6.3.1 Service interaction for FE21 .33
6.3.2 Process description for FE21 .33
6.4 Behaviour of CC to which FE21 is collocated .36
6.4.1 Service interaction for CC to which FE21 is collocated .36
6.4.2 Process description for CC to which FE21 is collocated .37
6.5 Behaviour of FE3 (SS entity of authorized user).38
6.5.1 Service interaction for FE3 .38
6.5.2 Process description for FE3 .39
6.6 Behaviour of visited SwMI FE25.40
6.6.1 Service interaction for FE25 .40
6.6.2 Process description for visited SwMI FE25.41
6.7 Behaviour of CCA to which FE5 is collocated .42
6.7.1 Service interaction for CCA to which FE5 is collocated .42
6.7.2 Process description for CCA to which FE5 is collocated .43
6.8 Inter-working considerations.43
Annex A (informative): Mapping of SS-PC priorities received from the user application to
priorities in basic service PDUs (for MS/LS) .44
A.1 Mapping of SS-PC priorities for circuit mode speech and data .44
Annex B (informative): Change Requests .45
History .46
ETSI
5 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
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 is part 12 sub-part 10 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";
EN 300 392-12: "Supplementary services stage 3";
EN 300 392-12-1: "Call Identification (CI)";
ETS 300 392-12-2: "Call Report (CR)";
EN 300 392-12-3: "Talking Party Identification (TPI)";
EN 300 392-12-4: "Call Forwarding (CF)";
ETS 300 392-12-5: "List Search Call (LSC)";
EN 300 392-12-6: "Call Authorized by Dispatcher (CAD)";
ETS 300 392-12-7: "Short Number Addressing (SNA)";
EN 300 392-12-8: "Area Selection (AS)";
ETS 300 392-12-9: "Access Priority (AP)";
EN 300 392-12-10: "Priority Call (PC)";
ETS 300 392-12-11: "Call Waiting (CW)";
EN 300 392-12-12: "Call Hold (HOLD)";
ETSI
6 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
ETS 300 392-12-13: "Call Completion to Busy Subscriber (CCBS)";
EN 300 392-12-14: "Late Entry (LE)";
ETS 300 392-12-16: "Pre-emptive Priority Call (PPC)";
EN 300 392-12-17: "Include Call (IC)";
EN 300 392-12-18: "Barring of Outgoing Calls (BOC)";
EN 300 392-12-19: "Barring of Incoming Calls (BIC)";
ETS 300 392-12-20: "Discreet Listening (DL)";
EN 300 392-12-21: "Ambience Listening (AL)";
EN 300 392-12-22: "Dynamic Group Number Assignment (DGNA)";
ETS 300 392-12-23: "Call Completion on No Reply (CCNR)";
ETS 300 392-12-24: "Call Retention (CRT)";
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: 6 February 2004
Date of latest announcement of this EN (doa): 31 May 2004
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 November 2004
Date of withdrawal of any conflicting National Standard (dow): 30 November 2004
ETSI
7 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
1 Scope
The present document defines the stage 3 specifications of the Supplementary Service Priority Call (SS-PC) for the
Terrestrial Trunked RAdio (TETRA).
The SS-PC enables a user to have preferential access to the network resources in the 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 operations are defined for the Switching and Management Infrastructure (SwMI), for the Mobile Station (MS) and
for the Line Station (LS). SS-PC can be defined to subscribers of one TETRA system, but the subscribers can be located
in several TETRA systems and the information flows can be delivered over the Inter System Interface (ISI). SS-PC can
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 are outside of the scope of the present document.
Man-Machine Interface (MMI) and Charging principles are outside the scope of the present document.
Supplementary Service stage 3 specification is preceded by the stage 1 and the stage 2 specifications of the service.
Stage 1 describes the functional capabilities from the user's point of view. Stage 2 defines the functional behaviour in
terms of Functional Entities (FEs) and information flows. Stage 3 gives a precise description of the Supplementary
Service from the implementation point of view. It defines the protocol for the service and the encoding rules for the
information flows. It defines the processes for the functional entities and their behaviour. The described protocols and
behaviour apply to the SwMI, for the MS and for the LS and can be applied over the ISI between TETRA systems.
Aspects relating to all supplementary services are detailed in EN 300 392-9 [2].
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.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
[1] ETSI EN 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air
Interface (AI)".
[2] ETSI EN 300 392-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 9: General requirements for supplementary services".
[3] ETSI EN 300 392-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 1: General network design".
[4] ITU-T Recommendation Z.100: "Specification and Description Language (SDL)".
[5] 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".
[6] ETSI EN 300 392-3-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 1: General design".
ETSI
8 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
3 Definitions and abbreviations
3.1 Definitions
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
Functional Entity (FE): specifies the functional characteristics of the SS sub-entity within an MS, a LS or a SwMI
related to an SS-PC action, e.g. management or operational functions of SS-PC
home system: TETRA system to which the subscriber identity is permanently defined
management functions: management functions for SS-PC are definition, activation, deactivation and interrogation
priority level: pre-agreed value allocated to each mobile Individual TETRA Subscriber Identity (ITSI) or Group
TETRA Subscriber Identity (GTSI) on a per call basis
NOTE: It is used to determine priority access to network resources in the event of network congestion.
Switching and Management Infrastructure (SwMI): all of the TETRA equipment for a Voice plus Data (V+D)
network except for subscriber terminals
NOTE: The SwMI enables subscriber terminals to communicate with each other via the SwMI.
system 1: TETRA system to which SS-PC is defined, activated, deactivated and interrogated and in which SS-PC can
be invoked and operated
system 2: TETRA system through which SS-PC definition, activation, deactivation and interrogation can be delivered.
SS-PC can also be invoked and operated in system 2
user A: calling party which invokes SS-PC
user B: called party in a call in which SS-PC is operated
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CC basic service Call Control functional entity
CCA basic service Call Control functional entity Agent
NOTE: CC and CCA are applied as defined in ISO/IEC 11574 [5].
GTSI Group TETRA Subscriber Identity
ITSI Individual TETRA Subscriber Identity
LS Line Station
MS Mobile Station
SDL Specification and Description Language
SS Supplementary Service
NOTE: The abbreviation SS is only used when referring to a specific supplementary service.
SS-PC Priority Call
SwMI Switching and Management Infrastructure
TETRA Terrestrial Trunked Radio
ETSI
9 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
4 SS-PC stage 3 specification
4.1 General
This clause describes the SS-PC services offered by Supplementary Service (SS) and call control sub-entities of CMCE
of the TETRA voice plus data layer 3 service boundary in the MS/LS. The SS-PC services shall be offered at the
Supplementary Services service access point (TNSS-SAP), the Call Control services Service Access Point
(TNCC-SAP). The SS-PC services described in this clause shall be applicable for the MS and the LS.
NOTE: The SS-PC services within the SwMI are outside the scope of the present document.
The SS-PC services specified in the present document shall complement the Supplementary services and Call control
services specified in EN 300 392-2 [1] clause 12 and 11 respectively and the Supplementary Services general design
standard EN 300 392-9 [2]. The SS-PC services shall act as sub-services within the general Supplementary services and
Call control services.
SS-PC shall be an optional supplementary service for TETRA voice plus data layer 3. If SS-PC is supported, this clause
shall specify the services and their availability.
4.2 SS-PC services offered over the TNSS-SAP
When the optional SS-PC definition, user definition, activation, deactivation and interrogation -indication are supported,
they shall be provided at TNSS-SAP.
NOTE: As the present document only deals with the SS-PC all the service primitives have been shown without a
TNSS-PC-prefix e.g. the TNSS-PC-ASSIGN request is shorten into an ASSIGN request.
The SS-PC primitives for the user A (FE1) at the MS/LS TNSS-SAP shall be:
a) INTERROGATE request;
b) INTERROGATE indication;
c) ASSIGN indication;
d) ASSIGN response.
The SS-PC primitives for the authorized user (FE3) at the MS/LS TNSS-SAP shall be:
a) DEFINE request;
b) DEFINE indication;
c) INTERROGATE request;
d) INTERROGATE indication.
The activation and deactivation shall be done with the DEFINE request; the acknowledgement for activation and
deactivation shall be done with DEFINE indication.
The information contained in the following primitive description tables correspond to the following key:
- Remark: comment;
- C: conditional;
- O: optional;
- M: mandatory.
ETSI
10 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
4.2.1 DEFINE request
DEFINE request primitive shall be offered from the user application to FE3 over TNSS-SAP. The primitive shall
contain the SS-PC parameters listed in table 1.
The definition process may support a single individual subscriber or to a range or list of individual subscribers. The
definition may also be made to one group or to a range or list of groups.
Table 1: DEFINE request contents
Parameter Request Remark
Subscriber identity M repeatable
Activated/deactivated M (see note 1)
Basic Services M repeatable
High priority value O Repeatable (see note 2)
Low priority value O Repeatable (see note 2)
Delivered to user A(s) M
Acknowledgement from user A(s) C (see note 3)
NOTE 1: Shall be used to indicate whether or not this PDU is used to activate a new PC value or to
deactivate an existing PC value. When a PC value is deactivated, a pre-programmed default
value may then apply.
NOTE 2: It is not necessary to define both High and Low priority values. A missing high priority shall
assume the same value as the low priority value while a missing low priority shall assume the
lowest possible priority value.
NOTE 3: Conditional on the information element "Delivered to user A(s)".
4.2.2 DEFINE indication
DEFINE indication primitive shall be offered from FE3 to the user application over TNSS-SAP as an acknowledgement
to a previously made definition request. The primitive shall contain the SS-PC parameters listed in table 2.
The parameters shall be interpreted as described for DEFINE request.
However, the Result for definition(s) parameter shall indicate the result for all listed subscriber numbers and all basic
service types.
NOTE 1: If the acknowledgements are different for different Subscriber identities, FE3 may deliver several
DEFINE indication primitives to the user application.
NOTE 2: If the Result for definition/activation/deactivation is "accepted, but some values changed by SwMI", the
interrogation can be used to interrogate the values.
Table 2: DEFINE indication contents
Parameter Indication Remark
Subscriber identity M repeatable
Activated/deactivated M
Result for definition M repeatable
ETSI
11 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
4.2.3 ASSIGN indication
ASSIGN indication primitive shall be offered from FE1 to the user application over TNSS-SAP. The primitive shall
contain the SS-PC parameters listed in table 3.
The parameters shall be interpreted as described for DEFINE request.
FE1 shall only consider definitions made to user A's subscriber number or to a group number of which the subscriber is
a member.
Table 3: ASSIGN indication contents
Parameter Indication Remark
Subscriber identity M
Activated/deactivated M
Basic Services M repeatable
High priority value O repeatable (see note 1)
Low priority value O repeatable (see note 1)
Acknowledgement from user A(s) M (see note 2)
NOTE 1: It is not necessary to define both High and Low priority values. A missing high
priority shall assume the same value as the low priority value while a missing
low priority shall assume the lowest possible priority value.
NOTE 2: Parameter shall indicate if FE1 shall acknowledge the reception of the
definition.
4.2.4 ASSIGN response
ASSIGN response primitive shall be offered from user application to FE1 over TNSS-SAP as an acknowledgement to a
previously received ASSIGN request, if acknowledgement was requested. The primitive shall contain the SS-PC
parameters listed in table 4.
The parameters shall be interpreted as described for DEFINE request/indication.
Table 4: ASSIGN response contents
Parameter Response Remark
Subscriber identity M
Activated/deactivated M
Basic Services M repeatable
Low priority value O repeatable
High priority value O repeatable
Result for definition M repeatable
4.2.5 INTERROGATE request
INTERROGATE request primitive shall be offered from -the user application to FE1 or FE3 over the TNSS-SAP. The
primitive shall be used to interrogate SS-PC definitions. INTERROGATE request primitive shall contain the SS-PC
parameters listed in table 5.
The parameters shall be interpreted as described for DEFINE request.
Table 5: INTERROGATE request contents
Parameter Request Remark
Subscriber identity M repeatable
ETSI
12 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
4.2.6 INTERROGATE indication
INTERROGATE indication primitive shall be offered from FE3 or FE1 to the user application over the TNSS-SAP as a
response to a previously sent interrogation request. INTERROGATE indication primitive shall contain the SS-PC
parameters listed in table 6.
The parameters shall be interpreted as described for DEFINE request.
If the Subscriber identity parameter is repeated, the definition(s) shall be valid for all given numbers. The Delivered to
user A(s) and Acknowledgement from user A(s) parameters shall indicate if these have been requested with the last
successful definition request. The Result for interrogation shall indicate, if the definition has been distributed to user
A(s) and if user A(s) have acknowledged the distribution.
NOTE: If definitions/responses are different for different Subscriber identity parameters FE3 may send several
INTERROGATE confirm primitives to the user application.
Table 6: INTERROGATE indication contents
Parameter Indication Remark
Subscriber identity M repeatable
Result for interrogation M
Activated/deactivated C see note
Basic Services C repeatable
High priority value C repeatable
Low priority value C repeatable
Delivered to user A(s) C MS/LS-subscribers, see note
Acknowledgement from user A(s) C see note
NOTE: The parameter appears only if the "Result for interrogation" has the value
"accepted" or "accepted, but one or more affected users could not accept the
request; or accepted, but one or more affected users were not reached".
4.3 SS-PC services offered over the TNCC-SAP
When the SS-PC invocation and operation are supported they shall be provided at TNCC-SAP.
4.3.1 PRIORITY1 request - SS-PC invocation
PRIORITY1 shall act as the invocation of SS-PC and the invoked SS-PC priority shall be included within the
TNCC-SETUP request primitive offered over the TNCC-SAP.
The service user, e.g. user A, invokes SS-PC by requesting a certain SS-PC priority with a call invocation. The user
application may verify that the priority is within the allowed range and if not, change it, before passing the priority to
CC. The user application shall pass the invoked Call priority within TNCC-SETUP to CC.
4.3.2 PRIORITY2 confirm/indication - SS-PC operation
PRIORITY2 shall act as the operation of SS-PC and the SwMI shall send the applied SS-PC priority to user A and user
B(s). The CC within user A and B(s) shall include the received SS-PC priority to the TNCC-SETUP confirm and
indication primitives and offer them over TNCC-SAP to the user application. The user application may indicate the
SS-PC priority to the service user.
ETSI
13 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
4.4 Void
4.5 Parameter descriptions
• Acknowledgement from user A(s) =
- acknowledgement requested from user A(s);
- acknowledgement not requested from user A(s).
• Activated/Deactivated =
- Activated;
- Deactivated.
• Basic services =
- all applicable basic services (circuit mode speech and circuit mode data);
- circuit mode speech;
- circuit mode data;
- packet mode data (connection-oriented).
• Delivered to user A(s) =
- delivered;
- not delivered.
• High priority value =
- predefined priority;
- lowest priority 1;
- .
- highest priority 11.
• Low priority value =
- see high priority value.
• Result for definition =
- accepted by SwMI/MS;
NOTE 1: Accepted by SwMI is applicable for DEFINE indication; accepted by MS is applicable for ASSIGN
response.
- accepted but some priority values changed by SwMI;
- user A could not accept the request/user A was not reached;
NOTE 2: User A can be referring to several user As.
ETSI
14 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
- request failed for any reason;
- user not authorized;
- unknown TETRA identity;
- parameters not valid;
- insufficient information.
• Result for interrogation =
- accepted;
- accepted but request pending in SwMI to user A(s);
- accepted but user A(s) could not accept the request/ user A(s) was not reached;
- SS-PC not defined for the given identity;
- request failed for any reason;
- user not authorized;
- unknown TETRA identity;
- parameters not valid.
• Subscriber identity =
- TETRA Subscriber Identity (TSI) = Short Subscriber Identity (SSI) + Mobile Country Code (MCC) +
Mobile Network Code (MNC), see EN 300 392-1 [3], clause 7.
5 SS-PC protocol description
5.1 General
This clause defines together with clause 6 the layer 3 SS-PC specific CMCE air interface protocol for the MS and the
LS. SS-PC protocol defines the SS-PC specific protocol for Supplementary Service sub-entity and call control
sub-entity within CMCE. The SS-PC specification shall be normative for the MS and the LS.
The protocol in this clause shall complement the CMCE protocol described in EN 300 392-2 [1], clauses 14 and 14.5.5
excluded, with the SS-PC specific protocol actions.
5.2 SS-PC protocol states
The normal SS-PC protocol states are described in the present clause.
ETSI
15 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
5.2.1 Protocol states of FE1
The capability to receive, save and acknowledge -SS-PC definitions and interrogation request shall be an optional
feature within an MS/LS. The state definitions given for the reception and acknowledgement of SS-PC definitions and
interrogation in this clause shall apply only, if the feature is supported.
State IDLE shall be the normal state of FE1. In the state IDLE FE1 shall:
- upon reception of an SS-PC definition request indicating activation from the SwMI, FE1 shall pass the request
to the user application;
- upon reception of an SS-PC definition request indicating deactivation from the SwMI, FE1 shall pass the
request to the user application;
- upon reception of an SS-PC definition acknowledgement from the user application, FE1 shall send it to the
SwMI;
- upon reception of an SS-PC interrogation request from the user application, FE1 shall send it to the SwMI;
- upon reception of an SS-PC interrogation response from the SwMI, FE1 shall pass it to the user application.
5.2.2 Protocol states of CCA to which FE1 is collocated
5.2.2.1 State IDLE
CCA to which FE1 is collocated shall be able to receive call invocation requests including the SS-PC invocation
(priority) from the user application. The requested priority shall be sent to SwMI with the call invocation request.
5.2.2.2 MO_CALL_SETUP
At the reception of the call set-up confirmation, CCA should give the priority to the user application.
NOTE: It is possible that the SwMI has changed the SS-PC priority.
5.2.3 Protocol states of FE21
The capability to receive, save and acknowledge SS-PC definitions and interrogation request shall be an optional feature
within FE21. The state definitions given for the reception and acknowledgement of SS-PC definitions and interrogation
in this clause shall apply only, if the feature is supported.
5.2.3.1 State IDLE
State IDLE shall be the normal state of FE21. In the state IDLE FE21 shall:
- upon reception of an SS-PC definition request indicating SS-PC activation, FE21 shall save the SS-PC
definition in the SwMI, if the request is valid and authorized, FE21 shall acknowledge the SS-PC definition
request to FE3;
- if FE21 was requested to send the SS-PC definitions to FE1(s), FE21 should send the definitions to FE1s;
- upon reception of an SS-PC definition request indicating SS-PC deactivation, the SS-PC definition for the
indicated subscriber identity (ies) shall be removed. A default SS-PC value may then apply for the subscriber
identity(ies);
- upon reception of an SS-PC interrogation request from FE1 or FE3, FE21 should send the response to the
request to FE1 or FE3 respectively.
FE21 shall apply the SS-PC definition-activation and define-deactivation from the moment it is made.
ETSI
16 ETSI EN 300 392-12-10 V1.2.1 (2004-02)
5.2.4 Protocol states of CC to which FE21 is collocated
The protocol states of CC to which FE21 is collocated shall carry the following tasks:
- start the call set-up;
- set-up the SS-PC call.
For these actions the corresponding states shall be: ANY-STATE and SETUP-STARTED.
The SETUP-STARTED corresponds to normal continuation of the call set-up.
5.2.4.1 State ANY-STATE
The protocol described for "ANY-STATE" shall refer to any state in which a call set-up request shall be received and
the call set-up started.
The functional tasks for the state ANY-STATE shall be:
- upon reception of an SS-PC call invocation, CC shall accept or reject the re
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...