SIST ETS 300 009:1997

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digitalno omrežje z integriranimi storitvami (ISDN) - Signalizacija št. 7 - Krmilni del signalizacijske zveze (SCCP) (nepovezavni in povezavni) za podporo mednarodnega vzajemnega povezovanjaIntegrated Services Digital Network (ISDN); Signalling System No.7; Signalling Connection Control Part (SCCP) [connectionless and connection-oriented] to support international interconnection33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 009 E2SIST ETS 300 009:199en01-PDUHF199SIST ETS 300 009:199SLOVENSKI
STANDARD



PSIST ETS 300 009:1996



EUROPEANETS 300 009TELECOMMUNICATIONJanuary 1995STANDARDSecond EditionSource: ETSI TC-SPSReference: RE/SPS-02003ICS:33.080Key words:ISDN, SS7, SCCPIntegrated Services Digital Network (ISDN);Signalling System No.7;Signalling Connection Control Part (SCCP)[connectionless and connection-oriented]to support international interconnectionETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1995. All rights reserved.PSIST ETS 300 009:1996



Page 2ETS 300 009: January 1995Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.PSIST ETS 300 009:1996



Page 3ETS 300 009: January 1995ContentsForeword.51Scope.72Normative references.73Abbreviations.74Requirements.85Modifications to ITU-T Recommendations Q.711 to Q.714.85.1Modifications to ITU-T Recommendation Q.711 "Functional description of thesignalling connection control part".85.2Modifications to ITU-T Recommendation Q.712 "Definition and function of SCCPmessages".115.3Modifications to ITU-T Recommendation Q.713 "SCCP formats and codes".135.4Modifications to ITU-T Recommendation Q.714 "Signalling connection control partprocedures".156Modifications not included in the ITU-T Recommendations.206.1Compatibility issues.206.1.1Interface to MTP according to ETS 300 008.206.1.2Segmenting/reassembly of connectionless messages.216.1.3Embedded method.216.2Additional information for the SCCP embedded method.216.2.1Service request for UUS3.216.2.2Treatment in transit exchanges.216.2.3Failure situations.226.2.3.1SCCP not existing in another network.226.2.3.2Embedded method not supported by SCCP.226.2.3.3ISUP fails to invoke a REQUEST TYPE 2 primitive in atransit exchange.226.2.3.4Node restarting during setup.226.3Specification and Description Language (SDL) diagrams for connectionlesssegmenting/reassembly.23Annex A (informative):Bibliography.36History.37PSIST ETS 300 009:1996



Page 4ETS 300 009: January 1995Blank pagePSIST ETS 300 009:1996



Page 5ETS 300 009: January 1995ForewordThis second edition European Telecommunication Standard (ETS) has been produced by the SignallingProtocols and Switching (SPS) Technical Committee of the European Telecommunications StandardsInstitute (ETSI).This ETS further develops the Signalling System No.7 protocols for the Integrated Services DigitalNetwork (ISDN), Public Switched Telephone Network (PSTN) and Public Land Mobile Networks (PLMNs).It is based on ITU-T Recommendations Q.711 to Q.714 and Q.716 (1993).This ETS is based on the assumption concerning the interconnection of national Signalling ConnectionControl Parts (SCCPs) that the Message Transfer Part (MTP) specified in ETS 300 008 (1991) supportsthe SCCP for international interconnection.This second edition of ETS 300 009 introduces:-the use of connectionless functions in international relay points and gateways;-the use of the connection-oriented (Class 2, with embedded connection setup only) service, whichis required to support the ISDN User-To-User Signalling Service 3 (UUS3) (see ETS 300 356-2);-the procedures for connectionless segmentation and reassembly, needed to support the IntelligentNetwork Application Protocol (INAP) and the Mobile Application Part (MAP), Version 2;-the rules for the application of Signalling Connection Control Part (SCCP) addressing in theinternational network.In (a) later edition(s), the following features are foreseen to be added:-the possibility of having subsystems within the international network, for example the Operations,Maintenance and Administration Part (OMAP);-the SCCP restart procedure;-Open System Interconnection (OSI) adaptations to allow the use of Signalling System No.7 astransport network for Telecommunications Management Network (TMN) information.Proposed transposition datesDate of latest announcement of this ETS (doa):30 April 1995Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 October 1995Date of withdrawal of any conflicting National Standard (dow):31 October 1995PSIST ETS 300 009:1996



