NAT L INST. OF STAND & TECH R.I.C.

AlllDM Minflb

NiST

PUBLICATIONS

NIST Special Publication 823-6

Systems

Technology

U.S. DEPARTMENT OF

COMMERCE

Technology Administration

National Institute of Standards and

Technology

ISDN Conformance Testing Guidelines:

Guidelines for Implementors of ISDN

Customer Premises Equipment to Conform

to Both National ISDN-1 and North

American ISDN Users' Forum Layer 3

Basic Rate Interface Basic Call Control

Abstract Test Suites

4

QC-
7he National Institute of Standards and Technology was established in 1988 by Congress to "assist

industry in the development of technology . . . needed to improve product quality, to modernize

manufacturing processes, to ensure product reliability . . . and to facilitate rapid commercialization ... of

products based on new scientific discoveries."

NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S.

industry's competitiveness; advance science and engineering; and improve public health, safety, and the

environment. One of the agency's basic functions is to develop, maintain, and retain custody of the national

standards of measurement, and provide the means and methods for comparing standards used in science,

engineering, manufacturing, commerce, industry, and education with the standards adopted or recognized

by the Federal Government.

As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic

and applied research in the physical sciences and engineering and performs related services. The Institute

does generic and precompetitive work on new and advanced technologies. NIST's research facilities are located at Gaithersburg, MD 20899, and at Boulder, CO 80303. Major technical operating units and their

principal activities are listed below. For more information contact the Public Inquiries Desk, 301-975-3058.

Technology Services

• Manufacturing Technology Centers Program

• Standards Services

• Technology Commercialization

• Measurement Services

• Technology Evaluation and Assessment

• Information Services

Electronics and Electrical Engineering

Laboratory

• Microelectronics

• Law Enforcement Standards

• Electricity

• Semiconductor Electronics

• Electromagnetic Fields'

• Electromagnetic Technology'

Chemical Science and Technology

Laboratory

• Biotechnology

• Chemical Engineering'

• Chemical Kinetics and Thermodynamics

• Inorganic Analytical Research

• Organic Analytical Research

• Process Measurements

• Surface and Microanalysis Science

• Thermophysics^

Physics Laboratory

• Electron and Optical Physics

• Atomic Physics

• Molecular Physics

• Radiometric Physics

• Quantum Metrology

• Ionizing Radiation

• Time and Frequency'

• Quantum Physics'

Manufacturing Engineering Laboratory

• Precision Engineering

• Automated Production Technology

• Robot Systems

• Factory Automation

• Fabrication Technology

Materials Science and Engineering

Laboratory

• Intelligent Processing of Materials

• Ceramics

• Materials Reliability'

• Polymers

• Metallurgy

• Reactor Radiation

Building and Fire Research Laboratory

• Structures

• Building Materials

• Building Environment

• Fire Science and Engineering

• Fire Measurement and Research

Computer Systems Laboratory

• Information Systems Engineering

• Systems and Software Technology

• Computer Security

• Systems and Network Architecture

• Advanced Systems

Computing and Applied Mathematics

Laboratory

• Applied and Computational Mathematics^

• Statistical Engineering^

• Scientific Computing Environments^

• Computer Services^

• Computer Systems and Communications^

• Information Systems

'At Boulder, CO 80303. ^Some elements at Boulder, CO 80303.
NIST Special Publication 823-6

ISDN Conformance Testing Guidelines:

Guidelines for Implementors of ISDN

Customer Premises Equipment to Conform

to Both National ISDN-1 and North

American ISDN Users' Forum Layer 3

Basic Rate Interface Basic Call Control

Abstract Test Suites

Leslie A. Collica and Dawn M. Hoffman

Advanced Systems Division

Computer Systems Laboratory

National Institute of Standards and Technology

Gaithersburg, MD 20899-0001

July 1994

U.S. Department of Commerce

Ronald H. Brown, Secretary

Technology Administration

Mary L. Good, Under Secretary for Technology

National Institute of Standards and Technology

Arati Prabhakar, Director
Reports on Computer Systems Technology

The National Institute of Standards and Technology (NIST) has a unique responsibility for computer

systems technology within the Federal government. NIST's Computer Systems Laboratory (CSL) develops standards and guidelines, provides technical assistance, and conducts research for computers and

related telecommunications systems to achieve more effective utilization of Federal information technology resources. CSL's responsibilities include development of technical, management, physical, and administrative standards and guidelines for the cost-effective security and privacy of sensitive unclassified

information processed in Federal computers. CSL assists agencies in developing security plans and in improving computer security awareness training. This Special Publication 823 series reports CSL re- search and guidelines to Federal agencies as well as to organizations in industry, government, and

academia.

National Institute of Standards and Technology Special Publication 823-6

Natl. Inst. Stand. Technol. Spec. Publ. 823-6, 27 pages (July 1994)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1994

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
ISDN CONFORMANCE TESTING GUIDELINES -

Guidelines for Implementors of ISDN Customer Premises Equipment

To Conform to Both National ISDN-1 and North American ISDN Users' Forum

Layer 3 Basic Rate Interface Basic Call Control

Abstract Test Suites

ABSTRACT

The following document is intended to provide information, as a supplement to the abstract test suites, to allow

conformance to both the Bellcore National ISDN-1 (NI-1) and North American ISDN Users' Forum (NIUF) NIU.301

specifications for the ISDN Layer 3 Basic Rate Interface for Basic Call Control (user-side). It was developed to guide implementors in the design of customer premises equipment in a manner which would allow them to pass both

the NI-1 and NIUF conformance tests. It may also be useful to vendors of test equipment, government procurement

agents, and testing laboratories.

This testing guideline was developed by members of the North American ISDN Users' Forum's ISDN Conformance

Testing Working Group and members of the Corporation for Open Systems' Task Force.

This document was approved in the North American ISDN Users' Forum as NIUF 429-94.

KEYWORDS

Abstract Test Suite, Basic Rate Interface, Conformance Testing, Customer Premises Equipment, Implementation

Under Test, Integrated Services Digital Network, ISDN, Network Layer, Protocol Implementation Extra Information

for Testing.

iii
NOTICE OF DISCLAIMER

This document contains NIUF conformance testing guidelines as agreed among participating expert

