Abstract

To correct the errors detected and introduced the solution agreed during the Brighton meeting (TD202).

Status
Published
Publication Date
31-Dec-2004
ICS
33.080 - Integrated Services Digital Network (ISDN)
 
35.100.30 - Network layer
Technical Committee
SPN - Services and Protocols for Networks
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Jan-2005
Due Date
01-Jan-2005
Completion Date
01-Jan-2005
Mandate
T-234B
Ref Project
ETSI EN 300 403-2 V1.3.1 (2000-11) - Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 2: Specification and Description Language (SDL) diagrams

Buy Documents

SIST EN 300 403-2 V1.3.1:2005 - Page 1 previewSIST EN 300 403-2 V1.3.1:2005 - Page 2 previewSIST EN 300 403-2 V1.3.1:2005 - Page 3 previewSIST EN 300 403-2 V1.3.1:2005 - Page 4 preview
PreviousNext
Standard

SIST EN 300 403-2 V1.3.1:2005

English language (168 pages)
Preview
Preview
e-Library read for
×1 day

SIST EN 300 403-2 V1.3.1:2005 is the Slovenian adoption of ETSI EN 300 403-2 V1.3.1, published by SIST. It gives Specification and Description Language (SDL) diagrams for the Integrated Services Digital Network (ISDN) Digital Subscriber Signalling System No. one (DSS1) signalling network layer for circuit-mode basic call control. Engineers, test teams, and equipment buyers use it to understand the call-state model, message handling, and restart behavior for ISDN interfaces.

What does SIST EN 300 403-2 V1.3.1:2005 specify?

SIST EN 300 403-2 V1.3.1:2005 specifies the SDL description of stage-three circuit-mode on-demand basic telecommunication services at the T reference point or the coincident S and T reference point. It is the diagram part of the DSS1 protocol specification for ISDN basic call control.

The document is organized into clauses for scope, references, definitions, call states, network-side SDL diagrams, user-side SDL diagrams, restart SDL diagrams, and graphical SDL diagrams.

AnnexWhat it covers
Annex AInformative differences to ETS 300 102-2

The scope also states that the SDL diagrams in this part and clause 5 of ETS 300 403-1 together provide a complete specification of the protocol within its scope.

What are the key requirements of SIST EN 300 403-2 V1.3.1:2005?

The document defines the protocol behavior through state-based SDL models rather than through prose requirements alone. In practice, that means implementers follow the diagrams for message handling, state transitions, and timer behavior.

1. Use the defined call-state model

Clause 4 lists user-side and network-side call states for idle, outgoing call, incoming call, active, call clearing, suspend/resume, and restart procedures. This gives implementers and test labs a common vocabulary for checking which events are valid in each phase.

2. Treat network-side multipoint operation as two linked processes

Clause 5 explains that the network side uses a global process plus individual processes in point-to-multipoint operation. The global process tracks Connection Endpoint Suffix (CES) values and coordinates the individual terminal processes, which matters when one call is offered to several terminals.

3. Follow the primitive sets in Tables 3 and 6

The network-side and user-side SDL diagrams use defined primitives such as SETUPREQUEST, ALERTINGINDICATION, CONNECTINDICATION, RELEASEREQUEST, and STATUSENQUIRYREQUEST. These tables tell implementers which messages cross the protocol-control boundary and which ones are internal to the SDL model.

4. Handle timers exactly as shown in the diagrams

The diagrams refer to timers such as T301, T302, T304, T305, T306, T308, T309, T310, T312, T313, T316, T317, T318, T319, and T322. Their use depends on state and configuration, so timer handling is part of interoperability, not an implementation detail to improvise.

5. Use the restart model as a separate procedure

Clause 7 defines restart SDL diagrams with the REST 0, REST 1, and REST 2 states and flags such as RESTRESP, RESTACK, and T317 EXPIRED. This is important for reinitializing call references and channels after a restart event.

6. Read the graphical diagrams as the operative model

Clause 8 contains the graphical SDL diagrams for the network side, user side, and restart procedure. These diagrams are the detailed reference for protocol design, implementation, and conformance checking.

What terms does SIST EN 300 403-2 V1.3.1:2005 define?

  • Connection Endpoint Suffix (CES) - The identifier used in point-to-multipoint handling to distinguish and manage individual terminal processes.
  • Digital Subscriber Signalling System No. one (DSS1) - The signalling protocol family used on the ISDN user-network interface.
  • Integrated Services Digital Network (ISDN) - The digital telecommunication network environment for which the protocol is specified.
  • Specification and Description Language (SDL) - The formal notation used to describe the protocol behavior as state machines.
  • Point-to-multipoint configuration - A terminal configuration with more than one signalling entity.
  • Point-to-point configuration - A terminal configuration with one signalling entity.
  • Broadcast datalink - A datalink that can support more than two connection endpoints.

Who uses SIST EN 300 403-2 V1.3.1:2005?

Telecommunications protocol engineers use this standard to implement DSS1 call control on ISDN interfaces. Network vendors and terminal manufacturers use it to align behavior at the user side and network side.

Test engineers and conformance labs use it together with the protocol specification to derive test cases and check state transitions, timer handling, and restart behavior. Quality managers and buyers use it to compare equipment claims against the protocol model for ISDN basic call control.

What changed in SIST EN 300 403-2 V1.3.1:2005 from the previous edition?

SIST EN 300 403-2 V1.3.1:2005 is an extended and updated version of ETS 300 102-2 and is based on ITU-T Recommendation Q.931 (1993) rather than Q.931 (1988).

The document states these changes in Annex A and the foreword:

  • the text was aligned with the PNE rules and gained scope, references, definitions, symbols, and abbreviations clauses
  • clause 5.4 was expanded with guidance for network-side timer representation
  • clause 6.4 was added to explain the user-side representation method
  • a new restart clause was added, with its own SDL diagrams and explanatory flags
  • the internal primitive lists were updated for the new SDL diagrams
  • the SDL diagrams were redrafted with more cross-references and cause values, and the user-side diagrams were aligned with the network-side ones
  • technical changes aligned the diagrams with ETS 300 403-1, including updated timer handling and the REPORTSTATUS subroutine

Which standards are used with SIST EN 300 403-2 V1.3.1:2005?

ReferenceContribution
ETSI ETS 300 403-1Protocol specification that, together with this part, completes the protocol specification within scope
ITU-T Recommendation I.130Method for characterizing telecommunication services and network capabilities
ITU-T Recommendation I.411ISDN user-network interface reference configurations
ITU-T Recommendation Z.100SDL notation used for the diagrams
ETSI ETR 018Guidance on Bearer Capability, High Layer Compatibility, and Low Layer Compatibility information elements
ETSI ETS 300 102-2Earlier SDL diagram document that this edition updates
ITU-T Recommendation Q.931Base ISDN user-network layer 3 basic call control specification
ETSI ETS 300 403-1, Parts 3-7PICS proformas and test suite structure / ATS / PIXIT parts for user and network

What does the SIST EN 300 403-2 V1.3.1:2005 document contain?

This document contains call-state tables, block diagrams, primitive lists, and SDL representation rules for the network side, user side, and restart procedure. It also contains the graphical SDL diagrams themselves: 85 sheets for the network side, 57 sheets for the user side, and 7 sheets for the restart procedure.

