SIST ETS 300 392-11-3 E1:2003

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 3: Talking Party Identification (TPI)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:ETS 300 392-11-3 Edition 1SIST ETS 300 392-11-3 E1:2003en01-december-2003SIST ETS 300 392-11-3 E1:2003SLOVENSKI
STANDARD
EUROPEANETS 300 392-11-3TELECOMMUNICATIONJuly 1999STANDARDSource: TETRAReference: DE/TETRA-03001-11-03ICS:33.020Key words:TETRA, V+DTerrestrial Trunked Radio (TETRA);Voice plus Data (V+D);Part 11: Supplementary services stage 2;Sub-part 3: Talking Party Identification (TPI)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEInternet: secretariat@etsi.fr - http://www.etsi.orgTel.: +33 4 92 94 42 00 - Fax: +33 4 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 1999. All rights reserved.SIST ETS 300 392-11-3 E1:2003

Page 2ETS 300 392-11-3: July 1999Whilst 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 Standards Making Support Dept." at the address shown on the title page.SIST ETS 300 392-11-3 E1:2003

Page 3ETS 300 392-11-3: July 1999ContentsForeword.51Scope.72References.73Definitions and abbreviations.83.1Definitions.83.2General abbreviations.83.3Supplementary service abbreviations.84Functional model.84.1Functional model description.84.2Description of functional entities.104.2.1Served user functional entity, FE1.104.2.2Served user current SwMI functional entity, FE21.104.2.3Group controlling functional entity, FE22.104.2.4Affected user current SwMI functional entity, FE25.114.2.5SS-CAD diverting SwMI functional entity, FE2SS-CAD.114.2.6Managed user/group home SwMI FE, FE20.114.2.7Authorized user's functional entity, FE3.124.3Relationship of functional model basic call functional model.125Information flows.145.1Definition of information flows.145.1.1ACTIVATE.145.1.2ACTIVATE ACK.145.1.3DEFINE.155.1.4DEFINE ACK.155.1.5INFORM.165.1.6INTERROGATE.165.1.7INTERROGATE ACK.165.1.8INTERROGATE BY NAME.175.1.9INTERROGATE BY NAME ACK.175.1.10NAME.185.1.11NAME ACK.185.1.12TX PRIORITY REQUEST.195.1.13TX DEMAND PRIORITY.195.1.14Information flow elements.195.2Relationship of information flows to basic call information flows.195.3Service primitives.225.4Examples of information flow sequences.235.4.1Activation/deactivation.235.4.2Definition.235.4.3Operation of SS-TPI in a group call.245.4.4SS-TPI operation in an individual call.285.4.5SS-TPI operation in the case of SS-CAD diverted call.305.4.6Interrogation about name and activation, using identity.315.4.7Interrogation about identity and activation, using name.316Functional entity actions.316.1Functional Entity actions of FE1.316.2Functional Entity actions of FE20.326.3Functional entity actions of FE21.326.4Functional entity actions of FE22.336.5Functional entity actions of FE25.336.6Functional entity actions of FE2SS-CAD.33SIST ETS 300 392-11-3 E1:2003

Page 4ETS 300 392-11-3: July 19996.7Functional Entity actions of FE3.337Allocation of functional entities to physical equipment.348Interworking considerations.34History.36SIST ETS 300 392-11-3 E1:2003

Page 5ETS 300 392-11-3: July 1999ForewordThis European Telecommunication Standard (ETS) has been produced by the Terrestrial Trunked Radio(TETRA) Project of the European Telecommunications Standards Institute (ETSI).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:"Interworking at the Inter-System Interface (ISI)";Part 4:"Gateways basic operation";Part 5:"Peripheral Equipment Interface (PEI)";Part 6:"Line connected Stations (LS)";Part 7:"Security";Part 9:"General requirements for supplementary services";Part 10:"Supplementary services stage 1";Part 11:"Supplementary services stage 2";Part 12:"Supplementary services stage 3";Part 13:"SDL model of the Air Interface (AI)";Part 14:"Protocol Implementation Conformance Statement (PICS) proforma specification".Transposition datesDate of adoption of this ETS:2 July 1999Date of latest announcement of this ETS (doa):31 October 1999Date of latest publication of new National Standardor endorsement of this ETS (dop/e):30 April 2000Date of withdrawal of any conflicting National Standard (dow):30 April 2000SIST ETS 300 392-11-3 E1:2003

Page 6ETS 300 392-11-3: July 1999Blank pageSIST ETS 300 392-11-3 E1:2003