technical personnel according to the texts of isdn standards, configurations and descriptions that

are intended to promote interoperability and efficiency. this conformance testing guideline was

developed and approved by organizations participating in the north american isdn users' forum

(NIUF) MEETINGS. Neither The National Institute Of Standards And Technology (NIST) nor any of the

PARTICIPANTS IN THE NIUF MAKE ANY REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED WITH RESPECT TO THE

SUFHCIENCY, accuracy, or use of ANY INFORMATION OR OPINION CONTAINED HEREIN. THE USE OF THIS

INFORMATION OR OPINION IS AT THE RISK OF THE USER. UNDER NO CIRCUMSTANCES SHALL NIST, OR ANY

PARTICIPANT IN THE NIUF BE LIABLE FOR ANY DAMAGE OR INJURY INCURRED BY ANY PERSON ARISING OUT OF THE

SUFHCIENCY, ACCURACY, OR USE OF ANY INFORMATION OR OPINION CONTAINED HEREIN.

iv
ACKNOWLEDGMENTS

NIST would like to acknowledge the NIUF ISDN Conformance Testing (ICOT) Working Group, and especially the

following individuals for their valuable technical contributions to this document:

List of Contributors Organization

Tom Berriman IDACOM/HP

Robert Blackshaw Corporation for Open Systems

H. Gordon Brown AT&T Bell Laboratories

Yi Chin AT&T Bell Laboratories

Laurie Izzi Bellcore

Chris Leising Bellcore

Roxe Murray Northern Telecom

Pierre Prescott Tekelec

Suresh Ranganna AT&T Bell Laboratories

Kirby Spencer Joint Interoperability Test Center

Michelle Stevens Bellcore

Al Vitenas Bellcore

V

TABLE OF CONTENTS

1 INTRODUCTION 1

2 BACKGROUND 1

2.1 NIUF and NM Test Suites 1 2.2 Contents of the Guideline 1

3 NIU.301 AND NI-1 MESSAGE OPTIONS 2

3.1 Unexpected or Unrecognized Messages 2

3.2 Nonmandatory Information Element Content Error 2

3.3 Other Message Option Test Cases 3

4 NIU.301 AND NI-1 INFORMATION ELEMENT OPTIONS 3

4.1 Cause values 3

4.2 Information Element Fields 3

5 GENERAL CATEGORIES 3

5.1 Call Reference 3

5.2 Tests Unique to NIU.301 3

5.3 Tests Unique to NI-1 4

5.4 Error handling procedures 4

5.5 Optional and Uniquely Supported Messages 4

6 ABBREVIATIONS 18

7 REFERENCES 19

vii
List of Tables

Table 1. MESSAGE OPTIONS - Unexpected and Unrecognized Message Test Cases 5

Table 2. MESSAGE OPTIONS - Nonmandatory Information Element (IE) Content Error Test Cases 6

Table 3. MESSAGE OPTIONS - MisceUaneous Test Cases 7

Table 4. INFORMATION ELEMENT OPTIONS - Cause Value Test Cases 8

Tables. TEST CASES UNIQUE TO NIU.301 ATS 10

Table 6. TEST CASES UNIQUE TO NI-1 ATS 11

Table?. INFORMATION ELEMENTS - Specific to Messages 13

Table 8. INFORMATION ELEMENTS - Specific to Coding 15

Table 9. OPTIONAL AND UNIQUELY SUPPORTED MESSAGES - User to Network 17

viii
1 INTRODUCTION

The following document is intended to provide information, as a supplement to the abstract test suites (ATS), to allow conformance to both the Bellcore National ISDN-1 (NI-1) [1] and North American ISDN Users' Forum

(NIUF) NIU.301 [2] specifications for the ISDN Layer 3 Basic Rate Interface for Basic Call Control (user-side).

It was developed to guide implementors in the design of customer premises equipment (CPE) in a manner which

would allow them to pass both the NI-1 and NIUF conformance tests [3,4]. It may also be useful to vendors of

test equipment, government procurement agents, and testing laboratories.

This document emphasizes the common set of implementation options at the message and information element levels

of the specifications. Only the protocol events which have multiple options are addressed. This Guideline covers

the common set of options of the specifications for the basic call control test suites for Layer 3.

Section 2 provides background and a description of this Guideline. Section 3 provides the selection of options at the message level which allows conformance to both specifications; section 4 provides selection at the information

element level. Section 5 lists options for several general categories.

2 BACKGROUND

2.1 NIUF and NI-1 Test Suites

For conformance testing of ISDN basic rate access for NIUF and NI- 1 specifications, comparison of the test suites

showed:

• For Layer 1 - no difference between the test suites

• For Layer 2 - no difference between the test suites

• For Layer 3 - some difference between the test suites

• For Supplementary Services (SS) - 10 test suites for NI-1 SS; no test specification in NIUF.

For comparison of the Layer 3 basic call control specifications, several studies have addressed the question "What

are the differences between the specifications?" During such a comparison for testing aspects, many similarities were

found. The focus of the comparison was changed to address the question "Can CPE equipment be built to pass both

NI-1 and NIUF test suites for Layer 3?" The answer to the second question seems to be more useful information

for vendors of CPE and test equipment, procurement agents, and testing laboratories. This Guideline answers the

question by showing the common set of options of the specifications for the basic call control test suites for Layer

3 which would allow conformance to both NI-1 and NIUF.

2.2 Contents of the Guideline

The Guideline is divided into message options, information element options, and general categories. Within these

sections, groups of tests cases are described with the "intersecting" option which, if implemented, allows CPE to pass

both the NIUF and NI-1 test cases for that particular test event. The tables list the test cases, the test messages sent

to the CPE under test, and the preferred CPE response, which is the common set options. The notations given in brackets in the tables refer to the related protocol specification section(s).

This Guideline covers the common set of implementation options at the message level and at the information element

level. While there may be two options allowed by each specification (NIU.301 and NI-1) for a particular Layer 3

test event, there may be only one option which is the same for both - the "common set" of options.

The following table illustrates an example of a test message which is an "unexpected" message.

1
Allowed CPE Actions Upon Receipt of an Unexpected Message

NIUF

