ITU-T Q 1600 BIS-1999 Signalling System No 7 - Interaction between ISDN User Part ISUP-97 and INAP CS-1 Test Suite Structure and Test Purposes (TSS & TP) Series Q Switching and SigNo.pdf

《ITU-T Q 1600 BIS-1999 Signalling System No 7 - Interaction between ISDN User Part ISUP-97 and INAP CS-1 Test Suite Structure and Test Purposes (TSS & TP) Series Q Switching and SigNo.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 1600 BIS-1999 Signalling System No 7 - Interaction between ISDN User Part ISUP-97 and INAP CS-1 Test Suite Structure and Test Purposes (TSS & TP) Series Q Switching and SigNo.pdf（52页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.1600 bis SERIES Q: SWITCHING AND SIGNALLING Intelligent Network (1 2/1999) Signalling System No. 7 - Interaction between ISDN User Part ISUP97 and INAP CS-1: Test Suite Structure and Test Purposes (TSS all

2、users of this Recommendation 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-T Recommendations is regularly published. 1 ITU-T Recommendation Q. 1600 (1 997), Signa

3、lling System No. 7 - Interaction between ISUP and INAP. 2 ITU-T Recommendation 4.763 (1997), Signalling System No. 7 - ISDN User Partsformats and codes. ITU-T Recommendation 4.764 (1997), Signalling System No. 7 - ISDN User Part signalling procedures. ISOIIEC 9646- 1 : 1994, Information technology -

4、 Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts. ISOIIEC 9646-2: 1994, Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification. ISOIIEC 9646-3 : 1 998, I

5、nformation technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN). ISOIIEC 9646-5 : 1994, Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 5: Require

6、ments on test laboratories and clients for the conformance assessment process. ISOIIEC 9646-7: 1995, Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements. ITU-T Recommendation Q. 121 4 network CS-I. ITU-

