SIST EN 301 846 V1.1.1:2005

• Abstract:

  Profile Standard specifying the combination of base Standards, together with selection of options and parameter values for the use of QSIG/PSS1 in Air Traffic Management communication networks.

• Status: Published
• Publication Date: 28-Feb-2005
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Mar-2005
• Due Date: 01-Mar-2005
• Completion Date: 01-Mar-2005
• Mandate: M/239
• Ref Project: ETSI EN 301 846 V1.1.1 (2001-07) - Private Integrated Services Network (PISN); Profile Standard for the use of PSS1 (QSIG) in Air Traffic Services networks

SIST EN 301 846 V1.1.1:2005 is the Slovenian adoption of ETSI EN 301 846 Version 1.1.1, published by SIST. It is a profile standard for Private Integrated Services Network (PISN) signalling in Air Traffic Services (ATS) networks, specifying how PSS1 (QSIG) is used between Private Integrated services Network eXchanges (PINX) so implementations from different vendors can interoperate.

What does SIST EN 301 846 V1.1.1:2005 specify?

SIST EN 301 846 V1.1.1:2005 specifies the combination of base standards, selected options and parameter values needed to use QSIG/PSS1 in Air Traffic Management communication networks. It covers the interface behaviour, call handling and supplementary services needed for ATS use.

The scope includes:

• physical and electrical characteristics at the interface to the transmission system
• data link layer procedures for error-free communication
• network layer procedures for call establishment and clearing
• supplementary services needed for ATS requirements

The standard is organized into clauses 1 to 11 and five annexes.

Annex	What it covers
A	Requirements List (RL) linked to PICS proformas
B	Profile-specific ICS proforma
C	Procedures for detecting and resolving Simultaneous Call Attempts on a single Inter-PINX Link
D	Informative encodings for Facility information element contents
E	Bibliography

What are the key requirements of SIST EN 301 846 V1.1.1:2005?

SIST EN 301 846 V1.1.1:2005 turns the general QSIG/PSS1 standards into a concrete ATS profile. In practice, that means an implementation must support the exact signalling choices, message contents and timing values needed for predictable interworking.

Physical and link behaviour

• Clause 8 requires speech compression with ITU-T G.728 for 16 kbit/s speech calls when the PINX acts as an End PINX. A Transit PINX must not decompress and recompress speech, which avoids unnecessary voice impairment.
• Clause 9 requires the physical and electrical interface from ETS 300290 and the 4 x 16 kbit/s sub-multiplexing defined in EN 301039. The Mapping (MP) function also has to support Alarm Indication Signal (AIS) handling and synchronization choices.
• Clause 9.2 requires the data link layer procedure from ETS 300402-2 Annex ZA with ATS profile choices such as continuous flags when no layer 3 information is sent and configured layer 2 timer values. This gives the link stable, testable behaviour.

Call control and signalling

• Clause 10 modifies EN 300172 for ATS use. A PINX must generate complete SETUP messages with Sending complete, defined bearer capability coding, defined numbering plan values, and Transit counter information.
• Clause 10.6 and 10.7 define channel selection and channel agreement rules. The A side starts from the lowest available channel number, the B side from the highest, and the first response can select an alternative channel. This matters when several calls compete for limited B-channels.
• Clause 10.13 and 10.14 address call collisions and Simultaneous Call Attempts. Annex C gives an optional method for a single Inter-PINX Link, so implementers can avoid ambiguous busy outcomes.
• Clause 10.16 fixes key timer values, and clause 10.18 limits restart use to all channels, not single channels. This keeps management actions consistent across implementations.

Supplementary services and transport

• Clause 10.19 limits the Generic Functional Protocol to Remote Operations Service Element (ROSE) and connection-oriented APDU transport. That reduces implementation scope to the parts used by ATS supplementary services.
• Clauses 10.21 and 10.22 require support for call priority interruption and intrusion, plus the Transit counter ANF. These features let higher-priority ATS traffic pre-empt lower-priority calls when needed.

What terms does SIST EN 301 846 V1.1.1:2005 define?

• Call Control (CC) - The function that controls calls between TE functions, including protocol control and the supplementary-service control parts used by QSIG/PSS1.
• Mapping (MP) - The function that adapts the PINX to the external transmission facility and handles multiplexing and rate adaptation.
• Private Integrated Services Network eXchange (PINX) - A network exchange inside a PISN that participates in the inter-PINX signalling defined by this profile.
• Private Termination System (PTS) - The part that provides signalling and transmission between Terminal Equipment (TE) and Switching (SW).
• Alarm Indication Signal (AIS) - An all-one-bit pattern used as an indication that the transmission facility or peer PINX is out of service.
• Requirements List (RL) - Annex A list that identifies which profile capabilities are mandatory, optional or excluded for conformance testing.
• Implementation Conformance Statement (ICS) - A supplier statement of which profile capabilities and options are implemented.