[NIU.301 section 5.8.4]

NI-1

[SR-1953 section 6.5.2]

Guideline Recommendation

("Common set" of options

to Pass NIUF and NI-1)

A) return a STATUS message

with cause #97, 98, or 101, or

B) clear the call

A) return a STATUS message, or

C) ignore the message

Return a STATUS message with cause #97, 98, or 101

In this case, the Guideline would list only the "intersecting" option: return a STATUS message with cause #97, 98, or 101. If STATUS with cause #97, 98, or 101 is implemented, CPE could Pass both the NIUF (NIU.301) and NI-1

test cases for unexpected messages. The Unexpected Messages in section 3.1.1 note the protocol sections of NIU.301

[NIU.301 5.8.4] and NI-1 [NI-1 6.5.2], refers to Table 1 for test cases, and describes the "common set" option as

"in states Ul-UlO - responding with a STATUS message with cause value 97, 98, or 101 would Pass both NIUF

and NI-1 ATSs." In Table 1, the specific test cases and test messages are listed along with the preferred CPE

response (the common set option).

3 NIU.301 AND NI-1 MESSAGE OPTIONS

This section lists the common set of message options for each particular protocol event which, if implemented, would

allow CPE to pass both test suites.

3.1 Unexpected or Unrecognized Messages

3.1.1 For unexpected messages (except RELEASE or RELEASE COMPLETE) received in any state other

than the Null state, specified in NIU.301 5.8.4 and NI-1 6.5.2:

• in states Ul-UlO - responding with a STATUS message with cause value 97, 98, or 101 would Pass both

NIUF and NI-1 ATSs.

• in states Ull and U19 - responding with either

1) a STATUS message (with cause value 97, 98, or 101), or

2) no response

would allow CPE to pass both NIUF and NI-1 ATSs.

Table 1 contains the list of these 45 unexpected messages test cases.

3.1.2 For unrecognized messages, as specified in NIU.301 5.8.4 and NI-1 6.5.2 - responding with a STATUS message with cause value 97, 98, or 101 would Pass both NIUF and NI-1 ATSs.

Table 1 contains the two unrecognized message type test cases.

3.2 Nonmandatory Information Element Content Error

For messages which contain a nonmandatory information element content error as specified in NIU.301 5.8.7.2 and

NI-1 6.5.3.2:

2
• Responding by "acting on the test message" (and not also sending a STATUS message), would Pass both

NIUF and NM ATSs.

Table 2 contains the list of 16 test cases.

3.3 Other Message Option Test Cases

• Responding according to the Preferred CPE Response in Table 3 would allow CPE to Pass both NIUF

and NI-1 ATSs.

Table 3 contains the list of five test cases.

4 NIU.301 AND NI-1 INFORMATION ELEMENT OPTIONS

In this section, the information element (IE) options are listed which would allow CPE to pass both NI-1 and NIUF

ATSs. The expected response at the message level is already the same in both NIU.301 and NI-1. The messages

are listed in the tables for information only; it is the particular value or presence of an IE which is emphasized in

the Preferred CPE Response column of the test case tables.

4.1 Cause values. In these cases, it is the particular cause value(s) which would allow CPE to pass both NI-1

and NIUF ATSs; the messages expected in response to the test events are already the same in both NIU.301 and Nl1. The message and the particular cause value option(s) are listed as the preferred CPE response in Table 4. Although the NI-1 specification does not require specific cause values in these cases, in several cases, the intersecting cause value is also the "preferred" cause value specified in NI-1.

• Responding according to the Preferred CPE Response in Table 4 would Pass both NIUF and NI-1 ATSs.

Table 4 contains the list of 25 test cases.

4.2 Information Element Fields

The results of the comparison of the Information Element fields for each message specified in NIU.301 and NI-1

are included in Tables 7 and 8. Comments and recommendations for testing are included in the tables.

5 GENERAL CATEGORIES

5.1 Call Reference. NI-1 requires only the one octet call reference value, while NIU.301 allows for one or two

octet call reference values. The addenda to NIU.301 [5] (June 1993) specifies only the one octet call reference

value. No test cases are affected, since a three octet call reference value is used in the call reference length error

test.

• Implementation of the single octet call reference would allow the CPE to pass both NI- 1 and NIUF ATSs.

5.2 Tests Unique to NIU.301

Several of these tests are optional depending upon implementation capabilities. The test case selection is determined

from answers to the NIU.301 Protocol Implementation Extra Information for Testing (PIXIT) questionnaire which

is completed by a CPE vendor prior to testing. Table 5 contains the list of 17 test cases.

3
5.3 Tests Unique to NM.

5.3.1 STATUS ENQUIRY received in states other than UIO. NIU.301 specifies only the occurrence of

the STATUS ENQUIRY received in UIO, and, therefore tests STATUS ENQUIRY only in state UIO. NI-1 defines

the behavior of STATUS ENQUIRY received in all states. Table 6 lists the nine test cases. The addenda to NIU.301 (June 1993) specifies the response to STATUS ENQUIRY in all states. The related STATUS ENQUIRY

tests will be added to the next version of the NIU.301 test suites.

• Implementation of STATUS ENQUIRY procedures according to NI-1 would allow CPE to pass both NI-1

and NIUF ATSs.

5.3.2 Terminal Initialization. For basic call control, NI-1 requires terminal initialization, while NIU.301

does not require terminal initialization. For NIUF, it is currently outside of the scope of testing NIU.301. However,

NIUF Implementation Agreement NIU89-311 [6] does provide optional procedures for terminal initialization. See

Table 6 for the list of 20 test cases.

• Implementation of terminal initialization procedures according to NI-1 would allow CPE to pass both NI-1

and NIUF ATSs.

5.4 Error handling procedures. Although the error handling procedures referenced in NIU.301 section 5.8.4 are not defined in NI-1 (SR-NWT-001953), NI-1 does provide direction to the implementor by pointing to Section

5.8 of ANSI T1.607 [7]. The introduction in the Generic Guidelines for ISDN Terminal Equipment on

Basic Access Interfaces revision J [1] states:

"Some ANSI requirements that do not impact terminal portability or compatibility with National

ISDN-1 switches are not addressed in SR-NWT-001953. Specifically, procedures for handling