Page 6ETS 300 009: January 1995Blank pagePSIST ETS 300 009:1996



Page 7ETS 300 009: January 19951ScopeThis European Telecommunication Standard (ETS) defines the use of connectionless functions ininternational relay points and gateways1), the use of the connection-oriented (Class 2, with embeddedconnection setup only) service, the procedures for connectionless segmentation and reassembly, and therules for the application of Signalling Connection Control Part (SCCP) addressing in the internationalnetwork.This ETS is applicable to the international network and does not intend to restrict national networks.2Normative referencesThis ETS incorporates by dated or undated reference, provisions from other publications. Thesenormative references are cited as the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ITU-T Recommendation Q.711 (1993): "Specifications of Signalling SystemNo.7; Functional description of the signalling connection control part".[2]ITU-T Recommendation Q.712 (1993): "Specifications of Signalling SystemNo.7; Definition and function of SCCP messages".[3]ITU-T Recommendation Q.713 (1993): "Specifications of Signalling SystemNo.7; SCCP formats and codes".[4]ITU-T Recommendation Q.714 (1993): "Specifications of Signalling SystemNo.7; Signalling connection control part procedures".[5]ITU-T Recommendation Q.716 (1993): "Specifications of Signalling SystemNo.7; Signalling Connection Control Part (SCCP) performances".[6]ETS 300 008 (1991): "Integrated Services Digital Network (ISDN); CCITTSignalling System No.7; Message Transfer Part (MTP) to support internationalinterconnection".3AbbreviationsFor the purposes of this ETS, the following abbreviations apply:CCConnection Confirm messageCCBSCompletion of Calls to Busy SubscriberCRConnection Request messageDAData Acknowledgement messageDPCDestination Point CodeDT2Data Form 2 messageEAExpedited Data Acknowledgement messageEDExpedited Data messageINAPIntelligent Network Application ProtocolISDNIntegrated Services Digital NetworkISSISDN Supplementary ServicesISUPISDN User PartITInactivity Test messageLBCSLocal Broadcast ControlMAPMobile Application PartMTPMessage Transfer PartOMAPOperations, Maintenance and Administration PartOPCOriginating Point Code
1)The SCCP gateway functions are relay functions that bridge two Message Transfer Part (MTP) networks.PSIST ETS 300 009:1996



Page 8ETS 300 009: January 1995OSIOpen System InterconnectionPLMNPublic Land Mobile NetworkPSTNPublic Switched Telephone NetworkRIRouteing IndicatorRSCReset Confirm messageRSRReset Request messageSCCPSignalling Connection Control PartSCLCSCCP ConnectionLess ControlSCOCSCCP Connection-Oriented ControlSDLSpecification and Description LanguageSLSSignalling Link SelectionSOGSubsystem-Out-of-service-Grant messageSORSubsystem-Out-of-service-Request messageSPACSignalling Point Allowed ControlSPCSignalling Point CodeSPCCSignalling Point Congested ControlSPPCSignalling Point Prohibited ControlSSASubSystem-Allowed messageSSNSubSystem Number messageSSPSubSystem-Prohibited messageSSTSubSystem-status-Test messageTCAPTransaction Capabilities Application PartTMNTelecommunications Management NetworkUDTUnitDaTa messageUDTSUnitDaTa Service messageUUSUser-to-User SignallingUUS3UUS Service 3XUDTeXtended UnitDaTa messageXUDTSeXtended UnitDaTa Service message4RequirementsThis ETS is based on ITU-T Recommendations Q.711 to Q.714 ([1] to [4]) and Q.716 [5]. Therequirements of these recommendations shall apply with the modifications identified in clause 5 and thespecific requirements given in clause 6 of this ETS.NOTE:Some of the clauses in this ETS on SCCP management procedures are indicated as"not required". In these cases, ITU-T White Book (1993) procedures may be applied ifdesirable. This should not cause incompatibilities with this ETS.5Modifications to ITU-T Recommendations Q.711 to Q.714The following exceptions to ITU-T Recommendations Q.711 to Q.714 ([1] to [4]) shall apply.5.1Modifications to ITU-T Recommendation Q.711 "Functional description of the signallingconnection control part"§ 2Services provided by the SCCPClass 3 is not required.§ 2.1Connection-oriented servicesPermanent signalling connections are not required.§ 2.1.1.1.2Data transfer phaseSequence control and Flow control are not required.PSIST ETS 300 009:1996