Page 7ETS 300 392-11-3: July 19991ScopeThis ETS specifies the stage 2 description of the Supplementary Service Talking Party Identification(SS-TPI) for the Terrestrial Trunked Radio (TETRA).The SS-TPI supplementary service enables connected parties in a call to receive the identification of thetalking party. The SS-TPI is activated against individual identity in individual call and against group identityin group calls. Man-Machine Interface and charging principles are outside the scope of this ETS.Supplementary service specifications are produced in three stage according to the method defined inCCITT Recommendation I.130 [4]. The stage 2 description identifies the functional capabilities and theinformation flows needed to support the supplementary service as specified in its stage 1 description (seeETS 300 392-10-3 [2]). The stage 2 description is followed by the stage 3 description, which specifies theprotocols at the air interface and at the various Inter-System Interfaces (ISI) to support the service.2ReferencesThis ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative 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]ETS 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);Part 2: Air Interface (AI)".[2]ETS 300 392-10-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);Part 10: Supplementary services stage 1; Sub-part 3: Talking Party Identification(TPI)".[3]ETS 300 392-12-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);Part 12: Supplementary Services stage 3; Sub-part 3: Talking PartyIdentification (TPI)".[4]CCITT Recommendation I.130 (1988): "Method for the characterization oftelecommunication services supported by an ISDN and network capabilities ofan ISDN (Blue Book)".[5]ISO/IEC 11574: "Information technology - Telecommunications and informationexchange between systems - Private Integrated Service Network - Circuit-mode64 kbit/s bearer services - Service description, functional capabilities andinformation flows".[6]ETS 300 392-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);Part 9: General requirements for supplementary services".SIST ETS 300 392-11-3 E1:2003

Page 8ETS 300 392-11-3: July 19993Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the definitions given in ETS 300 392-9 [6] apply with the followingmodifications:authorized user: identified user who is allowed to define, activate, deactivate and/or interrogate theinfrastructure about the activation/deactivation state of the supplementary service and its' relatedparametersserved user: user for whom SS-TPI is invoked. That user will thus receive the SS-TPI information whenhe is the talking/sending party in a calluser B: talking/sending party in a callNOTE:The qualifiers listening/receiving and talking/sending are used in the above definitionsof SS-TPI as a reminder that this supplementary service applies to both speech anddata services.3.2General abbreviationsFor the purposes of this ETS, the following general abbreviations apply:CCBasic Service Call Control functional entityCCABasic Service Call Control Agent functional entityNOTE:CC and CCA are applied as defined in ISO/IEC 11574 [5].FEFunctional EntityGTSIGroup TETRA Subscriber IdentityISIInter-System InterfaceITSIIndividual TETRA Subscriber IdentityLSLine StationMSMobile StationSSSupplementary ServiceNOTE:The abbreviation SS is only used when referring to a specific supplementary service.SwMISwitching and Management Infrastructure3.3Supplementary service abbreviationsTPITalking Party Identification4Functional model4.1Functional model descriptionThe functional model shall comprise the following Functional Entities (FEs):FE1Served user functional entity;FE21Served user current SwMI FE;FE22Group controlling FE;FE25Affected user current SwMI FE;FE2SS-CADSS-CAD controlling FE;FE20Managed user/group home SwMI FE;FE3Authorized user's functional entity.NOTE:No FE is associated to the affected user since no SS-TPI specific procedures apply forthat user.SIST ETS 300 392-11-3 E1:2003

Page 9ETS 300 392-11-3: July 1999The following relationships shall exist between these FEs:rabetween FE1 and FE21 and between FE1 and FE22;rbbetween FE21 and FE25;rcbetween FE22 and FE25;rdbetween FE3 and FE20;rebetween FE21 and FE2SS-CAD;rfbetween FE2SS-CAD and FE25.Figures 1 and 2 show these FEs and relationships for the operational part of SS-TPI in the cases ofindividual call and group call respectively, and figure 3 for the management part of SS-TPI.FE21rarbFE1FE2SS-CADrerfFE25Figure 1: Functional model for the operational part of SS-TPI in the case of individual callraFE22rcFE25FE1Figure 2: Functional model for the operational part of SS-TPI in the case of group callNOTE:No FE2SS-CAD has been shown in figure 2, because the interactions between SS-TPIand SS-CAD are either internal to the originating SWMI or to the group controllingSwMI, thus in any case outside the scope of SS-TPI standardization.FE3rdFE20Figure 3: Functional model for the management part of SS-TPISIST ETS 300 392-11-3 E1:2003