error conditions defined in Section 5.8 of ANSI Tl.607- 1990 that do not affect terminal portability are not included in SR-NWT-001953. However, terminals will still be compatible with switches

that conform to the NI-1 agreement if designed in accordance with SR-NWT-001953 plus the

requirements in ANSI Tl.607- 1990 for procedures to handle error conditions that are not included

in SR-NWT-001953."

• Implementing the error handling procedures as specified in NIU.301 section 5.8.4 would allow CPE to pass both NIUF and NI-1 ATSs.

5.5 Optional and Uniquely Supported Messages.

The list of optional messages is provided in Table 9 as information. The majority of these messages are for use for

Supplementary Services. These messages do not impact the testing.

4
Table 1. MESSAGE OPTIONS - Unexpected and Unrecognized Message Test Cases

[ NIU.301 5.8.4 / NI-1 6.5.2 ]

Test Case # (state xx) Test Message

^Receive Events

Preferred CPE Response

NLxxJOl (XX = U1,U4,U7,U8,U10) ALERT STATUS (cause = 97,98,101)

NLxxJOl (xx=Ull,U19) ALERT STATUS (cause = 97,98,101)

or iNO response

NLxx_I03 (XX = U3,U4,U7,U8,U10) CALL PROCEEDING STATUS (cause = 97,98,101)

NLxx_I03 (xx= U11,U19) CALL PROCEEDING STATUS (cause = 97,98,101)

or iNO response

NLxx_I06 (xx= U1,U7,U8,U10) PROGRESS STATUS (cause = 97,98,101)

NLxx_I06 (xx=Ull,U19) PROGRESS STATUS (cause = 97,98,101)

or No response

NLxx_I09 (xx= U1,U7,U8,U10) CONNECT STATUS (cause = 97,98,101)

NLxx_I09 (xx= U11,U19) CONNECT STATUS (cause = 97,98,101)

or No response

NLxxJll (xx= U2,U3,U4,U7,U8,U10) SETUP

ACKNOWLEDGE

STATUS (cause = 97,98,101)

NLxxJll (xx=Ull,U19) SETUP

ACKNOWLEDGE

STATUS (cause = 97,98,101)

or No response

NLxx_I13 (xx= U1,U2,U3,U4,U7,U10) CONNECT

ACKNOWLEDGE

STATUS (cause = 97,98,101)

hfLxxJB (xx= U11,U19) CONNECT

ACKNOWLEDGE

STATUS (cause = 97,98,101)

or No response

NLxx_I14 (xx= U19) DISCONNECT STATUS (cause = 97,98,101)

or No response

NLxx_I19 (xx= Ul) INFORMATION STATUS (cause = 97,98,101)

NLxx_I19 (xx=U19) INFORMATION STATUS (cause = 97,98,101)

or No response

NLxx_N120 (xx= Ul.UlO) Unrecognized message

type

STATUS (cause = 97,98,101)

5
Table 2. MESSAGE OPTIONS - Noninandatory Information Element (IE) Content Error Test Cases

[ NIU301 5^7J. 1 NI-1 633^ ]

Test Case # (state xx) Test Message (Receive Event) Preferred CPE Response

NLxx_N218 (xx=Ul) CALL PROCEEDING (Progress

indicator IE length mismatch)

No response

NLxx_N219 (xx=Ul) CALL PROCEEDING (Progress

indicator IE conflicting values)

No response

NLxx_N220 (xx=U2) CALL PROCEEDING (Signal IE

length mismatch)

No response

NLxx_N222 (xx=U4) PROGRESS (Signal IE length

mismatch)

No response

NLxx_N224 (xx=UO) SETUP (Progress indicator IE

conflicting values)

CALL PROCEEDING,

ALERT, or CONNECT

NLxx_N225 (xx=U4) CONNECT (Progress indicator IE

length mismatch)

CONNECT ACKNOWLEDGE

or No response

NLxx_N226 (xx=U4) CONNECT (Progress indicator IE

conflicting values)

CONNECT ACKNOWLEDGE

or No response

NLxx_N227 (xx=Ul) SETUP ACKNOWLEDGE (Progress

indicator IE length mismatch)

No response

NLxx_N228 (xx=Ul) SETUP ACKNOWLEDGE (Progress

indicator IE conflicting values)

No response

NLxx_N229 (xx=U8) CONNECT ACKNOWLEDGE

(Unrecognized nonmandatory IE error)

No response

NLxx_N230 (xx=U10) DISCONNECT

(User-user/Feature indicator length

mismatch)

RELEASE

NLxx_N231 (xx=Ull) RELEASE (Cause IE length

mismatch)

RELEASE COMPLETE

NLxx_N233 (xx=U3) INFORMATION (Signal IE length

mismatch)

No response

NLxx_N238 (xx=UO) SETUP (Called party subaddress

conflicting values)

CALL PROCEEDING,

ALERT, or CONNECT

NLxx_N239 (xx=UO) SETUP (Low layer compatibility

length mismatch)

CALL PROCEEDING,

ALERT, or CONNECT

NLxx_N240 (xx=UO) SETUP (High layer compatibility

length mismatch)

CALL PROCEEDING,

ALERT, or CONNECT

6
Table 3. MESSAGE OPTIONS - Miscellaneous Test Cases

Test Case # Test Message (Receive Event) Preferred CPE Response

NLU1_I14 DISCONNECT

[NIU.301 5.3.4.2 and 5.8.4/NM

6.4]

RELEASE

NLU0_N2ir Mandatory Information Element out

of sequence

[NIU.301 5.8.5.1/ ]

RELEASE COMPLETE (cause = 96)

NLU0_N234 SETUP with

Unrecognized nonmandatory IE

[NIU.301 5.8.7.1/NI-l 6.5.3.1]

CALL_PROCEEDING,

or ALERT

or CONNECT

NLU3_N234 ALERT with Unrecognized

nonmandatory IE

[NIU.301 5.8.7.1/NI-l 6.5.3.1]

No response

NLU1_V243» B channel selection collision

[NIU.301 5.2.1]

CALL_PROCEEDING

or ALERT

or CONNECT

" See section 5.4 of this Guidelines.
Test Case # Test Message