The tables and diagrams are used to model call establishment, call clearing, suspend and resume, overlap sending and receiving, status handling, and restart handling. Annex A gives the background differences from ETS 300 102-2.

Buy Documents

SIST EN 300 403-2 V1.3.1:2005 - Page 1 previewSIST EN 300 403-2 V1.3.1:2005 - Page 2 previewSIST EN 300 403-2 V1.3.1:2005 - Page 3 previewSIST EN 300 403-2 V1.3.1:2005 - Page 4 preview
PreviousNext
Standard

SIST EN 300 403-2 V1.3.1:2005

English language (168 pages)
Preview
Preview
e-Library read for
×1 day

Get Certified

Connect with accredited certification bodies for this standard

BSI Group

BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.

UKAS United Kingdom Verified
Visit Website

NYCE

Mexican standards and certification body.

EMA Mexico Verified
Visit Website

ANCE

Mexican certification and testing association.

EMA Mexico Verified
Visit Website

Sponsored listings

Frequently Asked Questions

SIST EN 300 403-2 V1.3.1:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 2: Specification and Description Language (SDL) diagrams". This standard covers: To correct the errors detected and introduced the solution agreed during the Brighton meeting (TD202).

To correct the errors detected and introduced the solution agreed during the Brighton meeting (TD202).

SIST EN 300 403-2 V1.3.1:2005 is classified under the following ICS (International Classification for Standards) categories: 33.080 - Integrated Services Digital Network (ISDN); 35.100.30 - Network layer. The ICS classification helps identify the subject area and facilitates finding related standards.

SIST EN 300 403-2 V1.3.1:2005 is associated with the following European legislation: Standardization Mandates: T-234B. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.