Page 10ETS 300 392-11-3: July 19994.2Description of functional entities4.2.1Served user functional entity, FE1FE1 is the functional entity that serves the served user application. There shall be no managementSS-TPI related function in FE1.4.2.2Served user current SwMI functional entity, FE21When an individual call is being set-up, FE21 shall determine if SS-TPI is activated, and if so, theapplicable subscription parameters (i.e. whether talking/sending party mnemonic name has to bedelivered and/or the priority of each request for transmission grant sent by the talking/sending party). IfSS-TPI has been activated and if the talking/sending party mnemonic name has to be delivered, FE21shall then invoke SS-TPI in requesting FE25 to send the mnemonic name of the other user involved in theindividual call (i.e. the affected user).NOTE 1:This other user may or may not be granted transmission permission during the call. Ifyes, he will become the talking/sending user. If not, the served user will not receive anySS-TPI information during the call.Similarly if SS-TPI has been activated and if the priority of each request for transmission grant from thetalking/sending user has to be delivered, FE21 shall then invoke SS-TPI in requesting FE25 to send thispriority every time the affected user requests transmission grant, when this information is not readilyavailable through a basic call information flow.NOTE 2:Since the priority of the request for transmission grant sent by the talking/sending partyis delivered in ISI-TX DEMAND, sent from the terminating SwMI to the originatingSwMI, FE21 will request FE25 to send this information only when the served user isthe connected user.Still for an individual call, FE21 shall store:-the affected user identity received by the associated basic call functional entity at call set-up time(see note 3); and-the affected user mnemonic name if FE21 has received it from FE25 (following its request).NOTE 3:If the individual call is an intra-TETRA call, the affected user identity is readilyavailable; if it is an inter-TETRA call, the affected user identity is sent as part of one ofthe ANF-ISIIC SETUP or COMPLETE information flows.FE21 shall then operate SS-TPI in sending to FE1, either the information received from FE22 during agroup call, or the SS-TPI information which it has stored at call set-up time for an individual call plus if ithas to be delivered, the priority of each request for transmission grant from the affected user.4.2.3Group controlling functional entity, FE22When establishing a group call, FE22 shall determine if SS-TPI is activated, and if so, the applicablesubscription parameters. If SS-TPI has been activated FE22 shall then invoke SS-TPI. If thetalking/sending party mnemonic name has to be delivered and if the calling user is not a member of thegroup and the calling user's FE25 has not already sent his mnemonic name together with the group callset-up request, FE22 shall request that FE25 to send the mnemonic name of that user, if available, whenrequesting transmission grant for him.NOTE:According to the specification of group call, it is not possible for users not members ofthe group other than the calling user to become talking/sending parties in a group call.FE22 shall then operate SS-TPI in delivering to FE1 the talking/sending party identity, that it shallsupplement with the mnemonic name of this party and with the priority of its corresponding request fortransmission grant, if these parameters have been subscribed to and are available.SIST ETS 300 392-11-3 E1:2003

Page 11ETS 300 392-11-3: July 19994.2.4Affected user current SwMI functional entity, FE25In an individual call, when requested by FE21, FE25 shall send at call set-up time the mnemonic name ofthe affected user (i.e. the user who is not the served user) if available. Still if requested by FE21 and if inaddition the served user is the connected user, FE25 shall send the priority of the request for transmissiongrant sent by that affected user (who will then become the talking/sending party).In a group call, when requested by FE22 at call set-up time, the originating SwMI FE25 shall send themnemonic name of the calling user the first time that user requests transmission permission. In addition, itshould send it at call set-up time without prior request by FE22 when the calling user is not member of thegroup.NOTE:There no need for FE25 to send the affected user identity, since either it is readilyavailable in the case of an intra-TETRA call, or it is sent as part of one of theANF-ISIIC or ANF-ISIGC information flows in the case of an inter-TETRA call.Similarly in a group call there is no need for FE25 to send the priority of the request fortransmission grant sent by the party who is to become the talking/sending party sincethat information is sent in the ANF-ISIGC TX DEMAND request/indication informationflow.4.2.5SS-CAD diverting SwMI functional entity, FE2SS-CADWhen an individual call is being set-up, when the call is diverted by SS-CAD and when the served user isthe calling user, FE2SS-CAD shall store the possible request from FE21 to FE25 to send the affected usermnemonic name. FE2SS-CAD shall reissue it to FE25 when the dispatcher authorizes the call to continue (tothe terminating SwMI with which FE25 is collocated).NOTE:FE2SS-CAD does not exist when the served user is the connected user.4.2.6Managed user/group home SwMI FE, FE20If the optional activation/deactivation procedure is supported by the served user home SwMI, FE20 shallreceive SS-TPI activation/deactivation requests from FE3 and check them. For those requests that FE20finds authorized and correct, it shall carry out the corresponding activations/deactivations in the SwMI andshall confirm their completions to FE3. As to the others, FE20 shall reject them and inform FE3.Similarly, if the optional definition procedure is supported by the affected user home SwMI, FE20 shallreceive SS-TPI definition requests from FE3 and check them. For those requests that FE20 findsauthorized and correct, it shall carry out the corresponding definitions in the SwMI and shall confirm theircompletions to FE3. As to the others, FE20 shall reject them and inform FE3.Finally, if the optional interrogation procedure is supported by the affected used home SwMI, or by theserved user home SwMI, FE20 shall receive SS-TPI interrogation requests from FE3 about availability orstate of a SS-TPI service and check them. For those requests that FE20 finds authorized and correct, itshall prepare and send a response to the interrogation. As to the others, FE20 shall reject them andinform FE3.NOTE:The SS-TPI managed user may be either the served user (e.g. for activating thesupplementary service for this user), or the would be talking/sending user (e.g. fordefining the supplementary service in giving a mnemonic name to that user, orchanging this name).As a result:-interrogation requests for getting mnemonic names corresponding to identitiesare to be addressed to the home SwMIs of the would be talking/sending parties;-the same applies for interrogation requests for getting identities correspondingto mnemonic names; while-interrogation requests regarding activation are to be addressed to the homeSwMIs of the served users.SIST ETS 300 392-11-3 E1:2003

