Telcordia is now part of Ericsson
Read more >
Services > Testing > Conformance, Interoperability and Performance >

ATM UNI 4.0 Signaling Conformance Test Suites

Part Number 803310 - Point-to-Point, Network Side

The Telcordia® ATM UNI 4.0 Signaling Conformance Test Suite for Point-to-Point Network Side Connections Conformance Test Suite provides a fully automated conformance testing of network side equipment, such as ATM switches, that implement ATM Forum UNI 4.0 signaling requirements for point-to-point connectivity. The test suite consists of the following conformance test groups:

  • General - this test group addresses the basic signaling procedures to verify the Implementation Under Test (IUT)'s capability to support valid call/connection control procedures for point-to-point connections, which include all valid combination of Bearer Class, Traffic Parameters and Quality of Service (QoS). All valid combinations of supported optional information element. Call/connection clearing procedure. These specifications are covered under the following sub-groups:
    • Basic Setup - these test cases verify the IUT's functionality for receiving a SETUP message containing a combination of traffic parameters.
    • Setup Message for Optional Information Elements - these test cases verify the IUT's functionality for sending a message from and to the remote party.
    • Call Proceeding - these test cases verify the IUT's functionality for processing an optional Call Proceeding message from the remote party.
    • Connect - these test cases verify the IUT's functionality for processing a Connect message from the remote party.
    • Clearing - these test cases verify the IUT's functionality for call/connection clearing under various conditions.
  • Error - this test group covers procedures to verify IUT's capability to handle error conditions including error conditions for mandatory and non-mandatory information elements. This test group consists for the following sub-groups:
    • Protocol Error - these test cases verify the IUT's functionality for handling a message containing a protocol discriminator error.
    • Short Message Error - these test cases verify the IUT's functionality for handling short message.
    • Call Reference Error - these test cases verify the IUT's functionality for handling messages that contain a call reference error in which bits 5 through 8 of octet 1 are non-zero/ a call reference length error/a call reference value that is not recognized/ call reference flag set to 1 or call reference value in use/message containing a global call reference value. Specification reference: ITU Q2931 section 5.6.3.1 and 5.6.3.2.
    • Message Sequence Error - these test cases verify the IUT's functionality for handling an unexpected (out of sequence) message.
    • Unrecognized Message Error - these test cases verify the IUT's functionality for handling an unrecognized message.
    • Message Length Error - these test cases verify the functionality for handling a message length error.
    • Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of missing mandatory IE, mandatory IEs with length errors and mandatory IEs with content error.
    • Non-Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of messages containing unrecognized IEs, error in the contents of a non-mandatory IE, non-mandatory IE with length error and a message with unexpected recognized IE.
    • Status Message Inquiry - these test cases verify the IUT's functionality for status inquiry procedures.
    • UNI 4.0 Procedure - this test group verifies the IUT's functionalities for the following ATM Forum UNI 4.0 specific procedures as defined in UNI 4.0 specification:
    • Traffic Negotiation - these test cases verify the IUT's functionality for traffic negotiation.
    • Individual QoS - these test cases verify the IUT's functionality for signaling individual QoS parameter procedures.
    • ABR - these test cases verify the IUT's functionality for Available Bit Rate (ABR) signaling procedure.
    • ATM Anycast - these test cases verify the IUT's functionality for ATM Anycast signaling procedures.
    • VPCI/VCI Selection - these test cases verify the IUT's functionality for VPCI/VCI selection procedures.
  • Timers - this test group of test cases verify the IUT's functionality for network side timer implementation.

Part Number 803320 - Point-to-Point, User Side