(Receive Event)

Preferred CPE Response

Message Cause

Call Reference Procedural Errors [ NIU.301 5.8.3.2(1) / NI-1 6.5.1 ]

NT Tin Tni RFT fa<;f pompt ftp o 1

NT TIO 10'^ CAT T PROCFFDTNG fTJnexnectedl RFT FASF rOMPT FTF O 1 NLUO 106 PROGRESS CUnexoected') RELEASE COMPLETE O X

NT TJO 109 rONNFCT fTJnexnectedl RFT FASF rOMPT FTF O 1

NT TJO Tl 1 SFTTJP ACKNOWT FDCiF fTJnexnected'l RFT FASF rOMPT FTF O 1

NLU0_I13 CONNECT ACKNOWLEDGE (Unexpected) RELEASE COMPLETE 81

NLU0_I14 DISCONNECT (Unexpected) RELEASE COMPLETE 81

NLU0_I15 RELEASE (Unexpected) RELEASE COMPLETE 81

NLU0_I19 INFORMATION (Unexpected) RELEASE COMPLETE 81

NLU1_N213 CALL PROCEEDING (Call reference value not in use) RELEASE COMPLETE 81

NLU8_N213 CONNECT (Call reference value not in use) RELEASE COMPLETE 81

NLU10_N213 DISCONNECT (Call reference value not in use) RELEASE COMPLETE 81

Mandatory Information Element (IE) Content Error [ NIU.301 5.8.6.2 ]

NLU1_N133 CALL PROCEEDING

(Channel identification with length mismatch)

STATUS or Clear Call" 100

NLU4_N135 PROGRESS (Progress indicator length mismatch) STATUS or Clear Call" 100

^fLU0_N139 SETUP (Bearer capability undefined) RELEASE COMPLETE 100

NLU0_N143 SETUP (Channel identification with conflicting

values)

RELEASE COMPLETE 98 or 100

NLU1_N144 SETUP ACKNOWLEDGE

(Channel identification with length mismatch)

STATUS or Clear Call" 100

NLU10_N159 DISCONNECT (Cause length mismatch) RELEASE 100

NLU10_N160 RELEASE (Cause length mismatch) RELEASE COMPLETE 100

8
Table 4. Cause Value Test Cases (continued)

Test Case # Test Message

Preferred CPE Response

Message Cause

Mandatory Information Element Missing [ NIU301 5^6.1 ]

NLU1_N122 CALL PROCEEDING STATUS or Clear Call" 96

NLU4_N123 PROGRESS STATUS or Clear Call" 96

NLU0_N124 SETUP RELEASE COMPLETE 96

NLU1_N126 SETUP ACKNOWLEDGE STATUS or Clear Call" 96

Cause values [ Other reference sections ]

NLU10_V18 STATUS ENQUIRY

[NIU.301 5.8.10 /NI-1 6.5.5]

STATUS

(Call State = UIO)

30

Cause (CA) Value and Call State (CS)

NLU10_I98 Data Link Establishment

[NIU.301 5.8.9]

STATUS CA=30

CS=U10

" The preferred cause value is the information emphasized in this table. The Message of the

Preferred CPE Response is already the same in both specifications.

" The Clear Call message is a DISCONNECT, RELEASE or RELEASE COMPLETE

9
Table 5. TEST CASES UNIQUE TO NIU.301 ATS

NIU.301 Test Case #

(state xx)

Test Message

(Event)

NLU2_I01 ALERT (Unexpected) [NIU.301 6.5.2]

NLU2_I09 CONNECT (Unexpected) [NIU.301 6.5.2]

NLU4_N137 PROGRESS with mandatory Information Element (IE) error (Progress indicator with conflicting values) [NIU.301 5.8.6.2]

NLU3_N216 ALERT with nonmandatory IE error (Progress indicator with length mismatch) [NIU.301 5.8.7.2]

NLU3_N217 ALERT with nonmandatory IE error (Progress indicator with conflicting values) [NIU.301 5.8.7.2]

NLU2_N221 CALL PROCEEDING with nonmandatory IE error (Channel identification with conflicting values) [NIU.301 5.8.7.2]

NLU0_N223 SETUP with nonmandatory IE error (User-user with length mismatch) [NIU.301 5.8.7.2]

Optional Test Cases

NLU4_T192 Timer T301 expiry (selected if T301 .IMPLEMENTED)

NLU2_T195 Timer T304 expiry (selected if T304_IMPLEMENTED)

NLU3_T200 Timer T310 expiry (selected if T310_IMPLEMENTED)

NLxx_V241

(xx=Ul,U2,U3,

U4,U10,U11,U19)

SETUP with Call Reference (CR) flag=0; CR value in use

(2 simultaneous calls)

(selected if CPE supports simultaneous calls on two B-Channels)

10
Table 6. TEST CASES UNIQUE TO NI-1 ATS

NI-1 Test Case #

(state xx)

Test Message

(li<vent)

NLxx_V18 * (xx=U0,Ul,U2,U3,U4,

U7,U8,U11,U19)

STATUS ENQUIRY [NI-1 6.5.5]

Terminal Initialization test cases in NI-1

NLU0NI_V001 Verify that the lUT sends an INFOrmation message with Service Profile

Identification Information Element (SPI IE) = Service Profile Identifier (SPID)

when the Implementation Under Test (lUT) is in state UONI (not initialized).

[NI-1 8.5.2]

NLU0S_V002 Verify that the lUT does not respond after receiving an INFO with the Endpoint

Identifier (EID) = User Service Identifier (USID), Terminal Identifier (TID)

when the lUT is in state UOS (lUT sent the SPID). [NI-1 8.5.2]

NLU0IR_V002 Verify that the lUT does not respond after receiving an INFO with

EID=USID,TID when the lUT is in state UOIR (tester requested a SPID, SPID

sent). [NI-1 8.5.3]

NLU0I_V002 Verify that the lUT does not respond after receiving an INFO with

EID=USID,TID when the lUT is in state UOI (initialized). [NI-1 8.5.3]

NLU0S_V003 Verify that the lUT does not respond after receiving an INFO with Cause =

invalid IE contents (100) when the lUT is in state UOS (lUT sent the SPID).