Page 12ETS 300 392-11-3: July 19994.2.7Authorized user's functional entity, FE3If the optional activation/deactivation and/or definition and/or interrogation procedures are supported bythe authorized user MS/LS, FE3 shall send SS-TPI activation/deactivation, definition or interrogationrequests to FE20. FE3 may perform local checks for the corresponding requests before sending them: itshall then send them only if it finds them valid. If FE3 rejects a request, it shall indicate it to the userapplication. When it receives the response from FE20, FE3 shall pass the result to the user application.4.3Relationship of functional model basic call functional modelAlthough no formal models have been defined for basic individual call nor for basic group call, thosemodels can be readily derived from the PISN model for basic call, in ISO/IEC 11574 [5].Being call unrelated, the activation/deactivation, definition and interrogation procedures are independent ofCC or CCA.FE1 shall be collocated with a CCA.NOTE 1:This CCA may either be that of the calling user, or that:-of the called user in an individual call; or-of a participating user in a group call.FE21 shall be collocated with the originating CC if the calling user is the/(each) served user (the serveduser in an individual call or a served user in a group call) with the terminating CC if the served user is theconnected user in an individual call or with a terminating CC for the called users served by that terminatingCC in a group call.NOTE 2:There is one terminating CC within the group controlling SwMI, serving the groupmembers registered in that SwMI, and one terminating CC per participating SwMI.FE22 shall be collocated with the transit CC which is controlling the group call.FE25 shall be collocated with the originating CC if the affected user is the calling user, with the terminatingCC if the affected user is the called user in an individual call or with a terminating CC if the affected user isa called user in a group call.When it exists, FE2SS-CAD shall be collocated with a transit CC (i.e. when the call is diverted to adispatcher).Figure 4 shows the relationships between the model for SS-TPI in the case of group call and the model forthe basic group call. Figures 5 and 6 show the relationships between the model for SS-TPI in the case ofindividual call and the model for the basic individual call, figure 5 in the absence of interaction withSS-CAD and figure 6, in the case of interaction with SS-CAD.SIST ETS 300 392-11-3 E1:2003

Page 13ETS 300 392-11-3: July 1999raFE22rcFE25FE1CCACCCCCCr1/r3r2r2CCAr3/r1Figure 4: Relationship between models for SS-TPI and basic call in the case of group callraFE21rbFE25FE1CCACCCCr1/r3r2CCAr3/r1Figure 5: Relationship between models for SS-TPI and basic call in the case of individual call withno interaction with SS-CADCCACCCCCCr1FE21rarbFE1FE2SS-CADrerfr2r2CCAFE25r3Figure 6: Relationship between models for SS-TPI and basic call in the case of individual call withinteraction with SS-CADSIST ETS 300 392-11-3 E1:2003

