ITU-T Q 755 1-1998 MTP Protocol Tester《MTP协议测试仪-系列Q 交换和信令-NO 7信令系统的准则-NO 7信令系统管理(第11研究组)》.pdf

《ITU-T Q 755 1-1998 MTP Protocol Tester《MTP协议测试仪-系列Q 交换和信令-NO 7信令系统的准则-NO 7信令系统管理(第11研究组)》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 755 1-1998 MTP Protocol Tester《MTP协议测试仪-系列Q 交换和信令-NO 7信令系统的准则-NO 7信令系统管理(第11研究组)》.pdf（43页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UN ION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.755.1 SERIES Q: SWITCHING AND SIGNALLING Specifications of Signalling System No. 7 - Signalling System No. 7 management (05/98) MTP Protocol Tester ITU-T Recommendation Q.755.1 (Previously CCITT Recommenda

2、tion) ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI- AUTOMATIC WORKING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEMS

3、No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM R1 SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 General , Message transfer part (MTP) Signalling connection control p

4、art (SCCP) Telephone user part (TUP) ISDN supplementary services Q.l-Q.3 Q.4-Q.59 Q.60-Q.99 Q.1OO-Q. 1 19 Q.12O-Q.249 Q.25O-Q.309 4.310-4.399 Q.400-Q.499 Q.50O-Q.599 4.6004.699 4.7004.849 4.700 Q.701-Q.709 4.71 14.719 4.720-4.729 4.7304.739 Data user part 4.7404.749 Signalling System No. 7 managemen

5、t 4.75-Q.759 ISDN user part Transaction capabilities application part Test specification 43 interface DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK BROADBAND ISDN 4.760-4.769 4.770-4.779 4.7804.799 4.8004.849 Q.85

6、0-Q.999 Q. 1000-Q.1099 Q.1100-Q.1199 Q. 12004.1999 Q.2000-Q.2999 For further details, please refer to ITU-T List of Recommendations. ITU-T RECOMMENDATION Q.755.1 MTP PROTOCOL TESTER Summary This is a revised version of the MTP Protocol Tester, published in March 1993 as Recommendation 4.755. The MTP

7、 Protocol Tester is used as an aid in testing between two implementations of the MTP of Signalling System service. in the international network, it would be the preferred message traffic generator. It is also a possible tool for validation testing when message traffic generation is needed whilst per

8、forming tests, and a possible message traffic generator for compatibility tests between different network operators. The tester is connected to the MTP as a user part, i.e. it is identified by a service indicator. It generates test traffic messages containing a serial number (and possibly additional

9、 information). On reception of these messages, the receiving tester checks that they have been delivered correctly (e.g. without loss, corruption, mis-sequencing or duplication). There is only one message traffic stream in any test; this means that the tester is not suitable for all tests of Recomme

10、ndation 4.782. The tester would need extensions for message rate and length considerations for broadband MTP testing. I No. 7. Its main use is as a tool for performing routing and bidirectionality tests for SS No. 7 in networks which are in Source IT-T Recommendation Q.755.1 was prepared by ITU-T St