[NI-1 8.5.2]

NLU0IR_V003 Verify that the lUT does not respond after receiving an INFO with Cause =

invalid IE contents (100) when the lUT is in state UOIR (tester requested a SPID). [NI-1 8.5.2]

NLU0S_V004 Verify that the lUT sends an INFO with SPI=SPID after receiving an INFO with an Information Request (IRQ) = prompt,TID when the lUT is in state UOS (lUT

sent the SPID). [NI-1 8.5.3]

NLU0SR_V004 Verify that the lUT sends an INFO with SPI=SPID after receiving an INFO with

IRQ=prompt,TID when the lUT is in state UOSR (tester rejected the SPID).

[NI-1 8.5.3]

NLU0I_V004 Verify that the lUT sends an INFO with SPI=SPID after receiving an INFO with

IRQ=prompt,TID when the lUT is in state UOI (Initialized). [NI-1 8.5.3]

NLU0S_V005 Verify that the lUT does not respond after receiving an INFO with

IRQ=Complete, EID=USID,TID when the lUT is in state UOS (lUT sent the

SPID). [NI-1 8.5.3]

NLU0IR_V005 Verify that the lUT does not respond after receiving an INFO with

IRQ=Complete, EID=USID,TID when the lUT is in state UOIR (tester requested

a SPID, SPID sent). [NI-1 8.5.3]

11
Table 6. TEST CASES UNIQUE TO NI-1 ATS (continued)

NM Test Case #

(state xx)

Test Message

(Event)

NLU0I_V005 Verify that the lUT does not respond after receiving an INFO with

IRQ=Complete, EID=USID,TID when the lUT is in state UOI (initialized). [NI-1

8.5.3]

NLU0S_N006 Verify that the lUT does not respond after receiving an INFO with a duplicated

IRQ=Coniplete and an EID=USID,TID when the lUT is in state UOS (lUT sent the SPID). [NI-1 8.5.3, 6.5.7]

NLU0IR_N006 Verify that the lUT does not respond after receiving an INFO with a duplicated

IRQ=Coniplete and an EID=USID,TID when the lUT is in state UOIR (tester

requested a SPID). [NI-1 8.5.3, 6.5.7]

NLU0S_N007 Verify that the lUT does not respond after receiving an INFO with

IRQ=Complete and a duplicated EID=USID,TID when the lUT is in state UOS

(SPID sent). [NI-1 8.5.3, 6.5.7]

NLU0IR_N007 Verify that the lUT does not respond after receiving an INFO with

IRQ=Complete and a duplicated EID=USID,TID when the lUT is in state UOIR

(test requested a SPID, SPID sent). [NI-1 8.5.3, 6.5.7]

NLU0S_N008 Verify that the lUT does not respond after receiving an INFO with

IRQ=Complete, EID=USID,TID and an unrecognized IE when the lUT is in

state UOS (SPID sent). [NI-1 8.5.3, 6.5.3]

NLU0IR_N008 Verify that the lUT does not respond after receiving an INFO with

IRQ=Complete, EID=USID,TID and an unrecognized IE when the lUT is in

state UOIR (tester requested a SPID, SPID sent). [NI-1 8.5.3, 6.5.3]

Optional Terminal Initialization Test Cases

NLU0S_V001 Verify that the lUT sends an INFO with SPI IE=SPID when the lUT is in state UOS (lUT sent the SPID). [NI-1 8.5.2]

(Conditional on supporting T-SPID Timer)

NLU0IR_V001 Verify that the lUT sends an INFO with SPI=SPID when the lUT is in state UOIR (tester requested a SPID, SPID sent). [NI-1 8.5.3]

(Conditional on supporting T-SPID Timer)

* Note: For NLxx_V18, the revised NIU.301 specifies response to STATUS ENQUIRY in all states. These STATUS ENQUIRY tests will be added to the next version of the NIU.301 test suites.

12
laoie /. ii>r UKJVIA 1 lurN tLLiiiiiVirLrN io - apecitic to Messages

(Information for Testing)

Information Element NIU.301 1 NI-1 Recommendation

ALERTING - User to Network

Channel

identification

Either preferred or exclusive B

channel allowed

Exclusive B channel For testing, use

exclusive B channel.

User-user Optional Not supported No impact to testing -

this IE is allowed in both ATSs.

CALL PROCEEDING - User to Network

Progress indicator Supported Not supported For testing, recommend

not sending Progress

indicator.

CONNECT - User to Network

User-user Optional Future No impact on testing - allowed in both ATSs.

DISCONNECT - User to Network

User-user Optional Future Recommend not

including this IE in user

to network direction.

INFORMATION - User to Network

Keypad facility Mandatory O.l* Used for supplementary

services in NI-1 - for

basic call, recommend

using Keypad facility,

rather than Called Party

Number.

Feature activation Not supported For supplementary

services

No impact on testing -

used for Supplementary

Services.

Service Profile ID Not supported For initialization See section 5.3.2 of this Guideline.

Called party

number

Not supported O.l* Used for supplementary

services in NI-1 - for

basic call, recommend

using keypad facility,

rather than Called Party

Number

13
Table 7. INFORMATION ELEMENTS - Specific to Messages (continued)

(Information for Testing)

Information Element NIU.301 NI-1 Recommendation

INFORMATION - Network to User

Progress indicator (PI) Not supported Allowed, but not

required

JUT should be able to handle

receipt of PI. For NIU.301, treat as an unrecognized non- mandatory IE and ignore PI, but

process the information message.

RELEASE - User to Network

User-user Optional Future Recommend not including this IE

in user to network direction

RELEASE COMPLETE - User to Network

User-user Optional Future Recommend not including this IE

in user to network direction

SETUP User to Network

Channel

identification

Either preferred or exclusive B

channel allowed

Exclusive B

channel allowed

For testing, use exclusive B

channel

Feature activation Not supported For

supplementary

services

Not used for basic call - for

supplementary services

User-user Optional Future No impact on testing - allowed in both ATSs

Call appearance Not supported For

supplementary

services

Not used for basic call - for

supplementary services

* 0.1 = optional, but support of at least one of the group of options labeled 0.1 is required

14
Table 8. INFORMATION ELEMENTS - Specific to Coding