Page 14ETS 300 392-11-3: July 19995Information flows5.1Definition of information flowsIn the tables listing the elements in information flows, the column headed "Type" indicates which of theseelements are Mandatory (M), which are Optional (O) and which are Conditional (C).5.1.1ACTIVATEACTIVATE is an unconfirmed information flow across relationship rd from FE3 to FE20 which activates ordeactivates SS-TPI for one or more identities (either GTSIs or ITSIs).NOTE:The response/confirmation information flow corresponding to the ACTIVATErequest/indication information flow is ACTIVATE ACK (see subclause 5.1.2).Table 1 lists the elements within the ACTIVATE information flow.Table 1: Contents of ACTIVATEElementTypeActivated/deactivated identityM (note)Activation/deactivation requestMNOTE:May be repeated.The element activated/deactivated identity may include a GTSIs or an ITSI.The element activation/deactivation request, defined in subclause 5.2.2.5 of ETS 300 392-12-3 [3],indicates if SS-TPI is to be activated/deactivated for speech calls and/or for data calls, with or withoutmnemonic name.5.1.2ACTIVATE ACKACTIVATE ACK is actually the response/confirmation information flow corresponding to the ACTIVATErequest/indication information flow. It is thus across relationship rd from FE20 to FE3. It is used toacknowledge the activation state of SS-TPI for one or more identities.NOTE:The definition of how a given ACTIVATE ACK information flow relates to thecorresponding ACTIVATE information flow is outside the scope of the stage 2description.Table 2 lists the elements within the ACTIVATE ACK information flow.Table 2: Contents of ACTIVATE ACKElementTypeActivated/deactivated identityM (note 1)Activation/deactivation resultM (note 2)Activation stateC (notes 2 and 3)NOTE 1:May be repeated.NOTE 2:Shall be repeated as appropriate if the elementactivated/deactivated identity is repeated.NOTE 3:Present if activation/deactivation result is positive.The element activation/deactivation result, defined in subclause 5.2.2.6 of ETS 300 392-12-3 [3], indicatesif the ACTIVATE information flow request/indication has been successful or not. If it has been successful,the element activation state, defined in subclause 5.2.2.7 of ETS 300 392-12-3 [3], gives the detail aboutSS-TPI activation/deactivation.SIST ETS 300 392-11-3 E1:2003

Page 15ETS 300 392-11-3: July 19995.1.3DEFINEDEFINE is an unconfirmed information flow across relationship rd from FE3 to FE20 which definesmnemonic names of one or more individual identities.NOTE 1:The response/confirmation information flow corresponding to the DEFINErequest/indication information flow is DEFINE ACK (see subclause 5.1.4).Table 3 lists the elements within the DEFINE information flow.Table 3: Contents of DEFINEElementTypeIndividual identityM (note 1)Mnemonic nameM (note 2)NOTE 1:May be repeated.NOTE 2:Shall be repeated if the element individualidentity is repeated.NOTE 2:The DEFINE request/indication information flow may not be used with the elementidentity being a group identity.5.1.4DEFINE ACKDEFINE ACK is actually the response/confirmation information flow corresponding to the DEFINErequest/indication information flow. It is thus across relationship rd from FE20 to FE3. This flow is used toinform FE3 about the completion of the corresponding definition request.NOTE:The definition of how a given DEFINE ACK information flow relates to thecorresponding DEFINE information flow is outside the scope of the stage 2 description.Table 4 lists the elements within the DEFINE ACK information flow.Table 4: Contents of DEFINE ACKElementTypeIndividual identityM (note 1)Definition resultM (note 2)Activation stateC (note 3)NOTE 1:May be repeated.NOTE 2:Shall be repeated as appropriate if the elementindividual identity is repeated.NOTE 3:Conditional on the definition result being positive.The element definition result, defined in subclause 5.2.2.11 of ETS 300 392-12-3 [3], indicates if theDEFINE request/indication information flow has been successful or not. If it has been successful, theelement activation state, defined in subclause 5.2.2.7 of ETS 300 392-12-3 [3], gives the detail aboutSS-TPI activation/deactivation.SIST ETS 300 392-11-3 E1:2003

