1、CCITT RECMN*E-505 92 4862593 0573679 5T3 INTERNATIONAL TELECOMMUNICATION UNION CCITT THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITTEE TELEPHONE NETWORK AND ISDN QUALITY OF SERVICE, NETVVORK MANAGEMENT AND TRAFFIC ENGINEERING E.505 MEASUREMENTS OF THE PERFORMANCE OF COMMON CHANNEL SIG
2、NALLING NETWORK Recommendation E.505 Geneva, 1992 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesCCITT RECflN*E.505 92 4862591 0573680 215 INTERNATIONAL TELECOMMUNICATION UNION CCITT THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATI
3、VE COMMITTEE E.505 TELEPHONE NETWORK AND ISDN QUALITY OF SERVICE, NETWORK MANAGEMENT AND TRAFFIC ENGINEERING MEASUREMENTS OF THE PERFORMANCE OF COMMON CHANNEL SIGNALLING NETWORK Recommendation E.505 Geneva, 1992 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Infor
4、mation Handling Services- I_ - I_- _- - P _II_. . CCITT RECMN*E.505 92 4862593 0573681 151 M FOREWORD The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (UV. CCITT is responsible for studying technical, opera
5、ting and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of
6、Recommendations by the members of CCI“ between Plenary Assemblies is covered by the procedure laid down in CCIIT Resolution No. 2 (Melbourne, 1988). Recommendation ES05 was prepared by Study Group TI and was approved under the Resolution No. 2 procedure on the 16th of June 1992. CCIIT NOTES 1) telec
7、ommunication Administration and a recognized private operating agency. 2) in this Recommendation, the expression “Adminisiration“ is used for conciseness to indicate both a A list of abbreviations used in this Recommendation can be found in Annex A. O ITU 1992 AU rights reserved. No part of this pub
8、lication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesCCITT RECMN*
9、E-505 92 m 4862593 0573682 O98 m Recommendation ES05 MEASUREMENTS OF THE PERFORMANCE OF COMMON CHANNEL SIGNALLING NETWORK 1 Introduction In this Recommendation, measurements relating to CCIIT Signalling System No. 7 are specified. The specification of measurements for CCITT Signalling system No. 6 h
10、as not been defined in such a sructured way as for CCIT Signalling System No 7. However, some of the measurements indicated for CCTI Signalling System No. 7 may also be valid for CCI“ Signalling System No. 6 (albeit with slight variation in meaning), and may be used for the network operations functi
11、ons of the relevant networks. Recommendation Q.752 establishes the general requirements for measurements to support operation, administration and maintenance of CCIT No. 7 signalling networks. The focus of the measurements in this Recommendation is on operation and administration of CCI“ No. 7 signa
12、lling networks, Le. for traffk engineering, network management and Quality of Service functions. Recommendation Q.752 provides measurements requirements in the form of tables, whereas this Recommendation provides measurements according to the traffic measurement model in 0 2 of Recommendation E.502,
13、 which indicates the object on which the measurements are performed and the entities that describe the quantities for which the data collection must be performed. This Recommendation is intended to be supportive of and complementary to Recommendation Q.752. Most of this Recommendation is considered
14、as the objective for traffk measurements which relate to network operations functions of planning, dimensioning and operational management of common channel signalling system networks, whereas Recommendation Q.752 provides the basic Signalling System No. 7 measurements and monitoring in support of t
15、his objective. The measurements indicated in this Recommendation are considered appropriate for a full developed signalling network using a mesh network configuration. A selected sub-set of measurements may be sufficient for “ other applications. 2 Conceptual Signalling measurement model The main tr
16、affic flows in an exchange are shown in Figure 4E.502. The conceptual model for CCITT No. 7 network signalling flows and measurements is shown in Figure lE.505 and is related to Figure 4E.502. In the model, the totality of signalling traffic is exchanged between the Message Transfer Part (MTP) and t
17、he relevant User Parts. Each User Part, in turn, exchanges signalling messages with the exchange. Logical reference points for measurement are indicated and numbered in Figure 1E.505. The measurement types in 0 3 are associated with the relevant numbered reference points. It should be noted that all
18、 the reference points are not associated with measurement types at this time, but may be related to additional measurement types which may be specified in the future. Recommendation ES05 1 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling Service
19、sCCITT RECMNaE.505 72 m L18b257L 0573683 T24 m I I r m I Cu 03 r- c9 I 21-n t 2 Recommendation ES05 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesCCITT RECMN*E.505 92 m 4862571 0573684 960 m 3 Measurements types 3.1 Message Transfer P
20、art (MTP) measurements Note - The MV is described in Recommendations Q.701 to Q.709, Type I: Signalling link performance (reference points 1,36) Object: MTP signalling links (selectable). Entities: a) number of local automatic changeover; b) cumulative duration of signalling link unavailability; c)
21、cumulative duration of signalling link unavailability due to remote processor outage; d) number of remote processor outage events; e) number of local management inhibit events; f) cumulative duration of local management inhibit status; g) number of signal information field (SE) octets and service in
22、formation octets (SIO) transmitted; h) number of octets retransmitted; i) j) k) number of MSU received; 1) number of signalling link congestion events; m) cumulative duration of signalling link congestion; n) number of MSUs discarded due to signalling link congestion. Type 2: Signalling link set per
23、formance (1,36). c number of message signal unit (MSU) transmitted, number of SIF and SI0 octets received; Object: MTP signalling link sets (selectable). Entities: a) b) c) cumulative duration of unavailability of signalling link set; number of signalling link set unavailability events; number of tr
24、ansfer prohibited signals (TFP) broadcasted due to failure of signalling link set (at signalling transfer points only), Type 3: Signalling point performance (1,36). Object: MTP signalling point (overall). I Entities: a) b) number of events of adjacent signalling point (SP) inaccessible; cumulative d
25、uration of adjacent SP inaccessible. Recommendation ES05 3 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling Services4 - -_I_ - - - - _ _-I_ CCITT RECMN*Em505 92 = 4862593 0573685 8T7 M Type 4: Destination performance (36). Object: destination po
26、int code (DE) (selectable). Entities: a) number of unavailability of signalling route set to a destination, or set of destinations; b) cumulative duration of unavailability of signalling route set to a destination, or set of destinations. Type 5: Signalling route performance (1). Object: originating
27、 point code (0PC)DpC combination (selectable). Entities: a) number of TFP messages received; b) cumulative duration of TFP conditions; c) number of transfer controlled (TFC) messages received; d) cumulative duration of TFC conditions; e) number of transfer restricted (“FR) messages received (nationa
28、l option); f) cumulative duration of TFR conditions; g) number of transfer allowed (TFA) messages received. Type 6: Received signalling traffic distribution (i). Object: OPC (selectable). Entities: - Type 7: Transmitted signalling traffic distribution (36). Object; DPC (selectable). Entities: - numb
29、er of SIF and SI0 octets transmitted. Type 8: TP signalling message distribution (1, 36). Object: SI0 (selectable). Entities: - Type 9: TP received signalling message distribution (i). Object: OpC/SIO combination (selectable). Entities: - number of SIF and SI0 octets received. number of SIF and SI0
30、octets handled. number of SIF and SI0 octets received. Recommendation ESOS COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesCCITT RECMN*E.505 92 Y86257L 0573686 733 Type IO: MTP transmitted signalling message distribution (36). Object: D
31、PC/SIO combination (selectable). Entities: - Type II: Detailed MTP signalling message distribution (1,36). Object: OPC/DPC/SIO combination (selectable). Entities: - number of SE and SI0 octets transmitted. number of SIF and SI0 octets handled. 3.2 Signalling Connection Control Part (SCCP) measuremen
32、ts Note -The SCCP is described in Recommendations Q.711 to Q.716. Type 12: SCCP performance (6,3 1). Object: SCCP (overall). Entities: a) number of routing failures -no translation for address of such nature (1); b) number of routing failures - no translation for this specific address (1); c) number
33、 of routing failures - signalling network failure (point code not available); d) number of routing failures - signalling network congestion; e) number of routing failures - local sub-system failure (unavailable); f) number of routing failures - local sub-system congestion (2); g) number of routing f
34、ailures - unequipped user (local sub-system); h) number of routing failures -reason unknown. Note 1 -These measurements only required at SCCP nodes with global title translation capabilities. Note 2 - For further study. Type 13: SCCP availability (5,29, 30,40). Note -While this measurement type is s
35、een to be useful, its availability may be implementation dependent. Object: SCCP (overall). Entities: a) number of start of local SCCP unavailability - failure; b) number of start of local SCCP unavailability -maintenance made busy; c) number of local SCCP unavailability events - congestion; d) cumu
36、lative duration of local SCCP unavailability - ail reasons. Recommendation ESOS 5 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesI_ - ._ -I . CCITT RECMN*E.505 92 9 4862593 0573687 67T I Type 14: SCCP utilization (6,3 I). Object: SCCP
37、(overall). Entities: a) number of Unit Data Service (UDTS) messages sent; b) number of UDTS messages received; c) number of messages handled (from local or remote sub-system); d) number of messages intended for local sub-systems; e) number of messages requiring global title translation (1); f) numbe
38、r of messages sent (for connectionless only) (by class O, 1); g) number of messages received (for connection only) (by class O, 1); h) number of messages sent to a back up sub-system (2). Note 1 - This measurement is only required at SCCP nodes with global title translation capabilities. Note 2 - Th
39、is measurement is system dependent. 3.3 ISDN User Part (ISUP) measurements Note - The ISUP is described in Recommendations 4.761 to 4.766; Type 15: ISUP availability (7,22,37). Note - While this measurement type is seen to be useful, its availability may be implementation dependent. Object: ISUP (ov
40、eraU). Entities: a) number of start of local ISUP unavailability - failure; b) number of start of local ISUP unavailability -maintenance made busy; c) number of start of ISUP unavailability - congestion; d) cumulative duration of ISUP unavailability - ail reasons. Type 16: ISUP message utilization (
41、7,22). Object: ISUP message types (selectable). Entities: a) number of total ISUP messages sent; b) number of total ISUP messages received. Type 17: ISUP node performance (17). Note - This measurement type does not relate to signalling network performance; rather, it uses signalling network User Par
42、t information to indicate the performance of the network node supported by the signalling network. This measurement type relates to the total incoming uaffic delivered to the node by ISUP. The unsuccessful call attempt categories are based on the ISUP cause indicator parameter, and relate to the uns
43、uccessful call attempts that fall in the node where the measurements are taken. Object: ISUP (overall). 6 Recommendation ESOS COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesCCITT RECMN*E.505 92 H Y862591 0573688 50b H Entities: a) numb
44、er of total incoming call attempts; b) number of unsuccessful call attempts - switching congestion; c) number of unsuccessful call attempts - no circuit available; d) number of unsuccessful call attempts - address incomplete; e) number of unsuccessful call attempts - temporary failure; f) number of
45、unsuccessful cai1 attempts - unallocated number; g) number of unsuccessful call attempts -busy; h) number of unsuccessful call attempts - destination out of service; i) number of unsuccessful caii attempts - other causes. Type 18: ISUP network performance (22). Note - This measurement type does not
46、relate to signalling network performance; rather, it uses signalling network User Part information to indicate the performance of the associated switched network onward from the node where the measurements are taken. The unsuccessful call attempt categories are based on the ISUP cause indicator para
47、meter received, and relate to the unsuccessful call attempts that fail in the distant node. Object: OPC in the received message (selectable). Entities: a) number of total outgoing cd attempts; b) number of switching congestion indicators received; c) number of no circuit available indicators receive
48、d; d) number of address incomplete indicators received; e) number of temporary failure indicators received; f) number of unallocated number indicators received; g) number of no route to destination indicators received; h) number of busy indicators received; i) number of destination out of service in
49、dicators received; j) number of other causes indicators received. 3.4 Transaction Capabilities Application Part (TCAP) measurements Note - The TCAP is described in Recommendations Q.771 to Q.775. Type 19: TCAP availability (8,23). Note - While this measurement is seen to be useful, its availability may be implementation dependent. Object: TCAP (overall). Entities: a) number of start of local TCAP unavailable - failure; b) number of start of local TCAP unavailable -maintenance made busy; c) number of start of local TCAP unavailable - congestion; d) cumulative dur
