Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 12: Call Hold (CH)

To define the Stage 2 requirements for TETRA SS Call Hold

Prizemni snopovni radio (TETRA) – Govor in podatki (V+D) – 11. del: Dopolnilne storitve stopnje 2 – 12. poglavje: Zadržanje klica (HOLD)

General Information

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Standard

Standard
EN 300 392-11-12 V1.1.1:2003
English language
22 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Prizemni snopovni radio (TETRA) – Govor in podatki (V+D) – 11. del: Dopolnilne storitve stopnje 2 – 12. poglavje: Zadržanje klica (HOLD)Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 12: Call Hold (CH)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:EN 300 392-11-12 Version 1.1.1SIST EN 300 392-11-12 V1.1.1:2003en01-december-2003SIST EN 300 392-11-12 V1.1.1:2003SLOVENSKI
STANDARD



SIST EN 300 392-11-12 V1.1.1:2003



ETSIEN300392-11-12V1.1.1(2001-01)EuropeanStandard(Telecommunicationsseries)TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part11:Supplementaryservicesstage2;Sub-part12:CallHold(CH)SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)2ReferenceDEN/TETRA-03A-11-12Keywordsdata,HOLD,radio,speech,stage2,supplementaryservice,TETRA,V+DETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.53Definitionsandabbreviations.63.1Definitions.63.2Abbreviations.64Functionalmodel.64.1Functionalmodeldescription.64.2Descriptionoffunctionalentities.74.2.1Serveduserfunctionalentity,FE1.74.2.2ServeduserSwMIfunctionalentity,FE21.74.2.3ServedusernewSwMIfunctionalentity,FE21'.84.2.4AffecteduserSwMIfunctionalentity,FE25.84.2.5Affecteduserfunctionalentity,FE5.84.3Relationshipoffunctionalmodeltobasiccallfunctionalmodel.85Informationflows.95.1Definitionofinformationflows.95.1.1INFORM1.95.1.2INFORM2.95.1.3INFORM3.95.1.4INTERROGATE.95.1.5INTERROGATEACK.95.1.6INVOKE.105.1.7INVOKEACK.105.1.8rd_LOCATIONCHANGE.115.1.9re_LOCATIONCHANGE.115.1.10RETRIEVE.125.1.11RETRIEVEACK.125.2Relationshipofinformationflowstobasiccallinformationflows.135.3Serviceprimitives.145.4Examplesofinformationflowsequences.145.4.1Interrogation.145.4.2Invocationandoperation.155.4.2.1Successfulinvocation.155.4.2.2Successfulretrievalofcallonhold.155.4.2.3Invocationfailure.165.4.2.4Retrievalfailure.165.4.2.5Migrationofserveduserwithcallsonhold.176FEactions.176.1FunctionalEntityactionsofFE1.176.2FunctionalEntityactionsofFE21.186.3FunctionalEntityactionsofFE21'.196.4FunctionalEntityactionsofFE25.196.5FunctionalEntityactionsofFE5.207Allocationoffunctionalentitiestophysicalequipment.208Interworkingconsiderations.21History.22SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)4IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSIProjectTerrestrialTrunkedRadio(TETRA).ThepresentdocumenthadbeensubmittedtoPublicEnquiryasETS300392-11-12.DuringtheprocessingforVoteitwasconvertedintoanEN.Thepresentdocumentisamulti-partstandardandwillconsistofthefollowingparts:Part1:"Generalnetworkdesign";Part2:"AirInterface(AI)";Part3:"InterworkingattheInter-SystemInterface(ISI)";Part4:"Gatewaysbasicoperation";Part5:"PeripheralEquipmentInterface(PEI)";Part6:"LineconnectedStation(LS)";Part7:"Security";Part9:"Generalrequirementsforsupplementaryservices";Part10:"Supplementaryservicesstage1";Part11:"Supplementaryservicesstage2";Part12:"Supplementaryservicesstage3";Part13:"SDLmodeloftheAirInterface(AI)";Part14:"ProtocolImplementationConformanceStatement(PICS)proformaspecification".NationaltranspositiondatesDateofadoptionofthisEN:19January2001DateoflatestannouncementofthisEN(doa):30April2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31October2001DateofwithdrawalofanyconflictingNationalStandard(dow):31October2001SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)51ScopeThepresentdocumentspecifiesthestage2descriptionoftheSupplementaryServiceCallHold(SS-HOLD)fortheTerrestrialTrunkedRadio(TETRA).SS-HOLDenablesausertointerruptcommunicationonanexistingcallandthensubsequently,ifdesired,re-establishcommunication.Man-MachineInterface(MMI)andchargingprinciplesareoutsideofthescopeofthepresentdocument.SupplementaryservicespecificationsareproducedinthreestagesaccordingtothemethoddefinedinITU-TRecommendationI.130[1].Thestage2descriptionidentifiesthefunctionalcapabilitiesandtheinformationflowsneededtosupportthesupplementaryserviceasspecifiedinitsstage1description(seeEN300392-10-12[7]).Thestage2descriptionisfollowedbythestage3description,whichspecifiestheprotocolsattheairinterfaceandatthevariousInter-SystemInterfaces(ISI)tosupporttheservice.ThepresentdocumentisapplicabletoTETRAVoiceplusDataterminalequipmentandnetworks.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublicationand/oreditionnumberorversionnumber)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.[1]ITU-TRecommendationI.130(1993):"MethodforthecharacterizationoftelecommunicationservicessupportedbyanISDNandnetworkcapabilitiesofanISDN".[2]ETSIEN300392-1:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part1:Generalnetworkdesign".[3]ETSIEN300392-2:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part2:AirInterface(AI)".[4]ETSIEN300392-3-2:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part3:InterworkingattheInter-SystemInterface(ISI);Sub-part2:AdditionalNetworkFeatureIndividualCall(ANF-ISIIC)".[5]ETSIETS300392-3-5:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part3:InterworkingattheInter-SystemInterface(ISI);Sub-part5:AdditionalNetworkFeatureforMobilityManagement(ANF-ISIMM)".[6]ETSIEN300392-9:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part9:Generalrequirementsforsupplementaryservices".[7]ETSIETS300392-10-12:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part10:Supplementaryservicesstage1;Sub-part12:CallHold(CH)".[8]ETSIEN300392-12-12:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part12:Supplementaryservicesstage3;Sub-part12:CallHold(CH)".[9]ISO/IEC11574(1994):"Informationtechnology-Telecommunicationsandinformationexchangebetweensystems-PrivateIntegratedServicesNetwork-Circuit-mode64kbit/sbearerservices-Servicedescription,functionalcapabilitiesandinformationflows".SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)63Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thedefinitionsgiveninEN300392-9[6]applywiththefollowingmodifications:affecteduser:otherpartythantheserveduserinanindividualcallserveduser:userparticipatinginanindividualcallwhoinvokesthesupplementaryserviceNOTE:Whentheserveduserhasmanycallsonhold,hemaybethecallingpartyforsomeofthemandtheconnectedpartyfortheothers.3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ANF-ISIMMAdditionalNetworkFeature-Inter-SystemInterfaceMobilityManagementCCBasicServiceCallControlfunctionalentityCCABasicServiceCallControlfunctionalentityagentNOTE1:CCandCCAareappliedasdefinedinISO/IEC11574[9].FEFunctionalEntityHOLDCallHoldISIInter-SystemInterfaceITSIIndividualTETRASubscriberIdentityLSLineStationMSMobileStationSDLSpecificationanDescriptionLanguageSSSupplementaryServiceNOTE2:TheabbreviationSSisonlyusedwhenreferringtoaspecificsupplementaryservice(e.g.SS-HOLD).SwMISwitchingandManagementInfrastructure4Functionalmodel4.1FunctionalmodeldescriptionThefunctionalmodelshallcomprisethefollowingFunctionalEntities(FEs):FE1ServeduserfunctionalentityFE21ServeduserSwMIFEFE21'ServedusernewSwMIFEFE25AffecteduserSwMIFEFE5AffecteduserFEThefollowingrelationshipsshallexist:rabetweenFE1andFE21rbbetweenFE21andFE5+rcbetweenFE21andFE25rdbetweenFE21andFE21'SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)7Figure1showstheseFEsandrelationshipsforthebasicoperationalpartofSS-HOLD,whentheserveduserdoesnotchangelocationafterhehasputa(individual)callonhold.rarbFE1FE21FE25FE5rcFigure1:FunctionalmodelforthebasicoperationalpartofSS-HOLDFigure2showstheseFEsandrelationshipsfortheoperationalpartofSS-HOLD,whentheserveduserchangeslocationafterhehasputa(individual)callonhold.FE21FE1raFE25rcFE21'rerdFE5rbFigure2:FunctionalmodelfortheoperationalpartofSS-HOLDwithlocationchangeoftheserveduserNOTE:Bothfigures1and2applyonlyinthecaseofindividualcallsinceSS-HOLDdoesnotapplytogroupcall.4.2Descriptionoffunctionalentities4.2.1Serveduserfunctionalentity,FE1FE1isthefunctionalentitythatservesthecallinguserfortheinvocationofSS-HOLD.Iftheserveduserchangeslocationwithoneormoreindividualcallstillonhold,FE1maybeinformedbyFE21'aboutpossiblechangesforthosecalls.Itwillprocessthatinformationaccordingtoitscontents;notablyifitindicatesacallreferencechangeforsomecallsonhold,itwillupdateaccordinglyitscallreferencesforthosecalls.FE1mayalsorelaytheinterrogationrequestsreceivedfromtheservedusertoFE21,andthecorrespondingresponsesfromFE21totheserveduser(asindicationprimitives).4.2.2ServeduserSwMIfunctionalentity,FE21WhenitreceivesaSS-HOLDinvocationfromFE1,FE21checkswhetherSS-HOLDhasbeenactivated(i.e.subscribed)and,ifso,putsthecallonhold,ininformingFE5andFE25.Iftheserveduserchangeslocationwithanindividualcallstillonhold,FE21mayattempttocreateFE21'.Ifthatattemptissuccessful,FE21passesthedataaboutthatcalltoFE21'.Ifnot,itinformsthecollocatedindividualcallcontrolentityaboutthesituation.SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)84.2.3ServedusernewSwMIfunctionalentity,FE21'Iftheserveduserchangeslocationwithacallstillonhold,FE21'maybecreated.FE21'thenreceivesthedataaboutthatcall,informsFE1aboutthecallsonholdforwhichoneofthetwofollowingchangeshasoccurredduetothelocationchange:callreferencechangedorcalllost.AfterthatFE21'replacesFE21.4.2.4AffecteduserSwMIfunctionalentity,FE25FE25receivesfromFE21theinformationthatSS-HOLDhasbeeninvoked(bytheserveduser)forthecallandpassesittothecollocatedindividualcallcontrolentity.4.2.5Affecteduserfunctionalentity,FE5FE5isthefunctionalentitythatservestheaffectedusertoinformhimwhenthecallhasbeenputonholdandthen,whenitisretrieved.4.3RelationshipoffunctionalmodeltobasiccallfunctionalmodelAlthoughnoformalmodelshavebeendefinedforbasicindividualcallnorforbasicgroupcall,thosemodelscanbereadilyderivedfromthePISNmodelforbasiccall,inISO/IEC11574[9].FE1shallbecollocatedwiththeCCAofthecallinguserorofthecalleduserinanindividualcall.FE21shallbecollocatedwiththeCCfunctionalentityintheserveduserSwMIinanindividualcall.Dependingonwhethertheserveduserhasroamedormigrated(withoneormoreindividualcallsonhold),FE21'shallbecollocatedwiththeCCfunctionalentityeither:-inthesameserveduserSwMIiftheserveduserhasroamed;-intheservedusernewSwMIiftheserveduserhasmigrated.FE5shallbecollocatedwiththeCCAoftheremotepartyinanindividualcall.Figure3showstherelationshipbetweenthemodelsforSS-HOLDandforthebasicindividualcall.CCACCCCCCACC(note)FE5r3/r1r2r2r1/r3FE25FE1FE21rcrbraNOTE:ItispossiblethatnointermediateCCbepresent(i.e.whenthecalleduser(whetherheistheserveduserorthe/anaffecteduser)isregisteredinhishomeSwMIandwhennotransitPrivateIntegrated(services)NetworkExchanges-PINXs-arepresent).Figure3:RelationshipbetweenmodelsforSS-HOLDandbasicindividualcallSIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)95Informationflows5.1DefinitionofinformationflowsInthetableslistingtheinformationelementsininformationflows,thecolumnheaded"Type"indicateswhichoftheseelementsareMandatory(M),whichareOptional(O)andwhichareConditional(C).5.1.1INFORM1INFORM1isanunconfirmedinformationflow:-acrossrelationshiprbfromFE21toFE5toinformtheaffecteduseraboutthesuccessfulresultofSS-HOLDinvocation;-acrossrelationshiprcfromFE21toFE25toinformtheaffecteduserSwMIaboutthesuccessfulresultofSS-HOLDinvocation.Therearenoelementsinthatinformationflow.5.1.2INFORM2INFORM2isanunconfirmedinformationflow:-acrossrelationshiprbfromFE21toFE5toinformtheaffecteduseraboutthesuccessfulretrievalofthecall(previouslyonhold);-acrossrelationshiprcfromFE21toFE25toinformtheaffecteduserSwMIaboutthesuccessfulthesuccessfulretrievalofthecall(previouslyonhold).Therearenoelementsinthatinformationflow.5.1.3INFORM3INFORM3isanunconfirmedinformationflowacrossrelationshiprbfromFE21toFE5toinformtheaffecteduserthatthecallonholdisbeingclearedbecausetheserveduserhaschangedlocationandeithertheFE21'functionalentitycannotbecreated(e.g.caseofmigrationintoanewSwMIthatdoesnotsupportSS-HOLD)oritcannottakeoverFE21roletosupportalaterrequestfromtheserveduser(afterthechangelocationprocedurehasbeencompleted)toretrievethecallonhold.Therearenoelementsinthatinformationflow.5.1.4INTERROGATEINTERROGATEisanunconfirmedinformationflowacrossrelationshiprafromFE1toFE21whichisusedtointerrogatetheserveduserSwMIaboutthecallscurrentlystillonholdfortheserveduser.NOTE:Theresponse/confirmationinformationflowcorrespondingtotheINTERROGATErequest/indicationinformationflowisINTERROGATEACK(seeclause5.1.5).Therearenoelementsinthatinformationflow.5.1.5INTERROGATEACKINTERROGATEACKisactuallytheresponse/confirmationinformationflowcorrespondingtotheINTERROGATErequest/indicationinformationflow.ItisthusacrossrelationshiprafromFE21toFE1.Itisusedtorespondtothecorrespondinginterrogationrequest.SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)10Table1liststheelementswithintheINTERROGATEACKinformationflow.Table1:ContentsofINTERROGATEACKElementTypeInterrogationresultMNumberofcallsbeingonholdC(note1)CallreferenceC(note2)AffecteduserITSIC(note2)InterrogationfailurecauseC(note3)NOTE1:Conditionalontheinvocationresultbeingpositive.NOTE2:Conditionalontheinvocationresultbeingpositive.Shallthenberepeatedforeachcallonhold.NOTE3:Conditionalontheinvocationresultbeingnegative.Theelementinterrogationresultshallindicatewhetherthecorrespondinginterrogationrequesthasbeensuccessfulornot.Theelementnumberofcallsbeingonholdshallindicatehowmanycallsarecurrentlystillonholdfortheserveduser(i.e.callspreviouslyputonholdbytheserveduserandnotretrievedordisconnected).TheelementcallreferenceshallidentifythecallintheserveduserSwMI.TheelementGTSIshallcontaintheidentityofthegroupofwhichthecallisonhold.Theelement-affecteduserITSIshallindicatetheidentityoftheotherpartythantheserveduserinanindividualcallonhold.TheITSIofanindividualsubscriberisdefinedinclause7.2.2ofEN300392-1[2].Theelementinterrogationfailurecauseshallindicatethereasonwhytheinterrogationrequestbytheserveduserhasfailed.Thatreasonmaybee.g.becauseFE21doesnotsupporttheinterrogationprocedure.5.1.6INVOKEINVOKEisanunconfirmedinformationflowacrossrelationshiprafromFE1toFE21toinvokeSS-HOLD.NOTE:Theresponse/confirmationinformationflowcorrespondingtotheINVOKErequest/indicationinformationflowisINVOKEACK(seeclause5.1.7).Therearenoelementsinthatinformationflow.5.1.7INVOKEACKINVOKEACKisactuallytheresponse/confirmationinformationflowcorrespondingtotheINVOKErequest/indicationinformationflow.ItisthusacrossrelationshiprafromFE21toFE1.Itisusedtorespondtothecorrespondinginvocation.Table2liststheelementswithintheINVOKEACKinformationflow.Table2:ContentsofINVOKEACKElementTypeInvocationresultMInvocationfailurecauseC(note)NOTE:Conditionalontheinvocationresultbeingnegative.Theelementinvocationresultshallindicatewhetherthecorrespondinginvocationrequestbytheserveduserhasbeensuccessfulornot.Theelementinvocationfailurecauseshallindicatethereasonwhytheinvocationrequestbytheserveduserhasfailed.Thatreasonmaybee.g.becausethemaximumnumberofcallsonholdforFE1hasalreadybeenreached.SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)11NOTE:TheabovestatementimpliesthatthereisaFE21functionalentity.OtherwisebydefinitionthereisnoINVOKEACKinformationflow(sincetheserveduserSwMIdoesnotsupportSS-HOLD).Ifthisisthecase,theserveduserwhohasinvokedSS-HOLDwillbeinformedaboutitbythegenericfailurecausedefinedinEN300392-9[6]clause11.2.1.5.1.8rd_LOCATIONCHANGErd_LOCATIONCHANGEisanunconfirmedinformationflowacrossrelationshiprdfromFE21'toFE1inthecaseoflocationchangeoftheservedusertoallowthelaterretrievalofthecallsstillonhold.ThesupportofthatinformationflowisoptionalforFE21',butmandatoryforFE1(i.e.ifFE21'sendsthatinformationflow,FE1hasfirsttoreceiveit,secondtoactaccordingtoitsinformation).Table3liststheelementswithintherd_LOCATIONCHANGEinformationflow.Table3:Contentsofrd_LOCATIONCHANGEElementTypeLocationchangeproceduresupportMCallreferenceupdateO(note1)CallslostO(note2)NOTE1:Ifthelocationchangeprocedureissupported(informationgivenbytheelementlocationchangeproceduresupport):-maybepresentinthecaseofroaming(i.e.FE21'locatedinthesameSwMIasFE21);-shallbepresentinthecaseofmigration(i.e.FE21'locatedinanotherSwMIthanFE21).NOTE2:Shallbepresentifthelocationchangeprocedureissupportedandifcallshavebeenlostduringthatprocedure(e.g.bylackofresources).TheelementlocationchangeproceduresupportshallindicatewhetherornotFE21'cantakeoverFE21roletosupportalaterrequestfromtheserveduser(afterthechangelocationprocedurehasbeencompleted)toretrievethecallonhold.NOTE:ThechoicehasbeenmadenottoconsiderthecasewherethecallcontrolentitycollocatedwithFE21'wouldsupporttheprocedureforkeeping"alive"callsstillonholdwhentheserveduserhaschangedlocationbutwouldnotbeabletosupportanylaterretrievalrequestforsuchcalls:thereasonforthatchoiceisthatsuchFE21'wouldnothavebeenabletosuccessfullytakeoverFE21roleforthepossiblelaterrequestfromtheservedusertoretrieveanyofhiscallsonhold.Theelementcallreferenceupdateshallindicatethenewcallreferenceswhentheyhavechangedduetothelocationchange.Theelementcallslostshallindicatethecallsonholdwhichhavebeenclearedduringthelocationchangeprocedure.5.1.9re_LOCATIONCHANGEre_LOCATIONCHANGEisaconfirmedinformationflowacrossrelationshiprefromFE21toFE21'inthecaseoflocationchangeoftheservedusertoallowthelaterretrievalofhiscallsonhold.ThesupportofthatinformationflowisoptionalforbothFE21andFE21'.NOTE1:re_LOCATIONCHANGEisovertheInter-SystemInterface(ISI)onlywhentheserveduserchangeslocationinregisteringinanewSwMI(i.e.accordingtoTETRAterminology,theservedusermigrates).Otherwise,whentheserveduserchangeslocationwithinthesameSwMI(i.e.accordingtotheTETRAterminology,theserveduserroams),re_LOCATIONCHANGEisinternaltothatSwMI.Table4definesthecontentofthere_LOCATIONCHANGErequest/indicationinformationflowandtable5,thatofthere_LOCATIONCHANGEresponse/confirmationinformationflow.Table4:Contentofre_LOCATIONCHANGErequest/indicationElementTypeNumberofcallsonholdMTheelementnumberofcallsonholdshallindicatehowmanycallstheserveduserhasstillonhold.SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)12Table5:Contentofre_LOCATIONCHANGEresponse/confirmationElementTypeLocationchangesupportMTheelementlocationchangesupportshallindicatewhetherornotFE21'cantakeoverFE21roletosupportalaterrequestfromtheserveduser(afterthechangelocationprocedurehasbeencompleted)toretrievethecallonholdtowhichthere_LOCATIONCHANGEresponse/confirmationinformationflowrefers.NOTE2:Seenoteinclause5.1.8.5.1.10RETRIEVERETRIEVEisanunconfirmedinformationflowacrossrelationshiprafromFE1toFE21torequesttheretrievalofacallonhold.NOTE:Theresponse/confirmationinformationflowcorrespondingtotheRETRIEVErequest/indicationinformationflowisRETRIEVEACK(seeclause5.1.11).Table6definesthecontentoftheRETRIEVEinformationflow.Table6:ContentofRETRIEVEElementTypeCallreferenceMTheelementcallreferenceshallidentifythecalltoberetrieved.5.1.11RETRIEVEACKRETRIEVEACKisactuallytheresponse/confirmationinformationflowcorrespondingtotheRETRIEVErequest/indicationinformationflow.ItisthusacrossrelationshiprafromFE21toFE1.Itisusedtorespondtothecorrespondingretrievalrequest.Table7liststheelementswithintheRETRIEVEACKinformationflow.Table7:ContentsofRETRIEVEACKElementTypeCallreferenceMRetrievalresultMRetrievalfailurecauseC(note)NOTE:Conditionalontheretrievalresultbeingnegative.Theelementcallreferenceshallidentifythecallretrieved.Theelementretrievalresultshallindicatewhetherthecorrespondingretrievalrequestbytheserveduserhasbeensuccessfulornot.Theelementinvocationfailurecauseshallindicatethereasonwhytheretrievalrequestbytheserveduserhasfailed.Thatreasonmaybee.g.becausethecallhasbeenclearedinthemeantime.SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)135.2RelationshipofinformationflowstobasiccallinformationflowsTable8showstherelationshipoftheSS-HOLDinformationflowstothoseofbasiccalloverboththeairinterfaceandtheintersysteminterface(ISI).NOTE:Thebasicindividualcallinformationflowsaredefined:-fortheairinterface,ifnotexplicitlyinEN300392-2[3],atleastimplicitlyinclauses11and14ofthepresentdocument;and-fortheISI,inEN300392-3-2[4].Table8:RelationshipofSS-HOLDinformationflowstobasiccallInformationflowIndependentofbasiccall?Withbasiccall?Basiccallflows:INFORM1yesnoINFORM2yesyesISI-CALLRESTORATION(note2)INFORM3noyesD-RELEASE(note3)INTERROGATEyes(note1)noINTERROGATEACKyes(note1)noINVOKEyesnoINVOKEACKyesnord_LOCATIONCHANGEyes(note1)nore_LOCATIONCHANGErequest/indicationnoyesCALLRESTOREPREPARErequest/indication(note4)re_LOCATIONCHANGEresponse/confirmationnoyesCALLRESTOREPREPAREresponse/confirmation(note4)RETRIEVEyesnoRETRIEVEACKyesnoNOTE1:Thisinformationflowisnotonlyindependentofbasiccall,butcallunrelated.NOTE2:INFORM2issenttogetherwiththe(ANF)-ISI(IC)-CALLRESTORATIONinformationflowiftheserveduserretrievesthecallonholdafterhavingchangedlocationinregisteringinanewSwMI(i.e.afterhavingmigrated)whilethecallwasonhold.NOTE3:InadditionifthecallisovertheISI(i.e.theterminatingSwMIisdifferentfromtheoriginatingSwMI),INFORM3issenttogetherwiththeANF-ISIICRELEASEinformationflow.NOTE4:TheCALLRESTOREPREPARErequest/indicationandresponse/confirmationinformationflowsareISIbasicindividualcallinformationflowsonlywhentheserveduserchangeslocationinregisteringinanewSwMI(i.e.theservedusermigrates).TheCALLRESTOREPREPARErequest/indicationinformationflowisthensenttogetherwiththePISNSETUPrequest/indicationinformationflow.Ifthatinformationflowissuccessful,thecorrespondingCALLRESTOREPREPAREresponse/confirmationinformationflowissenttogetherwiththePISNSETUPresponse/confirmationinformationflow(thePISNSETUPresponse/confirmationinformationflowtranslatesintothePSS1CONNECTmessageinthecorrespondingprotocol).Ifthatinformationflowisunsuccessful,thecorrespondingCALLRESTOREPREPAREresponse/confirmationinformationflowissenttogetherwiththePISNRELEASErequest/indicationinformationflow.WhentheserveduserchangeslocationwithinthesameSwMIwithacallstillonhold(i.e.theserveduserroams),theCALLRESTOREPREPARErequest/indicationandresponse/confirmationinformationflowsremaininternaltothatSwMI.SIST EN 300 392-11-12 V1.1.1:2003



ETSIETSIEN300392-11-12V1.1.1(2001-01)145.3ServiceprimitivesThisclauselistsSS-HOLDserviceprimitivesusedtoinvokeorbeingaresultofinformationflowsequences.TheSS-HOLDserviceprimitivesaredefinedinEN300392-12-12[8]clause5.4.TheSS-HOLDserviceprimitivesfortheserveduserattheMS/LSTNSS-SAPshallbe:-INTE
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.