LM6. Establish a LAP connection. Send a connect request from two different SLSAPs to a single DLSAP. DUT should respond with Connect Confirm for each request. Transfer data on each unique connection. Test is only valid if the DUT support multiple connections to a single LSAP. DUT should respond with a disconnect if the maximum number of connections is exceeded..

LM7. Show that the DUT will respond with a Disconnect when an attempt is made to connect to an LSAP that is not supported.

LM8. Show that the DUT will respond with a Disconnect if a request is made to connect to an already connected LSAP(half open).

LM9. Show that the DUT will ignore a Connect Confirm to an already connected LSAP.

LM10. Show that the DUT will respond with a Disconnect if a Connect Confirm is sent to an LSAP that does not have a connection.

Reverse Data

LM11. Establish a LAP connection. Open the maximum number of unique non-IAS LSAP connections supported by the DUT. Send data to each of the open DLSAPs that will cause data to be returned. Confirm that DUT can send data on each open LSAP.

LM12. Establish a LAP connection. Open the maximum number of unique non-IAS LSAP connections supported by the DUT and the IAS. Send data to each of the open DLSAPs that will cause data to be returned. Confirm that DUT can send data on each open LSAP while IAS is open.

LM13. Establish a LAP connection. Send a connect request from two different SLSAPs to a single DLSAP. DUT should respond with Connect Confirm for each request. Transfer data on each unique connection that will cause data to be returned. Verify that data can be returned on each connection.

LM14. Confirm that zero length LM-PDU data packets do not impact LM functionality. Establish LMP connection, send 20 empty LM-PDUs. Confirm disconnect as part of the pass criteria.

LM15. Confirm that one byte length LM-PDU data packets do not impact LM functionality. Establish LMP connection, send 20 one byte (0x00 data byte) LM-PDUs. Confirm disconnect as part of the pass criteria.

LM16. Demonstrate support for LM-UData by alternately sending LM-UData frames filled with null bytes and LM-Data frames from a file. File transfer should be unaffected by UData frames.

LM Disconnect (LD Series)

LD1. Demonstrate basic LM Disconnect functionality by opening an LM connection, closing the connection and then sending a data frame to the closed connection. DUT should respond with LM-Disconnect with a 0x06 reason code.

LD2. Open two non-IAS connections. Alternately close and re-open the connections to verify that the connections can be controlled independently. Open and close each connection 4 times and verify that each connection is closed by sending a data frame. The DUT should respond with LM-Disconnect status 0x06 or 0xff for each of the closed connections.

15

LD3. Open two connections one of them IAS. Alternately close and re-open the connections to verify that the connections can be controlled independently. Open and close each connection 4 times and verify that each connection is closed by sending a data frame. The DUT should respond with LM-Disconnect status 0x06 or 0xff for each of the closed connections.

LD4. Establish simultaneous connections between a single SLSAP and multiple DLSAPs, confirm that incremental disconnects do not impact the functionality of the other connections by sending a data frame on the open connections after each disconnect.

LD5. Establish simultaneous connections between a multiple SLSAPs and a single DLSAP, confirm that incremental disconnects do not impact the functionality of the other connections by sending a data frame on the open connections after each disconnect.

LD6. Determine the impact of LMS-UserData on LM-Disconnect by establishing a connection then sending a LM-Disconnect with a zero length LMS-UserData string. Include reason code of 0x01. DUT should respond with LM-Disconnect reason 0x06 or 0xff.

LD7. Determine the impact of LMS-UserData on LM-Disconnect by establishing a connection then sending a LM-Disconnect with a 60 byte length LMS-UserData string. Include reason code of 0x01. DUT should respond with LM-Disconnect reason 0x06 or 0xff.

LD8. Determine the impact of LMS-UserData on LM-Disconnect by establishing a connection then sending a LM-Disconnect with a zero length LMS-UserData string. Repeat using each of the 8 unique reason codes defined in the protocol. Confirm that each Disconnect request was successful by sending an I frame to the closed DLSAP. DUT should respond with LM-Disconnect reason 0x06 or 0xff.

IAS (IA Series)

The following table of IAS GetValueByClass queries will be used in these test cases.

16