ETSI EN 301 007-1 V1.1.3 (1998-05)

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 - Obratovalni, vzdrževalni in administrativni del (OMAP) - 1. del: Specifikacija protokolaIntegrated Services Digital Network (ISDN); Signalling System No.7; Operations, Maintenance and Administration Part (OMAP); Part 1: Protocol specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 007-1 Version 1.1.3SIST EN 301 007-1:2000en01-december-2000SIST EN 301 007-1:2000SLOVENSKI
STANDARD
EN 301 007-1 V1.1.3 (1998-05)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Signalling System No.7;Operations, Maintenance and Administration Part (OMAP);Part 1: Protocol specificationSIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)2ReferenceDEN/SPS-02010-1 (9bo90ie0.PDF)KeywordsISDN, MRVT, OMAP, SS7ETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frhttp://www.etsi.frhttp://www.etsi.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998.All rights reserved.SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)3ContentsIntellectual Property Rights.5Foreword.51Scope.62References.62.1Normative references.62.2Informative references.73Abbreviations.74General exceptions and clarifications to ITU-T Recommendations Q.750 to Q.751.84.1Q.750.84.2Q.751.1.84.2.1Subclause 1 to 6.1 inclusive of Q.751.1.84.2.2Subclause 6.2 of Q.751.1.84.2.3Subclause 7 of Q.751.1.104.2.4Subclause 7.1 of Q.751.1.104.2.4.1Subclause 7.1.8 of Q.751.1.104.2.4.2Subclause 7.1.9 of Q.751.1.104.2.5Subclause 7.4 of Q.751.1.104.2.6Subclause 7.5 of Q.751.1.104.2.8Subclause 7.8 of Q.751.1.104.2.9Annex A of Q.751.1.104.2.10Annex B of Q.751.1.104.2.11Annex E and annex F of Q.751.1.104.2.12Object model for MTP accounting and verification.115Exceptions and clarifications to ITU-T Recommendation Q.752.115.1Subclause 1 of Q.752.115.2Subclause 2 through 5 of Q.752.125.3Subclause 6 of Q.752.125.4Subclause 7 of Q.752.135.5The tables of Q.752.166General exceptions and clarifications to ITU-T Recommendations Q.750 to Q.754 for the MRVTest.186.1Use of SCCP addressing.186.2Definitions.187Specific exceptions and clarifications to ITU-T Recommendations Q.750 to Q.754 for the MRVTest.197.1Q.750.197.2Q.752.197.3Q.753.197.3.1Subclause 2 of Q.753.197.3.2Subclause 2.5.2 of Q.753.297.4Q.754.437.4.1Subclause 1.437.4.2Subclause 2.447.4.3Subclause 6 of Q.754.48SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)4Annex A (informative):Issues to be determined for the MRV test.53Annex B (informative):Network interconnection issues.54B.1Network design issues.54B.2Network naming issues.54B.3Network implementation issues.55History.56SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)5Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin ETR 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect ofETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSIWeb server (http://www.etsi.fr/ipr).Pursuant to the ETSI Interim IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. Noguarantee can be given as to the existence of other IPRs not referenced in ETR 314 (or the updates onhttp://www.etsi.fr/ipr) which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).The present document details exceptions and clarifications to ITU-T Recommendations Q.750 [1], Q.751.1 [10], Q.752to Q.754 [2] to [4], defining the management of international ITU-T Signalling System No.7 networks, for examplethose used to provide the pan-European cellular digital radio system and the Integrated Services Digital Network(ISDN).The present document also lists considerata for the interconnection of ITU-T Signalling System No.7 (SS7) networks,using ITU-T Recommendation M.4110 [17] as an aid, as well as ITU-T Recommendations Q.750 [1], Q.752
toQ.755
[2] to [18] and Q.780 [15].The present document is part 1 of a multi-part EN covering Integrated Services Digital Network (ISDN) SignallingSystem No.7 Operations, Maintenance and Administration Part (OMAP), as identified below:Part 1:"Protocol specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification".National transposition datesDate of adoption of this EN17 April 1998Date of latest announcement of this EN (doa):31 August 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):28 February 1999Date of withdrawal of any conflicting National Standard (dow):28 February 1999SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)61ScopeThis first part of EN 301 007 defines the requirements for monitoring and measuring in Signalling System No.7networks (including measurements for message traffic accounting), the requirements for the Message Transfer Part(MTP) and the Signalling Connection Control Part (SCCP) managed objects, and the requirements for the MTP RoutingVerification Test (MRVT) of Signalling System No.7 management. It also lists the considerations applicable when inter-connecting Signalling System No.7 networks.The requirements in the present document are based upon ITU-T Recommendations Q.750 [1], Q.751.1 [10], Q.752 toQ.754 [2] to [4], and ETS 300 356-1 [11].The present document draws upon ITU-T Recommendations Q.750 [1], Q.752 to Q.754 [2] to [4], Q.755 [18] andM.4110 [17] as informative references, for considerations applicable to the inter-connection of
Signalling System No.7networks.NOTE:The requirements of M.4110 [17] are used to derive the considerations in the present document, but thepresent document does not make any statement as to the applicability or otherwise of M.4110 [17].2ReferencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)publications without mention of a specific version, in which case the latest version applies.A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.2.1Normative references[1]ITU-T Recommendation Q.750 (1993): "Overview of Signalling System No. 7 management".[2]ITU-T Recommendation Q.752 (1993): "Monitoring and measurements for Signalling SystemNo. 7 networks".[3]ITU-T Recommendation Q.753 (1993): "Signalling System No. 7 management functions MRVT,SRVT and CVT and definition of the OMASE-user".[4]ITU-T Recommendation Q.754 (1993): "Signalling System No. 7 management application serviceelement (ASE) definitions".[5]ITU-T Recommendation Q.704 : "Signalling network functions and messages".[6]ETS 300 008-1 (1997): "Integrated Services Digital Network (ISDN); Signalling System No.7;Message Transfer Part (MTP) to support international interconnection; Part 1: Protocolspecification [ITU-T Recommendations Q.701 (1993), Q.702 (1988), Q.703 to Q.706 (1993),Q.707 (1988) and Q.708 (1993), modified]".[7]ETS 300 009-1 (1996), Third Edition: "Integrated Services Digital Network (ISDN); SignallingSystem No.7; Signalling Connection Control Part (SCCP) (connectionless and connection-orientedclass 2) to support international interconnection; Part 1: Protocol specification [ITU-TRecommendations Q.711 to Q.714 and Q.716 (1993), modified]".SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)7[8]ETS 300 287-1 edition 2 (1996): "Integrated Services Digital Network (ISDN); Signalling SystemNo.7; Transaction Capabilities (TC) version 2; Part 1: Protocol specification [ITU-TRecommendations Q.771 to Q.775 (1993), modified]".[9]CCITT Recommendation X.209 (1988): "Specification of basic encoding rules for Abstract SyntaxNotation One (ASN.1)".[10]ITU-T Recommendation Q.751.1: "Network element management information model for theMessage Transfer Part".[11]ETS 300 356-1 (1995): "Integrated Services Digital Network (ISDN); Signalling System No.7;ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services [ITU-TRecommendations Q.761 to Q.764 (1993), modified]".[12]ITU-T Recommendation Q.751.3 (1997): "Network Information Model for MTP Accounting andAccounting Verification".[13]ITU-T Recommendation X.690 (1994) | ISO/IEC 8825-1: "Information technology - ASN.1encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER)and Distinguished Encoding Rules (DER)".[14]CCITT Recommendation X.208 (1988): "Specification of Abstract Syntax Notation One(ASN.1)".[15]ITU-T Recommendation Q.780 (1995): "Signalling System No.7 test specification generaldescription".[16]ITU-T Recommendation M.3100 (1995): "Generic network information model".2.2Informative references[17]ITU-T Recommendation M.4110: "Inter-Administration agreements on Common ChannelSignalling System No. 7".[18]ITU-T Recommendation Q.755 (1993): "Signalling System No. 7 protocol tests".[19]ITU-T Recommendation Q.822 (1994): "Stage 1, stage 2 and stage 3 description for the Q3interface – Performance management".[20]ITU-T Recommendation Q.2210 (1996): "Message transfer part level 3 functions and messagesusing the services of ITU-T Recommendation Q.2140".[21]ITU-T Recommendation Q.756 (1997): "Guidebook to Operations, Maintenance andAdministration Part (OMAP)".[22]ITU-T Recommendation Q.705 (1993): "Signalling Network Structure".3AbbreviationsASN.1Abstract Syntax Notation 1BECBasic Error CorrectionBERBasic Encoding RulesCDPACalleD Party AddressCGPACallinG Party AddressCICCircuit Identification CodeGTGlobal TitleGTAIGT Address InformationGTIGT IndicatorILSIncoming LinkSetISDNIntegrated Services Digital NetworkISUPISDN User PartSIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)8MRVTMTP Routing Verification TestMTPMessage Transfer PartNAINature of Address IndicatorNPNumbering PlanOLSOutgoing LinkSetOMAPOperations, Maintenance and Administration PartPCPoint CodePCRPreventive Cyclic RetransmissionPICSProtocol Implementation Conformance StatementSAPService Access PointSEPSignalling End PointSCCPSignalling Connection Control PartSIService IndicatorSLCSignalling Link CodeSPSignalling Point (general)SSNSub System NumberSTPSignalling Transfer PointTMNTelecommunications Management NetworkTTTranslation typeUDTUniDatTa messageXUDTExtended UniDatTa messageXUDTSExtended UniDatTa Service message4General exceptions and clarifications to ITU-TRecommendations Q.750 to Q.7514.1Q.750ITU-T Recommendation Q.750 [1] is an overview document which is generally applicable.4.2Q.751.1ITU-T Recommendation Q.751.1 [10] defines the network information model (in the form of managed objects) for theMTP of Signalling System No.7. If the network operator uses a Telecommunications Management Network (TMN)Operations System to control the Signalling System No.7 network, the management of the MTP shall be via theManaged Objects defined in ITU-T Recommendation Q.751.1 [10] with the clarifications and exceptions listed here.The requirements specified in the present document referring to subclause 6 of ITU-T Recommendation Q.751.1 [10]shall also constrain the conditional packages and optional parameters in subclause 7 of ITU-T RecommendationQ.751.1 [10].4.2.1Subclause 1 to 6.1 inclusive of Q.751.1Subclause 1 to 6.1 inclusive shall apply.4.2.2Subclause 6.2 of Q.751.1The Signalling Link Set Timer Profile (subclause 6.2.1) may be used, Managed Switching Element (subclause 6.2.2)may apply, MTP Access Point (instance) (subclause 6.2.3) shall apply.The MTP Level 2 Protocol Profile (subclause 6.2.4) may be used, but the bufferMechanismPackage,multipleTransmissionCongestionLevelsPackage and multipleTransmissionCongestionStatesPackage shall not apply.The MTP Signalling Point (subclause 6.2.6) shall apply. The conditional package spTimersPackage may be used, butattributes 14, 17, 21, 22 and 30 (ITU-T Recommendation Q.704 [5] timers T7, T11, T15, T16 and T24 respectively)SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)9shall not apply; (note that if this package is used then the Signalling Point Timers Profile shall not be used at the samesignalling point - this is required in the conditional packages statement of the formal description of subclause 7 of ITU-TRecommendation Q.751.1 [10] ).The Signalling Data Link Termination Point (subclause 6.2.7) shall apply.The Signalling Link Set Termination Point (subclause 6.2.8) shall apply. If the conditional package spTimersPackage isused in the superior MTP Signalling Point instance, the lsTimersProfilePointerPackage shall not be used. If thespTimersProfilePointerPackage is used in the superior MTP Signalling Point instance, thelsTimersProfilePointerPackage shall not be used.The Signalling Link Termination Point (subclause 6.2.9) shall apply, but attribute 11 (linkCongestionLevel) shall notapply. Attributes 13 and 15 (signDataLinkTpList and signTermList) may be used, but only to support the basicsignalling link management procedures of ITU-T Recommendation Q.704 [5] subclause 12.2 (see ETS 300 008-1 [6]).In addition, create and set rejection reasons vii) and viii) referring to ITU-T Recommendation Q.704 [5] timer T17 shallnot apply. If the conditional package spTimersPackage is used in the superior MTP Signalling Point instance, theslTimersProfilePointerPackage shall not be used. If the spTimersProfilePointerPackage is used in the superior MTPSignalling Point instance, the slTimersProfilePointerPackage shall not be used.The Signalling Link Timer Profile (subclause 6.2.10) may be used, but attribute 5 (ITU-T Recommendation Q.704 [5]timer T24) shall not apply.The Signalling Point Timers Profile (subclause 6.2.11) shall apply if the spTimersPackage of the MTP Signalling Pointis not used, but ITU-T Recommendation Q.704 [5] timers T7, T11, T15 and T16 shall not apply.The Signalling Route Network Element Part shall apply (subclause 6.2.12).The Signalling Route Set Network Element Part (subclause 6.2.13) shall apply, with the congestedStatePackage. ThecongestionLevelPackage shall not apply.The Signalling Terminal may be used, but only to support the basic signalling link management procedures of ITU-TRecommendation Q.704 [5] subclause 12.2 (see ETS 300 008-1 [6]).The Signalling Transfer Point (STP) Screening Table may be used.For all object classes additionally applies:"Creation of new object class instances may be rejected due to lack of system resources, e.g. the system specificmaximal number of instances of this object class per superior object instance have been exceeded."Object class mtpAccessPoint:Additionally applies:The MTP status is mapped to the operationalState and availabilityStatus attributes as follows:MTP StatusoperationalStateavailabilityStatusallowedenabled{ }congestedenabled{degraded}prohibiteddisabled{off line}Object class signDataLinkTp:Additionally applies:"If an attempt is made to delete a signDataLinkTp instance which is still referenced by a signLinkTp, the deleterequest is rejected".Object class signLinkTp:Attribute "mtpL2ProtocolProfilePointer" (and all references to it) is renamed to "protocolProfilePointer".Object class signLinkSetTp:For the congestionControlMethod only the values "unknown" or "ccmQ704International" apply.SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)104.2.3Subclause 7 of Q.751.1Subclause 7 of ITU-T Recommendation Q.751.1 [10] is the formalization of the informal specification of subclause 6.2.Subclause 7 shall apply, but shall be constrained by the exceptions and clarifications to subclause 6.2 given previously,and by the corrections and additions listed below.4.2.4Subclause 7.1 of Q.751.14.2.4.1Subclause 7.1.8 of Q.751.1Object class signLinkSetTp:For attribute inLsLoadShareAlgorithm also the operation SET BY CREATE applies.4.2.4.2Subclause 7.1.9 of Q.751.1Object class signLinkTp:For attribute maxCapacitySl also the operation SET BY CREATE applies. For attributes signDataLinkTpListand signTermList also the operations SET BY CREATE and ADD-REMOVE apply.4.2.5Subclause 7.4 of Q.751.1Attribute template signLinkTpPointer does not apply.4.2.6Subclause 7.5 of Q.751.1Action replaceSignTerm does not apply.4.2.8Subclause 7.8 of Q.751.1The ASN.1 type Point Code is extended to: (unrestricted) INTEGER.For the CHOICE components of StpScreeningTableLineId the typing is replaced by "designatedLinkSet" and"designatedOpc".The ASN.1 type TimerValue is extended to: INTEGER (0.360000).4.2.9Annex A of Q.751.1This annex is informative.4.2.10Annex B of Q.751.1This annex is informative.It is an informal definition of the Signalling System No.7 MTP resources and their management, as seen from the MTP.It is written from a network management perspective, and does not apply directly, although it may be useful for anexplanation of the MTP and its management.4.2.11Annex E and annex F of Q.751.1Annex E is the formal description of MTP measurements. The MTP measurements used for message traffic accountingare for further study in ITU-T Recommendation Q.751.1 [10], the requirements of the present document are defined insubclause 3.2.12.Only those portions of annex E apply which correspond to required measurements defined in ITU-T RecommendationQ.752 [2] (see clause 4 of the present document).SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)11Annex F is the definition of the MRVT managed object class, and shall apply.4.2.12Object model for MTP accounting and verificationITU-T Recommendation Q.751.3 [12] shall apply, with the exception that MTP accounting verification is not required.5Exceptions and clarifications to ITU-TRecommendation Q.752If a Protocol Implementation Conformance Statement (PICS) associated with an ETSI deliverable contains a referenceto an optional Signalling System No.7 function, and that function has an associated measurement which is obligatory ifthe function is used, then the measurement shall be supplied if the function is supplied.The references to Recommendation Q.751 in ITU-T Recommendation Q.752 [2] should be replaced throughout by "theseries of Recommendations Q.751".5.1Subclause 1 of Q.752Subclause 1 shall apply with the following exceptions:Subclause 1.1.1: add to the hyphenated list at the end:"ITU-T Recommendation Q.752 [2] does not describe any filtering techniques to be applied after measurementsare taken (apart from the "first and interval" method to reduce the number of output reports). The Q.820 series ofRecommendations define filtering techniques useful for control of the Signalling System No.7 network. Inparticular, ITU-T Recommendation Q.822 [19] defines packages of counters, grouped into one data object. So,for instance, if the operator wishes to monitor error performance, all counters in a group could be activated at thesame time. The distinction made in the
ITU-T Recommendation Q.752 [2] Recommendation between"permanent" and "activated" measurements also disappears - all measurements are inherently "activated",permanency can be achieved by keeping a measurement activated all the time."Subclause 1.1.2 should refer to the operations, maintenance and administration part and not the operations andmaintenance application part.Subclause 1.4.2: delete the words "according to the managed object being measured" in the first sentence.Subclause 1.6: refer to ITU-T Recommendation X.701 and not paragraph 2.2 in ITU-T Recommendation Q.750 [1].Subclause 1.6.4: delete the last sentence "However, certain measurements … for STP accounting purposes".Subclause 1.7.1.2: delete the clause apart from its first sentence.Subclause 1.7.1.7: add a paragraph at the end "The "1st & interval" measurements "Units" column contains two items ifthe units for the first event report are different from those applied in the interval, and in that case the ones applied in theinterval are the second in the column."Add a subclause 1.8:"1.8Techniques for filtering measurements1.8.1Single faults giving rise to multiple error reportsWhere a single fault could cause recurring event reports (e.g. a single MTP routing data corruption could result in manyMSUs being discarded), the first and interval measurement technique can be used. The initial report should containenough information to establish the location of the fault, the interval count will then indicate its severity. The intervalshould be short enough to allow real time control. This technique presents information essential to the maintenance staff,and filters out that which is redundant."SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)125.2Subclause 2 through 5 of Q.752The provisions of these clauses shall apply where the measurements referred-to apply (see the references to the tables ofITU-T Recommendation Q.752 [2] in the present document).Subclause 2.1: add a paragraph at the beginning: "The measurements for MTPs according to Q.2210 [20] have yet to bedefined in detail, however the ones included here for level 3 are likely to be appropriate also in the broad bandenvironment."Subclause 2.3.1: change to "Item 2.1 could be derived from measurements 1.2, 1.12, 2.5 and 2.6."Subclause 3.2.1: replace the subclause with:"Subclause 3.2.1Routing failure measurements (items 7.1 through 7.7 and 7.9) refer to all possible failures (both localand remote) detected by SCCP Routing Control, and count all SCCP messages which encounter transport problems,regardless of whether or not a (X)Unitdata Service message or N-NOTICE primitive is returned to the originator.Receipt of a (X)Unitdata Service message is not included in this count. The measurements refer to both primary andsecondary entities, or just the primary if no secondary entity is prescribed.All of these measurements are marked as "1st & interval". They enable SCCP routing failures to be identified.The reassembly error measurements (items 7.10 through 7.12) are prescribed for the SCCP connectionless reassemblyservice. item 7.12 (no reassembly space) indicates a resource limitation when the first segment of a sequence is received.Item 7.13 (Hop counter violation) indicates a routing failure, possibly an SCCP circular route. All hop counter violationsare reported with this item, including those from Connection Request messages.The report associated with the first event of items 7.10 and 7.11 should contain at least the calling party address and thesegmentation local reference as diagnostic information.The report associated with the first event of item 7.13 should contain as diagnostic information at least the called partyaddress, and the OPC of the MTP routing label. If present, the calling party address should also be included.The report associated with the first event of item 7.14 should contain as diagnostic information the subsystem numberand called party address.The reports associated with the first event of items 7.15, 7.16 and 7.18 should contain as diagnostic information at leastthe MTP Service Access Point (SAP) identity (implementation dependent), the connection references (local and remote)and the DPC.Item 7.18 should also contain the cause."Subclause 3.4.4 and 3.4.5 should be replaced by:"Subclause 3.4.4Measurements 9.6 and 9.7 are taken per protocol class (as present in the protocol class parameter of(X)UDT messages) and per SSN. 9.6 is counted at the origin per source SSN and refers to messages delivered to anMTP Service Access Point, 9.7 is counted at the destination per sink SSN and refers to messages received from an MTPService Access Point."Subclause 3.4.5Measurement 9.8 refers only to those messages which would normally have been routed to a localsubsystem but because of a change in the translation process (e.g. due to a routing failure towards that subsystem), aredirected to a backup subsystem. The measurement is only applicable at replicated nodes with translation capabilities."Subclause 3.4: delete the last sentence.5.3Subclause 6 of Q.752This subclause is informative.SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)135.4Subclause 7 of Q.752Add a clause 7 to ITU-T Recommendation Q.752 [2], and note that
the network operator shall be able to determine towhat date and time the start of each accounting interval belongs. It should be noted that implementations might respondwith different delays in starting accounting when requested, and the network operator should take this into considerationwhen determining when to start the first accounting interval. In addition, depending upon implementation, it might ormight not be sufficient to associate a date and time only with the first accounting interval, and then to determine the dateand time of the start of each successive interval from its position and the length of preceding intervals.The text of the new clause 7 is:"Subclause 7Accounting of MTP and SCCP message trafficSubclause 7.1GeneralSubclause 7.1.1This section covers all registration items appropriate to support cascade remuneration. This accounting method is basedon the principle that the originator pays the operator (if different) of the next node in the message's path for deliveringthe message; the next node's operator pays the operator of its next node, and so on. The measurements here, becausethey differentiate on the basis of the destination of the messages, would allow all the network operators involved to beremunerated.Subclause 7.1.2Two functions are defined for Signalling System No.7 message accounting:1)verification of the number of messages sent for which the receiving operator should be paid (this function isoptional);2)registration by the receiving operator of the number of messages for which payment is to be received.Subclause 7.1.3Two types of traffic registration are distinguished. The registration of the MTP signalling traffic refers to the usage ofthe "transfer" resources. The registration of the SCCP signalling traffic refers to the usage of the "relay" resources.Traffic registration will not only be needed for remuneration but also for remuneration verification. Correlation betweenboth kinds of traffic registration within one node is not required. The role of Signalling End Points (SEPs) and SCCPendpoints in accounting and accounting verification is for further study.NOTE:The use of Service Indicator (SI), SSN and SCCP class as registration items for accounting purposesshould be considered in the light of the need for data protection, information security and fair competition(see Q.756 [21]).Subclause 7.2 MTP traffic registrationMTP traffic registration is applicable within one Operator's MTP network or a group of Operators of one MTP network(e.g. different countries owning parts of the overall international signalling network). If required, these networks canalso be subdivided into different parts (in order to apply different tariffs).Subclause 7.2.1 Basic registration principlesSubclause 7.2.1.1For remuneration purposes, the incoming MTP signalling traffic should be registered against thefollowing items:-The identity of the adjacent network operator sending the MTP message. If discrimination between severaloperators is not required the identity of a group of these operators should be used.-Destination information, as far as relevant for the accounting agreements. This information may identify one ormore networks. If also required, network parts could be identified.-Optionally, the identity of the requested service or group of services.For each relevant combination the number of messages transferred as well as the number of octets should be registeredper specific time interval (e.g. every 30 minutes).SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)14Subclause 7.2.1.2For remuneration verification, the outgoing MTP signalling traffic should be registered against thefollowing items:-The identity of the adjacent network operator receiving the MTP message. If discrimination between severaloperators is not required the identity of a group of these operators should be used.-Destination information, as far as relevant for the accounting agreements. This information may identify one ormore networks. If also required, network parts could be identified.-Optionally, the identity of the requested service or group of services.For each relevant combination the number of messages sent out as well as the number of octets should be registered perspecific time interval (e.g. every 30 minutes).Subclause 7.2.1.3The results of both periodic measurements should be provided with the date (year, month, day) andtime (hours, minutes) of the start of each time interval.Subclause 7.2.1.4The following MTP related information is used to identify the items involved in remuneration andremuneration verification.-The Incoming LinkSet (ILS) or set of ILSs should be used to identify the adjacent network operator or group ofoperators from which the MTP message was received.-The Outgoing LinkSet (OLS) or set of OLSs should be used to identify the adjacent network operator or group ofoperators to which the message is sent.-The DPC or set of DPCs should be used to identify the relevant destination information.-If the option is selected, the SI value or set of values should be used to identify the requested service or group ofservices.Subclause 7.2.2. LimitationsSubclause 7.2.2.1 Although each network operator is responsible for defining the relevant combinations, limits shouldbe placed on the number of registration items mentioned in subclauses 7.2.1.1 and 7.2.1.2. A limit should also be placedon the number of combinations.Subclause 7.2.2.2 The effect of re-transmissions due to e.g. changeover can be ignored. Tariffs could always be adjustedto compensate for the predicted traffic volume from this effect.Subclause 7.2.2.3 No particular attempt will be made to account separately for, or exclude from accounting, MTP-ownmessages with SI = 0000 or 0001 (the number of messages should anyway be small).Subclause 7.3 SCCP traffic registrationSCCP traffic registration is applicable in all cases where a G.T.T. (global title translation) is done, e.g. at relay nodes orat gateways between MTP networks.Subclause 7.3.1 Basic registration principles.Subclause 7.3.1.1 For remuneration purposes, the incoming SCCP signalling traffic should be registered against thefollowing items:-The identity of the operator of the previous network adjacent to the gateway (where accounting is done) sendingthe SCCP message (identity of the previous SCCP node). If discrimination between several operators is notrequired the identity of a group of these operators should be used.-Destination information, as far as relevant for the accounting agreements. This information may identify one ormore destination or intermediate networks. If also required, network parts could be identified.-Optionally, the identity of the requested service application type (HLR, VLR, ISUP, ISDN supplementaryservices, etc.) or group of service application types. The required number of such groups and their constituents isfor further study.-Optionally, the identity of the SCCP class requested (0, 1, 2 or 3).SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)15For each relevant combination the number of transferred messages as well as the number of SIF + SIO octets should beregistered per specific time interval (e.g. every 30 minutes).It is for further study for which network arrangements the last two registration items might be required.Subclause 7.3.1.2For remuneration verification, the outgoing SCCP signalling traffic should be registered against thefollowing items:-The identity of the operator of the following network adjacent to the gateway (where accounting is done) whichreceived the SCCP message (identity of the next SCCP node). If discrimination between several operators is notrequired the identity of a group of these operators should be used.-Destination information, as far as relevant for the accounting agreements. This information may identify one ormore destination or intermediate networks. If also required, network parts could be identified.-Optionally, the identity of the requested service application type (HLR, VLR, ISUP, ISDN supplementaryservices, etc.) or group of service application types. The required number of such groups and their constituents isfor further study.-Optionally, the identity of the SCCP class used (0, 1, 2 or 3).For each relevant combination the number of messages sent out as well as the number of SIF + SIO octets should beregistered per specific time interval (e.g. every 30 minutes).It is for further study for which network arrangements the last two registration items might be required.Subclause 7.3.1.3 The results of both periodic measurements should be provided with the date (year, month, day) andtime (hours, minutes) of the start of each time interval.Subclause 7.3.1.4 The following SCCP related information should be used to identify the items involved inremuneration and remuneration verification. For remuneration, the information of the received message should be used.For remuneration verification, the information resulting from the global title translation in the sending node should beused.-The OPC (+MTP service access point instance (which is implementation dependent and indicates the MTPnetwork)), as provided by the MTP to the SCCP, should be used to identify the operator of the previousnode/network from which the SCCP message was received.-The DPC (+MTP service access point instance (which is implementation dependent and indicates the MTPnetwork)), resulting from a global title translation, should be used to identify the operator of the followingnode/network to which the SCCP message is sent.-The following called party address global title items should be used to deduce the relevant destinationinformation:-Global Title Indicator (GTI);-The relevant parts of the address information;-Nature of address indicator (NAI) (optional);-Numbering plan (NP) (optional);-Translation type (TT) (optional).Whether or not the GTI, NAI, NP and TT are used, their values, and which parts of the address information are used,depend upon the particular network arrangements, and are for further study.NOTE 1:Although a DPC may be used instead of a global title, it is assumed that accounting will only be neededbetween MTP network boundaries (in which case the GT Address Information (GTAI) is mandatory) andtherefore the DPC is not included here.-If the option is selected, the SSN or set of SSNs should be used to identify the requested service application type(HLR, VLR, ISUP, ISDN supplementary services, etc.).SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)16NOTE 2:The network operator will decide how to handle (to group) a called party address with a SSN value 0 orSSN that is not recognized and/or standardized.-If the option is selected, the "protocol class" parameter field should be used to identify the requested SCCP class(0, 1, 2 or
3).Subclause 7.3.2 LimitationsSubclause 7.3.2.1 Although the network operator is responsible for defining the relevant combinations, limits shouldbe placed on the number of registration items mentioned in subclauses 7.3.1.1 and 7.3.1.2. A limit should also be placedon the number of combinations.Subclause 7.3.2.2 No particular attempt will be made to account separately for, or exclude from accounting, SCCP-own messages with SSN = H01 (the number of messages should anyway be small).".5.5The tables of Q.752In these tables, delete the "Activated/Permanent" column, and delete notes of managed objects.Table 1 items 1.1 and 1.2 and 1.8 (30 minute duration) shall apply.Table 2 item 2.1 shall apply.Table 3 item 3.1 (30 minute duration), item 3.4 (30 minute duration) and item 3.10 (30 minute duration) shall apply.Table 4 items 4.9 and 4.10 shall apply.Table 5 item 5.1 (on occurrence), item 5.2 (5 and 30 minute duration), item 5.5 (30 minute duration) shall apply.Table 6 is not required.Table 7 items 7.1 through 7.16, 7.18 and 7.20 (all with 1st & D duration) shall apply, subject to the provisions of theNotes to table 7, and to the provisions of ETS 300 009-1 [7].The items 7.9 onwards of this set should be replaced by:"7.9 is Routing Failure - unqualified; units are Events; usage F, R, P, C, N; interval 1st & D; reference Q.714/2.4."7.10 is Reassembly error - Timer Treass expiry; units are Event/CGPA/seg.LR, Events; usage F,R,P;interval 1st&D; note (d) applies; reference Q.714/4.1.1.2.3.2."7.11 is Reassembly error - segment received out of sequence (inc. duplicates, recpt. of non-first segment forwhich no reassembly process); units are Event/CGPA/seg.LR, Events; usage is F,R,P; interval 1st&D; note (d)applies; reference Q.714/4.1.1.3.2."7.12 is Reassembly error - no reassembly space; units are Events; usage is R,P,N; interval 1st&D; note (d)applies; reference Q.714/4.1.1.2.3.4."7.13 is Hop counter violation (XUDT, XUDTS and CR); units are Event/[CGPA]/CDPA, Events; usage F,R,P;interval 1st&D; note (e) applies; reference Q.714/2.3.1 3."7.14 is Message too large for segmentation; units Event/SSN, Events; usage F,R,P; interval 1st&D ; note (d)applies; reference Q.714/4.1.1.1.1."7.15 is Failure of release complete supervision; units Event/DPC/Protocol class, Events; usage F,R,P;interval 1st&D ; note (f) applies; reference Q.714/3.3.4.2."7.16 is Timer T(iar) expiry; units Event/DPC/Protocol class, Events; usage F,R,P; interval 1st&D; note (f)applies; reference Q.714/3.4."7.18 is Provider initiated release of a connection; units Event/DPC/Protocol class, Events; usage F,R,P;interval 1st&D ; note (f) applies; reference Q.714/3.3, Q.713/ Table A-2.SIST EN 301 007-1:2000

ETSIEN 301 007-1 V1.1.3 (1998-05)17"7.20 is segmentation error - segmentation failed; units Event; usage F,R,P; interval 1st&D ; referenceQ.714/4.1.1.1."
...