Page 16ETS 300 392-11-3: July 19995.1.5INFORMINFORM is an unconfirmed information flow across relationship ra from FE21 or FE22 to FE1 whichdelivers SS-TPI information to FE1.Table 5 lists the elements within the INFORM information flow.Table 5: Contents of INFORMElementTypeTalking party identityO (note)Talking party mnemonic nameOTX demand priorityONOTE:Shall be present except in the specific case where the served user at set-uptime is the connected user of an individual call. In that specific case, twoINFORM information flows may be sent, the second one being sent only tocarry the mnemonic name of the talking/sending party (i.e. the calling party), if itis available and if SS-TPI is to be provided with the corresponding subscriptionparameter, i.e. with no element talking party identity being present.The element TX demand priority, defined in subclause 5.2.2.24 of ETS 300 392-12-3 [3], indicates theurgency status that the subscriber may have added in its request to transmit.5.1.6INTERROGATEINTERROGATE is an unconfirmed information flow across relationship rd from FE3 to FE20 which isused to interrogate the home SwMI of a user known by its identity about:-the activation state of SS-TPI for this user;-the mnemonic name of this user as a potential talking/sending user.NOTE:The response/confirmation information flow corresponding to the INTERROGATErequest/indication information flow is INTERROGATE ACK (see subclause 5.1.7).Table 6 defines the content of the INTERROGATE information flow.Table 6: Contents of INTERROGATEElementTypeInterrogated identityM (note)NOTE:May be repeated.5.1.7INTERROGATE ACKINTERROGATE ACK is actually the response/confirmation information flow corresponding to theINTERROGATE request/indication information flow. It is thus across relationship rd from FE20 to FE3. Itis used to respond to the corresponding interrogation request.NOTE:The definition of how a given INTERROGATE ACK information flow relates to thecorresponding INTERROGATE information flow is outside the scope of the stage 2description.SIST ETS 300 392-11-3 E1:2003

Page 17ETS 300 392-11-3: July 1999Table 7 lists the elements within the INTERROGATE ACK information flow.Table 7: Contents of INTERROGATE ACKElementTypeInterrogated identityM (note 1)Interrogation resultM (note 2)Activation stateC (notes 2 and 3)Mnemonic nameC (notes 2 and 4)NOTE 1:May be repeated.NOTE 2:Shall be repeated as appropriate if the element interrogated identity is repeated.NOTE 3:Conditional on the interrogation result being positive.NOTE 4:May be absent even with an interrogation result positive.NOTE:The reason why no mnemonic name may be given for a user in the INTERROGATEACK response/confirmation information flow even with an interrogation result positivemay be either because the interrogated SwMI does not support mnemonic names orsimply because no mnemonic name has been given to that user.5.1.8INTERROGATE BY NAMEINTERROGATE BY NAME is an unconfirmed information flow across relationship rd from FE3 to FE20which is used to interrogate the home SwMI of a user known by its mnemonic name about the identity ofthis user and the activation state of SS-TPI for this user.NOTE:The response/confirmation information flow corresponding to the INTERROGATE BYNAME request/indication information flow is INTERROGATE BY NAME ACK (seesubclause 5.1.9).Table 8 defines the content of the INTERROGATE BY NAME information flow.Table 8: Contents of INTERROGATE BY NAMEElementTypeInterrogated mnemonic nameM (note)NOTE:May be repeated.5.1.9INTERROGATE BY NAME ACKINTERROGATE BY NAME ACK is actually the response/confirmation information flow corresponding tothe INTERROGATE BY NAME request/indication information flow. It is thus across relationship rd fromFE20 to FE3. It is used to respond to the corresponding interrogation request.NOTE:The definition of how a given INTERROGATE BY NAME ACK information flow relatesto the corresponding INTERROGATE BY NAME information flow is outside the scopeof the stage 2 description.SIST ETS 300 392-11-3 E1:2003

Page 18ETS 300 392-11-3: July 1999Table 9 lists the elements within the INTERROGATE BY NAME ACK information flow.Table 9: Contents of INTERROGATE BY NAME ACKElementTypeInterrogated mnemonic nameM (note 1)Interrogation resultM (note 2)IdentityC (notes 2 and 3)Activation stateC (notes 2 and 3)NOTE 1:May be repeated.NOTE 2:Shall be repeated as appropriate if the element interrogated mnemonic name isrepeated.NOTE 3:Conditional on the value of the element interrogation result.5.1.10NAMENAME is a confirmed information flow:-across relationships rb, and re and rf, from FE21 to FE25, in the case of an individual call to requestthe mnemonic name of the user at the other end (i.e. the calling or the connected user);-across relationship rc, from FE22 to FE25, in the case of a group call to request the mnemonicname of the calling user when such user is not a member of the group.NOTE 1:According to the specification of group call, it is not possible for users not members ofthe group other than the calling user to become talking/sending parties in a group call.The response indicates this mnemonic name, if available.NOTE 2:The response/confirmation information flow corresponding to the NAMErequest/indication information flow is NAME ACK (see subclause 5.1.11).The NAME information flow does not include any element.5.1.11NAME ACKNAME ACK is actually the response/confirmation information flow corresponding to the NAMErequest/indication information flow: it is used to indicate the requested mnemonic name, if available. It isacross relationship rb from FE25 to FE21 in the case of an individual call, and across relationship rc, fromFE25 to FE22, in the case of a group call.As a SwMI option, independent from the previous one, NAME ACK may also be an unconfirmedinformation flow across relationship rc from FE25 to FE22, i.e. with no NAME information flow sent before,when the calling user is not a member of the group. It is then sent together with the SETUPrequest/indication information flow.Table 10 defines the contents of the NAME ACK information flow.Table 10: Contents of NAME ACKElementTypeMnemonic nameM (note)NOTE:NAME ACK shall not be sent if the mnemonic namerequested is not available, as well as if FE25 does notsupport this information flow.SIST ETS 300 392-11-3 E1:2003