Page 9ETS 300 009: January 1995§ 2.1.1.2.1OverviewN-CONNECT REQUEST is not required. N-EXPEDITED DATA, N-DATA ACKNOWLEDGE, andN-RESET are not required.§ 2.1.1.2.2Connection establishment phaseThe N-CONNECT REQUEST primitive shall not be used. Instead, the ISDN User Part (ISUP) requestsconnection setup with the REQUEST TYPE 1 or REQUEST TYPE 2 interface elements.Negotiation of expedited data is not required.§ 2.1.1.2.3Data transfer phaseN-EXPEDITED DATA, N-DATA ACKNOWLEDGE, and N-RESET are not required.§ 2.1.1.3.2Connection establishment interface elementsThese interface elements are used by ISUP for the embedded setup of connections. The "receiptconfirmation selection" shall be set to false. The "quality of service parameter set" shall indicate protocolclass 2.NOTE:In the international network, the REQUEST TYPE 1 interface element would normallynot be used. This interface element only applies at the originating node in the nationalnetwork. However, it should be possible that ISUP performs an association ofconnection sections itself on user level (see ITU-T Recommendation Q.730,figure 12/Q.730). This may be necessary if different versions of SCCP are used in thenational and international networks, or if User-to-User data are transported in thenational network in another way.§ 2.1.2Permanent signalling connectionsNot required.§ 2.2.1DescriptionIf the in-sequence delivery is not required (protocol class 0), the SCCP shall insert Signalling LinkSelection (SLS) codes with respect to the appropriate load sharing within the signalling network. If the in-sequence delivery is required (protocol class 1), the SCCP, at the originating node, while adhering to thesequence control instruction from the user, shall allocate SLS codes between sequence streams withrespect to appropriate load sharing within the signalling network.As in relay nodes, user sequence control is not available, there shall be a fixed mapping betweenincoming and outgoing SLS code values for class 1. This mapping may be different for different signallingrelations.§ 2.3.2.1OverviewN-STATE and N-COORD are not required.NOTE:N-STATE and N-COORD are not required as long as there are no (duplicated)subsystems (other than ISUP) in the international network.§ 2.3.2.2Parameters"Affected subsystem", "Subsystem multiplicity indicator", "User status" and "Remote SCCP status" are notrequired.PSIST ETS 300 009:1996



Page 10ETS 300 009: January 1995§ 2.3.2.3.1COORDN-COORD is not required.NOTE:N-COORD is not required as long as there are no (duplicated) subsystems (other thanISUP) in the international network.§ 2.3.2.3.2STATESubsystem management is not required.NOTE:Subsystem management is not required as long as there are no (duplicated)subsystems (other than ISUP) in the international network.§ 3.2Primitives and parametersThe "cause" parameter in the MTP-STATUS primitive may take the values:-"Signalling point congested";-"User part unavailable".For the cause "Signalling point congested", no congestion priorities are used.NOTE:The values:-"User part unavailability: unknown";-"User part unavailability: unequipped remote user";-"User part unavailability: inaccessible remote user",occur in ITU-T Recommendation Q.701, § 8. The first one corresponds to "User partunavailable" in ETS 300 008 [6], the latter two are not part of ETS 300 008 [6].§ 3.2.4STATUSThe "cause" parameter in the MTP-STATUS primitive may take the values:-"Signalling point congested";-"User part unavailable".For the cause "Signalling point congested", no congestion priorities are used.NOTE:The values:-"User part unavailability: unknown";-"User part unavailability: unequipped remote user";-"User part unavailability: inaccessible remote user",occur in ITU-T Recommendation Q.701, § 8. The first one corresponds to "User partunavailable" in ETS 300 008 [6], the latter two are not part of ETS 300 008 [6].§ 4.1Connection-oriented functionsClass 3 functions are not required.§ 4.1.1.2Data transfer functionFlow control is not required.Expedited data support is not required.Missequence detection is not required.Reset is not required.Receipt confirmation is not required.PSIST ETS 300 009:1996