Information Element NIU.301 Nil Comments

Call reference 1 or 2 octets 1 octet See section 5.1 of this

Guideline.

Bearer capability

octet 3: Information

transfer capability

Kestricted digital

information allowed

Kestricted digital

information not allowed

For testing, choose a supported information

transfer capability

other than restricted

digital information.

Bearer capability

octet 5: User

information Layer 1

G.722 and X.31 HDLC

flag stuffing are

allowed

G.722 and X.31 HDLC

flag stuffing are not

allowed

For testing, choose julaw or rate adaption.

Called party number

octet 3: Type of

number

Network Specific

Number is not allowed

Network Specific

Number is allowed

For testing, use other

than network specific

number.

Calling party number

octet J: lype of

number and Numbering

Plan Identification

For user to network,

local (subscriber),

national and others are

allowed.

For user to network,

for type of number and

numbering plan, either

local or national and

ISDN numbering plan is allowed.

For testing, for type of

number and

numbering plan, use

local (subscriber) or national and ISDN

numbering plan.

Cause

octet 4: Cause value

Different values Different values See section 4.1 of this

Guidehne.

High layer compatibility

octet 4a: Extended

high-layer characteristics identification

Extended Higher Layer

characteristics is not

allowed

Extended Higher Layer

characteristics is allowed

No impact on testing.

Low layer compatibility

octet 3: Coding

standard

Codepoint '01' not

supported.

Supports codepoint '01'

(other international

standard)

No impact on testing.

Low layer compatibility

octet 3: Information

transfer capability

Video not allowed Video allowed No impact on testing.

Low layer compatibility

octet 3a: Negotiation

indicator

Out-band negotiation

not allowed

Out-band negotiation

allowed

No impact on testing.

Low layer compatibility

octets 4 and 4b:

Information transfer

rate

Codepoint '10001' not

supported

Supports codepoint

10001 (128 kbps)

No impact on testing.

Supports codepoint

'10100' (1472 kbps—

national standard only)

Codepoint '10100' not

supported

15
Table 8. INFORMATION ELEMENTS - Specific to Coding (continued)

Infonnation Element NIU.301 NI-1 Comments

LLC-octets 4 and

4b:information transfer rate (cont.)

Codepoint '10111' not

supported

Supports codepoint '10111'

(1920 kbps)

No impact on

testing.

Low layer compatibility

octet 5: User

information layer 1

pi ULOCOl

Codepoint '00011' not

supported

Supports codepoint '00011'

(G.711 A-law)

i>o nnpaci on

testing.

Codepoint '00100' not

supported

Supports codepoint '00100'

(G.721 32 kbps/ADPCM)

Codepoint '00110' not

supported

Supports codepoint '00110'

(H.261 for 384 kbps video)

Low layer compatibility

octet 5a: Synchronous/

asynchronous

Difference in content of noteDifference in content of

note

No impact on

testing.

Low layer compatibility

octet 5b; In-band/

out of band negotiation

Codepoint '0' not

supported

Supports codepoint '0'

(negotiation done with user information messages)

No impact on

testing.

Low layer compatibility

octet 5c: Number of

stop bits, number of

data bits excluding parity,

parity information

Usage note provided No note present No impact on

testing.

Low layer compatibihty

octet 6: User

information layer 2

Codepoint 'OHIO' not

supported

Supports codepoint 'OHIO'

(Q.922)

nU impat I UIl

testing.

Codepoint '01111' not

supported

Supports codepoint '01111'

(Q.922 core aspects)

Codepoint '10001' not

supported

Supports codepoint '10001'

(T.90)

Low layer compatibility

octet 7: User

information layer 3

protocol

Codepoint '00010' not

supported

Supports codepoint '00010'

(Q.931) No impact on

testing.

Codepoint '00101' not

supported

Supports codepoint '00101'

(T.90)

Progress indicator

octet 3: Location

General location

international is not

supported.

General location

international is supported.

No impact on

testing.

Signal

octet 3: Signal value

Network Specific Signal

value is not supported.

Network Specific Signal

value is supported.

No impact on

testing.

16
Table 9. OPTIONAL AND UNIQUELY SUPPORTED MESSAGES User to Network

(For Information - No Impact on Testing)

Message NIU.301 NI-1 Comments

HOT r> i^iUi suppuncu ouppuncu iNo impdLi in /\ 1 o - lor suppiemeniory services

IvC 1 JSltZ V C INOl SUppUllcU ouppuricu i>o impdci in /\ 1 o - lor suppiemeniary services

K'CV J\Jj, I oCQCTTTP I Ur i^ui auppuricu ouppuricu iNo irnpdci in /\ i o - lor suppiemeniary services

JVC I Kj21_o/\v3C iNoi suppuricu ouppuricu impdci in /\io - lor suppiemenidry services

KEY HOLD Not supported Supported No impact in ATS - for supplementary services

HOLD REJECT Not supported Supported No impact in ATS - for supplementary services

RETRIEVE REJECT Not supported Supported No impact in ATS - for supplementary services

HOLD

ACKNOWLEDGE

Not supported Supported No impact in ATS - for supplementary services

RETRIEVE

ACKNOWLEDGE

Not supported Supported No impact in ATS - for supplementary services

KEY SETUP

ACKNOWLEDGE

Not supported Supported No impact in ATS - for supplementary services

NOTIFY Allowed-"may

be ignored"

Not supported No impact in ATS - Not tested

17
ABBREVIATIONS

ANSI A • 'KT 1 J J T A Amencan National Standards Institute

ATS Abstract Test Suite

BRI Basic Rate Interface

COS Corporation for Open Systems

CPE Customer Premises Equipment

EID Endpoint Identifier

ICOT ISDN Conformance Testing Working Group

IE Information Element

llSrU Information

IRQ Information Request

ISDN Integrated Services Digital Network

lUT Implementation Under Test

kbps kilobits per second

NI-1 National ISDN-1 (Bellcore CPE Guidelines)

VTTT TT^ NIUF North Amencan ISDN Users Forum

pixrr Protocol Implementation Extra Information for Testing

SPID Service Prorile Identifier

SPI Service Profile Identification

SS Supplementary Services

USID User Service Identifier