Page 19ETS 300 392-11-3: July 19995.1.12TX PRIORITY REQUESTTX PRIORITY REQUEST is an unconfirmed information flow used across relationship rb from FE21 toFE25, (i.e. for individual call) when the served user is the connected user. It requests that the priority levelof the request for transmission grant sent by the calling user application be relayed by FE25 to FE21 everytime this request is granted during the (individual) call.NOTE 1:The priority level of the request for transmission grant from a user is given by theelement TX demand priority included of the basic call TX request/indication informationflow.NOTE 2:This flow does not exist for an individual call when the calling user is the served usernor for a group call, since it would be redundant with the ISI-TX DEMAND basic callflow, which being addressed to the controlling SwMI is thus sent across the samerelationships as rb and rc.The TX PRIORITY REQUEST information flow does not include any element.5.1.13TX DEMAND PRIORITYTX DEMAND PRIORITY is an unconfirmed information flow used across relationships rb from FE25 toFE21, (i.e. for individual call) when FE25 has previously received TX PRIORITY REQUEST.NOTE:Thus like TX PRIORITY REQUEST this flow exists only when the served user is theconnected user.This flow is sent every time the calling user application is granted permission to transmit, to relay theelement TX demand priority included in this request.The TX DEMAND PRIORITY information flow does not include any element.5.1.14Information flow elementsThe element contents of the information flows are derived from the service primitives and operational andmanagement requirements. Unless they are self-explanatory (e.g. individual identity in table 3), thoseelements have been given the same names as the corresponding PDU information elements defined inETS 300 392-12-3 [3].5.2Relationship of information flows to basic call information flowsTable 11 shows the relationship of the SS-TPI information flows to those of the basic call, both over the airinterface and Inter-System Interface (ISI).SIST ETS 300 392-11-3 E1:2003

Page 20ETS 300 392-11-3: July 1999Table 11: Relationship of SS-TPI information flows to basic callInformation flowIndependentof basiccall?With basiccall?Basic call flows:ACTIVATEyesnoACTIVATE ACKyesnoDEFINEyesnoDEFINE ACKyesnoINTERROGATEyesnoINTERROGATE ACKyesnoINTERROGATE BY NAMEyesnoINTERROGATE BY NAME ACKyesnoINFORMyes (note 12)yesD-SETUP (note 1)ANF-ISIGC-SETUP (note 1)D-CONNECT (note 2)ANF-ISIGC-CONNECT (note 2)D-CONNECT ACKNOWLEDGE (note 3)D-MODIFY (note 4)D-TX GRANTEDANF-ISIGC-TX GRANTEDD-TX INTERRUPTANF-ISIGC-TX INTERRUPTNAMEnoyesANF-ISIIC-SETUP (note 5)ISI-CONNECT (note 6)ISI-THROUGH CONNECT(note 6)NAME ACKnoyesANF-ISIGC -SETUP (note 7)ANF-ISIIC-CONNECT (note 8)ANF-ISIIC-THROUGH CONNECT (note 8)ANF-ISIIC-CONNECT ACKNOWLEDGE(note 9)ANF-ISIIC-THROUGH CONNECTACKNOWLEDGE (note 9)ISI-TX DEMAND (note 10)TX PRIORITY REQUESTnoyesANF-ISIIC-CONNECT (note 6)ANF-ISIIC-THROUGH CONNECT (note 6)TX DEMAND PRIORITYnoyesISI-TX GRANTED (note 11)ISI-TX INTERRUPT (note 11)NOTE 1:INFORM shall be sent together with the D-SETUP request/indication information flow whentransmission permission is granted automatically at set-up time:-to the calling user, in an individual call, the served user being then the called user. Insuch a case INFORM will not include the mnemonic name, since this iname will onlybe available later to FE21 (see note 3);-to the calling user or to another user, in a group call, the served users being then thecalled users. In such a case, INFORM shall include the mnemonic name if SS-TPI isto be provided with the subscription parameter delivery of the talking party mnemonicname, unless:-SS-CLIR has been invoked for the calling user; or-the calling user is not a member of the group and the NAME ACKrequest/indication information flow has not been sent together with theISI-SETUP request/indication information flow from the originating SwMI to thegroup controlling SwMI (see note 7).In the group call case described above, where INFORM will be sent together with theD-SETUP request/indication information flow, INFORM shall first be sent by the groupcontrolling SwMI to the participating SwMI together with the corresponding ISI-SETUPrequest/indication information flow.SIST ETS 300 392-11-3 E1:2003