11、udy Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 15th of May 1998. Recommendation 4.755.1 (0998) i - FOREWORD IT (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommuni- cations. The IT Telecommunication S

12、tandardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Confere

13、nce (WTSC, which meets every four years, establishes the topics for study by the IT-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. In some areas

14、of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operat

15、ing agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intelle

16、ctual Property Rights, whether asserted by IT members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, the IT had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation.

17、 However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O ITU 1998 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical

18、, including photocopying and microfilm, without permission in writing from the ITU. 11 Recommendation 4.755.1 (05/98) CONTENTS Scope References Symbols and abbreviations . Definitions General . MTP Tester (MT) . 6.1 6.2 6.3 6.4 6.5 Functions . 6.1.1 Objectives and scope . 6.1.2 Main functions . 6.1.

19、3 Architectural model . 6.1.4 Functional roles . 6.1.5 Identification of test sequences at a node 6.1.6 Message rate considerations Procedures . 6.2.1 Test set-up . 6.2.2 Procedures during the test . 6.2.3 Test termination . 6.2.4 Reaction to MTP management primitives and MTP restart SDL Procedure F

20、ormats and codes . 6.4.1 Header codes . 6.4.2 Timers 6.4.3 Interface requirements . State transition matrix . Recommendation 4.755.1 (05/98) Page 1 1 1 2 2 3 3 3 3 5 5 6 6 6 6 7 8 8 9 23 23 24 24 25 . 111 STD-ITU-T RECMN Q-755-1-ENGL 1998 48b259L Ob5L884 TTO Recommendation 4.755.1 MTP PROTOCOL TESTE

21、R (Geneva, 1998) 1 Scope This Recommendation defines the Message Transfer Part (MTP) Protocol Tester (MT), to be used as an aid when testing the MTP of IT Signalling System No. 7. The MTPs at nodes using the MT can be implemented according to any data of Recommendation Q.704I MTP Recommendations, as

22、 long as they provide the equivalent of the MTP primitives, and they support the MT Service Indicator (see i). This Recommendation draws upon Recommendation 4.750 for architectural considerations of the relationship behveen the Tester and SS No. 7 management (OMAP) (see SI). 2 References The followi

23、ng IT-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Reco

24、mmendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU Recommendations is regularly published. il IT-T Recommendation 4.704 (1 996), Signalling networkfunctions

25、 und messages. ITU-T Recommendation X.290 (1 999, OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications - General concepts. ISOnEC 9646-1 : 1994, Information technology - Open systems Interconnection - Conformance testing methodology andflamework -Part

26、 1: General concepts. ITLJ-T Recommendation 1.320 (1993), ISDNprotocol reference model. CCITT Recommendation 1.321 (1991), B-ISDNprotocol reference model and its application. ITU-T Recommendation 4.750 (1997), Overview of Signalling Sysrem No. 7 management. - i21 31 41 PI 3 Symbols and abbreviations

27、 This Recommendation uses the following abbreviations: AE Application Entity APDU Application Protocol Data Unit ASE Application Service Element ATS Abstract Test Suite CF DPC Destination Point Code GPC Generator Point Code (MT) Control Function (of OMAP in the MIB) But not according to the High Spe

28、ed Signalling Link Annex of Recommendation 4.703 (1996) nor to MTPs according to Recommendation Q.221 O. Recommendation 4.755.1 (05/98) 1 ISDN Integrated Services Digital Network ISUP ISDN User Part IUT Implementation Under Test LME Level Management Entity LT Lower Tester MAP Mobile Application Part

29、 MIB Management Information Base MSU Message Signal Unit MT MTP Protocol Tester MTP OMAP OMASE OMAPASE OPC Originating Point Code os1 Open Systems Interconnection PC Point Code PDU Protocol Data Unit SAP Service Access Point SAPi SAP instance SCCP SLS Signalling Link Selection (field) SP Signalling

30、Point SS No. 7 SUT System Under Test TC Transaction Capabilities TMP Test Management Protocol TPC Turnaround Point Code TT TC Test Responder TUP Telephony User Part UT Upper Tester (SS No. 7) Message Transfer Part Operations, Maintenance and Administration Part (SS No. 7 management) (SS No. 7) Signa

31、lling Connection Control Part Signalling System No. 7 4 Definitions This Recommendation defines the following term: 4.1 particular MTP network. MTP Service Access Point instance: The interface between an MTP user and the MTP, used to access a 5 General The MTP protocol tester may be used as an aid w

32、hen testing the Message Transfer Part (MTP) of Signalling System No. 7 (SS No. 7) between two implementations. The testers main function is simulation of an ordinary user part, as seen from the MTP, for the generation of test traffic messages. Recommendations 1.320 3 and 1.321 4 specifj the ISDN pro

33、tocol reference model to be used. User plane (U-plane), Control plane (C-plane) and Management plane (M-plane) are identified. The layering principles apply in each of these planes. The U-plane provides the user information flow transfer with associated controls. The C-plane handles the call and con

34、nection control information. The M-plane is divided into two portions: Layer Management functions and Plane Management functions. Plane Management performs management functions related to a system as a whole; it provides 2 Recommendation 4.755.1 (0998) coordination between all the planes and has no

35、layered structure. The Layer Management part of the M-plane contains Layer Management Entities. Each of these entities provides management functions relating to resources and parameters residing in its associated protocol layer. Layer Management handles the operation and maintenance information flow

36、s. The interfaces between adjacent layers within a plane and between the Layer Management Entity and its associated layer have to be defined in terms of service primitives. The interface between the Layer Management Entities and Plane Management does not need to be specified; it is implementation de

37、pendent. For SS No. 7, the Level Management Entity is defined by analogy with the Layer Management Entity of Recommendations 1.320 and 1.321. This is to account for the different positions of the boundaries between SS No. 7 lower levels and those of OS1 (e.g. the upper part of the MTP is level 3 in

38、SS No. 7, the SCCP is levei 4, but both would be within layer 3 if the OS1 model strictly applied). For SS No. 7 management, the term LME is taken to mean “Level Management Entity“. Thus the MT is contained in the LME of the MTP (MTP LME). In this Recommendation, the service primitives between the M

39、TP LME and the MTP are described, as are the procedures, the messages and the MT substructure. It is necessary to define the information flow across the interface between Plane Management (MIB) and the MT shown as the lowest Level Management Interface (LMI) in Figure 11, and so this is done in terms

40、 of signals which are required to control the concerned testing functions and to report results. See Figure 1 (which is a copy of Figure YQ.750) for the OMM architecturai model. 6 MTP Tester (MT) The MT is connected to the MTP as a user part, Le. it is identified by a service indicator. It generates

41、 test traffic messages (TEST TRAFFIC) containing a serial number (and possibly additional information) by using MTP-TRANSFER request primitives, and the MTP converts these into Message Signal Units (MSUs), with the TEST TRAFFIC in the Signalling Information Field (SIF). On reception of these message

42、s, the MT checks that they have been delivered correctly (eg without loss, corruption, mis-sequencing or duplication). 6.1 Functions 6.1.1 Objectives and scope The main use of the MT is: - as a tool for performing routing and bidirectionality tests for SS No. 7 in networks which are in service. If s

43、uch verification is required in the international network, the MT would be the preferred message traffic generator. The MT is also: - a possible tool for validation testing when message traffic generation is needed whilst performing tests. However, other traffic generators may be used if required wh

44、en performing validation tests; - NOTE - Caution is necessary in the case of a request to generate message trafic that might cause an overload. the possible message traffic generator for compatibility tests between different network operators. 6.1.2 Main functions The main function is the generation

45、 of bidirectional message test traffic, giving the possibility at the r eiving node of analyzing the received test traffic (Le. detection of mis-sequencing, duplication or loss of messages. Verification of transfer delays and detection of message corruption is only possible on the generating side.).

46、 Errors may be introduced in the SS No. 7 network (only by means external to the testers) during the transmission of test message traffic. NOTE - Undefined or unexpected messages with SI = “MTP Tester“ received during a test are discarded, optionally with a report. For the purposes of this Recommend

47、ation, an unexpected message is one that is not shown as input in a particular state in the SDL or the state transition matrix. Recommendation 4.755.1 (05/98) 3 4 I-, LMI SS No. 7 Management process + OMASE-User application services m MTP (Levels 1-3) LME MIB - SMSI OM-prim ridlid- Hi ASE - LM I - :

48、IF ISDN UP n SCCP (Level 4) I l Y L TUP LME NOTE 1 - Dotted lines (but not boxes) denote direct management interfaces. Only the SMSI (see Note 5 below) is realized with primitives. NOTE 2 -The LMI (Level Management Interface) is not a subject for standardization. NOTE 3 -The AMI (Application Managem

49、ent Interface) is not a subject for standardization. NOTE 4 -The items managed by OMAP can be regarded as conceptually resident in the MIB. NOTE 5 -The SMSI is the systems management service interface; the OM primitives are defined for use over it for managed object functions defined in Recommendation 4.753. NOTE 6 - OS1 layers 4,s and 6 are null in SS No. 7. TC forms the bottom of OS1 layer 7, SCCP the top of OS1 layer 3 (but is in SS No. 7 level 4). NOTE 7 - Interface x uses subsystem number to test the SCCP using the SCCP Tester (ST); interface y us