1、INTERNATIONAL TELECOMMUNICATION UNIONCCITT Q.785THE INTERNATIONALTELEGRAPH AND TELEPHONECONSULTATIVE COMMITTEESPECIFICATIONSOF SIGNALLING SYSTEM No. 7ISUP PROTOCOL TEST SPECIFICATIONFOR SUPPLEMENTARY SERVICESRecommendation Q.785Geneva, 1991FOREWORDThe CCITT (the International Telegraph and Telephone
2、 Consultative Committee) is a permanent organ of theInternational Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariffquestions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwidebasis.The Plenary Assembly of
3、CCITT which meets every four years, establishes the topics for study and approvesRecommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT betweenPlenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).Recommend
4、ation Q.785 was prepared by Study Group XI and was approved under the Resolution No. 2procedure on the 10thof September 1991._CCITT NOTEIn this Recommendation, the expression “Administration” is used for conciseness to indicate both atelecommunication Administration and a recognized private operatin
5、g agency. ITU 1991All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic ormechanical, including photocopying and microfilm, without permission in writing from the ITU.Recommendation Q.785 1Recommendation Q.785Recommendation Q.785ISUP P
6、ROTOCOL TEST SPECIFICATIONFOR SUPPLEMENTARY SERVICES1 IntroductionThis Recommendation contains a detailed set of tests for the supplementary services supported by SignallingSystem No. 7 Integrated Services Digital Network User Part (ISUP).Details of the supplementary services supported by ISUP can b
7、e found in Blue Book (1988) RecommendationQ.730. It should be noted that this test Recommendation covers those services which can be regarded as stable andclearly specified in Blue Book (1988) Recommendation Q.730.This Recommendation also covers supplementary services supported by Recommendation Q.7
8、67.The basic rules for the test specification can be found in Recommendation Q.780.2 Objective of the test specificationThe objective of this test specification is to check that the ISUP protocol supported by a given implementationhas the ability to correctly convey the necessary signalling informat
9、ion to support the supplementary services specifiedin Blue Book (1988) Recommendation Q.730 and Recommendation Q.767 (1991). Therefore this test list only coversareas of supplementary services where there is a direct impact on the ISUP protocol. However some call controlfunctions are also verified,
10、i.e. the transfer of speech/information is possible.It should be noted that this test specification does not attempt to test the operation of the supplementaryservices (end-to-end function tests), as these tests are outside the scope of this test specification.This test specification does not intend
11、 to provide exhaustive testing of Blue Book (1988)Recommendation Q.730 and Recommendation Q.767 (1991) supplementary services, but does intent to provide areasonable level of confidence that the protocol required to support Blue Book (1988) Recommendation Q.730 andRecommendation Q.767 (1991) supplem
12、entary services has been implemented at a signalling point.This test specification does not address interactions between supplementary services.3 General principles of testsThe tests are described as “validation” tests or “validation” and “compatibility” tests. Each test descriptionindicates in the
13、field “type of test” whether the test is a “validation” (VAT) or a “validation” and “compatibility” (VATii) provided by a network connected to the signalling point;iii) provided by a “test box” connected to the signalling point;iv) provided by exchange data set at the signalling point;v) provided by
14、 user-network signalling.This list is not intended to be exhaustive. The choice of stimulus is a matter for the Administration concernedand does not necessarily require bilateral agreement.4.4 Checking of correct reception of parameters at signalling point under testThis test specification requires
15、the checking of the correct reception of various ISUP parameters at SP A (SPunder test).No attempt is made in this Recommendation to specify how to perform this function, however depending on anumber of factors the function of the “checking of receiving correctly of messages and parameters” could be
16、 performedby various mechanisms. A number of possibilities are listed below.Recommendation Q.785 3The check could be performed by:i) an intrinsic part of the SP A;ii) a network connected to SP A;iii) a “test box” connected to SP A;iv) monitoring/printout at the SP A;v) monitoring of the messages and
17、 information elements at the user-network interface.The list is not intended to be exhaustive. The choice of the method is a matter for Administration concernedand does not necessarily require bilateral agreement.4.5 Check tableMany test scripts within the test specification include a check table. T
18、he check table lists specific indicatorswhich must be checked.The check table does not necessarily include all the parameters and indicators that should be carried within anymessage.5 ISUP protocol test list for supplementary servicesAll tests may be validation tests. Tests marked “*” are compatibil
19、ity tests. Tests marked “F.S” are for furtherstudy.1 User-to-User Signalling (UUS)1.1 User-to-User Signalling service 11.1.1 Implicit request* 1.1.1.1.1 Successful UUI in the forward message: sent* 1.1.1.1.2 Successful UUI in the forward message: received* 1.1.1.2.1 Successful UUI in the backward me
20、ssage: sent* 1.1.1.2.2 Successful UUI in the backward message: received* 1.1.1.3.1 Unsuccessful Explicit network rejection: sent* 1.1.1.3.2 Unsuccessful Explicit network rejection: received1.1.2 Explicit request F.S2 Closed User Group (CUG)2.1 Closed User Group (CUG) decentralized* 2.1.1 CUG call wi
21、th outgoing access allowed: sent* 2.1.2 CUG call, with outgoing access allowed: received* 2.1.3 CUG call, with outgoing access not allowed, to a network offering the CUG supplementaryservice: sent* 2.1.4 CUG call, with outgoing access not allowed, to a network offering the CUG supplementaryservice:
22、received* 2.1.5 CUG call, with outgoing access not allowed, to a network not offering the CUGsupplementary service: sent* 2.1.6 CUG call, with outgoing access not allowed, to a network not offering the CUGsupplementary service: received* 2.1.7 CUG call, international interlock code included: sent* 2
23、.1.8 CUG call, international interlock code included: received2.2 Closed User Group (CUG) centralizedFor further study.4 Recommendation Q.7853 Calling Line Identification (CLI)* 3.1.1 CLIP network provided: sent* 3.1.2 CLIP network provided: received* 3.2.1 CLIP user provided: sent* 3.2.2 CLIP user
24、provided: received* 3.3.1 CLIR network provided: sent* 3.3.2 CLIR network provided: received* 3.4.1 CLIR user provided: sent* 3.4.2 CLIR user provided: received* 3.5.1 CLI not available: sent* 3.5.2 CLI not available: received* 3.6.1 CLI not sent in IAM, available with INR/INF* 3.6.2 CLI not receive
25、d in IAM, available with INR/INF* 3.6.3 CLI not sent in IAM, not available with INR/INF* 3.6.4 CLI not received in IAM, not available with INR/INF3.7.1 CLI international address included: sent3.7.2 CLI international address included: received4 Direct Dialling InThe Direct Dialling In (DDI) service h
26、as no impact on the ISUP protocol. Therefore no test scripts areprovided for this supplementary service.5 Call ForwardingFurther study.6 Connected Line Identification (Col)Note These tests are only applicable to White Book Recommendation Q.767.* 6.1.1 COL request: sent* 6.1.2 COL request: received*
27、6.2.1 COLP network provided: sent* 6.2.2 COLP network provided: received* 6.3.1 COLP user provided: sent* 6.3.2 COLP user provided: received* 6.4.1 COLR network provided: sent* 6.4.2 COLR network provided: received* 6.5.1 COLR user provided: sent* 6.5.2 COLR user provided: received* 6.6.1 COL not av
28、ailable: sent* 6.6.2 COL not available: received6.7.1 COL international address included: sent6.7.2 COL international address included: received* 6.8.1 COL received, but not requestedRecommendation Q.785 5Recommendation Q.785TEST NUMBER: 1.1.1.1.1REFERENCE: Q.730, 2.2.1.6; Q.767TITLE: User-to-User S
29、ignalling service 1 Implicit requestSUBTITLE: Successful UUI in the forward messages: sentPURPOSE: To verify that user-to-user information can be correctly sent in the forward call control messagesPRE-TEST CONDITIONS: Arrange the stimulus such that the IAM and REL generated at SP A contains a UUI pa
30、rameterCONFIGURATION: 1 TYPE OF TEST: VAT Q.767TITLE: User-to-User Signalling service 1 Implicit requestSUBTITLE: Successful UUI in the backward messages: sentPURPOSE: To verify that user-to-user information can be correctly sent in the backward call control messagesPRE-TEST CONDITIONS:a) Arrange th
31、e stimulus such that the IAM generated at SP B contains a UUI parameterb) Arrange the stimulus such that the backward messages generated at SP A contains a UUI parameterCONFIGURATION: 1 TYPE OF TEST: VAT Q.767TITLE: Closed User Group DecentralizedSUBTITLE: CUG call with outgoing access not allowed,
32、to a network offering the CUG supplementary service: sentPURPOSE: To verify that the parameters necessary for a CUG call with outgoing access not allowed can be correctly sent.PRE-TEST CONDITIONS:a) SP A and SP B should belong to networks which offer the CUG supplementary service.b) Arrange the stim
33、ulus such that the IAM generated at SP A contains the Optional Forward Call Indicators parameter setto “CUG call outgoing access not allowed”, and a CUG interlock code that is acceptable at SP B.CONFIGURATION: 1 TYPE OF TEST: VAT Q.767TITLE: Closed User Group DecentralizedSUBTITLE: CUG call with out
34、going access not allowed, to a network not offering the CUG supplementary service:sentPURPOSE: To verify that the parameters necessary for a CUG call with outgoing access not allowed can be correctly sent,to a network not offering the CUG service, and that a release can be accepted in response by SP
35、 A.PRE-TEST CONDITIONS:a) SP A should belong to a network which offers the CUG supplementary service.b) SP B belongs to a network which does not offer the CUG service.c) Arrange the stimulus such that the IAM generated at SP A contains the optional forward call indicators parameter fieldwith the CUG
36、 call indicator set to “outgoing access not allowed”, and the CUG interlock code parameter field.CONFIGURATION: 1 TYPE OF TEST: VAT Q.767TITLE: Closed User Group DecentralizedSUBTITLE: CUG call with outgoing access not allowed, to a network not offering the CUG supplementary service:receivedPURPOSE:
37、 To verify that the parameters necessary for a CUG call with outgoing access not allowed can be correctlyreceived, by a network not offering the CUG service, and rejected with a release message.PRE-TEST CONDITIONS:a) SP B should belong to a network which offers the CUG supplementary service.b) SP A
38、belongs to a network which does not offer the CUG service.c) Arrange the stimulus such that the IAM generated at SP B contains the optional forward call indicators parameter fieldwith the CUG call indicator set to “outgoing access not allowed”, and the CUG interlock code parameter field.CONFIGURATIO
39、N: 1 TYPE OF TEST: VAT Q.767TITLE: Calling Line IdentificationSUBTITLE: CLIP Network provided: sentPURPOSE: To verify that CLIP (network provided) can be correctly sent in the Calling Party Number parameter.PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains a CLI-
40、network provided,presentation allowed.CONFIGURATION: 1 TYPE OF TEST: VAT Q.767TITLE: Calling Line IdentificationSUBTITLE: CLIP User provided: sentPURPOSE: To verify that CLIP (user provided) can be correctly sent in the Calling Party Number parameter.PRE-TEST CONDITIONS: Arrange the stimulus such th
41、at the IAM generated at SP A contains a CLI-user provided,presentation allowed.CONFIGURATION: 1 TYPE OF TEST: VAT Q.767TITLE: Calling Line IdentificationSUBTITLE: CLIP Network provided: sentPURPOSE: To verify that CLIR (network provided) can be correctly sent in the Calling Party Number parameter.PR
42、E-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains a CLI-network provided,presentation restricted.CONFIGURATION: 1 TYPE OF TEST: VAT Q.767TITLE: Calling Line IdentificationSUBTITLE: CLIR User provided: sentPURPOSE: To verify that CLIR (user provided) can be correctl
43、y sent in the Calling Party Number parameter.PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains a CLI-user provided,presentation restricted.CONFIGURATION: 1 TYPE OF TEST: VAT & CPT TYPE OF SP: SPEXPECTED MESSAGE SEQUENCE:SP A SP BIAM ANM TEST DESCRIPTION1. Make a
44、call from SP B to SP A.2. Record the message sequence and parameters using a signal monitor.3. CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER RECEIVED IN THE IAM BY SP A?4. CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THECHECK TABLE BELOW?5. CHECK C: WAS THE MESSAGE SEQUENC
45、E AS ABOVE?CHECK TABLEIAMCalling Party Number parameter Presentation restriction indicator: 01 (presentation restricted) Screening indicator: 01 (user provided, verified and passed)Recommendation Q.785 27TEST NUMBER: 3.5.1REFERENCE: Q.730, 4.1.1.1 b)TITLE: Calling Line IdentificationSUBTITLE: CLI No
46、t available: sentPURPOSE: To verify that a CLI (address not available) can be correctly sent in the Calling Party Number parameter.PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains a CLI address notavailable.CONFIGURATION: 1 TYPE OF TEST: VAT & CPT TYPE OF SP: SP
47、EXPECTED MESSAGE SEQUENCE:SP A SP BIAM ANM TEST DESCRIPTION1. Make a call from SP B to SP A.2. Record the message sequence and parameters using a signal monitor.3. CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER RECEIVED IAM BY SP A?4. CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICAT
48、ED IN THECHECK TABLE BELOW?5. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?CHECK TABLEIAMCalling Party Number parameter Odd/even indicator: 0 (even number of address digits) Nature of address signals: 0000000 (spare) Numbering plans indicator: 000 (spare) Calling party number incomplete indicator: 0 (complete) Presentation restriction indicator: 10 (address not available) Screening indicator: 11 (network provided) Address signal: none