Page 21ETS 300 392-11-3: July 1999Information flowIndependentof basiccall?With basiccall?Basic call flows:NOTE 2:INFORM shall be sent together with the D-CONNECT information flow when the served useris the calling user and when transmission permission has been automatically granted tothe/(a) connected user in the SETUP request/indication information flow(s). This holds bothfor individual call and for group call. For the latter, INFORM shall first be sent by the groupcontrolling SwMI to the originating SwMI together with the corresponding ISI-CONNECTinformation flow.NOTE 3:If SS-TPI is to be provided with the subscription parameter delivery of the talking partymnemonic name, INFORM shall be sent together with the D-CONNECT ACKNOWLEDGEinformation flow to inform the served user about that name when:-the served user is the called user in an individual call; and-that name is available to FE21 (see note 9); and-transmission permission has been granted to the calling user (in the CONNECTinformation flow).NOTE 4:INFORM shall be sent together with the D-MODIFY information flow when:-the served user is the calling user; and-SS-CAD has been invoked for the call, with the call being diverted to a dispatcher; and-the dispatcher was the talking/sending party when he authorized the establishment ofthe call originally requested (in transferring its call with the calling user); and-the call established to the connected user has been modified compared to the callwith the dispatcher when it ended.NOTE 5:If SS-TPI is to be provided with the subscription parameter delivery of the talking partymnemonic name, the NAME request/indication information flow shall be sent together withthe ISI-SETUP request/indication information flow when the served user is the calling user inan individual call.NOTE 6:If SS-TPI is to be provided with the subscription parameter delivery of the talking partymnemonic name, the NAME request/indication information flow shall be sent together withISI-THROUGH CONNECT if the call has been diverted to a dispatcher as a result ofSS-CAD operation, and with ISI-CONNECT otherwise:-in an individual call when the served user is the connected user;-in a group call, when the calling user is not a member of this group and the NAMEACK request/indication information flow has not been sent together with theISI-SETUP request/indication information flow (see note 7).Similarly, if SS-TPI is to be provided with the subscription parameter delivery of the TXdemand priority sent by the talking party as part of its request for transmission grant, the TXPRIORITY REQUEST request/indication information flow shall be sent together with theISI-CONNECT when the served user is the connected user in an individual call. This holdseven if the call has been diverted to a dispatcher, as a result of a specific SS-CAD invocationor operation.NOTE 7:The NAME ACK request/indication information flow should be sent together with theISI-SETUP request/indication information flow in the case of a group call from the originatingSwMI to the group controlling SwMI when the calling user is not a member of this group. It isan unconfirmed information flow and not the NAME response/confirmation information flowbecause no corresponding NAME request/indication information flow can have possiblybeen sent at this stage.NOTE 8:When the NAME request/indication information flow has been sent together with theISI-SETUP request/indication information flow for an individual call, the NAME ACKrequest/indication information flow shall be sent together with:-ISI-THROUGH CONNECT if the call has been diverted to a dispatcher, as a result ofa specific SS-CAD operation;-ISI-CONNECT otherwise.NOTE 9:In an individual call, the NAME ACK request/indication information flow shall be senttogether with:-ISI-CONNECT ACKNOWLEDGE when the NAME request/indication information flowhas been sent together with ISI-CONNECT;-ISI-THROUGH CONNECT ACKNOWLEDGE when the NAME request/indicationinformation flow has been sent together with ISI-THROUGH CONNECT if the call hasbeen diverted to a dispatcher, as a result of a specific SS-CAD operation.SIST ETS 300 392-11-3 E1:2003

Page 22ETS 300 392-11-3: July 1999Information flowIndependentof basiccall?With basiccall?Basic call flows:NOTE 10:In a group call, NAME ACK shall be sent together with the ISI-TX DEMANDrequest/indication information flow sent following the first request for transmission grantmade by the calling user:-when that user is not a member of the group; and-when the NAME request/indication information flow has been sent together with theISI-CONNECT request/indication information flow for this call; and-when NAME ACK has no
...