Page 11ETS 300 009: January 1995§ 4.1.2Functions for permanent signalling connectionsNot required.§ 4.3Management functionsCo-ordinated state change is not required.NOTE:Co-ordinated state change is not required as long as there are no (duplicated)subsystems (other than ISUP) in the international network.§ 4.4Routeing and translation functionsThe routeing and translation function of SCCP does not apply for the embedded method.NOTE:ISUP executes its own routeing function. It provides the minimally necessaryinformation for SCCP in the MTP-routeing label and the Originating Point Code (OPC)field of the embedded request (see ITU-T Recommendation Q.763, § 3.15).5.2Modifications to ITU-T Recommendation Q.712 "Definition and function of SCCPmessages"§ 1.2Connection Request (CR)Not required (only embedded connection requests are issued).§ 1.4Data Acknowledgement (DA)Not required.§ 1.6Data Form 2 (DT2)Not required.§ 1.7Expedited Data (ED)Not required.§ 1.8Expedited Data Acknowledgement (EA)Not required.§ 1.13Reset Confirm (RSC)Not required.§ 1.14Reset Request (RSR)Not required.§ 1.15SubSystem-Allowed (SSA)Not required.§ 1.16Subsystem-Out-of-service-Grant (SOG)Not required.§ 1.17Subsystem-Out-of-service-Request (SOR)Not required.PSIST ETS 300 009:1996



Page 12ETS 300 009: January 1995§ 1.18SubSystem-Prohibited (SSP)Not required.§ 1.19SubSystem-Status-Test (SST)Not required.§ 2.4creditNot required.§ 2.6diagnosticNot required.§ 2.11receive sequence numberNot required.§ 2.14reset causeNot required.§ 2.17sequencing/segmentingNot required.§ 2.18subsystem multiplicity indicatorFor further study.§ 3Inclusion of fields in messagesTable 1/Q.712: Inclusion of fields in messages andTable 2/Q.712: SCCP management messagesManagement messages are not required.PSIST ETS 300 009:1996



Page 13ETS 300 009: January 19955.3Modifications to ITU-T Recommendation Q.713 "SCCP formats and codes"§ 3.4.1Address indicatorOn transmission of the called party address, the SubSystem Number (SSN) indicator field shall always beincluded and set to 0 if unknown.Bit 8 (reserved for national use) shall always be coded 0 and is not evaluated.§ 3.4.2.2Subsystem numberExcept for ISUP, there are currently no SCCP-users in the international network. Nevertheless, SSNshave to be allocated for all those SCCP subsystems whose messages may cross network borders, so thatinternational agreement is needed for the SSNs used. If not yet specified by ITU-T, such SSNs will betaken up in this ETS. In addition to the SSNs allocated already in ITU-T Recommendation Q.713 [3], oneadditional SSN is necessary for ISDN Supplementary Services (ISS) to identify the services (completion ofcalls to busy subscribers, reverse charging, etc.) that are based on the Transaction CapabilitiesApplication Part (TCAP). The value 0000 1011 is allocated for ISS.Bits8 7 6 5 4 3 2 1.0 0 0 0 1 0 1 1ISDN Supplementary Services (ISS)0 0 0 0 1 1 0 0}to}spare1 1 1 1 1 1 1 0}1 1 1 1 1 1 1 1reserved for expansion§ 3.4.2.3.1Global title indicator = 0001Not required for transmission.§ 3.4.2.3.2Global title indicator = 0010Not required for transmission.For use by the Completion of Calls to Busy Subscriber (CCBS) supplementary service, one value isallocated for the translation type.Bits8 7 6 5 4 3 2 10 0 0 0 0 0 0 0not used.0 0 0 1 0 0 0 1ISDN end-to-end supplementary services (e.g. CCBS).1 1 1 1 1 1 1 1reserved for expansionNOTE:The CCBS supplementary service uses Global title indicator = 0100 (seeETS 300 356-18). However, the translation type is defined in § 3.4.2.3.2 of ITU-TRecommendation Q.713 [3] and referred to in the subsequent paragraphs coveringGlobal title indicator values 0011 and 0100.§ 3.4.2.3.3Global title indicator = 0011Not required for transmission.PSIST ETS 300 009:1996