SIST EN 300 403-2 V1.3.1:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 2: Specification and Description Language (SDL) diagrams35.100.30Omrežni slojNetwork layer33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 403-2 Version 1.3.1SIST EN 300 403-2 V1.3.1:2005en01-januar-2005SIST EN 300 403-2 V1.3.1:2005SLOVENSKI
STANDARD
ETSIEN300403-2V1.3.1(2000-11)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part2:SpecificationandDescriptionLanguage(SDL)diagramsSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)2ReferenceREN/SPAN-05210-2KeywordsISDN,DSS1,layer3,SDLETSI650RoutedesLuciolesF-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.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.53Definitions,symbolsandabbreviations.63.1Definitions.63.2Symbols.73.3Abbreviations.74Usersideandnetworksidecallstates.85NetworksideSDLdiagrams-overview.95.1Callstates.95.2Blockdiagram.95.3Listofprimitives.105.4Representationmethod.106UsersideSDLdiagrams-overview.136.1Callstates.136.2Blockdiagram.136.3Listofprimitives.146.4Representationmethod.147RestartSDLdiagrams-overview.147.1Statesrelatedtotherestartprocedure.147.2Blockdiagram.157.3Listofprimitivesexchangedwithsystemmanagement.157.4Representationmethod.158GraphicalSDLdiagrams.168.1NetworksideSDLdiagrams.178.2UsersideSDLdiagrams.1028.3RestartSDLdiagrams.158AnnexA(informative):RelevantdifferencestoETS300102-2.166A.1Structuralchanges.166A.2Technicalchanges.167History.168SIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)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)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).ThepresentdocumentwhichisbasedonITU-TRecommendationQ.931(1993)[7]isanextendedandupdatedversionofETS300102-2(1990)whichwasbasedonITU-TRecommendationQ.931(1988).AnnexAidentifiestherelevantdifferencesbetweenthepresentdocumentandETS300102-2.Thepresentdocumentispart2ofamulti-partstandardcoveringtheDigitalSubscriberSignallingSystemNo.one(DSS1)protocolspecificationfortheIntegratedServicesDigitalNetwork(ISDN)signallingnetworklayerforcircuit-modebasiccallcontrol,asdescribedbelow:Part1:"Protocolspecification[ITU-TRecommendationQ.931(1993),modified]";Part2:"SpecificationandDescriptionLanguage(SDL)diagrams";Part3:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part4:"TestSuiteStructureandTestPurposes(TSS&TP)specificationfortheuser";Part5:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuser";Part6:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork";Part7:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetwork".NationaltranspositiondatesDateofadoptionofthisEN:27October2000DateoflatestannouncementofthisEN(doa):31January2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31July2001DateofwithdrawalofanyconflictingNationalStandard(dow):31July2001SIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)51ScopeThepresentdocumentspecifiesthestagethreeofcircuit-modeon-demandbasictelecommunicationservicesforthepan-EuropeanIntegratedServicesDigitalNetwork(ISDN)asprovidedbyEuropeantelecommunicationsoperatorsattheTreferencepointorcoincidentSandTreferencepoint(asdefinedinITU-TRecommendationI.411[3])bymeansoftheDigitalSubscriberSignallingSystemNo.one(DSS1).Stagethreeidentifiestheprotocolproceduresandswitchingfunctionsneededtosupportatelecommunicationservice(seeITU-TRecommendationI.130[2]).Inaddition,thepresentdocumentspecifiestheprotocolrequirementsattheTreferencepointwheretheserviceisprovidedtotheuserviaaprivateISDN.NOTE1:ProceduresattheTreferencepoint,tosupporttheaccessofaprivateISDNtothepublicISDN,arenotexplicitlyidentifiedinthepresentdocument,howeversomeproceduresareapplicableonlytotheTreferencepoint.ThepresentdocumentdoesnotspecifytheadditionalprotocolrequirementswheretheserviceisprovidedtotheuserviaatelecommunicationnetworkthatisnotanISDN.ThepresentdocumentisspecifiedusingtheSpecificationandDescriptionLanguage(SDL)asspecifiedinITU-TRecommendationZ.100[4].Inordertodescribethepoint-to-multipointoperationoftheprotocol,theconceptofa"global"processrunninginparallelwithanumberof"individual"(dynamic)processeshasbeenintroduced.Thisapproach,andtheassociateddefinitionofinternalprimitivesisintendedtoprovideacoherentdescriptionoftheprotocolanddoesnotconstrainimplementations.TheSDLdiagramsinthispart,andthetextofclause5ofETS300403-1[1],togetherprovideacompletespecificationoftheprotocolwithinthescopeofthepresentdocument.Abasictelecommunicationserviceisafundamentaltypeofservice.Itformsthebasisonwhichsupplementaryservicesmaybeadded.NOTE2:Specificrequirementsofindividualcircuit-modebasictelecommunicationservicesarenotcoveredinthepresentdocument.However,ETR018[5]givesguidanceontheuseofservicespecificinformationelementstoimplementindividualbasictelecommunicationservices.ThemethodoftestingofthepresentdocumentiscommonwiththatforETS300403-1[1].Furtherpartsofthepresentdocumentspecifythemethodoftestinganddetailedapplicationspecificrequirementstodetermineconformancebasedonthepresentdocument.Thepresentdocumentisapplicabletoequipmentsupportingcircuit-modeon-demandbasictelecommunicationservices,tobeattachedateithersideofaTreferencepointorcoincidentSandTreferencepointwhenusedasanaccesstothepublicISDN.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIETS300403-1(1995):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part1:Protocolspecification[ITU-TRecommendationQ.931(1993),modified]".SIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)6[2]ITU-TRecommendationI.130(1988):"MethodforthecharacterizationoftelecommunicationservicessupportedbyanISDNandnetworkcapabilitiesofanISDN".[3]ITU-TRecommendationI.411(1993):"ISDNuser-networkinterfaces-Referenceconfigurations".[4]ITU-TRecommendationZ.100(1988):"Specificationanddescriptionlanguage(SDL)".[5]ETSIETR018:"IntegratedServicesDigitalNetwork(ISDN);ApplicationoftheBearerCapability(BC),HighLayerCompatibility(HLC)andLowLayerCompatibility(LLC)informationelementsbyterminalssupportingISDNservices".[6]ETSIETS300102-2:"IntegratedServicesDigitalNetwork(ISDN);User-networkinterfacelayer3;Specificationsforbasiccallcontrol;SpecificationDescriptionLanguage(SDL)diagrams".[7]ITU-TRecommendationQ.931:"ISDNuser-networkinterfacelayer3specificationforbasiccallcontrol".3Definitions,symbolsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapplyinadditiontothosegiveninETS300403-1[1]:point-to-multipointconfiguration;multipointterminalconfiguration;multipointconfiguration:terminalconfigurationinwhichthereismorethanonesignallingentitypoint-to-multipointdatalink;broadcastdatalink:datalinkconnectionwiththecapabilitytosupportmorethantwoconnectionendpointspoint-to-pointconfiguration;single-pointterminalconfiguration;single-pointconfiguration:terminalconfigurationinwhichthereisonesignallingentitypoint-to-pointdatalink:datalinkonwhichaframeisdirectedtoasingleendpointSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)73.2SymbolsForthepurposesofthepresentdocument,thefollowingsymbolsapply.AfulldescriptionofthesymbolsandtheirmeaningandapplicationisgiveninITU-TRecommendationZ.100[4].StatesymbolInputsymbol(eventoccurrence)Outputsymbol(signalgenerationwhichwillleadtoanassociatedeventoccurrence)Savesymbol(saveeventuntilcompletionofatransition)TasksymbolDecisionsymbolProcedurecallsymbolTransitionoptionsymbol(implementationoption)ProcedurestartsymbolProcedurereturnsymbolCreaterequestsymbol(usedtoinitiateanindividualnetworksidetransaction)Stopsymbol(usedtoendanindividualnetworksidetransaction)ConnectionsymbolUsedmark(aninputwhichislocaltothelayer3entityandwhichisrequiredasaresultoftherepresentationapproachadopted)3.3AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:CESConnectionEndpointSuffixDSS1DigitalSubscriberSignallingSystemNo.oneISDNIntegratedServicesDigitalNetworkSDLSpecificationandDescriptionLanguageSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)84UsersideandnetworksidecallstatesTable1showswhichcallstatesareapplicableattheuserandnetworksidesduringthevariousphasesofacall.Table1:CallstatesCallphaseCallstateUserNetworkIDLENullU0N0OUTGOINGCALL(fromuser)CallinitiatedOverlapsendingOutgoingcallproceedingCalldeliveredU1U2U3U4N1N2N3N4INCOMINGCALL(touser)CallpresentOverlapreceivingIncomingcallproceedingCallreceivedConnectrequestU6U25U9U7U8N6N25N9N7N8ACTIVEActiveU10N10CALLCLEARINGDisconnectrequest(clearingbytheuser)Disconnectindication(clearingbythenetwork)ReleaserequestCallabortU11U12U19-N11N12N19N22CALLSUSPEND/RESUMESuspendrequestResumerequestU15U17N15N17RESTARTPROCEDURE(note)RestartnullRestartrequestRestartREST0REST1REST2REST0REST1REST2NOTE:Thesestatesrelatetoglobalcallreferencesandareapplicablewhentherestartproceduresareused.Theymayexistinbothuserandnetworksides.SIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)95NetworksideSDLdiagrams-overview5.1CallstatesTable2:NetworksidecallstatesCallstateNameN0NullN1CallinitiatedN2OverlapsendingN3OutgoingcallproceedingN4CalldeliveredN6CallpresentN7CallreceivedN8ConnectrequestN9IncomingcallproceedingN10ActiveN11DisconnectrequestN12DisconnectindicationN15SuspendrequestN17ResumerequestN19ReleaserequestN22CallabortN25OverlapreceivingNOTE1:Networksidetimers,andthestatesinwhichtheyrun,arespecifiedinclause9ofETS300403-1[1].NOTE2:Eventsineachstatewhichleadtonormalcallestablishmentandclearingaremarkedwiththe"+"symbol.NOTE3:Theprimitiveswhichpasstoandfromthecallcontrolblockareshownforguidanceonlyandarenotfullyspecified.NOTE4:Internalprimitivesaremarkedby"*".Thesearearesultoftherepresentationmethodthathasbeenadopted.5.2BlockdiagramCallcontrolResourcemanagementProcedurecallQ.931protocolcontrolMessagesto/fromUsersideDatalinklayerPhysicallayerUser-networkinterfaceUserBlockdescribedbytheSDLdiagramsPrimitives(note1)NOTE1:InterfacenotdescribedintheSDLdiagrams.NOTE2:ControlofB-channelsisdescribedintheseSDLdiagramsaspartoftheQ.931protocolblock.Figure1:BlockdiagramforthenetworksideSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)105.3ListofprimitivesTable3:ListofprimitivesFromcallcontrolblockTocallcontrolblockALERTINGREQUESTDISCONNECTREQUESTINFOREQUESTMOREINFOREQUESTNOTIFYREQUESTPROCEEDINGREQUESTPROGRESSREQUESTREJECTREQUESTRELEASEREQUESTRESUMEREJECTREQUESTRESUMERESPONSESETUPCOMPLETEREQUESTSETUPREQUESTSETUPRESPONSESTATUSENQUIRYREQUESTSUSPENDREJECTREQUESTSUSPENDRESPONSERESTARTREQUEST(note1)ALERTINGINDICATIONCONNECTINDICATIONDISCONNECTINDICATIONINFOINDICATIONMOREINFOINDICATIONNOTIFYINDICATIONPROCEEDINGINDICATIONPROGRESSINDICATIONRELEASECONFIRMRELEASEINDICATIONRESUMEINDICATIONSETUPCONFIRMSETUPINDICATIONSTATUSINDICATIONSUSPENDINDICATIONTIMEOUTINDICATIONRESTARTCONFIRM(note2)NOTE1:Thisprimitivemaybereceivedfromglobalcallreferencecontrol.NOTE2:Thisprimitiveissenttoglobalcallreferencecontrol.5.4RepresentationmethodInordertodescribethepoint-to-multipointoperationoftheprotocol,theconceptofa"global"processrunninginparallelwithanumberof"individual"(dynamic)processesinthenetworksidehasbeenintroduced.Thisapproach,andtheassociateddefinitionofinternalprimitives,isintendedtoprovideacoherentdescriptionoftheprotocolanddoesnotconstrainimplementation.Thetextualdescriptioninclause5ofETS300403-1[1]isdefinitive.Individualprocessesareusedtotracktheresponsesofeachterminal.Theglobal(controlling)processrunsinparallelwiththe(dynamicallycreated/destroyed)individualprocess.Theglobalandindividualprocessescommunicatebymeansofinternalprimitives.Thesearerelatedtolayer3messagestypesandaredefinedintable4.Theinternalprimitivesrepresentinstantaneousactions.Thus,thereisnopossibilityoferrorscausedbythecrossoverofprimitives.TheglobalprocessmaintainsalistofrecordedConnectionEndpointSuffix(CES)valuestoenableittomanagetheindividualprocesses.Inthisrepresentationtheglobalprocessalsokeepsarecordofthestateoftheindividualprocessassociatedwitheachrespondingterminal.Additionallya"preselected"CESisrecordedwhenoneterminalrespondswithaCONNECTmessageandthisbecomesthe"selected"CESwhentheterminalisawardedthecall.Thissolutioniscompatiblewithpoint-to-pointconfigurations.Inthiscasetheglobalprocessnevercreatesanyindividualprocesses,andthetimersdefinedinETS300403-1[1]fortherelevantstatesarehandledbytheglobalprocess,includingtimerT322whichmayruninanystateexcepttheNullstate.Also,eversinceatransitiontotheNullstateoccurs,thestoppingofthistimer(ifrunning)shouldberegardedasanimplicitstatement,asitisnotshowninordernottoextendtheSDLrepresentation.Inapoint-to-multipointconfiguration,individualprocessesmayexistinthefollowingstates:N0Null(processesarecreatedinthisstate);N7Callreceived;N8Connectrequest;N9Incomingcallproceeding;N19Releaserequest;N25Overlapreceiving.SIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)11TwosetsofSDLdiagramsarerequiredforthesestatestoshowtheglobalandindividualprocesses.Theglobalprocesshandlesallcommunicationswithcallcontrol.Messagesfromindividualsterminalsaresenttotheindividualprocessforthatterminalifoneexists(i.e.iftheCESisrecognized).MessageswithanunrecognizedCESarepassedtotheglobalprocess.MessageswiththeselectedCESarealsosenttotheglobalprocess.Inapoint-to-multipointconfiguration,thehandlingofthetimersdefinedinETS300403-1[1]hasbeendoneaccordingtothefollowingprinciples:a)timersT301andT310onlyrunintheglobalprocesswhenanincomingcallisbeingoffered;b)timersT304,T308andT322onlyrunintheindividualprocesseswhenanincomingcallisbeingoffered.ThestoppingoftimerT322(ifrunning)whenanindividualprocessisdestroyedshouldberegardedasanimplicitstatementasitisnotshowninordernottoextendtheSDLrepresentation;c)intheotherphasesofacall,thetimersassociatedwitheachstate,aswellastimerT322whichmayruninanystateexcepttheNullstate,areallhandledbytheglobalprocess.Onceagain,thestoppingofthistimer(ifrunning)shouldberegardedasanimplicitstatementbecauseitextendstheSDLrepresentation.Table4:Networksidelayer3internalprimitivesPrimitivenameFromToMeaningINT.ALERTINGREQINT.CONNECTREQINT.CALLPROCREQINT.SETUPACKREQGlobalIndividualWhenglobalprocessreceivesALERTINGitstartsanindividualprocessandsendsINT.ALERTINGREQtoit(etc.)INT.ALERTINGINDINT.CONNECTINDINT.CALLPROCINDIndividualGlobalSentonreceiptofALERTING(etc.)ENDPROCESSGlobalIndividualSentwhentheglobalprocessterminatesanindividualprocessINT.RELEASEREQGlobalIndividualInstructsindividualprocesstoreleaseterminal(e.g.forreleasingnon-selectedterminals)INT.RELEASEINDIndividualGlobalInformsglobalprocessthataterminalhasbeguntoreleaseINT.INFOREQGlobalIndividualSentonreceiptofINFOREQINT.INFOINDIndividualGlobalSentonreceiptofINFOINT.STAT.ENQ.REQGlobalIndividualSentonreceiptofSTATUSENQUIRYREQINT.PROGRESSINDIndividualGlobalSentonreceiptofPROGRESSINT.REL.COMP.INDIndividualGlobalSenttoindicatethattheindividualprocesshasbeenclearedNOTE:Theglobalprocessshouldnotreleasethecallreferenceuntilallindividualprocesseshavecompletedclearing.Figure2(anarrowdiagram)showsanexampleofthisrepresentationmethod.SIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)12Terminal1Terminal2Terminal3NetworkSETUP(BROADCAST)0SETUPREQALERTINGT303ALERTINGINDINT.ALERTINGREQ7iALERTINGALERTINGINT.ALERTINGREQ7iINT.ALERTINGREQ7iINT.CONNECTINDCONNECTENDPROCESS8iRELEASEINT.RELEASEREQRELEASERELEASECOMPLETEINT.RELEASEREQ19iT3086T312CONNECTIND10T312expires(nostatechange)19iT308INT.REL.COMP.INDRELEASECOMPLETEINT.REL.COMP.INDCONNECTACKCONNECTACKREQ7Figure2:Multipointcallestablishment(andclearingofnon-selectedterminals)8NOTE:o=creationofstatemachine,x=deletionofstatemachine;numbersindicatestatesofthestatemachinesshown.xxxoooSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)136UsersideSDLdiagrams-overview6.1CallstatesTable5:UsersidecallstatesCallstateNameU0NullU1CallinitiatedU2OverlapsendingU3OutgoingcallproceedingU4CalldeliveredU6CallpresentU7CallreceivedU8ConnectrequestU9IncomingcallproceedingU10ActiveU11DisconnectrequestU12DisconnectindicationU15SuspendrequestU17ResumerequestU19ReleaserequestU25OverlapreceivingNOTE1:Usersidetimers,andthestatesinwhichtheyrun,arespecifiedinclause9ofETS300403-1[1].NOTE2:Eventsineachstatewhichleadtonormalcallestablishment/clearingareshownbythe"+"symbol.NOTE3:Primitivespassedtoandfromthecallcontrol(userapplication)blockareshownforguidanceonlyandarenotfullyspecified.6.2BlockdiagramCallcontrolResourcemanagementProcedurecallQ.931protocolcontrolMessagesto/fromUsersideDatalinklayerPhysicallayerUser-networkinterfaceNetworkBlockdescribedbytheSDLdiagramsPrimitives(note1)NOTE1:InterfacenotdescribedintheSDLdiagrams.NOTE2:ControlofB-channelsisdescribedintheseSDLdiagramsaspartoftheQ.931protocolblock.Figure3:BlockdiagramfortheusersideSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)146.3ListofprimitivesTable6:ListofprimitivesFromcallcontrolblockTocallcontrolblockALERTINGREQUESTDISCONNECTREQUESTINFOREQUESTMOREINFOREQUESTNOTIFYREQUESTPROCEEDINGREQUESTPROGRESSREQUESTREJECTREQUESTRELEASEREQUESTRESUMEREQUEST(note1)SETUPREQUESTSETUPRESPONSESTATUSENQUIRYREQUESTSUSPENDREQUEST(note1)RESTARTREQUEST(note2)ALERTINGINDICATIONDISCONNECTINDICATIONINFOINDICATIONMOREINFOINDICATIONNOTIFYINDICATIONPROCEEDINGINDICATIONPROGRESSINDICATIONRELEASECONFIRMRELEASEINDICATIONRESUMECONFIRMSETUPCOMPLETEINDICATIONSETUPCONFIRMSETUPINDICATIONSTATUSINDICATIONSUSPENDCONFIRMRESTARTCONFIRM(note3)NOTE1:Theseprimitivesarenotdefinedforaprimaryrateaccess,i.e.theuseofthecallrearrangementprocedureisrestrictedtobasicaccess.NOTE2:Thisprimitivemaybereceivedfromglobalcallreferencecontrol.NOTE3:Thisprimitiveissenttoglobalcallreferencecontrol.6.4RepresentationmethodTherepresentationmethodofusersideSDLdiagramshasnotfollowedtheconceptofaglobalprocessrunninginparallelwithanumberofindividualprocesses,becausefromasignallingpointofviewonlyonecallishandledbytheglobalprocessateachtime.Therefore,theglobalprocessnevercreatesanyindividualprocesses,andonlyonesetofSDLdiagramsisrequiredtorepresenttheusersidecallstates.Asaconsequence,thetimersassociatedwitheachstate,aswellastimerT322whichmayruninanystateexcepttheNullstate,areallhandledbytheglobalprocess.Also,asmentionedforthenetworkside,thestoppingofthistimer(ifrunning)shouldberegardedasanimplicitstatementbecauseitextendstheSDLrepresentation.7RestartSDLdiagrams-overview7.1StatesrelatedtotherestartprocedureTable7:StatesrelatedtotherestartprocedureCallstateNameREST0RestartnullREST1RestartrequestREST2RestartNOTE1:Timersrelatedtotherestartprocedure,andthestatesinwhichtheyrun,arespecifiedinclause9ofETS300403-1[1].NOTE2:Theprimitiveswhichpasstoandfromthesystemmanagementblock(seetable8)andtheprotocolcontrolblock(seetables3and6)areshownforguidanceonlyandarenotfullyspecified.SIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)157.2BlockdiagramCallcontrolResourcemanagementProcedurecallQ.931protocolcontrolDatalinklayerPhysicallayerUser/NetworkBlockdescribedbytheSDLdiagramsGlobalcallreferencecontrol(note)NOTE:InterfacenotdescribedintheSDLdiagrams.Figure4:Blockdiagramfortherestartprocedure7.3ListofprimitivesexchangedwithsystemmanagementTable8:ListofprimitivesFromsystemmanagementblockTosystemmanagementblockMANAGEMENTRESTARTREQUESTTIMEOUTMANAGEMENTINDICATIONSTATUSMANAGEMENTINDICATIONMANAGEMENTRESTARTCONFIRMNOTE:Primitivesrelatedtotherestartprocedurewhichmaybesentorreceivedto/fromprotocolcontrolblockarealreadyindicatedintables3and6.7.4RepresentationmethodTherepresentationmethodoftherestartSDLdiagramsfollowstheconceptofasinglefinitestatemachinerunningintheglobalcallreferencecontrolblock(seefigure4),inordertodescribetherestartprocedureandtheassociatedstatesdefinedinETS300403-1[1]subclause5.5andsubclause2.4,respectively.Wheneveracollisionofrestartproceduresinitiatedbyeithersideoftheinterfacemayoccur,itshallbehandledbyaseparatefinitestatemachineapproach.NOTE:Duetothecomplexityoftherepresentation,thisapproachisnotpresented.SIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)16Inthissubsetofdiagrams,referenceismadetosomeflagsinordertomaketheSDLrepresentationmoretransparent.Theflagshavethefollowingmeaning:a)RESTRESP:eitherbyinitiativeofthemanagemententityorbecauseaRESTARTmessagehasbeenreceived,theglobalcallreferencecontrolentityhassentprimitivesRESTARTREQUESTtoeachprotocolentityassociatedwithanactivecallreference,andiswaitingforareplyfromthem.Theflagissetwhentheyallhaveresponded;b)RESTACK:byinitiativeofthemanagemententity,theglobalcallreferenceentityhassentaRESTARTmessagetoitspeerentity(inthenetworksideorintheuserside),andiswaitingforaRESTARTACKNOWLEDGE.Theflagissetwhenthismessageisreceived;c)T317EXPIRED:eitherbyinitiativeofthemanagemententityorbecauseaRESTARTmessagehasbeenreceived,theglobalcallreferencecontrolentityhassentprimitivesRESTARTREQUESTtoeachprotocolentityassociatedwithanactivecallreference,andiswaitingforareplyfromthem.Theflagissetiftheyhavenotrespondedinduetime,andtimerT317hasexpired.8GraphicalSDLdiagramsThisclauseisseparatedintothreesubclauses:-networksideSDLdiagrams(figure5,sheets1to85);-usersideSDLdiagrams(figure6,sheets1to57);-restartSDLdiagrams(figure7,sheets1to7).AllreferencesinthefollowingdiagramsaretoETS300403-1[1].SIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)178.1NetworksideSDLdiagramsProcess NETWORK_SIDE1(85)NETWORK SIDE SDL DIAGRAMSNOTE 1. THE EXPIRY OF TIMER T307 IS NOT SHOWN IN THESE SDLs AS IT RUNS IN THE CALL CONTROL BLOCK.0NULLRELEASE5.8.3.2 (b)ESTABLISHCRRELEASECOMPLETE(CAUSE #81)RELEASECR0RESUMEACCESS?ESTABLISHCRRELEASECOMPLETE(CAUSE #81)RELEASECR0ESTABLISHCRRELEASE(CAUSE #81)STARTT30819ESTABLISHCRRESUMEINDICATION175.65.6.45.6.5+SETUP5.1.15.1.2+ESTABLISHCRCHNLSELECTIONSUCCESS?RELEASECOMPLETE(CAUSE #34 OR #44)RELEASECR0SETUPINDICATION1PRABRANYFigure5(sheet1of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)18Process NETWORK_SIDE2(85)NETWORK SIDE SDL DIAGRAMSNOTE 1. ANY OTHER MESSAGE EXCEPT STATUS ENQUIRY, SEE PAGES DEALING WITH DIAGRAMS RELATED TO ANY GLOBAL OR INDIVIDUAL STATE.NOTE 2. CAUSE #101 IS RETURNED IF A STATUS MESSAGE IS RECEIVED, WHILE CAUSE #81 APPLIES FOR OTHER MESSAGES.0NULLRELEASECOMPLETE5.8.3.2 (c)0OTHERMESSAGEESTABLISHCRRELEASECOMPLETE(CAUSE #81 OR #101)NOTE 2RELEASECR0ESTABLISHCRRELEASE(CAUSE #81 OR #101)NOTE 2STARTT308195.8.3.2 (a),NOTE 1STATUS5.8.11CS=0?0NYFigure5(sheet2of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)19Process NETWORK_SIDE3(85)NETWORK SIDE SDL DIAGRAMSNOTE 1. THIS INPUT MAY BE RECEIVED FROM A TERMINAL COMPLETING CLEARING IN A POINT-TO-MULTIPOINT CONFIGURATION.
THE CALL REFERENCE SHOULD NOT BE RE-USED UNTILL ALL TERMINALS HAVE COMPLETED CLEARING.0NULLINT
*REL COMPINDICATION(CES)DELETECES0NOTE 1NOTIFYREQUEST0SETUPREQUEST5.2.1+CHNLSELECTIONSUCCESS?RELEASEINDICATION0SELECTCRSTARTT303P-PSETUPREQUEST?STARTT312SETUP(B/CAST)6SETUP(P-P)6NYNYFigure5(sheet3of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)20Process NETWORK_SIDE4(85)NETWORK SIDE SDL DIAGRAMSNOTE 1. INDIVIDUAL PROCESSES ARE CREATED IN THIS STATE.OINULLINT
*ALERTINGREQUEST7IINT
*RELEASEREQUEST(CAUSE)STARTT308RELEASE(CAUSE)19IINT
*CALL PROCREQUEST9IINT
*CONNECTREQUEST8IINT
*SETUP ACKREQUESTSTARTT30425IINDIVIDUAL PROCESS,NOTE 1Figure5(sheet4of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)21Process NETWORK_SIDE5(85)NETWORK SIDE SDL DIAGRAMS1CALLINITIATEDREJECTREQUEST(CAUSE)RELEASECOMPLETE(CAUSE)RELEASEB-CHANNEL IFNOT RELEASEDRELEASECR05.3.2 (a)PROCEEDINGREQUESTCALLPROCEEDING(B-CHNL)CONNECTB-CHNL35.1.5.1+MORE INFOREQUEST5.1.3+STARTT302SETUP ACK(B-CHNL)CONNECTB-CHNLANYDIGITSRECEIVED?2TONEOPTION?2CONNECTDIALTONEYNNYFigure5(sheet5of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)22Process NETWORK_SIDE6(85)NETWORK SIDE SDL DIAGRAMS1CALLINITIATEDRELEASECOMPLETERELEASEB-CHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECR05.8.4RELEASERELEASEB-CHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECOMPLETERELEASECR05.8.4DISCONNECTDISCONNECTB-CHANNEL IFNOT DISCONNECTEDDISCONNECTINDICATION115.3.3Figure5(sheet6of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)23Process NETWORK_SIDE7(85)NETWORK SIDE SDL DIAGRAMS2OVERLAPSENDINGPROCEEDINGREQUESTSTOPT302CALLPROCEEDING35.1.5.2+ALERTINGREQUESTSTOPT302ALERTING45.1.7+SETUPRESPONSE5.1.8+STOPT302CONNECT10Figure5(sheet7of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)24Process NETWORK_SIDE8(85)NETWORK SIDE SDL DIAGRAMS2OVERLAPSENDINGINFOREQUESTINFO25PROGRESSREQUEST5.1.6PROGRESS2DISCONNECTREQUEST(CAUSE)STOPT302TONEOPTION?DISCONNECT(PI, CAUSE)STARTTONESTARTT30612DISCONNECTB-CHANNEL IFNOT DISCONNECTEDDISCONNECT(CAUSE)STARTT3055.1.5.25.3.4YNFigure5(sheet8of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)25Process NETWORK_SIDE9(85)NETWORK SIDE SDL DIAGRAMS2OVERLAPSENDINGRELEASECOMPLETESTOPT302RELEASEB-CHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECR05.8.4RELEASESTOPT302RELEASEINDICATIONRELEASEB-CHANNEL IFNOT RELEASEDRELEASECOMPLETERELEASECR05.8.4DISCONNECTSTOPT302DISCONNECTB-CHANNEL IFNOT DISCONNECTEDDISCONNECTINDICATION115.3.3Figure5(sheet9of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)26Process NETWORK_SIDE10(85)NETWORK SIDE SDL DIAGRAMS2OVERLAPSENDINGTIMEOUTT302CALL INFOINCOMPLETE?RELEASEINDICATIONTONEOPTION?DISCONNECT(PI, CAUSE #28)STARTTONESTARTT30612RELEASEB-CHANNEL IFNOT RELEASEDDISCONNECT(CAUSE #28)STARTT305TIMEOUTINDICATIONCALLPROCEEDING35.1.5.2INFO5.1.3+STOPT302FIRSTINFOMESSAGE?INFOINDICATIONSTARTT3022STOP ANYAPPLIEDDIAL TONEYYNNNYFigure5(sheet10of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)27Process NETWORK_SIDE11(85)NETWORK SIDE SDL DIAGRAMS3OUTGOING CALLPROCEEDINGDISCONNECTREQUEST(CAUSE)TONEOPTION?DISCONNECT(PI, CAUSE)STARTTONESTARTT30612DISCONNECTB-CHANNEL IFNOT DISCONNECTEDDISCONNECT(CAUSE)STARTT3055.1.5.15.3.4SETUPRESPONSECONNECT105.1.8+ALERTINGREQUESTALERTING45.1.7+YNFigure5(sheet11of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)28Process NETWORK_SIDE12(85)NETWORK SIDE SDL DIAGRAMS3OUTGOING CALLPROCEEDINGINFO5INFOINDICATION3INFOREQUESTINFO35PROGRESSREQUESTPROGRESS35.1.6Figure5(sheet12of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)29Process NETWORK_SIDE13(85)NETWORK SIDE SDL DIAGRAMS3OUTGOING CALLPROCEEDINGRELEASERELEASEB-CHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECOMPLETERELEASECR05.8.4DISCONNECTDISCONNECTB-CHANNEL IFNOT DISCONNECTEDDISCONNECTINDICATION115.3.3RELEASECOMPLETERELEASEB-CHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECR05.8.4Figure5(sheet13of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)30Process NETWORK_SIDE14(85)NETWORK SIDE SDL DIAGRAMS4CALLDELIVEREDDISCONNECTREQUEST(CAUSE)TONEOPTION?DISCONNECT(PI, CAUSE)STARTTONESTARTT30612DISCONNECTB-CHANNEL IFNOT DISCONNECTEDDISCONNECT(CAUSE)STARTT3055.3.4SETUPRESPONSECONNECT105.1.8+PROGRESSREQUESTPROGRESS45.1.6YNFigure5(sheet14of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)31Process NETWORK_SIDE15(85)NETWORK SIDE SDL DIAGRAMS4CALLDELIVEREDINFOINFOINDICATION45INFOREQUESTINFO45Figure5(sheet15of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)32Process NETWORK_SIDE16(85)NETWORK SIDE SDL DIAGRAMS4CALLDELIVEREDDISCONNECTDISCONNECTB-CHANNEL IFNOT DISCONNECTEDDISCONNECTINDICATION115.3.3RELEASECOMPLETERELEASEB-CHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECR05.8.4RELEASERELEASEB-CHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECOMPLETERELEASECR05.8.4Figure5(sheet16of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)33Process NETWORK_SIDE17(85)NETWORK SIDE SDL DIAGRAMS6CALLPRESENTSETUP ACK5.2.35.2.45.3.2+WASSETUPB/CAST?CHNLOK?STOPT303MORE INFOINDICATIONSTARTT30425STOPT303RELEASE(CAUSE #6)RELEASEINDICATIONSTARTT30819CHNLOK?STOPT303MORE INFOINDICATIONCREATEPROCESS(CES)INT
*SETUP ACKREQUEST(CES)25CREATEPROCESS(CES)INT
*RELEASEREQUEST(CES, CAUSE #6)6NYNYYNFigure5(sheet17of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)34Process NETWORK_SIDE18(85)NETWORK SIDE SDL DIAGRAMSNOTE 1. TIMER T301 IS NOT USED IF THE NETWORK IMPLEMENTS ANOTHER INTERNAL ALERTING SUPERVISION TIMING FUNCTION.6CALLPRESENTALERTING5.2.35.2.5.25.3.2+WASSETUPB/CAST?CHNLOK?STOPT303RELEASE(CAUSE #6)RELEASEINDICATIONSTARTT30819STOPT303ALERTINGINDICATIONSTARTT301NOTE 17CHNLOK?STOPT303ALERTINGINDICATIONCREATEPROCESS(CES)INT
*ALERTINGREQUEST(CES)STARTT301NOTE 17CREATEPROCESS(CES)INT
*RELEASEREQUEST(CES, CAUSE #6)6NNYYYNFigure5(sheet18of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)35Process NETWORK_SIDE19(85)NETWORK SIDE SDL DIAGRAMS6CALLPRESENTCONNECTWASSETUPB/CAST?CHNLOK ?STOPT303SETUPCONFIRMPRESELECTCESCREATEPROCESS(CES)INT
*CONNECTREQUEST(CES)8CREATEPROCESS(CES)INT
*RELEASEREQUEST(CES, CAUSE #6)6CHNLOK ?STOPT303SETUPCONFIRM8STOPT303RELEASE(CAUSE #6)RELEASEINDICATIONSTARTT308195.2.35.2.75.3.2+YYNNYNFigure5(sheet19of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)36Process NETWORK_SIDE20(85)NETWORK SIDE SDL DIAGRAMS6CALLPRESENTCALLPROCEEDINGWASSETUPB/CAST?CHNLOK?STOPT303PROCEEDINGINDICATIONSTARTT3109STOPT303RELEASE(CAUSE #6)RELEASEINDICATIONSTARTT30819CHNLOK?STOPT303PROCEEDINGINDICATIONCREATEPROCESS(CES)INT
*CALL PROCREQUEST(CES)STARTT3109CREATEPROCESS(CES)INT
*RELEASEREQUEST(CES, CAUSE #6)65.2.35.2.5.25.3.2+NYNYYNFigure5(sheet20of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)37Process NETWORK_SIDE21(85)NETWORK SIDE SDL DIAGRAMS6CALLPRESENTRELEASEWASSETUPB/CAST?STOPT303RELEASEB-CHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECOMPLETERELEASECR0RELEASECOMPLETE65.8.4RELEASECOMPLETEWASSETUPB/CAST?SAVECAUSE6STOPT303RELEASEB-CHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECR05.2.25.2.5.3NYYNFigure5(sheet21of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)38Process NETWORK_SIDE22(85)NETWORK SIDE SDL DIAGRAMS6CALLPRESENTINFOREQUESTDISCONNECTREQUEST(CAUSE)STOPT303WASSETUPB/CAST?DISCONNECTB-CHANNEL IFNOT DISCONNECTED22TONEOPTION?DISCONNECT(PI, CAUSE)STARTTONESTARTT30612DISCONNECTB-CHANNEL IFNOT DISCONNECTEDDISCONNECT(CAUSE)STARTT3055.3.2 (e)5.3.4YNYNFigure5(sheet22of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)39NETWORK SIDE SDL DIAGRAMSProcess NETWORK_SIDE23(85)NOTE 1. THIS PRIMITIVE MAY BE RECEIVED WHEN A TERMINAL IS CLEARED
DUE TO AN INVALID CHANNEL IDENTITY IN RESPONSE TO THE SETUP.NOTE 2. THIS MESSAGE IS IDENTICAL TO THE ORIGINAL SETUP MESSAGE.6CALLPRESENTINT
*REL COMPINDICATION(CES)NOTE 1DELETECES6TIMEOUTT3035.2.15.2.5.35.2.5.4FIRSTTIMEOUT?WASSETUPB/CAST?SETUP(PP)NOTE 2STARTT3036RELCOMPRCVD?SETUP(B/CAST)NOTE 2STARTT303RESTARTT3126RELEASEBCHANNEL IFNOT RELEASEDRELEASEINDICATION22WASSETUPB/CAST?DISCONNECTINDICATIONDISCONNECT(CAUSE #102)STARTT30512YNYNYNYNFigure5(sheet23of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)40Process NETWORK_SIDE24(85)NETWORK SIDE SDL DIAGRAMS7CALLRECEIVEDSETUPACKWASSETUPB/CAST?REPORTSTATUS(CAUSE #97,#98 OR #101)7CHNLOK?CREATEPROCESS(CES)INT
*RELEASEREQUEST(CES, CAUSE #6)7CREATEPROCESS(CES)INT
*SETUP ACKREQUEST(CES)75.2.3, 5.2.45.3.2, 5.8.4+CALLPROCEEDINGWASSETUPB/CAST?CHNLOK ?CREATEPROCESS(CES)INT
*RELEASEREQUEST(CES, CAUSE #6)7CREATEPROCESS(CES)INT
*CALL PROCREQUEST(CES)75.2.3, 5.2.5.25.3.2, 5.8.4+NYNYNYNYFigure5(sheet24of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)41Process NETWORK_SIDE25(85)NETWORK SIDE SDL DIAGRAMS7CALLRECEIVEDCONNECT5.2.35.2.75.3.2+WASSETUPB/CAST?CONNECTINDICATIONSTOP T301IF IMPLEMENTED8CHNLOK?CREATEPROCESS(CES)INT
*RELEASEREQUEST(CES, CAUSE #6)7CONNECTINDICATIONSTOP T301IF IMPLEMENTEDPRESELECTCESCREATEPROCESS(CES)INT
*CONNECTREQUEST(CES)8ALERTINGWASSETUPB/CAST?REPORTSTATUS(CAUSE #97,#98 OR #101)7CHNLOK?CREATEPROCESS(CES)INT
*RELEASEREQUEST(CES, CAUSE #6)7CREATEPROCESS(CES)INT
*ALERTINGREQUEST(CES)75.2.3, 5.2.5.25.3.2, 5.8.4+NYNYNYNYFigure5(sheet25of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)42Process NETWORK_SIDE26(85)NETWORK SIDE SDL DIAGRAMSNOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATE RETURNED IN THE STATUS MESSAGE SHOULD BE 6.NOTE 2. AS AN ALTERNATIVE, A STATUS ENQUIRY PROCEDURE ACCORDING TO SUBCLAUSE 5.8.4 OF ETS 300403-1 MAY ALSO BE FOLLOWED.
IN THIS CASE, AN INDIVIDUAL PROCESS SHOULD BE CREATED FOR THE RESPONDING TERMINAL IN ORDER TO CONTROL TIMER T322
AND THE APPROPRIATE RESPONSE. THIS PROCEDURE IS NOT DOCUMENTED IN THIS ETS AS IT INCREASES THE COMPLEXITY OF THE
REPRESENTATION. USE OF THE STATUS ENQUIRY PROCEDURE IN THIS CIRCUMSTANCE DOES NOT PROVIDE USEFUL ADDTIONAL
INFORMATION TO THE NETWORK.7CALLRECEIVEDPROGRESSWASSETUPB/CAST?STATUSNOTE 27PROGRESSINDICATION75.2.65.8.4,NOTE 1INFOWASSETUPB/CAST?INFOINDICATION755.8.4,NOTE 1YNYNFigure5(sheet26of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)43Process NETWORK_SIDE27(85)NETWORK SIDE SDL DIAGRAMSNOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATE RETURNED IN THE STATUS MESSAGE SHOULD BE 6.NOTE 2. AS AN ALTERNATIVE, A STATUS ENQUIRY PROCEDURE ACCORDING TO SUBCLAUSE 5.8.4 OF ETS 300403-1 MAY ALSO BE FOLLOWED.
IN THIS CASE, AN INDIVIDUAL PROCESS SHOULD BE CREATED FOR THE RESPONDING TERMINAL IN ORDER TO CONTROL TIMER T322
AND THE APPROPRIATE RESPONSE. THIS PROCEDURE IS NOT DOCUMENTED IN THIS ETS AS IT INCREASES THE COMPLEXITY OF THE
REPRESENTATION. USE OF THE STATUS ENQUIRY PROCEDURE IN THIS CIRCUMSTANCE DOES NOT PROVIDE USEFUL ADDITIONAL
INFORMATION TO THE NETWORK.7CALLRECEIVEDRELEASE5.8.4WASSETUPB/CAST?RELEASEINDICATIONRELEASECOMPLETESTOP T301IF IMPLEMENTEDRELEASEB-CHANNEL IFNOT RELEASEDRELEASECR0RELEASECOMPLETE7DISCONNECTWASSETUPB/CAST?STOP T301IF IMPLEMENTEDDISCONNECTB-CHANNEL IFNOT DISCONNECTEDDISCONNECTINDICATION11STATUSNOTE 275.3.35.8.4,NOTE 1RELEASECOMPLETE5.8.4WASSETUPB/CAST?STOP T301IF IMPLEMENTEDRELEASEB-CHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECR07NYNYNYFigure5(sheet27of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)44NETWORK SIDE SDL DIAGRAMSProcess NETWORK_SIDE28(85)NOTE 1. IF TIMER T301 EXPIRED, CAUSE #102
SHOULD BE SENT IN THE APPROPRIATE MESSAGE.7CALLRECEIVEDDISCONNECTREQUEST(CAUSE)5.3.2 (e)5.3.4STOP T301IF IMPLEMENTEDWASSETUPB/CAST?INT
*RELEASEREQUESTTO ALLACTIVE CESs,CAUSE,NOTE 1T312RUNNING?RELEASEBCHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECR0RELEASEBCHANNEL IFNOT RELEASED22DISCONNECT(CAUSE)NOTE 1STARTT30512TIMEOUTT3015.2.5.4RELEASEINDICATIONINFOREQUEST5WASSETUPB/CAST?INFO7INT
*INFOREQUESTTO ALLACTIVE CESs7YNYNNYFigure5(sheet28of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)45Process NETWORK_SIDE29(85)NETWORK SIDE SDL DIAGRAMS7CALLRECEIVEDINT
*PROGRESSINDICATION(CES)PROGRESSINDICATION7INT
*INFOINDICATION(CES)INFOINDICATION7INT
*CONNECTINDICATION(CES)+PRESELECTCESCONNECTINDICATIONSTOP T301IF IMPLEMENTED8INT
*CALL PROCINDICATION(CES)7INT
*ALERTINGINDICATION(CES)Figure5(sheet29of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)46Process NETWORK_SIDE30(85)NETWORK SIDE SDL DIAGRAMS7CALLRECEIVEDINT
*REL COMPINDICATION(CES)DELETECES7INT
*RELEASEINDICATION(CES)5.2.5.3OTHERCESs ABLE TOPROCEED?SAVECAUSE7T312RUNNING?RELEASEINDICATIONSTOP T301IF IMPLEMENTEDRELEASEB-CHANNEL IFNOT RELEASEDRELEASECR0TIMEOUTT3125.2.5.3ANYCES ABLE TOPROCEED?7YNYNNYFigure5(sheet30of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)47Process NETWORK_SIDE31(85)NETWORK SIDE SDL DIAGRAMS7ICALLRECEIVEDRELEASECOMPLETEINT
*RELEASEINDICATION(CES)INT
*REL COMPINDICATION(CES)RELEASEINT
*RELEASEINDICATION(CES)RELEASECOMPLETEINT
*REL COMPINDICATION(CES)DISCONNECTINT
*RELEASEINDICATION(CES)RELEASESTARTT30819IPROGRESSINT
*PROGRESSINDICATION(CES)7ICONNECTINT
*CONNECTINDICATION(CES)8IINFOINT
*INFOINDICATION(CES)7IINDIVIDUAL PROCESSFigure5(sheet31of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)48Process NETWORK_SIDE32(85)NETWORK SIDE SDL DIAGRAMS7ICALLRECEIVEDINDIVIDUAL PROCESSINT
*INFOREQUESTINFO7IINT
*RELEASEREQUEST(CAUSE)RELEASE(CAUSE)STARTT30819IFigure5(sheet32of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)49NETWORK SIDE SDL DIAGRAMSProcess NETWORK_SIDE33(85)8CONNECTREQUESTSETUPCOMPLETEREQUEST5.2.8,5.2.95.3.2 (b)+CONNECTBCHANNELWASSETUPB/CAST?SELECTCESCONNECT ACK(SELECTED CES)END PROCESS
*(SELECTED CES)INT
*RELEASEREQUEST(OTHER CESs, CAUSE #26)10CONNECTACK10DISCONNECTREQUEST(CAUSE)5.3.2 (e)5.3.4WASSETUPB/CAST?DISCONNECTSTARTT30512INT
*RELEASEREQUEST(TO ALL ACTIVE CESs, CAUSE)T312RUNNING?RELEASEBCHANNEL IFNOT RELEASEDRELEASEINDICATIONRELEASECR0RELEASEBCHANNEL IFNOT RELEASED22INFOREQUEST5WASSETUPB/CAST?INFO8INT
*INFOREQUESTTO ALLACTIVE CESs8YNNYNYNYFigure5(sheet33of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)50Process NETWORK_SIDE34(85)NETWORK SIDE SDL DIAGRAMSNOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATE RETURNED IN THE STATUS MESSAGE SHOULD BE 6.NOTE 2. AS AN ALTERNATIVE, A STATUS ENQUIRY PROCEDURE ACCORDING TO SUBCLAUSE 5.8.4 OF ETS 300403-1 MAY ALSO BE FOLLOWED.
IN THIS CASE, AN INDIVIDUAL PROCESS SHOULD BE CREATED FOR THE RESPONDING TERMINAL IN ORDER TO CONTROL TIMER T322
AND THE APPROPRIATE RESPONSE. THIS PROCEDURE IS NOT DOCUMENTED IN THIS ETS AS IT INCREASES THE COMPLEXITY OF THE
REPRESENTATION. USE OF THE STATUS ENQUIRY PROCEDURE IN THIS CIRCUMSTANCE DOES NOT PROVIDE USEFUL ADDITIONAL
INFORMATION TO THE NETWORK.8CONNECTREQUESTINFO55.8.4,NOTE 1WASSETUPB/CAST?INFOINDICATION8STATUSNOTE 28CALLPROCEEDING5.2.95.3.2 (b)5.8.4WASSETUPB/CAST?REPORTSTATUS(CAUSE #97,#98 OR #101)8CREATEPROCESS(CES)INT
*RELEASEREQUEST(CES, CAUSE #26)8CONNECTALERTINGSETUP ACKNYNYFigure5(sheet34of85):NetworksideSDLdiagramSIST EN 300 403-2 V1.3.1:2005

ETSIETSIEN300403-2V1.3.1(2000-11)51Process NETWORK_SIDE35(85)NETWORK SIDE SDL DIAGRAMSNOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL
...