The Telcordia® ATM UNI 4.0 Signaling Conformance Test Suite for Point-to-Point User Side Connections Conformance Test Suite provides a fully automated conformance testing of user side equipment, such as ATM NIC cards, that implement ATM Forum UNI 4.0 signaling requirements for point-to-point connectivity. The test suite consists of the following conformance test groups:

  • General - this test group addresses the basic signaling procedures to verify the Implementation Under Test (IUT)'s capability to support valid call/connection control procedures for point-to-point connections, which include all valid combination of Bearer Class, Traffic Parameters and Quality of Service (QoS). All valid combinations of supported optional information element. Call/connection clearing procedure. These specifications are covered under the following sub-groups:
    • Incoming - these test cases verify the IUT's functionality for receiving a SETUP message containing a combination of traffic parameters.
    • Outgoing - these test cases verify the IUT's functionality for sending a message to and from the remote party.
    • Clearing - these test cases verify the IUT's functionality for call/connection clearing under various conditions.
  • Error - this test group covers procedures to verify IUT's capability to handle error conditions including error conditions for mandatory and non-mandatory information elements. This test group consists for the following sub-groups:
    • Protocol Error - these test cases verify the IUT's functionality for handling a message containing a protocol discriminator error.
    • Short Message Error - these test cases verify the IUT's functionality for handling short message.
    • Call Reference Error - these test cases verify the IUT's functionality for handling messages that contain a call reference error in which bits 5 through 8 of octet 1 are non-zero/ a call reference length error/a call reference value that is not recognized/ call reference flag set to 1 or call reference value in use/message containing a global call reference value.
    • Message Sequence Error - these test cases verify the IUT's functionality for handling an unexpected (out of sequence) message.
    • Unrecognized Message Error - these test cases verify the IUT's functionality for handling an unrecognized message.
    • Message Length Error - these test cases verify the functionality for handling a message length error.
    • General IE - Repeat Information Element - these test cases verify the IUT's functionality for handling duplicate information elements (IEs).
    • Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of missing mandatory IE, mandatory IEs with length errors and mandatory IEs with content error.
    • Non-Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of messages containing unrecognized IEs, error in the contents of a non-mandatory IE, non-mandatory IE with length error and a message with unexpected recognized IE.
    • Status Message Inquiry - these test cases verify the IUT's functionality for status inquiry procedures.
  • UNI 4.0 Procedure - this test group verifies the IUT's functionalities for the following ATM Forum UNI 4.0 specific procedures as defined in UNI 4.0 specification:
    • Traffic Negotiation - these test cases verify the IUT's functionality for traffic negotiation.
    • Individual QoS - these test cases verify the IUT's functionality for signaling individual QoS parameter procedures.
    • ABR - these test cases verify the IUT's functionality for Available Bit Rate (ABR) signaling procedure.
    • ATM Anycast - these test cases verify the IUT's functionality for ATM Anycast signaling procedures.
    • VPCI/VCI Selection - these test cases verify the IUT's functionality for VPCI/VCI selection procedures.
  • Timers - this test group of test cases verify the IUT's functionality for network side timer implementation.

Part Number 803330 - Point-to-Multipoint, Network Side

The Telcordia® ATM UNI 4.0 Signaling Conformance Test Suite for Point-to-Multipoint Network Side Connections Conformance Test Suite provides a fully automated conformance testing of network side equipment, such as ATM switches, that implement ATM Forum UNI 4.0 signaling requirements for point-to-multipoint connectivity. The test suite consists of the following conformance test groups:

  • General - this test group addresses the basic signaling procedures to verify the Implementation Under Test (IUT)'s capability to support valid call/connection control procedures for point-to-point connections, which include all valid combination of Bearer Class, Traffic Parameters and Quality of Service (QoS). All valid combinations of supported optional information element. Call/connection clearing procedure. These specifications are covered under the following sub-groups:
    • Basic Setup - these test cases verify the IUT's functionality for receiving a SETUP message containing a combination of traffic parameters.
    • Incoming - these test cases verify the IUT's functionality for handling a message from and toward the remote party.
    • Clearing - these test cases verify the IUT's functionality for call/connection clearing under various conditions.
  • Error - this test group covers procedures to verify IUT's capability to handle error conditions including error conditions for mandatory and non-mandatory information elements. This test group consists for the following sub-groups:
    • Protocol Error - these test cases verify the IUT's functionality for handling a message containing a protocol discriminator error.
    • Short Message Error - these test cases verify the IUT's functionality for handling short message.
    • Call Reference Error - these test cases verify the IUT's functionality for handling messages that contain a call reference error such as a call reference value that is not recognized/ a message containing an Endpoint Reference IE length that is not valid/ a message containing an Endpoint reference IE type that is not valid/a message containing an Endpoint Reference IE flag that is not valid/ a message with an Endpoint Reference IE procedure that is not correct.
    • Message Sequence Error - these test cases verify the IUT's functionality for handling an unexpected (out of sequence) message.
    • ITU_T Message - these test cases verify the IUT's functionality for handling an ITU_T message.
    • Unrecognized Message Error - these test cases verify the IUT's functionality for handling an unrecognized message.
    • Message Length Error - these test cases verify the functionality for handling a message length error.
    • General IE - Repeat Information Element - these test cases verify the IUT's functionality for handling duplicate information elements (IEs).
    • Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of missing mandatory IE, mandatory IEs with length errors and mandatory IEs with content error.
    • Non-Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of messages containing unrecognized IEs.
    • Status Message Inquiry - these test cases verify the IUT's functionality for status inquiry procedures.
  • UNI 4.0 Procedure - this test group verifies the IUT's functionalities for the following ATM Forum UNI 4.0 specific procedures as defined in UNI 4.0 specification:
    • Traffic Negotiation - these test cases verify the IUT's functionality for traffic negotiation.
    • Individual QoS - these test cases verify the IUT's functionality for signaling individual QoS parameter procedures.
    • VPCI/VCI Selection - these test cases verify the IUT's functionality for VPCI/VCI selection procedures.
    • LIJ Procedure - these test cases verify the IUT's functionality for Leaf Initiated Join procedures.
  • Timers - this test group of test cases verify the IUT's functionality for network side timer implementation.