Page 14ETS 300 009: January 1995§ 3.5Calling party addressFor the international network, if segmenting/reassembly of connectionless messages or the return optionis used, it is necessary to supply in the calling party address a unique identification of the originator.Inclusion of a global title, uniquely identifying the caller would be sufficient for this purpose. The "addressindicator" field shall then never be coded as the "all zeroes" value.§ 3.8Receive sequence numberNot required.§ 3.9Sequencing/segmentingNot required.§ 3.10CreditNot required.§ 3.13Reset causeNot required.§ 4.2Connection requestNot required (only embedded connection requests are issued).§ 4.8Data form 2Not required.§ 4.9Data acknowledgementNot required.§ 4.12Expedited dataNot required.§ 4.13Expedited data acknowledgementNot required.§ 4.14Reset requestNot required.§ 4.15Reset confirmNot required.§ 5SCCP management messages and codesSubsystem management messages are not required.NOTE:Subsystem management messages are not required as long as no subsystems (otherthan ISUP) are introduced in the international network.PSIST ETS 300 009:1996



Page 15ETS 300 009: January 19955.4Modifications to ITU-T Recommendation Q.714 "Signalling connection control partprocedures"§ 1.1.2Protocol classesClass 3 procedures are not required.§ 1.1.2.2Protocol class 1The in-sequence delivery not only relies on the properties of the MTP-network, but also SCCP shallguarantee the sequential processing of SCCP-messages. This excludes e.g. arbitrary parallel processingof global title translations in relay nodes.§ 1.1.2.3Protocol class 2Only the embedded method of connection setup is required.§ 1.1.2.4Protocol class 3Not required.§ 1.1.3Signalling connectionsNOTE:The ITU-T White Book (1993) leaves the possibility of having relay points withoutcoupling for connection-oriented services for further study. This because it is not clearhow a connection can be completed (with a Connection Confirm (CC) message) to theoriginator without changing or including the calling address parameter of theConnection Request (CR) message in relay nodes.For the embedded method, there is in fact the possibility of having no association in anISUP relay point (ISUP would in this case simply pass the embedded request furtheron, without issuing a REQUEST TYPE 2). This is in this case no problem, since theOPC of the originating node or of the last relay node with coupling is included in theembedded connect request of the IAM message. It is therefore always possible toroute back the CC message to the correct originator.§ 1.2.1Connection establishmentThe CR message is not used. The connection request is carried embedded in an ISUP message instead.NOTE:See also the note relating to § 1.1.3.The ISUP has the control whether the association of connection sections shall be performed or not. If theSCCP receives a REQUEST TYPE 2 from ISUP with the "reply bit" set, an association of connectionsections shall be performed.§ 1.2.2Data transferFlow control is not required.Expedited data support is not required.Missequence detection is not required.Reset is not required.Receipt confirmation is not required.PSIST ETS 300 009:1996



Page 16ETS 300 009: January 1995§ 2.2.2Messages from connection-oriented or connectionless control to SCCP routeingcontrolIn order to route an SCCP message from one country to another, a global title shall always be available.Therefore, the possibility of routeing on Destination Point Code (DPC) and SSN shall not apply for thetransit traffic in the international network.NOTE 1:Routeing on DPC and SSN does not apply as long as no subsystems (other thanISUP) are introduced in the international network.For routeing from one network to another, passing through the international network, the RouteingIndicator (RI) shall always be set to route on global title.NOTE 2:The routeing of the embedded connect requests for ISUP, is not done by SCCP, but byISUP itself. The other connection-oriented messages are routed on DPC only.§ 3Connection-oriented proceduresClass 3 procedures are not required.§ 3.1.1GeneralN-CONNECT REQUEST is not required.§ 3.1.3.1Protocol class negotiationIf a connection request for protocol class 3 is received, it shall be lowered to class 2 in response.§ 3.1.3.2Flow control window negotiationNot required.§ 3.1.4.1Initial actionsThe N-CONNECT REQUEST is not required. Only the REQUEST TYPE 1 interface element is used. Theproposed protocol class shall be 2, no credit is initiated.§ 3.1.4.2Subsequent actionsIf the protocol class received in the CC message is not equal to 2, the connection shall be released. AN-DISCONNECT INDICATION primitive is sent to ISUP, and the release procedure is initiated on thesignalling connection, indicating "inconsistent connection data".§ 3.1.5.1Initial actionsThe CR message is not required. Only the REQUEST TYPE 2 interface element is used. If a connectionrequest for protocol class 3 is received, it shall be lowered to class 2 in response.§ 3.1.5.2Subsequent actionsIf the received protocol class received in the CC message is not equal to 2, the connection refusalprocedure shall be initiated, indicating "inconsistent connection data".§ 3.1.6.1Initial actionsThe CR message is not required. If a connection request for protocol class 3 is received, it shall belowered to class 2 in response.§ 3.1.6.2Subsequent actionsThere is no need to update the protocol class and credit anymore, since only class 2 is proposed to theuser.PSIST ETS 300 009:1996