Who uses SIST EN 301 846 V1.1.1:2005?

SIST EN 301 846 V1.1.1:2005 is used by equipment suppliers, system integrators, airport and air traffic telecommunication specialists, and conformity testers working on ATS PISNs. It is especially relevant when a PINX must interoperate with another vendor’s equipment and when a supplier must complete the profile-specific ICS or support conformance testing.

Which standards are used with SIST EN 301 846 V1.1.1:2005?

Reference	Contribution
EN 300172	Base circuit-mode basic services call control and call establishment/clearing procedures
ETS 300239	Generic Functional Protocol for supplementary services
ETS 300290 and Amendment 1	64 kbit/s digital unrestricted leased line interface used for the physical layer
ETS 300402-2	Datalink layer general protocol specification, including Annex ZA used here
EN 300402-4	PICS proforma specification for the general protocol
EN 300426	Call intrusion supplementary service
ETS 300475-1	PISN reference configuration and reference points
EN 301039	Mapping functions for 64 kbit/s circuit-mode connections with 16 kbit/s sub-multiplexing
EN 301048	Transit counter additional network feature
EN 301656	Call priority interruption and call priority interruption protection supplementary services
ISO/IEC 9646-7	Conformance testing and ICS methodology
ITU-T G.728	16 kbit/s LD-CELP speech coding
ITU-T T.50	7-bit coded character set used for number encoding
ITU-T Z.100	Specification and Description Language (SDL)

What does the SIST EN 301 846 V1.1.1:2005 document contain?

