ETSI EN 300 392-12-16 V1.2.1 (2004-09)

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) – 12. del: Dopolnilne storitve stopnje 3 – 16. poddel: Prednostni klic s predpravico (PPC)Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary services stage 3; Sub-part 16: Pre-emptive Priority Call (PPC)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:EN 300 392-12-16 Version 1.2.1SIST EN 300 392-12-16 V1.2.1:2006en01-april-2006SIST EN 300 392-12-16 V1.2.1:2006SLOVENSKI
STANDARD
ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 2
Reference REN/TETRA-03123 Keywords data, radio, speech, stage 3, supplementary service, TETRA, V+D 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, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp 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.
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-12-16 V1.2.1:2006

ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 3
Contents Intellectual Property Rights.6 Foreword.6 1 Scope.8 2 References.8 3 Definitions and abbreviations.9 3.1 Definitions.9 3.2 Abbreviations.9 4 SS-PPC service primitives.10 4.1 General.10 4.2 SS-PPC services offered over the TNSS-SAP.10 4.2.1 DEFINE request.11 4.2.2 DEFINE confirm.12 4.2.3 ASSIGN indication.12 4.2.4 ASSIGN response.12 4.2.5 INTERROGATE request.12 4.2.6 INTERROGATE confirm.13 4.2.7 REMOVE indication.13 4.2.8 REMOVE response.14 4.2.9 WITHDRAW request.14 4.2.10 WITHDRAW confirm.14 4.2.11 IMPENDING-PRE-EMPTION indication.14 4.2.12 USER-PRE-EMPTED indication.15 4.3 SS-PPC services offered over the TNCC-SAP.15 4.3.1 PRIORITY1 request - SS-PPC invocation.15 4.3.2 PRIORITY2 confirm/indication - SS-PPC operation.15 4.3.3 PRE-EMPTION.16 4.4 Parameter descriptions.16 5 SS-PPC protocol description.18 5.1 General.18 5.2 SS-PPC protocol states.18 5.2.1 Protocol states of FE1.18 5.2.2 Protocol states of CCA to which FE1 is collocated.19 5.2.2.1 State IDLE.19 5.2.2.2 MO-CALL-SETUP.19 5.2.3 Protocol states of FE21.19 5.2.3.1 State IDLE.19 5.2.4 Protocol states of CC to which FE21 is collocated.20 5.2.4.1 State ANY-STATE.20 5.2.4.2 State PARTIES-PRE-EMPTED.20 5.2.4.3 State SETUP-STARTED.21 5.2.5 Protocol states of FE3.21 5.2.6 Protocol states of visited SwMI FE25.21 5.2.7 Protocol states of CC to which FE25 is collocated.22 5.2.7.1 State ANY-STATE.22 5.2.7.2 State PARTIES-PRE-EMPTED.22 5.2.7.3 State SETUP-STARTED.23 5.2.8 Protocol states of FE5.23 5.2.9 Protocol states of CCA to which FE5 is collocated.23 5.2.9.1 ANY STATE.23 5.2.9.2 MT-CALL-SETUP.23 5.2.10 Protocol states of FE8.24 5.2.11 Protocol states of CCA to which FE8 is collocated.24 5.3 SS-PPC signalling procedures.24 SIST EN 300 392-12-16 V1.2.1:2006

ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 4
5.3.1 Procedures for FE1.24 5.3.2 Procedures for FE21.25 5.3.2.1 Definition in FE21.25 5.3.2.2 Distribution in FE21.25 5.3.2.3 Interrogation in FE21.25 5.3.3 Procedures for CC to which FE21 is collocated.26 5.3.3.1 Verify priority in CC to which FE21 is collocated.26 5.3.4 Procedures for FE3.26 5.3.4.1 Verification in FE3.26 5.3.5 Procedures for visited SwMI FE25.27 5.4 PDU descriptions.27 5.4.1 ASSIGN PDU.27 5.4.2 ASSIGN ACK PDU.28 5.4.3 DEFINE PDU.28 5.4.4 DEFINE ACK PDU.29 5.4.5 INTERROGATE PDU.29 5.4.6 INTERROGATE-ACK PDU.30 5.4.7 REMOVE PDU.30 5.4.8 REMOVE ACK PDU.30 5.4.9 WITHDRAW PDU.31 5.4.10 WITHDRAW ACK PDU.31 5.4.11 Pre-emption.31 5.4.11.1 D-RELEASE PDU.31 5.4.12 Priority 1 and Priority 2.31 5.4.12.1 D-CONNECT PDU.31 5.4.12.2 D-SETUP PDU.31 5.4.12.3 U-SETUP PDU.32 5.4.13 IMPENDING-PRE-EMPTION PDU.32 5.4.14 USER-PRE-EMPTED PDU.32 5.5 Information element coding.32 5.5.1 Basic service(s).32 5.5.2 Number of pre-empted parties.33 5.5.3 Number of SS-PPC definitions.33 5.5.4 PPC PDU type.34 5.5.5 Pre-empted party.34 5.5.6 Range type.35 5.5.7 Result for definition.35 5.5.8 Result for interrogation.36 5.5.9 Result for withdrawal.36 5.5.10 SS-PPC assignment.36 5.5.11 SS-PPC definition.37 5.5.12 SS-PPC priority, Call priority and Non group member SS-PPC priority.37 5.5.13 Subscriber extension present.37 5.5.14 Subscriber identity.38 5.5.15 Time to pre-emption.38 6 SS-PPC FE behaviour.38 6.1 Behaviour of FE1 (SS entity of user A).39 6.1.1 Service interaction for FE1.39 6.1.2 Process description for FE1.40 6.2 Behaviour of CCA to which FE1 is collocated.41 6.2.1 Service interaction for CCA to which FE1 is collocated.41 6.2.2 Process description for CCA to which FE1 is collocated.42 6.3 Behaviour of FE21.43 6.3.1 Service interaction for FE21.43 6.3.2 Process description for FE21.44 6.4 Behaviour of CC to which FE21 is collocated.45 6.4.1 Service interaction for CC to which FE21 is collocated.45 6.4.2 Process description for CC to which FE21 is collocated.46 6.5 Behaviour of FE3 (SS entity of authorized user).49 6.5.1 Service interaction for FE3.49 6.5.2 Process description for FE3.50 SIST EN 300 392-12-16 V1.2.1:2006

ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 5
6.6 Behaviour of visited SwMI FE25.51 6.6.1 Service interaction for FE25.51 6.6.2 Process description for visited SwMI FE25.52 6.7 Behaviour of CC to which FE25 is collocated.53 6.8 Behaviour of FE5.54 6.8.1 Service interaction for FE5.54 6.8.2 Process description for FE5.55 6.9 Behaviour of CCA to which FE5 is collocated.56 6.9.1 Service interaction for CCA to which FE5 is collocated.56 6.9.2 Process description for CCA collocated to FE5.57 6.10 Behaviour of FE8.59 6.10.1 Service interaction for FE8.59 6.10.2 Process description for FE8.60 6.11 Behaviour of CCA to which FE8 is collocated.61 6.11.1 Service interaction for CCA to which FE8 is collocated.61 6.11.2 Process description for CCA collocated to FE8.62 6.12 Inter-working considerations.62 Annex A (informative): Mapping of SS-PPC priorities received from the user application to priorities in basic service PDUs (for the MS).63 Annex B (informative): Bibliography.64 Annex C (informative): Change requests.65 History.66
ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 6
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 16 of a multi-part deliverable covering Voice plus Data 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)"; SIST EN 300 392-12-16 V1.2.1:2006

ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 7
ETS 300 392-12-13: "Call Completion to Busy Subscriber (CCBS)"; EN 300 392-12-14: "Late Entry (LE)"; EN 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"; TR 100 392-17: "TETRA V+D and DMO specifications". NOTE: Part 10, sub-part 15 (Transfer of control), part 13 (SDL) and part 14 (PICS) of this multi-part deliverable are in status "historical" and are not maintained.
National transposition dates Date of adoption of this EN: 3 September 2004 Date of latest announcement of this EN (doa): 31 December 2004 Date of latest publication of new National Standard or endorsement of this EN (dop/e):
30 June 2005 Date of withdrawal of any conflicting National Standard (dow): 30 June 2005
ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 8
1 Scope The present document defines the stage 3 specifications of the Supplementary Service Pre-emptive Priority Call
(SS-PC) for the Terrestrial Trunked Radio (TETRA). SS-PPC enables a user to have preferential access to the network resources in a TETRA system in times of congestion including pre-emption of calls. SS-PPC is applicable for pre-emptive priorities including the emergency priority.
SS-PPC includes the capability to pre-empt resources needed for higher priority calls and the capability to pre-empt users from ongoing calls in order to move them to a higher priority calls. SS-PPC specifies the definition, activation, deactivation and interrogation for the usage of pre-emptive call priorities in the TETRA system. The Switching and Management Infrastructure (SwMI) applies the SS-PPC priorities when it allocates the resources for calls. The SS-PPC operations are defined for the SwMI and for the Mobile Station (MS). SS-PPC is defined to 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-PPC is invoked for calls within one TETRA system or for calls that extend over ISI to several TETRA systems. 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 FEs and their behaviour. The described protocols and behaviour apply to the SwMI, for the MS and may be applied over the ISI between TETRA systems. Aspects relating to all supplementary services are detailed in EN 300 392-9 [3]. 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-1 (V1.2.1): "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 1: General network design". [3] ETSI EN 300 392-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 9: General requirements for supplementary services". [4] 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". [5] ITU-T Recommendation Z.100: "Specification and Description Language (SDL)". [6] ETSI EN 300 392-12-10: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary services stage 3; Sub-part 10: Priority Call (PC)". SIST EN 300 392-12-16 V1.2.1:2006

ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 9
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 SS-PPC CCA: Call Control sub-entity for Supplementary Service Pre-emptive Priority Call in Circuit Mode Control Entity in Mobile Station emergency priority: highest pre-emptive priority level Functional Entity (FE): functional characteristics of the SS sub-entity within an MS or a SwMI related to an SS-PPC action, e.g. definition or invocation SS-PPC call: basic service (call) to which the defined SS-PPC priority is applied SS-PPC invocation: sending of priority request to infrastructure NOTE: The SS-PPC invocation is done with the basic service invocation request. SS-PPC operation: usage of SS-PPC priority for and in a basic service set-up SS-PPC pre-emption: exclusion of one or more parties from an ongoing basic service due an SS-PPC operation for another basic service NOTE: The pre-emption may be done due to the lack of resources or due to the need to join a called party to a higher priority pre-emptive call. SS-PPC priority: any pre-emptive priority invoked and operated for an SS-PPC call user A: calling party, the party that invokes or generates invocation of SS-PPC user B: called party in a call in which SS-PPC is operated user C: pre-empted user, a user that is involved in a call, which is pre-empted due to lack of resources for a SS-PPC NOTE: There may be one, two or more pre-empted users due to a pre-empted call. user D: remaining user or users in a call from which a user or users have been pre-empted visited SwMI: TETRA system of which the Mobile Network Identity (MNI) is not equal to the MNI of the user 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CC Call Control sub-entity for SS-PPC in CMCE in SwMI CMCE Circuit Mode Control Entity FE Functional Entity GTSI Group TETRA Subscriber Identity ISI Inter System Interface ITSI Individual TETRA Subscriber Identity MCC Mobile Country Code MNC Mobile Network Code MNI Mobile Network Identity MS Mobile Station PDU Protocol Data Unit SS Supplementary Service sub-entity within CMCE SSI Short Subscriber Identity SS-PPC Supplementary Service Pre-emptive Priority Call SIST EN 300 392-12-16 V1.2.1:2006

ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 10
SwMI Switching and Management Infrastructure TETRA TErrestrial Trunked RAdio TNCC-SAP TETRA Network layer Call Control Service Access Point TNSS-SAP TETRA Network layer Supplementary Service Service Access Point TSI TETRA Subscriber Identity 4 SS-PPC service primitives 4.1 General This clause describes the SS-PPC 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. The SS-PPC services shall be offered at the Supplementary Services Service Access Point (TNSS-SAP) and the Call Control services Service Access Point
(TNCC-SAP). The SS-PPC services described in this clause shall be applicable for the MS. NOTE: The SS-PPC services within the SwMI are outside the scope of the present document. The SS-PPC services specified in the present document shall complement the Supplementary services and Call control services specified in EN 300 392-2 [1] clauses 12 and 11 respectively and the Supplementary Services general design standard EN 300 392-9 [3]. The SS-PPC services shall act as sub-services within the general supplementary services and call control services. SS-PPC shall be an optional supplementary service for TETRA voice plus data layer 3. If SS-PPC is supported, this clause shall specify the services and their availability. 4.2 SS-PPC services offered over the TNSS-SAP When the optional SS-PPC definition, user definition, activation, deactivation, interrogation, impending pre-emption indication and pre-empted party indication are supported, they shall be provided at TNSS-SAP. NOTE: As the present document only deals with the SS-PPC all the service primitives have been shown without a TNSS-PPC-prefix e.g. the TNSS-PPC-ASSIGN request is shorten into an ASSIGN request. The SS-PPC primitives for the user A (FE1) at the MS TNSS-SAP shall be: a) INTERROGATE request; b) INTERROGATE indication; c) ASSIGN indication; d) ASSIGN response. The SS-PPC primitives for the authorized user (FE3) at the MS TNSS-SAP shall be: a) DEFINE request; b) DEFINE indication; c) INTERROGATE request; d) INTERROGATE indication. SIST EN 300 392-12-16 V1.2.1:2006

ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 11
The SS-PPC primitives for the pre-empted called user (FE5) at the MS TNSS-SAP shall be: a) IMPENDING-PRE-EMPTION indication. The SS-PPC primitives for the pre-empted user (FE8) at the MS TNSS-SAP shall be: a) IMPENDING-PRE-EMPTION indication. The SS-PPC primitives for the user (FE9) remaining in a call after pre-emption at the MS TNSS-SAP shall be: a) USER-PRE-EMPTED 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. 4.2.1 DEFINE request Optional DEFINE request primitive may be offered from the user application to FE3 over TNSS-SAP. The primitive shall contain the SS-PPC information parameters listed in table 1. The subscriber identity parameter(s) shall indicate the subscriber identities on which the following definition shall be made. Table 1: DEFINE request contents Parameter
Request Remark Subscriber identity M Repeatable Activated/deactivated M Note 1 Basic service M Repeatable SS-PPC priority M Repeatable Delivered to user A(s) M
Acknowledgement from user A(s) C Note 2 NOTE 1: Shall be used to indicate whether or not this PDU is used to activate a new PPC value or to deactivate an existing PPC value. When a PPC value is de-activated, a pre-programmed default value may then apply. NOTE 2: Conditional on the information element "Delivered to user A(s)".
ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 12
4.2.2 DEFINE confirm If DEFINE request primitive is supported, then DEFINE confirm 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-PPC information parameters listed in table 2. The Result for definition 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 confirm 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 confirm contents Parameter
Indication Remark Subscriber identity M Repeatable Activated/deactivated M
Result for definition M
4.2.3 ASSIGN indication Optional ASSIGN indication primitive may be offered from FE1 to the user application over TNSS-SAP. The primitive shall contain the SS-PPC information parameters listed in table 3. FE1 shall only consider definitions made 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 service M Repeatable SS-PPC priority M Repeatable Acknowledgement from user A(s) M Note NOTE: Parameter shall indicate if FE1 shall acknowledge the reception of the definition.
4.2.4 ASSIGN response If ASSIGN indication primitive is supported, then ASSIGN response primitive shall be offered from the 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-PPC information parameters listed in table 4. Table 4: ASSIGN response contents Parameter
Response Remark Subscriber identity M
Activated/deactivated M
Basic service M
SS-PPC priority M
Result for definition M
4.2.5 INTERROGATE request Optional INTERROGATE request primitive may be offered from the user application to FE1 or FE3 over TNSS-SAP and it shall be used to interrogate SS-PPC definitions. INTERROGATE request primitive shall contain the SS-PPC information parameters listed in table 5. SIST EN 300 392-12-16 V1.2.1:2006

ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 13
Table 5: INTERROGATE request contents Parameter
Request Remark Subscriber identity M Repeatable
4.2.6 INTERROGATE confirm If INTERROGATE request primitive is supported, then INTERROGATE confirm primitive shall be offered from FE1 or FE3 to the user application over TNSS-SAP as a response to a previously sent interrogation request. INTERROGATE confirm primitive shall contain the SS-PPC information parameters listed in table 6. 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 confirm contents Parameter
Indication Remark Subscriber identity M Repeatable Result for interrogation M
Activated/deactivated C Note Basic service C Repeatable SS-PPC priority C Repeatable Delivered to user A(s) C MS/LS-subscribers, note Acknowledgement from user A(s) C Note NOTE: The parameter shall appear only if the "Result for interrogation" has the value "accepted", "accepted, but request to user A(s) pending in the SwMI" or "accepted, but user A(s) could not accept the request/ user A(s) was not reached".
4.2.7 REMOVE indication Optional REMOVE indication primitive may be offered from FE1 to the user application over TNSS-SAP. This primitive shall be used to withdraw the SS-PPC service from a subscriber. The primitive shall contain the SS-PPC information parameters listed in table 7. Table 7: REMOVE indication contents Parameter
Indication Remark Subscriber identity M
Acknowledgement from user A(s) M Note NOTE: Parameter shall indicate if FE1 shall acknowledge the reception of the removal.
ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 14
4.2.8 REMOVE response If REMOVE indication parameter is supported, then REMOVE response primitive shall be offered from the user application to FE1 over TNSS-SAP as an acknowledgement to a previously received REMOVE request, if acknowledgement was requested. The primitive shall contain the SS-PPC information parameters listed in table 8. Table 8: REMOVE response contents Parameter
Response Remark Subscriber identity M
Result for withdrawal M
4.2.9 WITHDRAW request Optional WITHDRAW request primitive may be offered from the user application to FE3 over TNSS-SAP and it shall be used to withdraw the PPC service from a subscriber. WITHDRAW request primitive shall contain the SS-PPC information parameters listed in table 9. Table 9: WITHDRAW request contents Parameter
Request Remark Subscriber identity M Repeatable Delivery to user A(s) M MS/LS-subscribers Acknowledgement from user A(s) M
4.2.10 WITHDRAW confirm If WITHDRAW request primitive is supported, then WITHDRAW confirm primitive shall be offered from FE3 to the user application over TNSS-SAP as an acknowledgement to a previously received WITHDRAW request. The primitive shall contain the SS-PPC information parameters listed in table 10. NOTE: If the acknowledgements are different for different subscriber identities, FE3 may deliver several WITHDRAW confirm primitives to the user application. Table 10: WITHDRAW confirm contents Parameter
Indication Remark Subscriber identity M Repeatable Result for withdrawal M
4.2.11 IMPENDING-PRE-EMPTION indication Optional IMPENDING-PRE-EMPTION indication may be offered from FE8 or FE5 to the user application to inform of a forthcoming pre-emption. IMPENDING-PRE-EMPTION indication primitive shall contain the SS-PPC information parameters listed in table 11. Table 11: IMPENDING-PRE-EMPTION indication contents Parameter
Indication Remark Impending pre-emption M
Time to pre-emption O (In seconds)
ETSI ETSI EN 300 392-12-16 V1.2.1 (2004-09) 15
4.2.12 USER-PRE-EMPTED indication
Optional USER-PRE-EMPTED indication may be offered from FE9 to the user application to inform that one or more parties have been pre-empted from the ongoing call. USER-PRE-EMPTED indication primitive shall contain the
SS-PPC information parameters listed in table 12. Table 12: USER-PRE-EMPTED indication contents Parameter
Indication Remark Subscribers pre-empted M
Subscriber identity O Pre-empted party
4.3 SS-PPC services offered over the TNCC-SAP When the SS-PPC invocation, operation and pre-emption are supported they shall be provided at TNCC-SAP. 4.3.1 PRIORITY1 request - SS-PPC invocation PRIORITY1 shall act as the invocation of SS-PPC and the invoked SS-PPC priority shall be included within the
TNCC-SETUP request primitive offered over the TNCC-SAP. The service user, e.g. user A, invokes SS-PPC by requesting a certain SS-PPC priority with a call invocation. The user application may verify that the priority is within the allowed range for a pre-emptive priority value 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-PPC operatio
...