Page 17ETS 300 009: January 1995§ 3.2.1Actions at node initiating connection refusal1a) is not required.§ 3.4Inactivity controlSupport of supervision of connection by the SCCP user function is not required. The SCCP itself performsthis supervision. The inactivity test procedure shall apply on all connection sections within the internationalnetwork.§ 3.5.1GeneralOnly the DT1 message is required.§ 3.5.2Flow controlNot required.§ 3.6Expedited data transferExpedited data support is not required.§ 3.7ResetReset is not required.§ 3.8.2.1Initial actions3) Permanent signalling connections are not required.§ 3.9Permanent signalling connectionsNot required.§ 4.1.1Segmentation/reassemblyThe international network shall be able to accept and route (including hop-counter check) the new XUDTand XUDTS messages.NOTE:The principle of Segmenting/reassembly of connectionless messages is such that noactions are necessary in relay nodes, except for routeing the XUDT and XUDTSmessages in the same way as UnitDaTa (UDT) and UnitDaTa Service (UDTS)messages, as long as no subsystems (other than ISUP) are introduced in theinternational network.§ 4.1.1.2.3Return on error proceduresThe timeout of the reassembly timer shall be considered to be one of the errors for which this procedureapplies.§ 5.1GeneralNo management procedures are required except those for updating SCCP translation tables in order totransfer messages to the backup node under primary node failure conditions, i.e. only ITU-TRecommendation Q.714 [4], § 5.2 applies, modified as indicated below.NOTE:The introduction of User-To-User Signalling Service 3 (UUS3) causes at least onesubsystem to exist in the international network (ISUP). However, the routeing for thissubsystem is performed by ISUP. ISUP will check Signalling Point Code (SPC) statusand take actions on SPC failures. Therefore, no subsystem management is neededuntil other subsystems like the Operations, Maintenance and Administration Part(OMAP) are introduced in the international network.PSIST ETS 300 009:1996



Page 18ETS 300 009: January 1995§ 5.2.1GeneralSignalling point status management shall update translation and status based on the information ofnetwork failure or recovery provided by the MTP-PAUSE INDICATION and MTP-RESUME INDICATIONprimitives. This allows alternative routeing to backup signalling points.§ 5.2.2Signalling point prohibitedWhen the SCCP management receives an MTP-PAUSE INDICATION relating to a destination thatbecomes inaccessible, SCCP management shall inform the SCCP translation function to update itstranslation tables.§ 5.2.3Signalling point allowedWhen the SCCP management receives an MTP-RESUME INDICATION relating to a destination that hasbecome accessible, SCCP management shall inform the SCCP translation function to update itstranslation tables.SCCP management messages are not required.If a MTP based on ETS 300 008 [6] is used, the MTP-STATUS INDICATION primitive and the indicationabout the end of MTP restart shall be processed.If a MTP-STATUS INDICATION with cause "user part unavailable" is received, the sending of traffic to theunavailable remote SCCP shall be temporarily stopped. The method used to stop the traffic isimplementation dependent.After reception of the indication of the end of MTP restart, the actions specified in § 5.2.5 apply.§ 5.2.5Local MTP availabilityIf a MTP based on ETS 300 008 [6] is used, the indication of the end of MTP restart shall be processed.SCCP shall assure as smooth and gradual a restart of the traffic as feasible. The means to do this areimplementation dependent.§ 5.3Subsystem status managementSubsystem management is not required.§ 5.3.1GeneralCongestion handling is not required.§ 5.3.2.1Receipt of a message for a prohibited subsystemSubsystem management is not required.§ 5.3.2.2Receipt of Subsystem-Prohibited message or N-STATE REQUEST primitive or localuser failedSubsystem management is not required.§ 5.3.3Subsystem allowedSubsystem management is not required.§ 5.3.4Subsystem status testSubsystem management is not required.PSIST ETS 300 009:1996



Page 19ETS 300 009: January 1995§ 5.3.5Co-ordinated status changeCo-ordinated status change is not required.§ 5.3.6.2User-out-of-serviceNot required.§ 5.3.6.3User-in-serviceNot required.§ 5.3.6.4Signalling point/remote SCCP ina
...