The document contains the profile scope, conformance statement, normative references, definitions and abbreviations, then detailed functional clauses for the specification framework, physical interface, switching, mapping and call control. It also includes the Requirements List in Annex A, the profile-specific ICS proforma in Annex B, a worked procedure for Simultaneous Call Attempts in Annex C, and example ASN.1/Facility information element encodings for supplementary services in Annex D. Annex E provides bibliography references used by the profile.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Zasebno omrežje z integriranimi storitvami (PISN) - Standard profila za uporabo PSS1 (QSIG) v omrežjih s storitvami radijskega prometaPrivate Integrated Services Network (PISN); Profile Standard for the use of PSS1 (QSIG) in Air Traffic Services networks33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 846 Version 1.1.1SIST EN 301 846 V1.1.1:2005en01-marec-2005SIST EN 301 846 V1.1.1:2005SLOVENSKI
STANDARD
ETSIEN301846V1.1.1(2001-07)EuropeanStandard(Telecommunicationsseries)PrivateIntegratedServicesNetwork(PISN);ProfileStandardfortheuseofPSS1(QSIG)inAirTrafficServicesnetworksSIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)2ReferenceDEN/ECMA-00189KeywordsPISN,PSS1,QSIGETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°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:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)3ContentsIntellectualPropertyRights.6Foreword.61Scope.72Conformance.73References.74Definitions.84.1Externaldefinitions.85Abbreviations.96Specificationframework.106.1General.106.2TerminalEquipment(TE).106.3PrivateTerminationSystem(PTS).106.4Switching(SW).116.5Mapping(MP).116.6CallControl(CC).117PhysicalinterfaceandprotocolstackattheCreferencepoint.128Switching(SW)functions.128.1Speechcompression.129Mapping(MP)functions.139.1Physicallayerfunctions.139.1.1Physicalandelectricalinterfacerequirements.139.1.2Rateadaptationandsub-multiplexing.139.1.3AlarmIndicationSignal(AIS).139.1.4Synchronization.139.2Datalinklayerfunctions.149.2.1Generalprocedures.149.2.2Systemparameters.149.3Octetsynchronizationprocedure.1510CallControl(CC)functions-EndPINXcase.1510.1Basiccallestablishmentandclearing.1510.2Messagesegmentationandre-assembly.1510.3STATUSENQUIRYprocedure.1510.4Overlapsending/receivingprocedures.1510.5CallrequestandtransmissionoftheSETUPmessage.1510.6Informationchannelselection.1610.7Agreementofchannelandcallproceeding.1610.8Callconfirmationindication.1710.9Callconnected.1710.10UseofthePROGRESSmessage.1710.11Failureofcallestablishment.1710.12Callclearing.1710.13Callcollisions.1710.14Simultaneouscallattempts.1810.15Alternativerouteing.1810.16Timervalues.1810.17Supportofinformationelements.1910.17.1General.1910.17.2Bearercapability.1910.17.3Callstate.2010.17.4Calledpartynumber.20SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)410.17.5Callingpartynumber.2010.17.6Cause.2110.17.7Channelidentification.2110.18Restartprocedureforlayermanagement.2110.19GenericFunctionalProtocol.2110.19.1ApplicablepartsoftheGenericFunctionalProtocol.2110.19.2Supportofinformationelements.2210.19.3Integerencodingofoperationvalues.2210.20Specificsupplementaryservices.2310.21Priorityinterruptionandintrusion.2310.21.1Signallingprocedures.2310.21.2Callcontrolprocedures.2310.21.3InvocationofpriorityfunctionsatOriginatingPINX.2410.21.4ExecutionofSS-CPI.2510.22Transitcounter.2511CallControl(CC)functions-TransitPINXcase.2511.1General.25AnnexA(normative):RequirementsList(RL).27A.1General.27A.2RelationshipbetweenRLandcorrespondingPICSproformas.27A.3RequirementList.27A.3.1Tablesforthephysicallayer.27A.3.2Tablesforthedatalinklayer(D-channel).28A.3.2.1Majorcapabilities.28A.3.2.2Framesreceived.28A.3.2.3Framestransmitted.28A.3.3Tablesforthenetworklayer.28A.3.3.1BasicCall(EN300172).28A.3.3.1.1Bearerssupported.28A.3.3.1.2StatusandStatusEnquiryprotocolprocedures.29A.3.3.1.3Circuitswitchedcallcontrol.29A.3.3.1.4Proceduresforlayermanagement.29A.3.3.1.5Timers.29A.3.3.1.6Messagesandinformationelementsforgeneralprocedures.30A.3.3.1.7Messagesegmentation/re-assemblyprocedures.30A.3.3.1.8Partycategoryfunctionality.30A.3.3.2GenericFunctionalProtocol.31A.3.3.2.1CallrelatedprotocolcontrolandGFT-Controlrequirements.31A.3.3.2.2ConnectionlessADPUtransportmechanism.31A.3.3.2.3ConnectionorientedAPDUtransportmechanism.31A.3.3.2.4CoordinationFunctionrequirements.31A.3.3.2.5ACSEandDSErequirements.31A.3.3.2.6Implementedparameters.31A.3.3.2.6.1ALERTINGmessage.31A.3.3.2.6.2CONNECTmessage.32A.3.3.2.6.3SETUPmessage.32A.3.3.2.6.4DISCONNECTmessage.32A.3.3.2.6.5RELEASEmessage.32A.3.3.2.6.6RELEASECOMPLETEmessage.32A.3.3.2.6.7FACILITYmessage.32A.3.3.2.6.8NOTIFYmessage.32A.3.3.2.6.9PROGRESSmessage.32A.3.4TablesforSupplementaryServicesandANFs.33A.3.4.1Callintrusion.33A.3.4.1.1General.33A.3.4.1.2Procedures.34A.3.4.1.3Coding.35A.3.4.1.4Timers.36SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)5A.3.4.2Callpriorityinterruption(protection).36A.3.4.2.1General.36A.3.4.2.2Procedures.36A.3.4.3Transitcounter.37A.3.4.3.1General.37AnnexB(normative):ProfilespecificICSproforma.38B.1General.38B.2InstructionforcompletingtheICSproforma.38B.2.1GeneralstructureoftheICSproforma.38B.2.2AdditionalInformation.39B.2.3ExceptionInformation.39B.3ICSproforma.39B.3.1ImplementationIdentification.39B.3.2Supportedinterfacesandprotocols.40B.3.3Physicallayer.40B.3.4Datalinklayer.40B.3.5Networklayer(BasicCall).41B.3.6Networklayer(GenericFunctionalProtocol).41B.3.7Priorityinterruptionandintrusionsupplementaryservices.41B.3.8TransitcounterANF.41AnnexC(normative):ProceduresfordetectingandresolvingSimultaneousCallAttemptsonasingleInter-PINXLink.42C.1General.42C.2Descriptionofprocedure.42C.2.1Detectionofasimultaneouscallattempt.42C.2.2Callswithoutcallcollision.42C.2.3Callsofequalpriorityandcallcollision.43C.2.4Callsofunequalpriorityandcallcollision.43C.3SpecificationandDescriptionLanguage(SDL)representationofprocedures.43AnnexD(informative):Facilityinformationelementcontentsencoding.50D.1General.50D.2callintrusionRequestinvoke(ciRequest.inv)operation.50D.3callintrusionRequestresult(ciRequest.res)operation.51D.4callintrusionGetCIPLinvoke(ciGetCIPL.inv)operation.52D.5callIntrusionGetCIPLresult(ciGetCIPL.res)operation.53D.6callIntrusionCompletedinvoke(ciCompleted.inv)operation.54D.7Callintrusionnotifications.55D.8Callintrusionerrors.56D.9callInterruptionRequestinvoke(cpiRequest.inv)operation.59D.10callProtectionRequestinvoke(cpipRequest.inv)operation.60D.11Callpriorityinterruptionnotifications.61AnnexE(informative):Bibliography.62History.63SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)6IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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)hasbeenproducedbyECMAonbehalfofitsmembersandthoseoftheEuropeanTelecommunicationsStandardsInstitute(ETSI).ThepresentdocumentisoneofaseriesofStandardsdefiningservicesandsignallingprotocolsapplicabletoPrivateIntegratedServicesNetworks(PISNs).TheseriesusesISDNconceptsasdevelopedbyITU-TandconformstotheframeworkofInternationalStandardsforOpenSystemsInterconnectionasdefinedbyISO/IEC.ThepresentdocumentspecifiesthefunctionalprofileforinterconnectingPrivateIntegratedservicesNetworkeXchanges(PINX)inAirTrafficServices(ATS)PISNstopermitinteroperabilitybetweenequipmentfromdifferentvendors.Itresultsfromamandate(M/239)fromtheCommissionoftheEuropeanCommunity(CEC)forstandardizationinthefieldofairtrafficmanagementequipmentandsystems.NationaltranspositiondatesDateofadoptionofthisEN:27July2001DateoflatestannouncementofthisEN(doa):31October2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):30April2002DateofwithdrawalofanyconflictingNationalStandard(dow):30April2002SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)71ScopeThepresentdocumentspecifiesthecombinationofbasestandards,togetherwiththeselectionofappropriateoptionsandparametervalues,necessarytospecifyhowQSIG/PSS1canbeusedtoprovidedigitalsignallingcapabilitiesbetweenPrivateIntegratedservicesNetworkseXchange(PINX)inanAirTrafficServices(ATS)PISN.Thepresentdocumentdefines:-physicalandelectricalcharacteristics(physicallayer)oftheinterfacestothetransmissionsystemstobeemployed;-datalinklayerprocedurestoensureerror-freecommunicationslinks;-networklayerproceduresforcallestablishmentandclearing;and-supplementaryservicestomeetspecificATSrequirements.ThepresentdocumentstatesrequirementsuponimplementationsinordertoachieveinteroperabilitybetweenequipmentinATSPISNs.NOTE1:Implementationofthepresentdocumentdoesnotprecludeamanufacturerfromofferingothermeansofinterconnection.ThepresentdocumentdoesnotspecifyrequirementsrelatedtointerworkingbetweenQSIGandothersignallingsystemsusedinATSPISNs.2ConformanceAsystemconformstothepresentdocumentifitcorrectlyperformsallthemandatorycapabilitiesdefinedintheRequirementList(RL)(annexA)andtheprofilespecificImplementationConformanceStatement(ICS)(annexB).Notethatmorecapabilitiesmaybemandatorythaninthebasestandards.3ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublicationand/oreditionnumberorversionnumber)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.ETSIEN300172:"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Circuit-modebasicservices[ISO/IEC11572(1996)modified]".ETSIETS300239(1995):"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Genericfunctionalprotocolforthesupportofsupplementaryservices[ISO/IEC11582(1995),modified]".ETSIETS300290(1994):"BusinessTeleCommunications(BTC);64kbit/sdigitalunrestrictedleasedlinewithoctetintegrity(D64U);Terminalequipmentinterface".ETSIETS300290,Amendment1(1995):"BusinessTeleCommunications(BTC);64kbit/sdigitalunrestrictedleasedlinewithoctetintegrity(D64U);Terminalequipmentinterface".ETSIETS300402-2(1995):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Datalinklayer;Part2:Generalprotocolspecification[ITU-TRecommendationQ.921(1993),modified]".SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)8ETSIEN300402-4(V1.2.3):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Datalinklayer;Part4:ProtocolImplementationConformanceStatement(PICS)proformaspecificationforthegeneralprotocol".ETSIEN300426:"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Callintrusionsupplementaryservice[ISO/IEC14846(1996),modified]".ETSIETS300475-1:"PrivateTelecommunicationNetwork(PTN);Referenceconfiguration;Part1:ReferenceconfigurationforPTNeXchanges(PTNX)[ISO/IEC11579-1(1994),modified]".ETSIEN301039:"PrivateIntegratedServicesNetwork(PISN);Mappingfunctionsfortheemploymentof64kbit/scircuitmodeconnectionswith16kbit/ssub-multiplexing".ETSIEN301048:"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Transitcounteradditionalnetworkfeature[ISO/IEC15056(1997)modified]".ETSIEN301656:"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Callpriorityinterruptionandcallpriorityinterruptionprotectionsupplementaryservices;[ISO/IEC15992(1998),modified]".ISO/IEC9646-7(1994):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part7:ImplementationConformanceStatements".ITU-TRecommendationG.728(1992):"Codingofspeechat16kbit/susinglow-delaycodeexcitedlinearprediction".ITU-TRecommendationT.50(1992):"Informationtechnology-7-bitcodedcharactersetforinformationinterchange".ITU-TRecommendationZ.100(1993):"Specificationanddescriptionlanguage(SDL)".4Definitions4.1ExternaldefinitionsForthepurposesofthepresentdocument,thetermsanddefinitionsgiveninthefollowingapply:Creferencepoint:(ETS300475-1)DestinationPINX:(ETS300239)EndPINX:(ETS300239)GatewayPINX:(EN300172)IncomingCall:(EN300172)Inter-PINXConnection:(EN301039)Inter-PINXLink:(EN301039)Mappingfunctionalgroup:(ETS300475-1)OriginatingPINX:(EN300172)OutgoingCall:(EN300172)PrecedingPINX:(ETS300239)PrivateIntegratedServicesNetwork(PISN):(ETS300475-1)PrivateIntegratedServicesNetworkExchange(PINX):(ETS300475-1)Qreferencepoint:(ETS300475-1)Side,IncomingSideandOutgoingSide:(EN300172)SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)9SourcePINX:(ETS300239)Sreferencepoint:(ETS300475-1)SubsequentPINX:(ETS300239)TerminatingPINX:(EN300172)TransitPINX:(EN300172)5AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ACSEAssociationControlServiceElementAISAlarmIndicationSignalANFAdditionalNetworkFeatureAPDUApplicationProtocolDataUnitASN.1AbstractSyntaxNotationOneATSAirTrafficServicesCCCallControlCICLCallIntrusionCapabilityLevelCIPLCallIntrusionProtectionLevelCPICLCallPriorityInterruptionCapabilityLevelCPIPLCallPriorityInterruptionProtectionLevelDSEDialogueServiceElementGFTGenericFunctionalTransportHLCHighLayerCompatibilityiirrelevantICSImplementationConformanceStatementIPCCInter-PINXConnectionControlLD-CELPLowDelayCodeExcitedLinearPredictionLLCLowLayerCompatibilitymmandatoryMPMaPpingn/anotapplicableNFENetworkFacilitiesExtensionooptionalo.ioptional,qualifiedPINXPrivateIntegratedservicesNetworkeXchangePISNPrivateIntegratedServicesNetworkPSS1PrivateSignallingSystemno.1PTSPrivateTerminationSystemQSIGQreferencepointSIGnallingsystemRLRequirementsListROSERemoteOperationsServiceElementSCASimultaneousCallAttemptSCMSignallingCarriageMechanismSS-CISupplementaryServiceCallIntrusionSS-CPISupplementaryServiceCallPriorityInterruptionSS-CPIPSupplementaryServiceCallPriorityInterruptionProtectionSWSWitchingTETerminalEquipmentTEITerminalEndpointIdentifierxeXcludedSIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)106Specificationframework6.1GeneralTheapproachtakeninthepresentdocumentistodefinethedetaileddigitalsignallingfunctionswithintheframeworkoffunctionalgroupingsdefinedinthereferenceconfigurationforPISNeXchanges(ETS300475-1).Thisapproachabstractsthespecificationofthefunctionsfromanyrealizationasarealpieceofequipment.Atthesametimeitprovidesacompletemodelofahypotheticalsystemthatcaneasilybetranslatedtoaphysicalimplementation.NOTE2:Theuseofsuchaframeworkfordescribingtherequiredfunctionsneednotconstrainsolutionsforprovidingthefunctionsnorisitintendedtoimplyanyparticulardesignarchitecture.Itsimplyprovidesaconvenientmethodofspecifyingtherequiredfunctionsand,lateron,theteststoconfirmthatsuchfunctionsaresupportedbyaparticularpieceofequipment.ThemajorPINXfunctionsandtheirrelationshipsareillustratedinfigure1;thefunctionsaredescribedinthefollowingclauses.MPSWTEPINXPTSCQCCSFigure1:MajorPINXfunctionsThemodelinfigure1,andthefunctionalitydefinedbyit,representsasingleinstanceofaserviceinvocation(i.e.acall).APINXclaimingconformancewiththepresentdocumentshallbecapableofprovidingmultiplesimultaneousinstancesofthedefinedfunctions.6.2TerminalEquipment(TE)TheTEfunctionprovidesthenecessarymeansforahumanuser,byactionsattheHumanMachineInterface,toinitiateoutgoingcallstoorrespondtoincomingcallsfromanotherTEfunction.TheTEfunctionmaybesimple(e.g.asimpletelephonehandset)orcomplex(e.g.anATSControllerWorkingPosition).Thedetailedrequirementsofthisfunctionareoutsidethescopeofthepresentdocument.6.3PrivateTerminationSystem(PTS)ThePTSfunctionprovidestransmissionandsignallingcapabilitiesbetweentheTEfunctionandtheSWfunction.ThePTSfunction,ifnecessary,adaptsthephysical,electricalandproceduralconditionsoftheinterfaceusedtoattachaTEtothePINX,totheinternalconditionsofthePINX.Thedetailedrequirementsofthisfunctionareoutsidethescopeofthepresentdocument.SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)116.4Switching(SW)TheSWfunctionprovidesthecapabilitytoswitchuserinformationandsignallinginformation.UserinformationisswitchedbetweenthePTSfunctionandtheMPfunction.Selectionoftheswitchingpathdependsupontheparametersoftheservicerequest.Signallinginformationisswitchedbetween:-thePTSfunctionandtheCCfunction;and-betweentheCCfunctionandtheMPfunction.NOTE3:Theswitchingfunctionmayalsoswitchbothuserandsignallinginformationbetweenthedescribedfunctionsandotherfunctionsoutsidethescopeofthepresentdocument.Thedetailedrequirementsofthisfunctionarespecifiedinclause8.6.5Mapping(MP)TheMPfunctionprovidesadaptationoftheinternalconditionsofthePINXtothephysical,electrical,andproceduralconditionsoftheinterfaceusedtoattachthePINXtoanexternaltransmissionfacility(e.g.aleasedcircuit)forinter-PINXcommunications.TheMPfunctionalsoprovidesthemultiplexingfunctionsrequiredtoseparateormergetheuserinformationandsignallinginformationfromthePINXtothetransmissionfacilityemployed.Thedetailedrequirementsofthisfunctionarespecifiedinclause9.6.6CallControl(CC)TheCCfunctionprovidesthefunctionsnecessarytocontrolcallsbetweenTEfunctionsattachedtotheATSPISN.ItincorporatesallthecomponentsofthePSS1(QSIG)protocolmodel(i.e.ProtocolControl,CallControl,GFT-Control,theCoordinationfunction,andapplicableSS-Controlentities)describedinEN300172andETS300239.NOTE4:TheCCfunctionalsoprovidesthefunctionsnecessarytocontrolcallsbetweenTEfunctionsattachedtotheATSPISNandothersubscribers(e.g.connectedtothepublictelecommunicationsnetwork).Itcanalsoprovidesignallinginterworkingfunctionswhennecessary.However,theseaspectsareoutsidethescopeofthepresentdocument.NOTE5:Inthepresentdocument,requirementsapplicabletotheCCfunctionarespecifiedseparatelyforeachofthefollowingcases:-OutgoingandIncomingsidesofaATSQSIGCall(EndPINXcase);and-InterworkingbetweenanIncomingsideandanOutgoingside(TransitPINXcase).Thedetailedrequirementsofthisfunctionarespecifiedinclauses10and11.SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)127PhysicalinterfaceandprotocolstackattheCreferencepointFigure1alsoshows,usingverticaldashedlines,the"referencepoints"atwhichphysicalinterfacesmayoccur.ThepresentdocumentdefinestherequiredbehaviourataphysicalinterfaceattheCreferencepoint.Figure2showstheprotocolstackapplicableattheCreferencepoint.PISNUserPlane(Userinformation)PISNControlPlane(Signalling)DataVoicePISNCallControlandSupplementaryServicesNetworklayerPSS1(QSIG)ProtocolControlEN300172,ETS300239DatalinklayerSymmetricLAP-DETS300402-2(annexZA)PhysicalLD-CELPITU-TRec.G.728layer64kbit/ssub-multiplexed(4x16kbit/s)ETS300290,EN301039PhysicalTransmissionMediumFigure2:Protocolstack8Switching(SW)functions8.1SpeechcompressionFor16kbit/sspeechcallsinwhichthePINXactsasthe"EndPINX",theSWfunctionshallprovideaspeechcompressionanddecompressioncapability(CELPcodec)accordingtotherequirementsofITU-TRecommendationG.728.OutgoingspeechinformationfromthePINXshallbecompressedusingtheencodingalgorithmspecifiedinITU-TRecommendationG.728.SpeechinformationincomingtothePINXshallbedecompressedusingthedecodingalgorithmspecifiedinITU-TRecommendationG.728.NOTE6:TheCELPcodecdescribedinITU-TRecommendationG.728containsselectableoptionstopermitoperationwithmodemorothernon-speechsignals.SuchoperationisnotanticipatedintheATScontext.Thebit-stealingmethod,asspecifiedinITU-TRecommendationG.728/clause3.11,shallbeusedforsynchronizingtheLD-CELPbitstream.Thestolenbitsshallbeanalternatingsequenceofzerosandones(i.e.either010101…or101010…).ForcallsinwhichthePINXactsasa"TransitPINX",speechinformationshallnotbedecompressedandre-compressed.SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)139Mapping(MP)functions9.1PhysicallayerfunctionsNOTE7:Thephysicalinterfaceandsub-multiplexingtechniquesspecifiedin9.1.1havebeenselectedasappropriateforATSPISNs.Theinclusionofotherphysicalinterfaces(e.g.at2048kbit/s)inafutureeditionofthepresentdocumentisnotprecluded.Oneconsequenceofthisisthatthenumberofchannelsandtheirattributes(e.g.informationtransferrate,userinformationlayer1protocol)attheQreferencepointmaybedifferentfromthatpresentlyspecified.SuchachangeimplieschangestotherequirementstobemetbytheMappingfunctionandtheCallControlfunction.Afurtherconsequenceisthat,whentheinter-PINXconnectionisprovidedbymeansofaleasedcircuit,establishmentoftheconnectionisachievedthroughanadministrativeprocedurewiththeleasedcircuitprovider.Functionsforthecontroloftheconnection(i.e.theIPCCfunctionalgroup,asspecifiedinETS300475-1)areneededonlywhenon-demandconnections(e.g.throughthepublicISDN)areusedastheinter-PINXconnection.Suppliersshouldbeawareofthesepossibilitiesandmaywishtodesigntheirsolutionsaccordingly.9.1.1PhysicalandelectricalinterfacerequirementsTheMPfunctionshallmeettherequirementsforphysicalandelectricalcharacteristicsspecifiedinETS300290anditsamendment.9.1.2Rateadaptationandsub-multiplexingTheMPfunctionshallmeettherequirementsspecifiedinEN301039forsub-multiplexinga64kbit/scircuit-modeinter-PINXconnectioninto4x16kbit/schannels.TheMPfunctionshallprovidearateadaptationcapability.Incomingspeechinformationshallbeadaptedtotheinternalchannelrate.Outgoingspeechinformationshallbeadaptedfromtheinternalchannelratetotheraterequiredbytheexternaltransmissionfacility,asspecifiedinEN301039.9.1.3AlarmIndicationSignal(AIS)IftheMPfunctionreceivesmultipleoctets(i.e.>3octets)containinganallone'sbitpatternfromtheexternaltransmissionfacilityitshallassumethistobeanAlarmIndicationSignal(AIS).TheMPfunctionshallassumethetransmissionfacilityand/orthepeerPINXisoutofserviceandtakeappropriatemanagementaction.TheMPfunctionshallbecapableofsendingAIStowardstheexternaltransmissionfacilitywhenitdetectslossofbitviolationsinthereceivedbitstream.OnresumptionofnormalbitviolationstheMPfunctionshallstopsendingAIS.NOTE8:Theremaybeother,implementationdependant,circumstanceswhentheMPfunctionisrequiredtosendAIS.Theseareoutsidethescopeofthepresentdocument.9.1.4SynchronizationSynchronizationfunctionsoftheMPfunctionshallbecompatiblewiththesynchronizationstrategyofthePINX.Thatistosay,theMPfunctionshallbecapableofboth(butnotsimultaneously):-extractingthetimingreceivedatthereceivesideofthephysicalinterfaceanddeliveringitasanexternalclocksourcefortheentiresystem,andsynchronizingtheMPfunction'sownoutputtimingtothissource;and-synchronizingtheMPfunction'sownoutputtimingtoanotherclocksourcenotderivedfromthephysicalinterfaceassociatedwiththisMPfunction.Selectionoftheoptionshallbebysystemconfigurationandruntimedetermination.SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)149.2Datalinklayerfunctions9.2.1GeneralproceduresTheMPfunctionshallsupportdatalinklayerproceduresasspecifiedinannexZAofETS300402-2,withmodificationsasspecifiedinthefollowingclauses.NOTE9:Inclause9,referencesoftheform:(clausex.x.x)refertoclausesinETS300402-2.Referencesoftheform(seex.x.x)refertothepresentdocument.APINXshallprovideamanagementmeansofconfiguringtheMPfunctionforeachinter-PINXlinktobeeitherthe"master"sideorthe"slave"side(clauseZA.2.3.2).ThedesignationofanyparticularMPfunctionaseithera"master"ora"slave"shallnotbeinfluencedbynorshallitinfluencetheconfigurationofanyotherMPfunctioninthesamePINX.ThereisnoneedforaPINXtosupporttheunacknowledgedmodeofoperation(clauseZA.4.2).Whennolayer3informationistobetransmitted,thetransmittingdatalinklayerentityshallcontinuouslysendflagsequencesintheD-channel(clauseZA.1.2).NOTE10:Thisrequirementpermitsthereceivingdatalinkentitytoperformoctetsynchronizationfunctions(see9.3)withoutimpactonthetransmittingentity.Thetransmittingdatalinklayerentityshallalwayssendanopeningflagandaclosingflagforeachlayer2frametransmitted(i.e.theclosingflagofoneframeshallnotserveastheopeningflagofthenextframe)(clauseZA.1.2).NOTE11:Thisrequirementpermitsthereceivingdatalinkentitytoperformoctetsynchronizationfunctionswithoutimpactonthetransmittingentity.9.2.2SystemparametersThedefaultvaluesshallapplyforallsystemparameters(clauseZA.4.9),asspecifiedintable1.APINXshouldprovideameansforconfiguringparametersindividuallyforeachinter-PINXlink.Table1:Layer2parametervaluesParameterDescriptionValueDefaultvalue?KMaximumnumberofoutstandingI-frames3YesT200Frametransmissiontimer(minimumtimebetweenframes)1sYesT201Minimumtimebetweenre-transmissionofTEIidentitycheckmessagesNotusedNotusedT202Minimumtimebetweenre-transmissionofTEIidentityrequestmessagesNotusedNotusedT203Maximumtimebetweenframes10sYesN200Maximumnumberofre-transmissions3YesN201Maximumnumberofoctetsinaninformationfield260YesN202MaximumnumberoftransmissionsofTEIidentitycheckmessagesNotusedNotusedSIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)159.3OctetsynchronizationprocedureTheMPfunctionshallprovideanoctetsynchronizationproceduretopermitrecoveryfromslipsinthe64kbit/sbitstream.NOTE12:Suchaprocedureisrequiredforaninterimperiodduringwhichsome64kbit/sleasedcircuitsmaybeunabletoguaranteeoctetintegrity.Itshallbepossibletoenableanddisabletheprocedureonanyinter-PINXlinkbymeansofmanagementactions.Whentheoctetsynchronizationprocedureisenabledforaparticularinter-PINXlink,theMPfunctionshallcontinuouslymonitorthelinkandcorrectforlossofoctetsynchronization.10CallControl(CC)functions-EndPINXcase10.1BasiccallestablishmentandclearingTherequirementsofEN300172shallapply,withmodificationsasspecifiedinthefollowingclauses.NOTE13:Clauses10.2to10.4specifyaspectsofQSIGthatdonotneedtobesupportedbyaPINX.Clauses10.5andonwardsspecifyrequirementsadditionaltothoseinEN300172.Theheadingsusedinclauses10.5onwardscorrespondtoheadingtitlesinEN300172.NOTE14:Inclause10,referencesoftheform:(clausex.x.x)refertoclausesinEN300172.Referencesoftheform(seex.x.x)refertothepresentdocument.10.2Messagesegmentationandre-assemblyAnnexZA(Messagesegmentationandre-assembly)ofEN300172shallnotapply.10.3STATUSENQUIRYprocedureAPINXshallnotsupportinitiationoftheSTATUSENQUIRYprocedure(clause9.3.1).NOTE15:Thismeansthattheoptionsinvariouserrorcases(e.g.whereamessageisreceivedwithamessagetypeormessagesequenceerror(clause9.2.4),orduringdatalinkreset(clause9.2.8)orfailure(clause9.2.9))ofEN300172thatpermitanentitytosendaSTATUSENQUIRYmessageshallnotbesupported.10.4Overlapsending/receivingproceduresAPINX(IncomingSide)neednotsupporttheOverlapReceivingstate(clause7.1.14).SimilarlyaPINXactingasaTransitPINXneednotsupporttheTCC_AwaitAdditionalDigitsstate(clause10.4.3).APINX(OutgoingSide)shallnotinitiatecallsusingstatesandproceduresforoverlapsending.10.5CallrequestandtransmissionoftheSETUPmessageCallrequest(clause10.1.1)andtransmissionoftheSETUPmessage(clause10.5.1)shallbemodifiedaccordingtotherequirementsinthefollowingparagraphs.If,duetocongestion,noB-channelisavailablefortherequestedcall,andifpreviouslyrequested(e.g.bytheTEfunctionduetoClassofServiceorPriorityKeydepression),CallControlshallimmediatelyperformthe"execution"functionoftheCallpriorityinterruptionsupplementaryservice(see10.21.4).Ifnorequestforcallpriorityinterruptionwasmade,CallControlshallinitiatecallestablishmentonanalternativeroute(see10.15).SIST EN 301 846 V1.1.1:2005

ETSIETSIEN301846V1.1.1(2001-07)16If,duetoareasonotherthancongestion,noB-channelisavailable,CallControlshallinitiatecallestablishmentonanalternativeroute(see10.15).TheBearercapabilityinformationelementsentintheSETUPmessageshallbeencoded(see10.17.2)toindicate"Speech16kbit/s"or"Unrestricteddigitalinformation16kbit/s",asappropriate.TheCalledpartynumberinformationsentintheSETUPmessageshallbecomplete.ThetransmittedSETUPmessageshallalwayscontaintheSendingcompleteinformationelement.WithintheCallingpartynumberandCalledpartynumberinformationelements
...