7、T Recommendation Q. 121 8 network CS-I. ITU-T Recommendation 4.784.1 ( Q. 767protocols. 1999, Distributed functional plane for intelligent (1 999, Interface Recommendation for intelligent 996), Validation and compatibility for ISUP92 and CCITT Recommendation E. 164 (1 988), Numbsringplan for the ISD

8、N era. This ATS specification incorporates by dated and undated reference, provisions from other publications. These normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of t

9、hese publications apply to this ATS and partial PIXIT proforma specification only when incorporated in it by amendment or revision. For undated references the latest edition of the publication referred to applies. 3 Definitions For the purposes of this ATS specification, the following definitions ap

10、ply: - - In particular, the following terms apply: 3.1 abstract test case (ATC): A complete and independent specification of the actions required to achieve a specific test purpose, defined at the level of abstraction of a particular Abstract Test Method, starting in a stable testing state and endin

11、g in a stable testing state (see 3.3.3 of 4). 3.2 abstract test method (ATM): The description of how an IUT is to be tested, given at an appropriate level of abstraction to make the description independent of any particular realization of a Means of Testing, but with enough detail to enable abstract

12、 test cases to be specified for this method (see 3.3.5 of 4). 3.3 terms defined in ISDN User Part (ISUP) reference specification i to 3; terms defined in ISOIIEC 9646-1 4, ISOIEC 9646-3 6 and in ISOIIEC 9646-7 SI. abstract test suite (ATS): A test suite composed of abstract test cases (see 3.3.6 of

13、4). 3.4 implementation under test (IUT): An implementation of one or more OS1 protocols in an adjacent user/provider relationship, being part of a real open system which IS to be studied by testing (see 3.3.43 of 4). 3.5 ISDN number: A number conforming to the numbering and structure specified in CC

14、ITT Recommendation E. 1 64 1 21. 3.6 means of testing (MOT): The combination of equipment and procedures that can perform the derivation, selection, parameterization and execution of test cases, in conformance with a reference standardized ATS, and can produce a conformance log (see 3.3.54 of 141).

15、3.7 PICS proforma: A document, in the form of a questionnaire, which when completed for an implementation or system becomes the PICS. 3.8 PIXIT proforma: A document, in the form of a questionnaire, which when completed for the IUT becomes the PIXIT. 3.9 point of control and observation: A point with

16、in a testing environment where the occurrence of test events is to be controlled and observed, as defined in an Abstract Test Method (see 3.3.64 of 4). 3.10 pre-test condition: A setting or state in the IUT which cannot be achieved by providing stimulus from the test environment. 3.1 1 protocol impl

17、ementation conformance statement (PICS): A statement made by the supplier of a protocol claimed to conform to a given specification, stating which capabilities have been implemented (see 3.3.39 and 3.3.80 of 4). 3.12 protocol implementation extra information for testing (PIXIT): A statement made by

18、a supplier or implementor of an IUT (protocol) which contains or references all of the information related to the IUT and its testing environment, which will enable the test laboratory to nin an appropriate test suite against the IUT (see 3.3.41 and 3.3.81 of 4). 3.13 system under test (SUT): The re

19、al open system in which the IUT resides (see 3.3.103 of 141). 4 Abbreviations This ITU-T Recommendation uses the following abbreviations: ASE Application Service Entity ASP Abstract Service Primitive A-SSP Assisting Signalling Switching Point ATC Abstract Test Case ATM Abstract Test Method ATS Abstr

20、act Test Suite CCBS CCF Call Control Function CD Call Deflection CDIV Call DIVersion CLIP Calling Line Identification Presentation CLIR Calling Line Identification Restriction Completion of Calls to Busy Subscriber COLP COLR cs-1 DLE DP ECT ICs IN INAP ISDN I-SSP ISUP IUT LT MCID MOT MTC MTP OLE P r

21、eceipt of INAP CS-1 operations in the SSF. t INAP ISUP I Exchange SSF INAP CS-I CCF ISUP97 I IUT SUT MAP Intelligent Network Application Protocol CS-1 Capability Set 1 ISUP ISDN User Part IUT Implementation Under Test SUT System Under Test SSF Service Switching Function CCF Call Control Function Fig

22、ure VQ.1600 bis _, ISUP T11103600-99 The ISUP signalling protocol and the INAP can be observed on the SS No. 7 link on the network nodal interface (“I). On the signalling links pointing to the Call Control Function (CCF) the ISDN User Part procedures can be observed. The signalling link emerging for

23、m the SSF the NAP procedures can be observed. 5.2 The Abstract Test Method (ATM) chosen for the Interaction between ISUP97 and INAP testing specification is the distributed multi-party test method. The ATM is defined at an appropriate level of abstraction so that the test cases may be specified appr

24、opriately, without adding restrictions to the implementation under test. The ATS is written in concurrent TTCN. ATM and testing configuration for ISUP97 5.3 IN exchange The configuration proposed for testing exchanges having an SSF (IN exchanges) is shown in Figure 2. In order to test the protocol a

25、nd functionality of these exchanges, one needs to consider the incoming and outgoing ISUP circuits and the signalling link to the SCP. The TUT is observed and controlled fi-om two ISUP links with associated circuits. The points of control and observation (PCO) are labelled LAC and CAC on one side, a

26、nd LAD and CAD on the other. The naming convention for the signalling link PCO is “L“ followed by two letters indicating the interface. Similarly for the circuit PCO, the name is “C“ followed by the same two letters designating the interface. The LAB PCO is used by the lower tester (LT) to control a

27、nd observe the INAP on the signalling to the SCP. The LAC and LAD PCOs are used by the lower testers (LT) for controlling the ISUP signalling link, whereas the CAC and CAD PCOs are used by the lower testers for observing circuit-related events, such as connectivity, DTMF tones, announcements, etc. T

28、he ISUP PDUs to be sent and observed on the LAC and LAD PCOs side allow for PDU constraints to be specified and coded down to the bit-level. The same applies for the NAP PDUs on the LAB PCO. The underlying network service provider is the Message Transfer Part (MTP) protocol as specified in ITU-T Rec

29、ommendations Q.701-4.707. Figure 2 shows the actual used configuration for IN exchanges, with a main testing component (MTC), responsible for the AB interface and two slave parallel testing components (PTCs), responsible for the AC and AD interfaces. The test coordination procedures (TCP) allow for

30、communication between the testers. The test components are mostly implicitly coordinated (asynchronously); the TCPs are only used when it is necessary to obtain the verdict from the parallel test component. The left and right side parallel test components may be of any kind: they may be internationa

31、l or national ISUP. MTC INAP signalling, SP A PTC ISUP signalling, circuits LAD 1 1CAD t-G- 71 circuit f Network service provider PTC ISUP signalling, circuits I I Network service provider T11103610-99 IUT Implementation Under Test LAB PCO for signalling link AB MTC Main Test Component CAB Circuit P

32、CO on AB interface PCO PCO - Point of Control and Observation LAC PCO for signalling link AC PTC Parallel Test Component CAC Circuit PCO on AC interface SP Signalling Point LAD PCO for signalling link AD SSF Service Switching Function CAD Circuit PCO on AD interface CCF Call Control Function TCP Tes

33、t Coordination Procedures Figure 2/Q.1600 bis - ISUP mixed test configuration for local exchanges 6 Test Suite Structure (TSS) 1 See Figure 3. SCS ISUF-INAp Interaction INDC DPP HOM-I SSP HOMASSP CG SF SCP-IC For each leaf: Figure 3/Q.1600 bis - Test suite structure Test Suite Structure (TSS) naming

34、 conventions are: ACON Abnormal CONditions AM-IS SP CG Call Gapping CON CONnect operation DPP Detection Point Processing HOM - ASSP HOM-ISSP IDP Initial Detection Point operation INB Assist Method - procedure in the Initiating SSP Hand-Off Method - procedure in the Assisting SSP Hand-Off Method - pr

35、ocedure in the Initiating SSP Setup of an IN call to destination B (v INBC INCD IPC ISS OIN SCP-IC SCS SF UID V INAP Basic Call IN call with SCP request to Collect further Digits SSP supports requested IP Capabilities Impact on Supplementary Services Other IN basic call-related issues SCP Initiated

36、Call Successful Call Setup Service Filtering User Interactive Dialogue (in-band) Valid behaviour stimulus 7 Test Purposes (TP) 7.1 Introduction For each test requirement a Test Purpose (TP) is defined. 7.2 Test Purposes are numbered ascending within each group. Groups are organized according to the

37、TSS down to the last but one level. The classification in the V/I groups is done by the inclusion of V or I in the test case name. Additional qualifiers, in form of lower case letters, are added to identify variants within one generic test case, see Table 1 below. Test purpose (TP) naming convention

38、 Table l/Q.1600 bis - TP Identifier naming convention scheme Identifier: ISN_(_( ISN = ISUP INAP Interaction = One character representing the test group: V: Valid stimulus I: Inopportune stimulus = Sequence number in the test suite structure y = Sequence number used within the group = Optional addit

39、ional number used = Optional lower-case character distinguishing tests with same reference number 7.2.1 The test purposes cover validation testing aspects and were developed within ETSI. Source of test purpose definition 7.2.2 Test purpose structure The test purpose structure overlaps with the Test

40、Suite Structure (TSS). Test purposes that test normal behaviour have been grouped in the V - valid behaviour group. Test purposes that test the IUT behaviour in situations that are not normal operation have been grouped in the I - Inopportune stimulus group. _ 7.3 All of the following test purposes

41、belong to the main group ISW-INAP-Interaction. Each test purpose is presented in a separate table. The first row of the table contains the following items: TSS Identifier in the test suite structure (test group/subgroup identifier). TP Identifier of the test purpose. Q.1600reference The reference to

42、 the requirement in the ISUP INAP interaction standard I, which led to the test purpose. Selection expression Selection criterion for the test purpose taking into account the exchanges role and the answers to the specified PICS questions (see Annex MQ.1600 bis). If there is no selection expression s

43、pecified, the TP is valid for all roles of exchanges. This is a reference to the test configuration used. Test purposes for the ISUP - INAP interaction Configuration The next row defines the test purpose itself, each having a title in italics and a text body. The ISUP messages, parameters, the INAP

44、operations and information elements are highlighted bold to ease the readability. In order to check the specified behaviour for some test purposes, a special prerequisite test condition has to be fulfilled. If such a condition is needed, it is presented after the test purpose under the heading “Pre-

45、test conditions“. For each test purpose the essential part of the message sequence chart is presented. If there are several scenarios of message sequence charts implied by the test purpose, the variants are presented distinguishing the different cases. TSS /INBC/IDP 7.3.1 INAP basic call Q. 1600 ref

46、erence lsN-v-l-l-l Table 4/Q.1600 9.1.1.1; Selection expression Configuration 1 TP 7.3.1.1 Initial Detection Point TSS /INBC/IDP Q. 1600 reference 9.1.1.1; Selection expression Configuration 1 TP 1sN-v-1-1-2 Table 4/Q.1600 Mapping of the calledparty number To verify that the TUT can successfully map

47、 the called party number from the IAM to the calledPartyNumber of the InitialDP operation. Pre-test conditions: Arm DP3 (Analyzed-Information) TSS i TP /INBC/IDP I 1SN-V-1-1-3 L I l I I I Q. 1600 reference 9.1.1.1; Selection expression Configuration 1 Table 4/Q.1600 Test purpose Mapping of the culli

48、ng party sub-address To verifi that the IT can successfully map the calling party number and the calling party sub-address contained in the access transport parameter from the IAM to the callingPartyNumber and CallingPartySubaddress of the InitialDP operation. Pre-test conditions: None TSS /INBC/IDP

49、 Q. 1600 reference 1sN-v-1-1-4 Table 4/Q. 1600 9.1.1.1; Selection expression Configuration 1 TP TSS /INl3C/IDP - Test purpose Mapping of the calling party .Y category To verifi that the IUT can successfully map the calling partys category fkom the IAM to the CallingPartysCategory of the InitialDP operation. Pre-test conditions: None Q. 1600 reference 9.1.1.1; Selection expression Configuration 1 TP 1sN-v-1-1-5 Table 4/Q. 1600 TSS /INBC/IDP Test purpose Mapping of the forward call indicators To verifi that the TUT can successfu