Part Number 803340 - Point-to-Multipoint, User Side

The Telcordia® ATM UNI 4.0 Signaling Conformance Test Suite for Point-to-Multipoint User Side Connections Conformance Test Suite provides a fully automated conformance testing of user side equipment, such as ATM NIC cards, that implement ATM Forum UNI 4.0 signaling requirements for point-to-multipoint connectivity. The test suite consists of the following conformance test groups:

  • General - this test group addresses the basic signaling procedures to verify the Implementation Under Test (IUT)'s capability to support valid call/connection control procedures for point-to-point connections, which include all valid combination of Bearer Class, Traffic Parameters and Quality of Service (QoS). All valid combinations of supported optional information element. Call/connection clearing procedure. These specifications are covered under the following sub-groups:
    • Incoming - these test cases verify the IUT's functionality for receiving a SETUP message containing a combination of traffic parameters.
    • Outgoing - these test cases verify the IUT's functionality for sending a message from and toward the remote party.
    • Clearing - these test cases verify the IUT's functionality for call/connection clearing under various conditions.
  • Error - this test group covers procedures to verify IUT's capability to handle error conditions including error conditions for mandatory and non-mandatory information elements. This test group consists for the following sub-groups:
    • Protocol Error - these test cases verify the IUT's functionality for handling a message containing a protocol discriminator error.
    • Short Message Error - these test cases verify the IUT's functionality for handling short message.
    • Call Reference Error - these test cases verify the IUT's functionality for handling messages that contain a call reference error such as a call reference value that is not recognized/ a message containing an Endpoint Reference IE length that is not valid/ a message containing an Endpoint reference IE type that is not valid/a message containing an Endpoint Reference IE flag that is not valid/ a message with an Endpoint Reference IE procedure that is not correct.
    • Message Sequence Error - these test cases verify the IUT's functionality for handling an unexpected (out of sequence) message.
    • ITU_T Message - these test cases verify the IUT's functionality for handling an ITU_T message.
    • Unrecognized Message Error - these test cases verify the IUT's functionality for handling an unrecognized message.
    • Message Length Error - these test cases verify the functionality for handling a message length error.
    • General IE - Repeat Information Element - these test cases verify the IUT's functionality for handling duplicate information elements (IEs).
    • Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of missing mandatory IE, mandatory IEs with length errors and mandatory IEs with content error.
    • Non-Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of messages containing unrecognized IEs.
    • Status Message Inquiry - these test cases verify the IUT's functionality for status inquiry procedures.
  • Timers - this test group of test cases verify the IUT's functionality for network side timer implementation.
  • LIJ Procedure - these test cases verify the IUT's functionality for Leaf Initiated Join procedures.