TID Terminal Identifier

Ul,U19User states Ul, U19
REFERENCES

Bellcore SR-NWT-001 953, Generic Guidelinesfor ISDN Terminal Equ^ment on Basic Access

Interfaces, Issue 1, June 1991, plus revision 1, December 1991.

NIU 90-301, Implementation Agreement of the North American ISDN Users' Forum, Layer 3 Signalling

Specification for the Minimal Set of Circuit Switched Bearer Services for the ISDN Basic Rate

Interface/Class I, 1990.

National ISDN-1 BRI Basic Call Control Abstract Test Suite for user-side conformance

testing. Corporation for Open Systems NI-1 Task Force (COS/ATS-93/001).

North American ISDN Users' s Forum NIUF 413-92, Layer 3 Network Layer - Circuit Switch

Call Control, Basic Rate Interface-Class I, User Side Abstract Test Suite (Version 1.2) June 1993.

NIUF 419-93, Implementation Agreement of the North American ISDN Users' Forum, Addenda to NIU

301 (June 1993).

NIU 89-31 1, Implementation Agreement of the North American ISDN Users' Forum, Generic Procedures

for the Control of ISDN Supplementary Services - Basic Rate Interface/Class I.

ANSI Tl.607- 1990, Telecommunications - Integrated Services Digital Network (ISDN) - Digital

Subscriber Signalling System Number 1 (DSSl) - Layer 3 Signalling Specification for Circuit Switched

Bearer Service.

ANSI Documents can be obtained by contacting the American National Standards Institute, 1

1

West 42nd Su-eet, New York, NY 10036.

Bellcore Documents can be obtained by calling 1-800-521 -CORE (2673) or by sending fax to (908)

336-2559.

COS Documents can be obtained by contacting Robert Blackshaw, COS, 8260 Willow Oaks

Corporate Drive, Suite 700, Fairfax, VA 22031.

NIUF(NIU) Documents can be obtained by contacting: NIUF Administrator, NIST, Building 223,

Room B-364, Gaithersburg, MD 20899.

19

ANNOUNCEMENT OF NEW PUBLICATIONS ON

lOTEGRATED SERVICES DIGITAL NETWORK

Superintendent of Documents

Government Printing Office

Washington, DC 20402

Dear Sir:

Please add my name to the announcement list of new publications to be issued in

the series: National Institute of Standards and Technology Special Publication 823-.

Name

Company

Address

City State Zip Code

(Notification key N-503)



NIST.Technical Publications

Periodical

Journal of Research of the National Institute of Standards and Technology — Reports NIST

research and development in those disciplines of the physical and engineering sciences in which

the Institute is active. These include physics, chemistry, engineering, mathematics, and computer

sciences. Papers cover a broad range of subjects, with major emphasis on measurement

methodology and the basic technology underlying standardization. Also included from time to time

are survey articles on topics closely related to the Institute's technical and scientific programs.

Issued six times a year.

Nonperiodicals

Monographs — Major contributions to the technical literature on various subjects related to the

Institute's scientific and technical activities.

Handbooks — Recommended codes of engineering and industrial practice (including safety codes)

developed in cooperation with interested industries, professional organizations, and regulatory

bodies.

Special Publications — Include proceedings of conferences sponsored by NIST, NIST annual

reports, and other special publications appropriate to this grouping such as wall charts, pocket

cards, and bibliographies.

Applied Mathematics Series — Mathematical tables, manuals, and studies of special interest to

physicists, engineers, chemists, biologists, mathematicians, computer programmers, and others

engaged in scientific and technical work.

National Standard Reference Data Series — Provides quantitative data on the physical and chemical

properties of materials, compiled from the world's literature and critically evaluated. Developed

under a worldwide program coordinated by NIST under the authority of the National Standard

Data Act (Public Law 90-396). NOTE: The Journal of Physical and Chemical Reference Data

(JPCRD) is published bimonthly for NIST by the American Chemical Society (ACS) and the

American Institute of Physics (AIP). Subscriptions, reprints, and supplements are available from

ACS, 1155 Sbcteenth St., NW, Washington, DC 20056.

Building Science Series — Disseminates technical information developed at the Institute on building

materials, components, systems, and whole structures. The series presents research results, test methods, and performance criteria related to the structural and environmental functions and the

durability and safety characteristics of building elements and systems.

Technical Notes — Studies or reports which are complete in themselves but restrictive in their

treatment of a subject. Analogous to monographs but not so comprehensive in scope or definitive

in treatment of the subject area. Often serve as a vehicle for final reports of work performed at NIST under the sponsorship of other government agencies.

Voluntary Product Standards — Developed under procedures published by the Department of

Commerce in Part 10, Title 15, of the Code of Federal Regulations. The standards establish

nationally recognized requirements for products, and provide all concerned interests with a basis

for common understanding of the characteristics of the products. NIST administers this program

in support of the efforts of private-sector standardizing organizations.

Consumer Information Series — Practical information, based on NIST research and experience,

covering areas of interest to the consumer. Easily understandable language and illustrations

provide useful background knowledge for shopping in today's technological marketplace.

Order the above NIST publications from: Superintendent of Documents, Government Printing Office,

Washington, DC 20402.

Order the following NIST publications— FIPS and NISTIRs—from the National Technical Information

Service, Springfield, VA 22161.

Federal Information Processing Standards Publications (FIPS PUB) — Publications in this series

collectively constitute the Federal Information Processing Standards Register. The Register serves

as the official source of information in the Federal Government regarding standards issued by

NIST pursuant to the Federal Property and Administrative Services Act of 1949 as amended,

Public Law 89-306 (79 Stat. 1127), and as implemented by Executive Order 11717 (38 FR 12315,

dated May 11, 1973) and Part 6 of Title 15 CFR (Code of Federal Regulations).

NIST Interagency Reports (NISTIR)— A special series of interim or final reports on work

performed by NIST for outside sponsors (both government and non-government). In general,

initial distribution is handled by the sponsor; public distribution is by the National Technical

Information Service, Springfield, VA z2161, in paper copy or microfiche form.
U.S. Department of Commerce

National Institute of Standards and Technology

Gaithersburg, MD 20899-0001

Official Business

Penalty for Private Use $300