46 LLC and SNDCP Tests

3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS

46.1 LLC Tests

This subclause contains the test case requirements for Logical Link Control (LLC) procedures in the General Packet Radio Service (GPRS).

46.1.1 Default Conditions

The default values of LLC layer parameters are as per "Table 9: LLC layer parameter default values" in clause 8.9.8 of 3GPP TS 04.64. It is possible that the MS negotiates values different from what is given in the table. In the case where the negotiated value affects the test operation, this is noted in the test.

– The MS default initial condition is that it is GPRS attached and ciphering disabled.

Unless stated otherwise, the default conditions shall apply. NMS denotes the frames sent from the MS and NSS denotes the frames sent from the SS.

Unless stated otherwise the timer T3192 should be set to 80ms.

For all timers, a measurement tolerance of ±10 % shall be applied.

The MS may send an XID command any time. The SS shall send an XID response accepting the values proposed by the MS, unless stated otherwise in the test case.

Test cases identified in TS 51.010-2 as “EC-GSM –IoT compatible” should consider the default cells in the “Initial Conditions” to be EC-GSM-IoT cells if the test has to be executed in “EC Mode”. Otherwise the cell should be considered as a basic GPRS cell.

46.1.2 Test cases

46.1.2.1 Unacknowledged data transfer

46.1.2.1.1 Data transmission in protected mode

46.1.2.1.1.1 Conformance requirement

LLC has two modes of operation – acknowledged and unacknowledged. In the unacknowledged mode of operation, layer3 information is transmitted in numbered Unconfirmed Information (UI) frames. The UI frames are not acknowledged at the LLC layer. Neither error recovery nor reordering mechanisms is defined, but transmission and format errors are detected. Duplicate UI frames are discarded.

In the protected mode of unacknowledged operation, the FCS field protects the frame header and the information field.

Unacknowledged mode of operation is defined for all SAPIs that are not reserved.

Reference

3GPP TS 04.64, subclause 4.3.

46.1.2.1.1.2 Test purpose

To verify that the MS performs unacknowledged data transfer for SAPIs 3, 5 and 11 in the protected mode to the network

46.1.2.1.1.3 Method of test

Initial conditions

For execution counter K = 4 (GEA4) Test USIM has to be plugged into the MS
The MS shall be GPRS attached with ciphering enabled. Encryption GEA1, GEA2, GEA3 or GEA4 is used depending on the execution counter K.

Specific PICS statements:

– Supported encryption Algorithm: GEA1 (TSPC_Feat_GEA1)

– Supported encryption Algorithm: GEA2 (TSPC_Feat_GEA2)

– Supported encryption Algorithm: GEA3 (TSPC_Feat_GEA3)

– Supported encryption Algorithm: GEA4 (TSPC_Feat_GEA4)

PIXIT statements:

Test procedure

During GPRS attach ciphering GEA1, GEA2, GEA3 or GEA4 is activated depending on the execution counter K.

During GPRS attach and PDP context activation, the GMM messages are sent and received by the LLC layer at the MS using UI frames in the unacknowledged mode, on SAPI 1. This implicitly verifies bi-directional unacknowledged data transmission on SAPI 1.

After the PDP context is activated, the MS is made to initiate unacknowledged data transfer on SAPI 3. MS shall transmit UI frames with the E and PM bits set to 1, indicating that encryption and protection are on. Transmit 5 000 octets from the MS.

Repeat the test case for SAPIs 5 and 11.

The test is performed for all GEAx encryption algorithm supported by the MS.

Maximum duration of the test

10 minutes.

Expected sequence

The sequence is performed for execution counter K=1 when the MS supports GEA1, for K=2 when the MS supports GEA2, for K=3 when the MS supports GEA3 and for K=4 when the MS supports GEA4.

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. PDP context activation from the MS. The PDP context used here is PDP context 5.

2

Initiate data transfer of 5000 octets from the MS.

3

MS -> SS

UI frame

Verify that the number of octets in the UI frame does not exceed N201-U.

Verify that E=1 and PM=1, PD=0, C/R = 0 and the FCS is correct. Check whether the SAPI is 3, 5 or 11 when data is sent from the MS on these SAPIs.

Verify that the sequence numbers are correct and that there are no duplicate or missing frames

4

Repeat step 3 until 5000 octets are sent.

5

Repeat the test case for SAPIs 5 and 11.The PDP context used for SAPI 5 is PDP Context 8 and the one for SAPI 11 is PDP Context 9.

46.1.2.1.2 Data transmission in unprotected mode

46.1.2.1.2.1 Conformance requirement

LLC has two modes of operation – acknowledged and unacknowledged. In the unacknowledged mode of operation, layer3 information is transmitted in numbered Unconfirmed Information (UI) frames. The UI frames are not acknowledged at the LLC layer. Neither error recovery nor reordering mechanisms is defined, but transmission and format errors are detected. Duplicate UI frames are discarded.

In the unprotected mode of unacknowledged operation, the FCS field protects the frame header and the first N202 octets of the information field

Unacknowledged mode of operation is defined for all SAPIs that are not reserved.

Reference

3GPP TS 04.64, subclause 4.3.

46.1.2.1.2.2 Test purpose

To verify that the MS performs unacknowledged data transfer without protection in the correct manner, on SAPIs 5 and 9.

46.1.2.1.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

After the PDP context is activated, the MS initiates unacknowledged data transfer on SAPI 5. The MS shall transmit UI frames with the E and PM bits set to 0, indicating that encryption and protection are off.

Repeat the test case for SAPI 9.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 10.

2

Initiate unacknowledged data transfer for 5000 octets, from the MS.

3

MS -> SS

UI frame

Verify that the number of octets received at the MS in the UI frame does not exceed N201-U.

Verify that E=0 and PM=0, PD=0, C/R = 0 and the FCS is correct.

Verify that SAPI = 5 for the first run of the test case and SAPI=9 for the second run of the test case.

Verify that the sequence numbers are correct and that there are no duplicate frames.

4

MS -> SS

Repeat step 3 until data transfer is complete.

5

Repeat the test case with PDP Context 6. This will use SAPI 9.

46.1.2.1.3 Reception of I frame in ADM

46.1.2.1.3.1 Conformance requirement

The DM unnumbered response shall be used by an LLE to report to its peer entity that the LLE is in a state such that ABM operation cannot be performed. An LLE shall transmit a DM response to any valid command received that it cannot action.

No information field is permitted within the DM response.

Reference

3GPP TS 04.64, clause 6.4.1.4.

46.1.2.1.3.2 Test purpose

To verify that the MS sends a DM response if an I frame is received while in unacknowledged mode.

46.1.2.1.3.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

After sending data to the MS in unacknowledged mode, send an I frame from the SS. The MS shall send a DM response to indicate that it cannot perform an ABM operation.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 1.

2

Initiate unacknowledged data transfer for 2000 octets, from the SS.

3

SS -> MS

UI frame

4

Repeat step 3 until 1500 octets are transmitted.

5

SS -> MS

I frame

Send an I Command frame (C/R bit set to 1) from the SS

6

MS -> SS

DM response

Verify that the MS sends a DM response with F = 0.

7

Repeat step 3 until all 2000 octets are transmitted. The MS must not send anymore DM frames.

46.1.2.2 Acknowledged data transfer

46.1.2.2.1 Link establishment
46.1.2.2.1.1 Link establishment from MS to SS

46.1.2.2.1.1.1 Conformance requirement

In the acknowledged operation, layer 3 information is transmitted in numbered Information (I) frames. The I frames are acknowledged at the LLC layer. Error recovery and reordering procedures based on retransmission of unacknowledged I frames are specified.

Acknowledged operation requires that ABM operation has been initiated by an establishment procedure using the Set Asynchronous Balanced Mode (SABM) command.

Acknowledged operation is allowed for all SAPIs that are not reserved except SAPIs 1 and 7 for Release 97-98 and 1, 2, 7 and 8 for Release 99.

Reference

3GPP TS 04.64, subclauses 4.4 and 8.5.2.

46.1.2.2.1.1.2 Test purpose

To test the establishment of acknowledged mode data transfer from the MS to the SS.

46.1.2.2.1.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate acknowledged data transfer from the MS on SAPI 3. Verify that the MS establishes a link before initiating data transfer.

Initiate data transfer from the MS and ensure that the data sent from the MS is received at the SS.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context11.

2

MS -> SS

SABM

Verify that P/F =1.

3

SS -> MS

UA

Send UA from the SS before T200 can expire at the MS.

Verify that the MS does not resend SABM.

4

Initiate data transfer of 5000 octets from the MS.

5

MS -> SS

I + S

6

SS -> MS

RR

Acknowledge whenever requested by the MS. Ensure that the MS does not retransmit the data.

7

Repeat steps 5 and 6 until data transfer is completed

46.1.2.2.1.2 Link establishment from SS to MS

46.1.2.2.1.2.1 Conformance requirement

In the acknowledged operation, layer 3 information is transmitted in numbered Information (I) frames. The I frames are acknowledged at the LLC layer. Error recovery and reordering procedures based on retransmission of unacknowledged I frames are specified.

Acknowledged operation requires that ABM operation has been initiated by an establishment procedure using the Set Asynchronous Balanced Mode (SABM) command.

Acknowledged operation is allowed for all SAPIs that are not reserved except SAPIs 1 and 7.

An LLE shall initiate a request for release of the ABM operation by transmitting a DISC command with the P bit set to 1.

An LLE receiving a DISC command while in ABM state shall transmit a UA response with the F bit set to the same binary value as the P bit in the received DISC command.

Reference

3GPP TS 04.64, subclauses 4.4 and 8.5.2.

46.1.2.2.1.2.2 Test purpose

To test the establishment and release of acknowledged mode data transfer from the SS to the MS.

46.1.2.2.1.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate PDP context activation from the MS . Do a PDP context modification from the SS, which will make the SS initiate a link establishment.

Initiate acknowledged data transfer from the SS on SAPI 9. Verify that the MS responds with a UA.

Initiate data transfer from the SS and ensure that the data sent from the SS is received at the MS.

Terminate data transfer from the SS.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context 10.

2

{PDP Context Modification}

Macro. Initiate PDP context modification from the SS using PDP Context 12.

3

SS -> MS

SABM

Send SABM with P/F = 1.

4

MS -> SS

UA

Verify that UA is received before the T200 timer at the SS expires.

5

Initiate data transfer of 2000 octets from the SS.

6

SS -> MS

I + S

Set the A bit to 1 in each I+S frame.

A7(optional step)

MS -> SS

RNR

The MS can send an RNR. Stop data transmission until the MS sends an RR.

7

MS -> SS

RR

Verify that the MS sends an RR for each frame.

8

Repeat steps 6 and 7 until 2000 octets are sent.

9

SS -> MS

DISC

Send DISC from the SS.

10

MS -> SS

UA

46.1.2.2.1.3 Loss of UA frame

46.1.2.2.1.3.1 Conformance requirement

If timer T200 expires before the UA or DM response with the F bit set to 1 is received, the LLE shall:

– retransmit the SABM command;

– set timer T200;

– increment the retransmission counter.

Reference

3GPP TS 04.64, subclause 8.5.1.3.

46.1.2.2.1.3.2 Test purpose

To test the MS response to the loss of a UA frame during link establishment.

46.1.2.2.1.3.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate link establishment for acknowledged data transfer from the MS, for SAPI 9. When the SS receives the SABM frame, do not send a response.

After the MS sends another SABM, respond with a UA from the SS and send some frames from the SS to ensure that the link is established.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP context 12.

2

MS -> SS

SABM

Verify that P/F = 1.

3

MS -> SS

SABM

Do not send UA from the SS.

Verify that MS sends another SABM with P/F = 1 after T200 seconds, with the same SAPI that it sent in the first SABM.

4

SS -> MS

UA

Send UA from the SS before T200 for that SAPI expires at the MS.

5

Initiate sending 5 I+S frames from the SS.

6

SS -> MS

I+S

Set the A bit to 1 in all the I+S frames.

A7 (optional step)

MS -> SS

RNR

The MS may send an RNR. If it does, stop transmitting from the SS until the MS sends an RR.

7

MS -> SS

RR

Verify that the MS receives and acknowledges all the frames by sending an RR for each I+S frame received.

8

Repeat steps 6 and 7 until 5 I+S frames are sent from the SS.

46.1.2.2.1.4 Total loss of UA frame

46.1.2.2.1.4.1 Conformance requirement

If timer T200 expires before the UA or DM response with the F bit set to 1 is received, the LLE shall:

– retransmit the SABM command;

– set timer T200;

– increment the retransmission counter.

Reference

3GPP TS 04.64, subclause 8.5.1.3.

46.1.2.2.1.4.2 Test purpose

To verify that:

– the MS attempts to establish a link N200 times after sending the first SABM.

46.1.2.2.1.4.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate link establishment from the MS by sending a SABM frame, for SAPI 11. At the SS, ignore the SABM from the MS.

The MS shall wait for time-out of timer T200 and then send a new SABM frame.

At the SS, ignore the SABM frame sent by the MS. Wait until the MS sends N200 + 1 SABM frames in all.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS, using PDP Context 13.

2

MS -> SS

SABM

Verify that P/F = 1, SAPI = 11.

3

MS -> SS

SABM

Do not send UA from the SS.

Verify that MS sends another SABM with P/F = 1 after T200 seconds, with the same SAPI that it sent in the first SABM .

4

Perform step 3 N200 times.

Ensure that the MS sends N200 + 1 SABM frames in step 2 and steps 3 only.

46.1.2.2.1.5 DM response

46.1.2.2.1.5.1 Conformance requirement

The DM unnumbered response shall be used by an LLE to report to its peer that the LLE is in such a state that ABM operation cannot be performed.

Upon reception of the DM response with the F bit set to 1, the originator of the SABM command shall enter the ADM state.

If the originator of the establishment procedure receives an LL‑RELEASE.indication with Cause "DM received", it shall inform the SM sub-layer using the SNSM-STATUS.request primitive with Cause "DM received". SM shall then deactivate all PDP contexts for that SAPI requiring acknowledged peer-to-peer LLC operation.

Reference

3GPP TS 04.64, subclauses 6.4.1.4 and 8.5.1.2.

3GPP TS 04.65, subclause 6.2.1.4.

46.1.2.2.1.5.2 Test purpose

To verify that a link is not established with the MS when a DM response is sent in response to a SABM command.

46.1.2.2.1.5.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate PDP context activation from the MS on SAPI 3. From the SS, send a DM with the F bit set to 1.

Verify that the MS deactivated the PDP Context.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation using PDP Context 11.

2

MS -> SS

SABM

Verify that P/F =1 in the SABM sent from the MS.

3

SS -> MS

DM

Send DM with F=1 from the SS before T200 can expire at the MS.

Wait for 2 * T200 seconds after the transmission of DM and verify that the MS does not resend SABM in this period.

4

{PDP Context De-Activation}

Verify that the MS initiates PDP Context Deactivation. MS may initiate this deactivation during 2*T200 sec wait given in step 3.

46.1.2.2.2 MS sends I+S frames
46.1.2.2.2.1 Checking N(S)

46.1.2.2.2.1.1 Conformance requirement

Having either transmitted the UA response to a received SABM command or received the UA response to a transmitted SABM command, I frames and supervisory frames may be transmitted and received. I frames shall be transmitted in ascending N(S) order.

When there is an opportunity to transmit a frame, then the LLE shall do one of the following in the order of priority:

– If there are any I frames marked for retransmission and if the LLE is not in the peer receive busy condition, then the LLE shall increment by 1 the retransmission count variable for the I frame with lowest send sequence number N(S). If the retransmission count variable does not exceed the value of N200, then the LLE shall retransmit the frame.

– If the LLE has a new frame to retransmit, if V(S) < V(A) + k and if the LLE is not in the peer receiver busy condition, then the new I frame shall be transmitted.

– If the LLE has an acknowledgement to transmit, then the LLE shall transmit an S frame.

Reference

3GPP TS 04.64, subclauses 8.6 and 8.6.1.

46.1.2.2.2.1.2 Test purpose

To verify that the MS handles the send sequence number N(S) correctly.

46.1.2.2.2.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate data transfer from the MS on SAPI 3. Send 515 I+S frames continuously. The value of N(S) shall begin from 0 and increment by 1 mod (512) for each frame.

Acknowledge each I frame by sending an RR frame to the MS, in sequence.

Maximum duration of the test

30 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate a PDP context activation using PDP Context 11, from the MS.

2

Initiate data transfer, from the MS.

3

MS -> SS

I+S frame

N(S) = 0 for the first frame.

4

SS -> MS

S frame with RR

Respond whenever acknowledgement is requested.

5

Repeat steps 3 and 4 until all 515 I+S frames have been transmitted from the MS. Verify that :

the MS does not retransmit any frame.

N(S) begins with 0 and is incremented by 1 mod (512).

NOTE: The application will resend data until all data have been sent.

46.1.2.2.2.2 Busy condition at the peer, with RR sent for resumption of transmission

46.1.2.2.2.2.1 Conformance requirement

The receive not ready (RNR) command shall be used by an LLE to indicate a busy condition. The value of N(R) in the RNR frame acknowledges I frames numbered up to and including N(R) – 1 . Subsequent frames, if any, shall not be considered confirmed.

After receiving a valid RNR frame, the LLE shall:

– set a peer receiver busy condition;

– not transmit or retransmit any frames to the peer LLE;

– treat the N(R) contained in the received RNR as an acknowledgement for all the I frames that have been (re‑)transmitted, up to and including N(R)- 1 and set its V(A) to the value of N(R ) contained in the RNR frame;

– set T201 to initiate the inquiry process; and

– reset the retransmission count variable.

If timer T201 expires, the LLE shall:

– if the value of the retransmission count variable is less than N200:

– transmit an appropriate supervisory frame with an A bit set to 1;

– set timer T201; and

– add one to its retransmission count variable.

The LLE receiving the supervisory frame with the A bit set to 1 shall respond, at the earliest opportunity, with an appropriate supervisory frame (see subclause 8.6.4.1) to indicate whether or not its own receiver busy condition still exists.

Upon receipt of the supervisory frame, the LLE shall reset timer T201, and:

– if the frame is an RR, ACK or SACK frame:

– the peer receiver busy condition shall be cleared;

– if timer T201 was active before the peer receiver busy condition was set, and if the associated I frame is still not acknowledged, then timer T201 shall be set and associated with the same I frame; and

– the LLE may transmit new I frames or retransmit I frames as defined in subclauses 8.6.1 or 8.6.3, respectively.

The busy peer shall respond at the earliest opportunity, with an appropriate supervisory frame.

– If the highest numbered I frame was received with N(S)=V(R), the appropriate supervisory frame is the RR frame.

Reference

3GPP TS 04.64, subclauses 6.4.3.4 and 8.6.4.

46.1.2.2.2.2.2 Test purpose

To verify that the MS:

– Handles busy condition when an RNR is sent from the SS;

– Resumes transmission upon reception of an RR.

46.1.2.2.2.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

The MS is made to send 1 I+S frame on SAPI 9.

The SS does not acknowledge the received I+S frame, when sending as response a supervisory RNR frame.

Immediately after the first RNR frame, the MS shall stop sending I+S frames and start the retransmission timer T201.

After T201 seconds, the MS shall send an RR frame with the A bit set to 1.

The SS responds with a RNR frame.

Within T201 after the second RNR frame, the SS transmit an RR frame to resume transmission.

Immediately after the RR frame, the MS shall start the retransmission of the I+S frame from the point at which it ceased to receive acknowledgement.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context 12.

Negotiate a value of at least 1 minute for T201.

2

Initiate data transfer of 1 LLC frame (<= N201-I octets) in acknowledged mode from the MS.

3

MS -> SS

I+S frame

Send 1 LLC frame (<=N201-I octets). N(S) = 0 for the first frame

4

SS -> MS

RNR frame

After sending an RNR frame with N(R) = 0 verify that the MS does not send any I + S frames during the next T201 seconds .

5

MS -> SS

RR frame

MS sends an RR frame at T201 after step 4. Verify that the A bit is set to 1.

6

SS -> MS

RNR frame

7

SS -> MS

RR

Send within T201 after step 6 an RR from the SS with N(R ) = 0

8

MS -> SS

I + S

Verify that the MS starts retransmission of the I+S frame from the point at which it had stopped sending, that is, from N(S) = 0

9

SS -> MS

RR

Acknowledge the I + S frame transmitted by the MS.

46.1.2.2.2.3 Busy condition at the peer, with ACK sent for resumption of transmission

46.1.2.2.2.3.1 Conformance requirement

The receive not ready (RNR) command shall be used by an LLE to indicate a busy condition. The value of N(R) in the RNR frame acknowledges I frames numbered up to and including N(R) – 1 . Subsequent frames, if any, shall not be considered confirmed.

After receiving a valid RNR frame, the LLE shall:

– set a peer receiver busy condition;

– not transmit or retransmit any frames to the peer LLE;

– treat the N(R) contained in the received RNR as an acknowledgement for all the I frames that have been (re‑)transmitted, up to and including N(R)- 1 and set its V(A) to the value of N(R ) contained in the RNR frame;

– set T201 to initiate the inquiry process; and

– reset the retransmission count variable.

If timer T201 expires, the LLE shall:

– if the value of the retransmission count variable is less than N200:

– transmit an appropriate supervisory frame with an A bit set to 1;

– set timer T201; and

– add one to its retransmission count variable.

The LLE receiving the supervisory frame with the A bit set to 1 shall respond, at the earliest opportunity, with an appropriate supervisory frame (see subclause 8.6.4.1) to indicate whether or not its own receiver busy condition still exists.

Upon receipt of the supervisory frame, the LLE shall reset timer T201, and:

– if the frame is an RR, ACK or SACK frame:

– the peer receiver busy condition shall be cleared;

– if timer T201 was active before the peer receiver busy condition was set, and if the associated I frame is still not acknowledged, then timer T201 shall be set and associated with the same I frame; and

– the LLE may transmit new I frames or retransmit I frames as defined in subclauses 8.6.1 or 8.6.3, respectively.

The busy peer shall respond at the earliest opportunity, with an appropriate supervisory frame.

– If the highest numbered frame was received with N(S) = V(R ) +1, the appropriate frame is the ACK frame.

Reference

3GPP TS 04.64, subclauses 6.4.3.4 and 8.6.4.

46.1.2.2.2.3.2 Test purpose

To verify that the MS:

– Handles busy condition when an RNR is sent from the SS;

– Resumes transmission upon reception of an ACK.

46.1.2.2.2.3.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

The MS is made to send I+S frames continuously on SAPI 9. The SS acknowledges the received I+S frames with supervisory RR frames.

After receiving the last transmitted frame, the SS responds with a supervisory RNR frame. The RNR frame will indicate that all frames except the one before and the last one have been received.

Immediately after the first RNR frame, the MS shall stop sending I+S frames and start the retransmission timer T201.

After T201 seconds, send an ACK frame from the SS, which acknowledges the last received I+S frame.

Immediately after the ACK frame, the MS shall retransmit the unacknowledged frame N(S)=NMS-2.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. PDP context activation from the MS with PDP Context 12. If the mobile negotiates a window size kU less than 3, this test shall end at this step.

2

Initiate acknowledged mode data transmission from the MS.

3

MS -> SS

I+S frame

N(S)=0 for the first frame

4

SS -> MS

RR frame

Acknowledge when requested.

5

Repeat steps 3 and 4. The N(S) of the frames shall range from N(S) = 0 until N(S) = NMS -3 mod 512.

6

MS -> SS

I+S frames

The MS sends the I+S frames with N(S) = NMS -2 and N(S) = NMS – 1

7

SS -> MS

RNR frame

After sending RNR frame with N(R) = NMS – 2 mod 512, wait for T201 seconds at the SS.

7a

(Optional)

MS -> SS

I+S frames

MS may send few I+S frames before the RNR frame is received completely at the mobile. SS does not acknowledge them.

8

MS -> SS

RR frame

MS sends an RR frame after T201 times out.

9

SS -> MS

RNR frame

10

SS -> MS

ACK

Send an ACK from the SS with N(R ) = NMS – 2 mod 512 within T201 after step 9.

11

MS -> SS

I + S frame

Verify that the MS sends an I+S frame with N(S) = NMS – 2 mod 512.

12

SS -> MS

RR

Acknowledge all the frames transmitted by the MS so far with N(R) = NMS.

46.1.2.2.2.4 SACK frame

46.1.2.2.2.4.1 Conformance requirement

On receipt of a valid SACK frame, the LLE shall consider all I frames with the corresponding bit set to 1 in the SACK bitmap as acknowledged.

Reference

3GPP TS 04.64, subclause 8.6.3.2.

46.1.2.2.2.4.2 Test purpose

To verify that the MS considers only the frames as indicated by the SACK bitmap have been received correctly and that it retransmits the frames that have not been acknowledged.

46.1.2.2.2.4.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

NMS >= 1.

Initiate data transfer from the MS and send frames from N(S) = 0 to N(S) = NMS , where NMS= kU ‑ 1.

If NMS is even, do not acknowledge an arbitrarily chosen sequence of NMS/2 frames and acknowledge the other frames by using SACK.

If NMS is odd, do not acknowledge an arbitrarily chosen sequence of (NMS -1)/2 frames and acknowledge the other frames by using SACK.

Verify that the MS retransmits the not-acknowledged frames.
Acknowledge the retransmitted frames.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. PDP context activation from the MS with PDP Context 11.

If the mobile negotiates a window size kU less than 2, this test shall end at this step.

2

Initiate acknowledged mode data transfer from the MS.

3

MS -> SS

I+S frames

N(S) = 0 for the first frame

4

Repeat step 3, with N(S) incremented by 1 for each step. These must be repeated until an I+S frame with the A bit set to 1 is received at the SS and at least NMS +1 I+S frames were transmitted.

5

SS -> MS

SACK

If NMS is even, do not acknowledge an arbitrarily chosen sequence of NMS /2 frames and acknowledge the other frames by using SACK.

If NMS is odd, do not acknowledge an arbitrarily chosen sequence of (NMS -1)/2 frames and acknowledge the other frames by using SACK.

6

MS -> SS

I+S frames

Verify that the MS retransmits the not acknowledged frames.

7

SS -> MS

RR

Acknowledge all the frames. N(R) = NMS + 1

46.1.2.2.3 Reception of I + S frames at the MS
46.1.2.2.3.1 Checking N(R)

46.1.2.2.3.1.1 Conformance requirement

Whenever an LLE receives a frame with the A bit set to 1, it shall transmit an I+S or S frame.

In ABM mode, all I frames and Supervisory frames contain N(R), the expected send sequence number of the next in-sequence received I frame. At the time that a frame of the above type is designated for transmission, the value of N(R) is equal to the value of the receive state variable V(R). N(R) indicates that the LLE transmitting the N(R) has correctly received all I frames numbered up to and including N(R) – 1.

Reference

3GPP TS 04.64, subclauses 6.3.5.4.5 and 8.6.3.1.

46.1.2.2.3.1.2 Test purpose

To verify that the MS transmits acknowledgements with the correct N(R).

46.1.2.2.3.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Send I+S frames continuously from the SS. Send more than 512 frames. The delay between two I+S frames should be less than T201.

Do not send any data from the MS.

When the MS sends RR frames, check the value of N(R) to verify that it indicates that all frames sent from the SS has been acknowledged.

Maximum duration of the test

30 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context 11.

2

Initiate acknowledged mode data transfer from the SS.

3

SS -> MS

I+S frame

4

SS -> MS

I+S frame

The last I+S frame shall have its N(S ) = NSS + i mod 512. Set the A bit to 1 in the last frame of each window and the last frame sent from the SS.

A5 (optional step)

MS -> SS

RR

Verify whether the RR frames received from the MS have the correct N(R) values. Verify whether all the I+S frames sent from the SS have been acknowledged.

B5 (optional step)

MS -> SS

RNR

The SS shall wait for an RR frame before it sends the next I+S frame.

The MS may not send an RR if the A bit is not set in step 4.

6

Repeat from step 4 515 times.

7

At the end of the test, all the frames sent shall have been acknowledged.

46.1.2.2.3.2 MS handling busy condition during bi-directional data transfer

46.1.2.2.3.2.1 Conformance requirement

The receive not ready (RNR) command shall be used by an LLE to indicate a busy condition. The value of N(R) in the RNR frame acknowledges I frames numbered up to and including N(R) – 1. Subsequent frames, if any, shall not be considered confirmed.

After receiving a valid RNR frame, the LLE shall:

– set a peer receiver busy condition;

– not transmit or retransmit any frames to the peer LLE;

– treat the N(R) contained in the received RNR as an acknowledgement for all the I frames that have been (re‑)transmitted, up to and including N(R)- 1 and set its V(A) to the value of N(R ) contained in the RNR frame;

– set T201 to initiate the inquiry process; and

– reset the retransmission count variable.

The busy peer shall respond at the earliest opportunity, with an appropriate supervisory frame.

– If the highest numbered frame was received with N(S) = V(R ) +1, the appropriate frame is the ACK frame.

Reference

3GPP TS 04.64, subclauses 6.4.3.4 and 8.6.4.

46.1.2.2.3.2.2 Test purpose

To verify that the MS handles peer receiver busy condition when it is transmitting to the SS and receiving data from the SS.

46.1.2.2.3.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Send 1 I+S frame (<=N201-I octets) from the MS.

Send 1 I+S frame from the SS, containing 1 octet of data.

Send an RNR from the SS to indicate receiver busy condition, after 1 frame (N(S) = 0) has been received at the SS. The N(R) value that is sent in the RNR frame is 0.

Verify that the MS stops transmission of I+S frames.

T201 seconds after sending the RNR frame, send an RR frame from the SS with N(R) = 0 to request the MS to resume transmission.

Verify that the MS resumes transmission. The frame sent from the MS should have its N(S) = 0.

Verify that the MS sends acknowledgements for all the I+S frames transmitted from the SS.

Maximum duration of the test

10 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context 12.

2

Initiate acknowledged mode data transfer of 1 LLC frame (<= N201-I octets)from the MS and the SS.

3

MS -> SS

I+S frame

N(S) =0 for the first frame

4

SS -> MS

I+S frame

A bit set to 1.

5

SS -> MS

RNR frame

Do not acknowledge the first I+S frame received at the SS. N(R) = 0.

A6 (optional step)

MS -> SS

RNR frame

The MS may repeat this step In this case, the MS shall send an RR frame for resumption of transmission.

6

MS -> SS

RR

Acknowledgement to the I+S frame sent in step 4.

This could have been sent by the MS already directly after step 4.

7

MS -> SS

RR

Verify that the MS sends this after T201 seconds after step 5. The MS shall not resend the I+S frame sent in step 3.

8

SS -> MS

RR

N(R) = 0. Send this to resume transmission from the MS.

9

MS -> SS

I+S

Verify that the MS – resends the I+S frame sent in step 3.

10

SS -> MS

RR

Acknowledge the frame transmitted by the MS.

46.1.2.2.3.3 SACK frame

46.1.2.2.3.3.1 Conformance requirement

The SACK supervisory frame shall be used by an LLE to acknowledge single or multiple frames. Frames up to and including N(R) – 1, and frames indicated by the SACK bitmap, have been received correctly.

If the LLE is in the own receiver busy condition, the appropriate supervisory frame is the RNR frame. Otherwise, if the highest numbered frame was received with N(S) = V(R), the appropriate supervisory frame is the RR frame. Otherwise, if the highest numbered I frame was received with N(S) = V(R) + 1, the appropriate supervisory frame is the ACK frame. Otherwise, the appropriate supervisory frame is the SACK frame.

Reference

3GPP TS 04.64, subclauses 6.4.3.3 and 8.6.4.1.

46.1.2.2.3.3.2 Test purpose

To verify whether the MS sends a SACK frame when it is required and that the SACK frame has the correct bits set.

46.1.2.2.3.3.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

NMS = 20, for this test case.

Initiate data transfer from the SS and send frames from N(S) = 0 to N(S) = NMS – 3. The A bit shall be set to 1 for all frames sent. Wait till all the frames are acknowledged. Send the frame with N(S) = NMS with the A bit set to 1..Verify that the MS acknowledges all the frames until NMS – 3 using RR and negatively acknowledges the other frames (NMS -2 and NMS-1) by using SACK. Retransmit the frames NMS –2 and NMS – 1 with A bit set to 1. Verify that the MS acknowledges the retransmitted frames.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation with PDP Context 12. If the negotiated window size is less than 3, the test shall end at this step.

2

Initiate acknowledged mode data transfer from the SS.

3

SS -> MS

I+S frame

N(S) = 0 for the first frame, A bit = 1.

A4 (Optional step)

MS -> SS

RNR frame

The MS can optionally send an RNR frame. If it does, do not send data until the MS sends an RR.

4

MS -> SS

RR frame

N(R) = 1 for the first frame

5

Repeat steps 3 and 4 with the N(S) and N(R) values incremented by 1 for each step and with A =1 for the I+S frame . The last RR frame shall have its N(R ) = NMS – 2.

6

SS -> MS

I+S frame

Send with N(S) = NMS , A bit = 1.

A7 (Optional step)

MS -> SS

RNR

N( R) = NMS –2. In this case the SS shall not transmit anything until the MS sends a SACK.

7

MS -> SS

SACK

Verify that the MS does not acknowledge the frames NMS – 2 and NMS – 1and acknowledges the other frames (NMS) using SACK.

8

SS -> MS

I+S frame

Retransmit the frame NMS – 2 with A bit = 1.

A9 (Optional step)

MS -> SS

RNR

In this case, the SS shall not transmit anything until the MS sends an ACK.

9

MS -> SS

ACK

10

SS -> MS

I+S

N(S) = NMS – 1, A bit = 1.

A11

MS -> SS

RR

N(R)=NMS+1

B11

MS -> SS

RNR

The RNR shall indicate that the MS has received all the frames sent from the SS. N(R)=NMS+1

46.1.2.2.3.4 ACK frame

46.1.2.2.3.4.1 Conformance requirement

Whenever an LLE receives a frame with the A bit set to 1, it shall transmit an I+S or S frame.

The ACK supervisory frame shall be used by an LLE to acknowledge a single or multiple I frames. Frames up to and including N(R) – 1, and frame N(R) + 1, have been received correctly.

Reference

3GPP TS 04.64, subclauses 6.4.3.2 and 8.6.3.1.

46.1.2.2.3.4.2 Test purpose

To verify that the MS transmits an ACK frame when frames up to and including N(R) – 1 and frame N(R) + 1 have been received correctly.

46.1.2.2.3.4.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

For this test case, NSS= 20.

Send I+S frames with N(S) = 0 to N(S) = NSS -2 from the SS. The delay between two I+S frames should be less than T201. Set the A bit to 1 in frames 0 to NSS – 2. Verify that the MS sends an RR frame as acknowledgement for these frames. Send the frame with A=1. Do not send frame NSS – 1. Verify that the MS sends an ACK frame, indicating that NSS and NSS – 2 have been received and that NSS – 1 has not been received. Now send a frame from the SS with N(S) = NSS – 1, with A=1. Verify that the MS acknowledges all the frames received so far, including this frame, with an RR.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation with PDP Context 13.

2

Initiate acknowledged mode data transmission from the SS.

3

SS -> MS

I+S frame

A = 1

A4 (Optional step)

MS -> SS

RNR

If the MS sends an RNR, do not transmit data until it has sent an RR.

4

MS -> SS

RR

5

Repeat steps 3 to 5 until frames 0 to NSS –2 have been sent.

Verify that RR frames are sent to acknowledge frames from N(S) = 0 until N(S) = NSS – 2.

6

SS -> MS

I+S frame

Send the frame NSS with A=1. Do not send the frame with N(S) = NSS – 1.

A7 (Optional step)

MS -> SS

RNR

N(R) = NSS – 2. If the MS sends an RNR, do not transmit data until it sends an ACK.

7

MS -> SS

ACK

Verify that an ACK frame is sent to acknowledge the frames NSS –2 and NSS , with N(R) = NSS –1

8

SS -> MS

I+S frame

N(S) = NSS – 1, with A=1.

A9 (Optional step)

MS -> SS

RNR

Verify that N(R) = NSS + 1

9

MS -> SS

RR

Verify that an RR frame is received to acknowledge frame NSS – 1 with N(R) = NSS + 1

46.1.2.2.4 Link Reestablishment
46.1.2.2.4.1 Reestablishment due to reception of SABM

46.1.2.2.4.1.1 Conformance requirement

The criteria for re-establishing the ABM mode of operation are defined in this clause by the following conditions:

– the receipt, while in the ABM state, of a SABM;

– the receipt of an LL-ESTABLISH-REQ primitive from layer 3;

– the occurrence of N200 retransmission failures;

– the occurrence of a frame rejection condition; and

– the receipt of an unsolicited DM response with F bit set to 0 while in ABM state.

In Asynchronous Balanced Mode, only I frames contain N(S), the send sequence number of transmitted I frames. At the time that an in-sequence I frame is designated for transmission, the value of N(S) is set equal to the value of the send state variable V(S).

An LLE receiving a SABM command, if it is able to enter the ABM state, shall:

– inform layer 3 using the LL-ESTABLISH-IND primitive;

– if the received SABM command contains a Layer-3 Parameters XID parameter, wait for the receipt of an LL-ESTABLISH-RES primitive from layer 3;

– respond with a UA response with the F bit set to the same binary value as the P bit in the received SABM command (i.e., F=1);

– reset timer T200 if active;

– set V(S), V(R), V(A), and B to 0;

– enter the ABM state;

– clear all existing exception conditions; and

– clear any existing peer receiver busy condition.

Reference

3GPP TS 04.64, subclauses 8.7.1, 6.3.5.4.3 and 8.5.1.2.

46.1.2.2.4.1.2 Test purpose

To verify whether the MS initiates reestablishment of the link if it receives a SABM while in ABM state.

46.1.2.2.4.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

After establishing a link, initiate data transfer from the MS . After receiving 1frame from the MS, send a SABM from the SS and verify whether the MS responds with a UA. After the link is re-established, verify that the MS resumes data transmission.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context establishment from the MS, using PDP Context 12. Negotiate kU = 1.

2

Initiate acknowledged mode data transfer of 2000 octets from the MS.

3

MS -> SS

I + S

4

SS -> MS

RR

Acknowledge one frame.

5

MS -> SS

I + S

N(S) = 1.

6

SS -> MS

SABM

After receiving 2 frame from the MS, send a SABM from the SS to re-establish the link.

7

MS -> SS

UA

Verify that the MS responds with a UA.

8

MS -> SS

I+S

Verify that that N(S) begins from 0.

9

SS -> MS

RR

Acknowledge the frame sent from the MS.

10

Repeat steps 8 and 9 until all the frames from the MS are transmitted.

46.1.2.2.4.2 Reestablishment due to N200 failures

46.1.2.2.4.2.1 Conformance requirement

The criteria for re-establishing the ABM mode of operation are defined in this clause by the following conditions:

– the receipt, while in the ABM state, of a SABM;

– the receipt of an LL-ESTABLISH-REQ primitive from layer 3;

– the occurrence of N200 retransmission failures;

– the occurrence of a frame rejection condition; and

– the receipt of an unsolicited DM response with F bit set to 0 while in ABM state.

In case of a re-establishment, all NSAPIs mapped to the affected SAPI shall enter the recovery state and all buffered N-PDUs (i.e. the ones whose complete reception has not been acknowledged and the ones that have not been transmitted yet) shall be transmitted starting with the oldest N-PDU when the link is re-established

Reference

3GPP TS 04.64, clause 8.7.1.

3GPP TS 04.65, subclauses 5.1.2.3, 5.1.2.5 and 6.2.1.2.

46.1.2.2.4.2.2 Test purpose

To verify whether the MS initiates reestablishment of the link when there is an N200 retransmission failure.

46.1.2.2.4.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

After establishing a link, initiate data transfer from the MS, to send 1 LLC frame (<=N201-I octets). Do not acknowledge the data frame sent from the SS. The MS shall retransmit the frame N200 times. Wait for (N200 * T201) seconds and see if the MS initiates link reestablishment by sending a SABM. After the link is re-established verify that the MS resumes data transmission.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP context 11.

2

Initiate acknowledged mode data transfer from the MS.

3

MS -> SS

I + S

Send 1 LLC frame (<= N201-I octets). Do not acknowledge this frame from the SS

4

MS -> SS

I + S

Verify that the MS retransmits the I+S frame N200 times and that it does not send any SABM frames during retransmission. SS does not acknowledge any of these frames.

5

MS -> SS

SABM

Verify that the MS sends a SABM and that it stops sending anymore data to the SS. Verify that this occurs after T201 seconds after the last I+S frame in step 4.

6

SS -> MS

UA

7

MS -> SS

I+S

Verify that the MS resumes transmission of data from step 2.

8

SS -> MS

RR

Acknowledge the frame transmitted from the MS.

46.1.2.2.4.3 Reestablishment due to reception of DM

46.1.2.2.4.3.1 Conformance requirement

The criteria for re-establishing the ABM mode of operation are defined in this clause by the following conditions:

– the receipt, while in the ABM state, of a SABM;

– the receipt of an LL-ESTABLISH-REQ primitive from layer 3;

– the occurrence of N200 retransmission failures;

– the occurrence of a frame rejection condition; and

– the receipt of an unsolicited DM response with F bit set to 0 while in ABM state.

In case of a re-establishment, all NSAPIs mapped to the affected SAPI shall enter the recovery state and all buffered N-PDUs (i.e. the ones whose complete reception has not been acknowledged and the ones that have not been transmitted yet) shall be transmitted starting with the oldest N-PDU when the link is re-established.

Reference

3GPP TS 04.64, subclause 8.7.1.

3GPP TS 04.65, subclauses 5.1.2.3, 5.1.2.5 and 6.2.1.2.

46.1.2.2.4.3.2 Test purpose

To verify whether the MS initiates reestablishment of the link if it receives a DM while in ABM state.

46.1.2.2.4.3.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

After establishing a link, initiate data transfer from the MS . After receiving 3 frames from the MS, send a DM with F=0 from the SS and verify whether the MS responds with a SABM. After the link is re-established, verify that the MS resumes data transmission.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS, using PDP context 12.

2

Initiate acknowledged mode data transfer of 8000 octets from the MS.

3

MS -> SS

I + S

4

SS -> MS

RR

Send RR frames as acknowledgements from the SS.

5

Repeat steps 3 and 4 once.

6

MS -> SS

I+S

7

SS -> MS

DM

Send a DM with the F bit set to 0 from the SS.

Discard all the I+S frames received at the SS.

8

MS -> SS

SABM

Verify that the MS re-establishes the link with a SABM

9

SS -> MS

UA

Respond with a UA

10

MS -> SS

I+S

Verify that the MS resumes data transmission , with N(S) set to 0, only for the first frame sent after resumption of transmission.

11

SS -> MS

RR

Acknowledge all frames sent from the MS.

12

Repeat steps 10 and 11 until all the frames from the MS are transmitted.

46.1.2.3 Collision of commands and responses

46.1.2.3.1 Collision of SABM

46.1.2.3.1.1 Conformance requirement

If the transmitted and received unnumbered commands are SABM commands and a Layer-3 Parameters XID parameter is present in both or in neither, then the SABM command transmitted by the SGSN shall be ignored and treated as not transmitted. The LLE in the SGSN shall send the UA response at the earliest possible opportunity if it is able to enter ABM.

Reference

3GPP TS 04.64 subclause 8.5.5.1

46.1.2.3.1.2 Test purpose

To verify that the MS ignores a SABM command received from the SS when it (the MS) is waiting for a UA response, when a Layer-3 Parameters XID parameter is present in both.

46.1.2.3.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate link establishment from the MS by sending a SABM with Layer-3 Parameters XID parameter present. Upon reception of the SABM at the SS, send a SABM with Layer-3 Parameters XID parameter present. Verify that the MS ignores the SABM sent by the SS. Wait for T200 seconds at the SS after receiving the SABM from the MS see if the MS resends the SABM. After reception of the SABM, respond with a UA. Initiate data transmission from the MS. Acknowledge all the frames sent from the MS.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS with PDP Context 11.

2

MS -> SS

SABM

Verify that P/F = 1. A layer-3 XID parameter shall be present in the SABM received from the MS.

3

SS -> MS

SABM

Send a SABM with P/F =1 to simulate collision. Send the SABM from the SS with a layer 3 XID parameter.

4

MS -> SS

SABM

Ensure that the MS resends the SABM.

5

SS -> MS

UA

Send UA from the SS before T200 can expire at the MS.

6

MS -> SS

I + S

Initiate data transfer from the MS.

7

SS -> MS

RR

Send a supervisory frame as acknowledgement. Wait for T201 seconds to ensure that the MS does not retransmit the data.

46.1.2.3.2 Collision of SABM and DISC

46.1.2.3.2.1 Conformance requirement

If the transmitted and received unnumbered commands are a SABM and DISC command, the LLEs shall issue a DM response at the earliest possible opportunity. Upon receipt of a DM response with the F bit set to 1, the LLE shall enter the ADM state and notify layer3 by means of the appropriate primitive.

Reference

3GPP TS 04.64, subclauses 8.5.5.2 and 8.5.4.

46.1.2.3.2.2 Test purpose

To verify that when the MS receives a DISC after sending a SABM, it shall send a DM response to the SS. Upon reception of a DM response, it shall enter the ADM state.

46.1.2.3.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate link establishment from the MS by sending a SABM command. Send a DISC command in response to this from the SS. Verify that the MS sends a DM and upon reception of a DM from the SS, it enters the ADM state. The MS might try to re-establish ABM directly, or after sending numbered frames from the SS verify that the MS does not acknowledge them and answers with a DM.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context 12.

2

MS -> SS

SABM

Verify that P/F = 1

3

SS -> MS

DISC

Send DISC from the SS before T200 can expire at the MS.

4

MS -> SS

DM

5

SS -> MS

DM

Send DM with F=1

Branch A, B or C is executed

A6

(Optional)

MS -> SS

DEACTIVATE PDP CONTEXT REQUEST

MS may deactivate the PDP context

A7

(Condi-tional)

SS -> MS

DEACTIVATE PDP CONTEXT ACCEPT

B6

(Optional)

MS -> SS

SABM

The MS may try to re-establish ABM.

C6 (Optional

)

SS -> MS

I+S

Send an I+S Command ( C/R bit set to 1)frame from the SS.

C7

(Condi-tional)

MS -> SS

DM

The MS shall send a DM as response to the I+S frame with the F bit set to 0.

46.1.2.3.3 Collision of SABM and XID commands

46.1.2.3.3.1 Conformance requirement

If the transmitted unnumbered command is a SABM command and the received unnumbered command is an XID command, then the LLE shall ignore the received XID command.

Reference

3GPP TS 04.64 subclause 8.5.5.2.

46.1.2.3.3.2 Test purpose

To verify that the MS ignores the XID command if it collides with a SABM command.

46.1.2.3.3.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

When the MS initiates link establishment using a SABM, send an XID command. Verify that the XID command is ignored.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context 12.

2

MS -> SS

SABM

Verify that P/F = 1.

3

SS -> MS

XID

Send an XID command without layer3 parameters.

4

MS -> SS

SABM

Ensure that the MS does not send an XID response and resends the SABM.

5

SS -> MS

UA

Send UA from the SS before T200 can expire at the MS.

Wait for T200 seconds after the transmission of UA to ensure that the MS does not send an XID response.

46.1.2.4 Unsolicited response frames

46.1.2.4.1 Unsolicited DM

46.1.2.4.1.1 Conformance requirement

When a DM response with the F bit set to 0 is received by an LLE, a collision between a transmitted SABM or DISC command and the unsolicited DM response may have occurred.

A DM response with the F bit set to 0 colliding with a SABM or DISC shall be ignored.

An LLE shall ignore a DM response received with F=0 when it is in the Local Establishment state.

Reference

3GPP TS 04.64 subclauses 8.5.6 and 8.8.4.

46.1.2.4.1.2 Test purpose

To verify that the MS ignores a DM response sent with F=0 when LLC is in the Local Establishment state.

46.1.2.4.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Send SABM with P/F =1 from the MS to establish a link. Send a DM response with F=0 from the SS, in response to this. Verify that the MS ignores this DM response and sends SABM after expiry of T200. Respond with UA from the SS after receiving SABM. Send 1 I+S frame from the SS and verify that the MS acknowledges it.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS with PDP Context 11.

2

MS -> SS

SABM

Initiate data transfer from the MS. Verify that P/F = 1.

3

SS -> MS

DM

Send a DM response with F=0

4

MS -> SS

SABM

Ensure that the second SABM is sent.

5

SS -> MS

UA

Send UA from the SS before T200 expires at the MS.

6

SS -> MS

I+S frame

Send one I+S frame from the SS.

A7 (Optional step)

MS -> SS

RNR

Verify that the RNR acknowledges the frame transmitted in step 6.

7

MS -> SS

RR frame

Verify that the MS acknowledges the I+S frame transmitted from the SS.

46.1.2.5 FRMR frames

46.1.2.5.1 Sending FRMR due to undefined command control field

46.1.2.5.1.1 Conformance requirement

The FRMR unnumbered response may be received by an LLE as a report of a frame rejection condition not recoverable by retransmission of the identical frame:

– receipt of a command or response control field that is undefined or not implemented;

– receipt of a supervisory or unnumbered frame with incorrect length; or

– receipt of an I frame with an information field that exceeds the maximum established length.

Upon occurrence of a frame rejection condition, the LLME shall issue an LLGMM-STATUS-IND primitive; and the LLE shall:

– discard the frame causing the frame rejection condition;

– transmit a FRMR response frame; and

– if the LLE is in ABM operation, initiate re-establishment.

Reference

3GPP TS 04.64, subclauses 6.4.1.5 and 8.8.2.

46.1.2.5.1.2 Test purpose

To verify that if the MS receives a frame with a command control field that is not implemented, it sends an FRMR frame and re-establishes the link.

46.1.2.5.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

After establishing a link, initiate data transfer from the MS. After receiving the first frame, send a supervisory frame from the SS to acknowledge the last I+S frame received. In this set the first byte of the S frame control field to 1110 0000. Verify whether the MS sends an FRMR. After the link is re-established, verify that the MS resumes data transmission.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS with PDP context 11.

2

Initiate acknowledged mode data transfer of 1 LLC frame (<= N201-I octets) from the MS.

3

MS -> SS

I + S

4

SS -> MS

After receiving the first I + S frame, send a frame, with the contents of the control field as 1110 0000.

5

MS -> SS

FRMR

Verify that the control field of the frame sent in step 4 is sent back in the FRMR response. Verify that the value of V(S) received is 1. W3 shall be set to 1. W1 and W2 shall be set to 0. W4 shall be set to 1.

6

MS -> SS

SABM

Verify that the MS re-establishes the link with a SABM and that it stops sending anymore data to the SS.

7

SS -> MS

UA

Respond with a UA

8

MS -> SS

I+S

Verify that the MS resumes data transmission, with N(S)=0, for the first frame transmitted

9

SS -> MS

RR

Acknowledge all frames sent from the MS.

46.1.2.5.2 Sending FRMR due to reception of an S frame with incorrect length

46.1.2.5.2.1 Conformance requirement

The FRMR unnumbered response may be received by an LLE as a report of a frame rejection condition not recoverable by retransmission of the identical frame:

– receipt of a command or response control field that is undefined or not implemented;

– receipt of a supervisory or unnumbered frame with incorrect length; or

– receipt of an I frame with an information field that exceeds the maximum established length.

Upon occurrence of a frame rejection condition whilst in ABM operation, the LLME shall issue an LLGMM-STATUS-IND primitive; and the LLE shall initiate re-establishment.

Reference

3GPP TS 04.64, subclauses 6.4.1.5 and 8.8.2.

46.1.2.5.2.2 Test purpose

To verify that if the MS receives an S frame with incorrect length, it sends an FRMR frame and re-establishes the link.

46.1.2.5.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

After establishing a link, initiate data transfer from the MS. Send an RR with incorrect length, from the SS, when an I+S frame from the MS with the A bit set is received. Verify whether the MS sends an FRMR. After the link is re-established, verify that the MS resumes data transmission.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS with PDP context 12.

2

Initiate acknowledged mode data transfer from the MS with a sufficient amount of data so that an I+S frame with the A bit set to 1 is sent by the MS.

3

MS -> SS

I + S

4

Repeat step 3 until a frame with the A bit set to 1 is received.

5

SS -> MS

RR

There shall be an extra octet in this RR frame, before the FCS. The RR frame shall appear as follows:

Address field (1 octet)

Control field (2 octets)

Extra field (1 octet)

FCS (3 octets)

SS shall discard I+S frames received from the MS.

6

MS -> SS

FRMR

Verify that the control field of the RR message is sent back in the FRMR response. W1, W3 and W4 shall be set to 1. The content of W2 shall not be checked.

7

MS -> SS

SABM

Verify that the MS re-establishes the link with a SABM and that it stops sending anymore data to the SS.

8

SS -> MS

UA

Respond with a UA

9

MS -> SS

I+S

Verify that the MS resumes transmission of data.

10

SS -> MS

RR

Acknowledge all frames sent from the MS.

11

Repeat 9 and 10 until all the frames from the MS are transmitted and acknowledged.

46.1.2.5.3 Sending FRMR due to reception of an I frame information field exceeding the maximum length

46.1.2.5.3.1 Conformance requirement

The FRMR unnumbered response may be received by an LLE as a report of a frame rejection condition not recoverable by retransmission of the identical frame:

– receipt of a command or response control field that is undefined or not implemented;

– receipt of a supervisory or unnumbered frame with incorrect length; or

– receipt of an I frame with an information field that exceeds the maximum established length.

Upon occurrence of a frame rejection condition whilst in ABM operation, the LLME shall issue an LLGMM-STATUS-IND primitive; and the LLE shall initiate re-establishment.

Reference

3GPP TS 04.64, subclauses 6.4.15 and 8.8.2.

46.1.2.5.3.2 Test purpose

To verify that if the MS receives an I frame with an information field that exceeds the maximum established length, it sends an FRMR frame and re-establishes the link.

46.1.2.5.3.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

After establishing a link, initiate data transfer from the SS. After sending 5 frames from the SS, send an I+S frame with length greater than N201-I, from the SS. Verify whether the MS sends an FRMR. After the link is re-established, send frames from the SS with N(S) = 0 until N(S) = 5. Verify that the MS acknowledges all the data sent.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP context 11,

2

Initiate acknowledged mode data transfer from the SS.

3

SS -> MS

I + S

A = 1

A4 (Optional step)

MS -> SS

RNR

If the MS sends an RNR, do not transmit data until it sends an RR.

4

MS -> SS

RR

Send RR frames as acknowledgements from the MS.

5

Repeat steps 3 and 4 until 5 frames are sent from the SS.

6

SS -> MS

I + S

Send an I+S frame with the information field length greater than N201-I, from the SS .

7

MS -> SS

FRMR

Verify that the control field of the I+S message is sent back in the FRMR response. Also verify that the value of V(R) indicates all the frames sent so far except the erroneous I+S frame have been received. W2 and W4 shall be set to 1. W1, W3 shall be set to 0.

8

MS -> SS

SABM

Verify that the MS re-establishes the link with a SABM .

9

SS -> MS

UA

Respond with a UA

10

SS -> MS

I+S

Send data from the SS.

A11 (Optional step)

MS -> SS

RNR

If the MS sends an RNR , do not transmit data until it has sent an RR.

B11 (Optional step)

MS -> SS

RR

Verify that all the frames sent from the SS are acknowledged.

12

Repeat 10 and 11 until all the frames from the SS are transmitted and acknowledged.

46.1.2.5.4 Frame reject condition during establishment of ABM

46.1.2.5.4.1 Conformance requirement

The FRMR unnumbered response may be received by an LLE as a report of a frame rejection condition not recoverable by retransmission of the identical frame:

– receipt of a command or response control field that is undefined or not implemented;

– receipt of a supervisory or unnumbered frame with incorrect length; or

– receipt of an I frame with an information field that exceeds the maximum established length.

Upon occurrence of a frame rejection condition whilst in ABM operation, the LLME shall issue an LLGMM-STATUS-IND primitive; and the LLE shall initiate re-establishment.

Upon occurrence of a frame rejection condition during establishment of or release from ABM operation, or whilst in ADM state, the LLE shall discard the frame.

Reference

3GPP TS 04.64, subclauses 6.4.15 and 8.8.2.

46.1.2.5.4.2 Test purpose

To verify that if the MS receives a U frame with its frame type not implemented during ABM establishment, it shall ignore the message.

46.1.2.5.4.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate link establishment from the MS by sending a SABM. Send an invalid U frame as response. Check if the MS resends the SABM. Respond with a UA. Initiate data transfer from the MS and acknowledge all the frames sent from the MS.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context 13.

2

MS -> SS

SABM

Verify that P/F = 1.

3

SS -> MS

Invalid U frame

Send a U frame with its control field M4 M3 M2 M1 = 0010

4

MS -> SS

FRMR

5

MS -> SS

SABM

Ensure that the MS resends SABM

6

SS -> MS

UA

7

MS -> SS

I + S

Initiate data transfer from the MS.

8

SS -> MS

RR

Acknowledge all frames sent from the MS.

46.1.2.6 Multiple Connections

46.1.2.6.1 Simultaneous acknowledged and unacknowledged data transfer on the same SAPI

46.1.2.6.1.1 Conformance requirement

The purpose of LLC is to convey information between layer-3 entities in the MS and SGSN. Specifically, LLC shall support:

– multiple MSs, at the Um interface;

– multiple layer-3 entities within the MS.

Reference

3GPP TS 04.64, subclause 4.2.

46.1.2.6.1.2 Test purpose

To verify that LLC supports simultaneous acknowledged and unacknowledged data transfer in the same direction on the same SAPI.

46.1.2.6.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate acknowledged data transfer from the MS on SAPI 3. Send 300 frames continuously. The value of N(S) shall begin from 0 and increment by 1 mod (512) for each frame. Initiate unacknowledged data transfer from the MS on the same SAPI within 1 minute from initiation of the acknowledged data transfer.

Acknowledge all the I frames sent from the SS by sending RR frames to the MS.

Maximum duration of the test

30 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation on PDP context 11 and 5 from the MS.

– For PDP context 11, SS negotiates a value of 140 for N201-I.

– For PDP context 5, SS triggers an XID negotiation to set

N201-U to 140.

2

Initiate acknowledged mode data transfer from the MS.

3

MS -> SS

I+S frame

N(S) = 0 for the first frame

4

SS -> MS

S frame with RR

Send RR only when A bit = 1.

5

Initiate unacknowledged mode data transfer of 200 UI frames (using PDP context 5) from the MS within 1 minute from step2.

6

MS -> SS

I+S frame

7

SS -> MS

RR

Send RR only when A bit = 1.

8

MS -> SS

UI

9

Repeat from step 6 until 300 I+S frames of acknowledged data and 200 UI frames of unacknowledged data are transmitted.

I Verify that :

The MS does not retransmit any frame.

N(S) begins with 0 and is incremented by 1 mod (512) for each transmission

N(U) begins with 0 and is incremented by 1 mod (512) for each transmission

46.1.2.6.2 Simultaneous acknowledged and unacknowledged data transfer on different SAPIs

46.1.2.6.2.1 Conformance requirement

The purpose of LLC is to convey information between layer-3 entities in the MS and SGSN. Specifically, LLC shall support:

– multiple MSs, at the Um interface;

– multiple layer-3 entities within the MS.

Reference

3GPP TS 04.64, subclause 4.2.

46.1.2.6.2.2 Test purpose

To verify that LLC supports simultaneous acknowledged and unacknowledged data transfer on different SAPIs in different directions.

46.1.2.6.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate unacknowledged data transfer from the MS on SAPI 5. Initiate acknowledged data transfer from the SS on SAPI 3 after the first i frames have been received from the MS. Send 300 I+S frames continuously from the SS. The value of N(S) shall begin from 0 and increment by 1 mod (512) for each frame.

Verify that the MS acknowledges all the I frames sent from the SS. Verify that the UI frames are received at the SS in sequence.

Maximum duration of the test

15 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation on PDP Contexts 8 and 11 from the MS.

For PDP context 8, SS triggers an XID negotiation to set N201-U to 140.

2

Initiate unacknowledged mode data transfer of 200 UI frames octets from the MS.

3

MS -> SS

UI frame

4

Initiate acknowledged mode data transfer of 300 I+S frames octets from the SS.

5

SS -> MS

I+S frame

Start sending I+S frames after i UI frames have been received. Set the A bit to 1 when the window is full and for the last I+S frame.

A6

MS -> SS

UI frame

B6

MS -> SS

RNR

If the MS sends an RNR, the SS shall resume transmission only after it transmits a SACK, RR or an ACK.

C6

MS -> SS

SACK

The SS shall retransmit the unacknowledged frames.

D6

MS -> SS

ACK

The SS shall retransmit the unacknowledged frames.

E6

MS -> SS

S frame with RR

Verify that the MS acknowledges all the frames sent from the SS.

The MS may not send any frame if the A bit was not set in step 5.

7

Repeat steps 5 and 6 until all 300 I+S frames have been transmitted for the acknowledged mode from the SS and 200 UI frames for the unacknowledged mode to the SS. Verify that :

The MS acknowledges all I+S frames sent.

-The MS sends all UI frames in the correct sequence.

46.1.2.7 XID Negotiation

46.1.2.7.1 Negotiation initiated by the SS during ABM, for T200 and N200

46.1.2.7.1.1 Conformance requirement

The negotiation procedure is one-step, i.e., one side shall start the process by sending an XID command, offering a certain set of parameters from the applicable parameter repertoire the sending entity wants to negotiate, proposing values within the allowed range. In return, the other side shall send an XID response, either confirming these requested values, or offering higher or lower ones in their place.

XID frames shall always be used with the P/F bit set to 1.

T200, N200 and N201-U can be negotiated in ADM and ABM.

Reference

3GPP TS 04.64, subclause 6.4.1.6.

46.1.2.7.1.2 Test purpose

To verify that when the SS initiates XID negotiations with a certain value of T200 and N200, the MS complies with the final negotiated values

46.1.2.7.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate XID negotiation from the SS, with N200 = 4 and T200 = 10 s. The MS will send an XID response. Initiate data transfer from the MS. Verify that the MS complies with the values of T200 and N200 that were agreed upon.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS for PDP Context 11

2

SS -> MS

XID

XID command with N200 = 4, T200 = 10 s. Check if the P/F bit is set to 1.

3

MS -> SS

XID

XID response. Check if the P/F bit is set to 1. The values, if received in this message shall be the negotiated values, else the values are deemed to be confirmed.

4

Initiate acknowledged mode data transfer of 1 LLC frame (<= N201-I octets)from the MS.

5

MS -> SS

I + S

6

Do not respond with an RR.

7

MS -> SS

I+S

Verify that the MS resends the I+S frame every T200 seconds N200 times.

8

MS -> SS

SABM

Verify that the MS sends a SABM to re-establish the link

9

SS -> MS

UA

Respond with a UA within T200 seconds.

46.1.2.7.2 Negotiation initiated by the SS during ADM, for N201-I

46.1.2.7.2.1 Conformance requirement

The negotiation procedure is one-step, i.e., one side shall start the process by sending an XID command, offering a certain set of parameters from the applicable parameter repertoire the sending entity wants to negotiate, proposing values within the allowed range. In return, the other side shall send an XID response, either confirming these requested values, or offering higher or lower ones in their place.

XID frames shall always be used with the P/F bit set to 1.

N201-I, mD, mU, kD and kU can be negotiated to any value in Range in ADM. In ABM, N201-I, mD, mU, kD and kU can only be negotiated to the same or higher value as previously used.

Reference

3GPP TS 04.64, subclause 6.4.1.6.

46.1.2.7.2.2 Test purpose

To verify that when the SS initiates XID negotiations with a certain value of N201-I during ADM, the MS complies with the final negotiated values.

46.1.2.7.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate PDP context activation from the MS and in the UA response from the SS send a value of 140 for N201-I. If the MS responds with an XID command, in the XID response, give N201-I = 140.

Initiate data transfer from the SS. Send an I+S frame of length N201-I with the A bit set to 1. Verify that the MS acknowledges this I+S frame.

The next I+S frame sent from the SS shall be of length N201-I +1. Verify that the MS sends FRMR and re-establishes the link.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context 11.

2

MS -> SS

SABM

3

SS -> MS

UA

Set N201-I = 140 in the UA sent. If the MS sends an XID command with a different value of N201-I, send back a response with N201-I = 140.

4

SS -> MS

I+S

Send an I+S frame from the SS with length N201-I with the A bit set to 1.

A5 (optional step)

MS -> SS

RNR

If the MS sends an RNR, verify that the RNR acknowledges the frame sent in step 4. Do not transmit the next I+S frame to the SS until the MS sends an RR.

5

MS -> SS

RR

Verify that the MS responds with an RR.

6

SS -> MS

I+S

The length of this I+S frame shall be N201-I + 1. Set the A bit to 1.

7

MS -> SS

FRMR

Verify that the control field of the I+S message is sent back in the FRMR response. Also verify that the value of V(R) indicates all the frames sent so far except the erroneous I+S frame have been received. W2 and W4 shall be set to 1. W1 and W3 shall be set to 0.

8

MS -> SS

SABM

Verify that the MS re-establishes the link with a SABM.

9

SS -> MS

UA

Respond with a UA within T200 seconds.

46.1.2.7.3 Negotiation initiated by the SS (using XID, for IOV-UI)

46.1.2.7.3.1 Conformance requirement

The negotiation procedure is one-step, i.e., one side shall start the process by sending an XID command, offering a certain set of parameters from the applicable parameter repertoire the sending entity wants to negotiate, proposing values within the allowed range. In return, the other side shall send an XID response, either confirming these requested values, or offering higher or lower ones in their place.

XID frames shall always be used with the P/F bit set to 1.

LLC layer and layer-3 parameters may be negotiated with the exchange of XID frames or with the exchange of SABM and UA frames. After successful negotiations of SABM and UA frames, the LLE shall be in ABM mode of operation.

IOV-UI shall only be negotiated in ADM. IOV-UI and IOV-I shall only be transmitted in the downlink direction.

Reference

3GPP TS 04.64, subclauses 6.4.1.6 and 8.5.3.

46.1.2.7.3.2 Test purpose

To verify that when the SS sends IOV-UI to the MS in a XID, the MS shall cipher its output using this value of IOV-UI.

46.1.2.7.3.3 Method of test

Initial conditions

For execution counter K = 4 (GEA4) Test USIM has to be plugged into the MS. The MS shall be GPRS attached with ciphering enabled. Encryption GEA1, GEA2, GEA3 or GEA4 is used depending on the execution counter K.

Specific PICS statements:

– Supported encryption Algorithm: GEA1 (TSPC_Feat_GEA1)

– Supported encryption Algorithm: GEA2 (TSPC_Feat_GEA2)

– Supported encryption Algorithm: GEA3 (TSPC_Feat_GEA3)

– Supported encryption Algorithm: GEA4 (TSPC_Feat_GEA4)

PIXIT statements:

Test procedure

During GPRS attach ciphering GEA1, GEA2, GEA3 or GEA4 is activated depending on the execution counter K.

Initiate link establishment from the SS. In the XID command, send a new value of IOV-UI, different from the default used. Send 1000 octets from the MS and verify that the frames have been ciphered as per the new value of IOV-UI.

The test is performed for all GEAx encryption algorithm supported by the MS.

Maximum duration of the test

5 minutes.

Expected sequence

The sequence is performed for execution counter K=1 when the MS supports GEA1, for K=2 when the MS supports GEA2, for K=3 when the MS supports GEA3 and for K=4 when the MS supports GEA4.

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context 5.

2

{PDP Context Modification}

Macro. Initiate PDP context modification to PDP Context 3 from the SS.

3

SS -> MS

XID

With IOV-UI = 2 27 * 10.

4

MS -> SS

XID

5

Initiate data transfer from the MS. Send 1000 octets.

6

MS -> SS

UI

Verify that ciphering is as per the new value of IOV-UI. The SS shall check this by analyzing the FCS.

7

Repeat the steps 6 till the data transfer is complete.

46.1.2.7.4 Negotiation initiated by the SS (during ADM, for N201-U)

46.1.2.7.4.1 Conformance requirement

The negotiation procedure is one-step, i.e., one side shall start the process by sending an XID command, offering a certain set of parameters from the applicable parameter repertoire the sending entity wants to negotiate, proposing values within the allowed range. In return, the other side shall send an XID response, either confirming these requested values, or offering higher or lower ones in their place.

XID frames shall always be used with the P/F bit set to 1.

T200, N200 and N201-U can be negotiated in ADM and ABM.

N201-U is used for U and UI frames.

Reference

3GPP TS 04.64, subclauses 6.4.1.6 and 8.9.5.

46.1.2.7.4.2 Test purpose

To verify that when the SS initiates XID negotiations with a certain value of N201-U during ADM, the MS complies with the final negotiated values.

46.1.2.7.4.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Initiate XID negotiation from the SS, with N201-U = 140. The MS shall send an XID response. The value of N201-U shall either be not present in the XID response or set to 140.

Initiate data transfer from the MS. Verify that the length of the UI frames sent from the MS never exceeds the negotiated value of N201-U.

Maximum duration of the test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context 9.

2

SS -> MS

XID

XID command with N201-U = 140

3

MS -> SS

XID

XID response. Check if the P/F bit is set to 1. The N201-U value, if received in this message shall beset to 140, else the value is deemed to be confirmed.

4

Initiate unacknowledged data transfer of 1000 octets from the MS.

5

MS -> SS

UI

Verify that the frame length does not exceed the negotiated value of N201-U.

6

Repeat step 5 until 1000 octets have been sent from the MS.

46.1.2.7.5 Negotiation initiated by the SS (during ADM, for IOV-UI)

46.1.2.7.5.1 Conformance requirement

The negotiation procedure is one-step, i.e., one side shall start the process by sending an XID command, offering a certain set of parameters from the applicable parameter repertoire the sending entity wants to negotiate, proposing values within the allowed range. In return, the other side shall send an XID response, either confirming these requested values, or offering higher or lower ones in their place.

XID frames shall always be used with the P/F bit set to 1.

IOV-UI shall only be negotiated in ADM. IOV-UI and IOV-I shall only be transmitted in the downlink direction.

IOV-UI is associated with a TLLI.

Reference

3GPP TS 04.64, subclauses 6.4.1.6, 8.5.3 and 8.9.

3GPP TS 04.08 subclause 4.7.12.

46.1.2.7.5.2 Test purpose

To verify that when the SS sends IOV-UI to the MS in an XID command:

– The MS shall cipher its output using this value of IOV-UI.

– This value of IOV-UI shall be applicable for all SAPIs using this TLLI.

– Identity Response sent from the MS shall not be ciphered.

46.1.2.7.5.3 Method of test

Initial conditions

– For execution counter K = 4 (GEA4) Test USIM has to be plugged into the MS.

Specific PICS statements:

– Supported encryption Algorithm : GEA1 (TSPC_Feat_GEA1)

– Supported encryption Algorithm : GEA2 (TSPC_Feat_GEA2)

– Supported encryption Algorithm : GEA3 (TSPC_Feat_GEA3)

– Supported encryption Algorithm : GEA4 (TSPC_Feat_GEA4)

PIXIT statements:

Test procedure

Send a value of IOV-UI from the SS, different from the default used. Send 1 000 octets from the MS and verify that the frames have been ciphered as per the new value of IOV-UI.

Send 1 000 octets from the MS on SAPI 11. Verify that the frames have been ciphered as per the new value of IOV-UI.

The test is performed for all GEAx encryption algorithm supported by the MS.

Maximum duration of the test

3 minutes.

Expected sequence

The sequence is performed for execution counter K=1 when the MS supports GEA1, for K=2 when the MS supports GEA2, for K=3 when the MS supports GEA3 and for K=4 when the MS supports GEA4.

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate a PDP context activation from the MS using PDP Context 10.

2

SS -> MS

UI [Authentication and Ciphering Request]

Send the Authentication and Ciphering Request from the SS to start ciphering using the following encryption algorithm:

GEA1 for K=1,

GEA2 for K=2,

GEA3 for K=3,

GEA4 for K=4.

3

MS -> SS

UI [Authentication and Ciphering Response]

For K=1,2,3 the SS checks the SRES

For K=4, the SS check the RES and "Auth. Response Parameter (extension)" IE might be included if the RES value is more than 4 octets long.

4

SS -> MS

XID

XID command with IOV-UI = 5000.

5

MS -> SS

XID

Verify that the MS accepts this value of IOV-UI by sending an XID response. Verify the XID response received. If the MS has requested for a new set of XID parameters, verify that the values requested are within range.

6

Initiate unacknowledged data transfer of 1000 octets from the MS.

7

MS -> SS

UI

Verify that these frames have been ciphered as per the new value of IOV-UI.

8

SS -> MS

UI [Identity Request]

This UI frame must not be sent ciphered.

9

MS -> SS

UI [Identity Response]

This UI frame shall not be ciphered. The E bit shall not be set to 1.

10

{PDP Context Deactivation}

Macro. Deactivate PDP Context 10.

A11
(Optional step)

If the MS performs a GMM detach the SS completes the Detach procedure.

11

{PDP Context Activation}

Macro. Activate PDP Context 9.
If the MS is detached in step A11, GPRS-re-attachment shall be performed.

A12
(Conditional step)

If the MS is re-attached in step 11, then step 2, 3, 4 and 5 shall be repeated to set IOV-UI parameter and restart ciphering.

12

Initiate a data transfer of 1000 octets from the MS on SAPI 11 for the same value of TLLI as before.

13

MS -> SS

UI

Verify that ciphering is as per the new value of IOV-UI.

Specific message contents

AUTHENTICATION AND CIPHERING REQUEST in step 2:

Same as default content except :

Information element

Value/remark

IE AUTN

Not present for K = 1

Not present for K = 2

Not present for K = 3

Present for K = 4

Ciphering Algorithm

Type of Algorithm

GEA/1 for K = 1

GEA/2 for K = 2

GEA/3 for K = 3

GEA/4 for K = 4

46.1.2.7.6 Negotiation initiated by the SS (during ABM, for Reset)

Send Reset during unacknowledged mode data transfer and check if N(S) begins from 0.

46.1.2.7.6.1 Conformance requirement

The negotiation procedure is one-step, i.e., one side shall start the process by sending an XID command, offering a certain set of parameters from the applicable parameter repertoire the sending entity wants to negotiate, proposing values within the allowed range. In return, the other side shall send an XID response, either confirming these requested values, or offering higher or lower ones in their place.

XID frames shall always be used with the P/F bit set to 1.

Reset shall only be negotiated with an XID frame, and only transmitted in the downlink direction. If Reset is present in an XID frame, it shall be the first parameter in the XID information field.

The Reset parameter shall be used, in the SGSN originating Reset and the MS receiving Reset, to:

– set all LLC layer parameters to the default values given in table 9;

– change any LLEs in ABM state to ADM state;

– set the unconfirmed state variable V(U) to value 0;

– set the unconfirmed receive state variable V(UR) to 0;

– set the OCs for unacknowledged information transfer to 0.

The Reset parameter shall be treated before any additional XID parameters present in the same XID frame.

Reference

3GPP TS 04.64, subclauses 6.4.1.6 and 8.5.3.1.

46.1.2.7.6.2 Test purpose

To verify that when the SS sends the Reset parameter to the MS in an XID:

– it sets all LLC layer parameters to the default values;

– change any LLEs in ABM state to ADM state;

– set the unconfirmed state variable V(U) to value 0;

– set the unconfirmed receive state variable V(UR) to 0;

– set the OCs for unacknowledged information transfer to 0.

46.1.2.7.6.3 Method of test

Initial conditions

System simulator

The System Simulator shall support two cells, each in a different SGSN Routing Area.

Mobile station:

The MS shall be GPRS attached with ciphering enabled.

Specific PICS statements:

PIXIT statements:

Test procedure

For this test case, NMS = NSS = 10.

Initiate unacknowledged data transfer from the MS. Send NMS UI frames.

Initiate unacknowledged data transfer from the SS. Send NSS UI frames.

During PDP context activation for Context 11, initiate XID negotiation from the SS, with N200 = 4 and T200 = 10, if it is not done by the MS or if the MS tries to negotiate with N200 < 4 and T200 < 10, otherwise accept the values proposed by the MS. Initiate data transfer from the MS. Do not acknowledge the first frame sent from the MS and verify that the MS complies with the values of T200 and N200 that were agreed upon.

Initiate inter-SGSN Routing Area Update from the MS, which will make the SS send an XID command with the Reset parameter. Send I+S frames from the MS, with the A bit set to 1. Do not acknowledge the first I+S frame. Verify that the MS sends the I+S frame N200 times, every T201 seconds. Verify that the values of N200 and T201 are the default values.

Initiate unacknowledged data transfer from the MS for the same SAPI and for the same TLLI used before sending Reset from the SS. Verify that the frames are numbered from 0 and not from NMS. Verify that the frames can be decrypted using OC = 0.

Maximum duration of the test

10 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS using PDP Context 9.

2

MS -> SS

UI frame

3

Repeat step 2 until NMS frames are sent.

4

SS -> MS

UI frame

5

Repeat step 4 until NSS frames are sent.

6

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS for PDP Context 11.

7

MS -> SS

SABM

If the MS negotiates N200 and T200, then accept the proposed values if N200 >= 4 and T200 >=10.

8

SS -> MS

UA

Send N200 = 4, T200 = 10 s in the UA response, if the MS does not negotiate N200 and T200, or if the values of N200 and T200 proposed by the MS are not accepted by the SS in step 7.

9

Initiate acknowledged mode data transfer of 1 octet from the MS.

10

MS -> SS

I + S

11

Do not respond with an RR. Verify that the MS retransmits the I+S frame every T200 seconds N200 times.

12

MS -> SS

SABM

Verify that the MS sends a SABM to re-establish the link

13

SS -> MS

UA

Respond with a UA within T200 seconds.

14

{Inter-SGSN Routing Area Update}

Macro. Initiate Inter-SGSN Routing Area Update from the MS. (This procedure sends XID reset). The MS shall reselect the new cell and do a Routing Area Update with the new SGSN.

15

SS->MS

SABM

Send N200 and T200 with values higher than the ones negotiated in step 7 and 8.

16

MS-> SS

UA

17

MS -> SS

I + S

Resume data transfer from the MS.

18

Do not respond with an RR from the SS. Check that the MS retransmits the frame after T201 seconds, N200 times. T201 and N200 shall be as per the values negotiated, if any, after link re-establishment and not as per the values of N200 and T200 negotiated before sending a Reset, in step 8.

19

MS -> SS

SABM

Verify that the MS sends a SABM to re-establish the link

20

SS -> MS

UA

Respond with a UA within T200 seconds.

21

MS -> SS

UI

Initiate unacknowledged data transfer from the MS and send 50 octets for the same SAPI and for the same TLLI used before sending Reset from the SS.

Verify that these frames have been ciphered with OC = 0 and are numbered from 0 and not from NMS.

46.1.2.7.7 XID command with unrecognised type field

46.1.2.7.7.1 Conformance requirement

If a SABM or XID command with an invalid XID information field is received, then the SABM or XID command, respectively, shall be ignored.

If a SABM or XID command with unrecognised type field is received, then this parameter shall be ignored.

Reference

3GPP TS 04.64, subclause 8.5.3.3.

46.1.2.7.7.2 Test purpose

To test the MS response to an XID command with an unrecognised type field.

46.1.2.7.7.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Send an XID frame from the SS with N201-U = 800 and another parameter with type = 15. Verify that the MS responds with an XID response. Verify that the MS sends UI frames with N201-U taking negotiated value.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate a PDP context from the MS using PDP Context 10.

2

SS -> MS

XID

Send an XID command with N201-U = 800 and an XID parameter with its type = 15, length =4 and value = 1500.

3

MS -> SS

XID

Verify the XID response received. If the MS has requested for a new XID value, verify that

the new values are within range

the sense of negotiation is correct

The values received in the XID response shall be regarded as the final negotiated values.

4

Initiate unacknowledged mode data transfer of 2000 octets from the MS.

5

MS -> SS

UI frame

Verify that the frame length does not exceed the negotiated value for N201-U

46.1.2.7.8 XID Response with out of range values

46.1.2.7.8.1 Conformance requirement

If UA or XID response with an invalid XID information field is received, then the UA or XID response shall be ignored, the SABM or XID command shall be retransmitted, and the retransmission counter shall be incremented.

Reference

3GPP TS 04.64, subclause 8.5.3.3.

46.1.2.7.8.2 Test purpose

To test the MS response to an XID response with the N201-I value out of range.

46.1.2.7.8.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Send an XID frame within SABM , from the MS with layer3 parameters. Respond from the SS with an XID, with N201-I = 1600. Verify that the MS ignores this response and resends the SABM with the XID command. Now accept the XID values received at the SS. Send an I+S frame with length less than N201-I and the A bit set to 1 and verify that the MS responds with an RR. Send an I+S frame from the SS with its length larger than the maximum negotiated value of N201-I and verify that the MS sends an FRMR and re-establishes the link.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS, using PDP context 11.

2

MS -> SS

SABM[XID]

XID command with layer3 parameters, sent with SABM.

3

SS -> MS

UA[XID]

Send an XID response in UA, with N201-I = 1600

4

MS -> SS

SABM[XID]

Verify that the MS resends the SABM command.

5

SS -> MS

UA[XID]

Send UA accepting all the XID values.

6

SS -> MS

I+S

Send an I+S frame with the maximum negotiated value of N201-I, with the A bit set to 1.

A7

(optional step)

MS -> SS

RNR

If the MS sends an RNR, verify that the RNR acknowledges the frame sent in step 6. Do not transmit the next I+S frame to the SS until the MS sends an RR.

7

MS -> SS

RR

Verify that the MS responds with an RR

8

SS -> MS

I+S

Send an I+S frame with length = N201 – I + 1, with the A bit set to 1.

9

MS -> SS

FRMR

Verify that the MS responds with an FRMR

10

MS -> SS

SABM

Verify that the MS initiates link re-establishment

11

SS -> MS

UA

Respond with a UA.

46.2 SNDCP Tests

This clause contains the test case requirements for Subnetwork Dependent Convergence Protocol(SNDCP) procedures in the General Packet Radio Service (GPRS).

46.2.1 Default Conditions

– The MS default initial condition is that it is GPRS attached.

– Data and header compression are off.

The N-PDU size shall be more than the negotiated values of N201-U and N201-I so that segmentation at SNDCP is ensured. Unless stated otherwise, the default conditions shall apply.

If the MS sends an XID command with XID parameters any time before a data transfer, the SS shall send an XID response, accepting the values proposed by the MS.

Test cases identified in TS 51.010-2 as “EC-GSM –IoT compatible” should consider the default cells in the Initial Conditions to be EC-GSM- IoT Cells if the test has to be executed in “EC Mode”.Otherwise the cell should be considered as a basic GPRS cell.

46.2.2 Test cases

46.2.2.1 Data transfer

46.2.2.1.1 Mobile originated normal data transfer with LLC in acknowledged mode

46.2.2.1.1.1 Conformance requirement

The SNDCP entity shall initiate acknowledged data transmission only if the PDP context for the NSAPI identified in the SN-DATA.request has been activated and if acknowledged LLC operation has been established.

The N-PDU number in acknowledged mode is a number assigned to each N-PDU received by SNDCP through an SN-DATA.request. N-PDU numbers for different NSAPIs shall be assigned independently. The N-PDU number shall be included in the SNDCP header of the first segment of an N-PDU.

Upon reception of an SN-DATA.request, the SNDCP entity shall assign to the N-PDU received the current value of the Send N-PDU number as the N-PDU number, increment the Send N-PDU number by 1, perform the compression and segmentation functions, then forward the SN-PDU(s) in LL-DATA.request to the LLC layer. The N-PDU shall be stored into a buffer in the SNDCP entity. The buffered N-PDU shall be deleted when the SN-DATA PDU carrying the last segment of the N-PDU is confirmed by an LL-DATA.confirm primitive.

A (possibly compressed) N-PDU shall be segmented into one or more SN-PDUs. The length of each SN-PDU shall not be greater than N201-I (for acknowledged mode) or N201-U (for unacknowledged mode).

Reference

3GPP TS 04.65, subclauses 6.9.1 and 6.7.1.1.

46.2.2.1.1.2 Test purpose

To verify that:

– The MS sends the N-PDU number in the first segment of every N-PDU.

– The MS increments the N-PDU number properly.

– The size of a segment must not be greater than N201-I.

46.2.2.1.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Activation of PDP context 13 is initiated from MS.

Verify that the first segment of the first N-PDU received has N-PDU number 0. Acknowledge all the segments received from the MS. For the subsequent N-PDUs received, verify that the N-PDU number is incremented properly.

Repeat the test case for PDP contexts 11 and 12.

Maximum duration of the test

10 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. The PDP context used here is PDP context 13.

2

Initiate data transfer of 5000 octets from the MS .

3

MS -> SS

SN-DATA PDU

Verify that the number of octets in the SN-DATA PDU does not exceed N201-I.

Verify that the first SN-DATA PDU received has M=1, T=0, F=1, X = 0, DCOMP = PCOMP = 0,N-PDU number = 0.

4

Verify that the last segment of every N-PDU received has M=0, T=0, and F=0.

Note: Final SN-DATA-PDU could have M=0, T=0 and F=1, if the last N-PDU is too short to be segmented

5

Verify that for the subsequent N-PDUs, the N-PDU number is incremented properly

6

Repeat step 3 to 5 until data transfer is completed.

7

Repeat the test case for SAPIs 3 and 9.The PDP context used for SAPI 3 is PDP Context 11 and the one for SAPI 9 is PDP Context 12.

46.2.2.1.2 Mobile originated normal data transfer with LLC in unacknowledged mode

46.2.2.1.2.1 Conformance requirement

The SNDCP entity shall initiate unacknowledged data transmission only if the PDP context for the NSAPI identified in the SN-DATA.request has been activated. The SNDCP entity may initiate unacknowledged data transmission even if the acknowledged peer-to-peer operation is not established for that NSAPI. The N-PDU number in unacknowledged mode is a number assigned to each N-PDU received by SNDCP through an SN-UNITDATA.request. N-PDU numbers for different NSAPIs shall be assigned independently. The N-PDU number shall be included in the SNDCP header of every SN-UNITDATA PDU.

A variable, the Send N-PDU number (unacknowledged), shall be maintained for each NSAPI using unacknowledged peer-to-peer LLC operation. When an NSAPI using unacknowledged peer-to-peer LLC operation is activated, the Send N-PDU number (unacknowledged) shall be set to 0. The Send N-PDU number (unacknowledged) shall also be set as described in subclauses 5.1.2.1 and 5.1.2.22. Modulo 4096 operation shall be applied to the Send N-PDU number (unacknowledged).

Upon reception of an SN-UNITDATA request, the SNDCP entity shall assign the current value of the Send N-PDU number (unacknowledged) as the N-PDU number of the N-PDU received, increment Send N-PDU number (unacknowledged) by 1, compress and segment the information, then forward the SN‑PDU(s) in LL‑UNITDATA.request to the LLC layer. The N-PDU shall be deleted immediately after the data has been delivered to the LLC layer.

A (possibly compressed) N-PDU shall be segmented into one or more SN-PDUs. The length of each SN-PDU shall not be greater than N201-I (for acknowledged mode) or N201-U (for unacknowledged mode).

The segment number is a sequence number assigned to each SN-UNITDATA PDU. The sequence number shall set to 0 in the first SN-UNITDATA PDU of an N-PDU, and incremented by 1 for each subsequent SN-UNITDATA PDU. Modulo 16 operation is applied. N-PDU number is included in every SN-UNITDATA PDU.

The SNDCP entity shall perform the mapping function of SN_UNITDATA primitives onto LL_UNITDATA primitives

Reference

3GPP TS 04.65, subclauses 6.9.2, 6.7.1.1, 6.7.3 and 5.2.

46.2.2.1.2.2 Test purpose

To verify that:

– The MS sends the N-PDU number in every segment of every N-PDU.

– The MS increments the N-PDU number and segment number properly and modulo 16 operation is applied.

– The size of a segment shall not be greater than N201-U.

– The MS maps the SN_UNITDATA PDUs onto SAPIs allocated by Network.

46.2.2.1.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

PDP context 10 is initiated from MS.

Initiate unacknowledged data transfer from MS.

Verify that the first segment of the first N-PDU received has N-PDU number 0. For the subsequent N-PDUs received, verify that the N-PDU number is incremented properly.

Verify that the SN-UNITDATA PDUs are numbered correctly.

Verify the SAPI number on which the data PDU is received.

Verify that Modulo 16 operation is applied.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. The PDP context used here is PDP context 10.

2

SS -> MS

XID

XID command with N201-U = 140.

3

MS -> SS

XID

XID response.

4

Initiate data transfer of 5000 octets (with each N-PDU being more than 140 octets) from the MS.

5

MS -> SS

SN-UNITDATA PDU

Verify that the number of octets in the SN-UNITDATA PDU does not exceed N201-U.

Verify that the first SN-UNITDATA PDU received has M=1, T=1, F=1, X = 0, DCOMP = PCOMP = 0, N-PDU number = 0, segment = 0.

6

SS

Verify that the segment number is incremented properly for every SN-PDU.

Verify that the last segment of every N-PDU received has M=0, T=1, and F=0.

The last N-PDU may not be segmented; the F bit shall not be checked.

7

SS

Verify that for the subsequent N-PDUs, the N-PDU number is incremented properly and N-PDU number is present in every SN-UNITDATA PDU

8

SS

Verify the SAPI number In the received LLC frame header

9

Repeat steps 5 to 8 until data transfer is completed.

Verify modulo 16 operation is applied for the 17th segment of SN-UNITDATA PDU,

Note: This check of ‘Modulo 16 operation’ is to be done only if; the NPDUs are having 17 or more segments.

46.2.2.1.3 Usage of acknowledged mode for data transmission before and after PDP Context modification, on different SAPIs

46.2.2.1.3.1 Conformance Requirement

Upon reception of the SNSM-MODIFY.indication from the SM sublayer:

– the SNDCP entity shall, if necessary, establish the acknowledged peer-to-peer LLC operation for the indicated SAPI (the establishment criteria and procedure are described in subclause 6.2.1);

– the SNDCP entity shall also, if necessary, release the acknowledged peer-to-peer LLC operation for the originally-assigned SAPI (the release criteria and procedure are described in subclause 6.2.2); In addition, if the newly-assigned SAPI is different from the original SAPI:

– LL-DATA.indication, LL-DATA.confirm and LL-UNITDATA.indication received on the old SAPI shall be ignored;

– LL-DATA.request and LL-UNITDATA.request shall be sent on the new SAPI; and

– if acknowledged peer-to-peer LLC operation is used both before and after the receipt of the SNSM‑MODIFY. indication, then all buffered N-PDUs (i.e., the ones whose complete reception has not been acknowledged and the ones that have not been transmitted yet) shall be transmitted starting from the oldest N-PDU.

Reference

3GPP TS 04.65, subclause 5.1.2.23.

46.2.2.1.3.2 Test purpose

To verify that after the PDP context modification:

– the MS resumes acknowledged data transfer correctly with the oldest N-PDU which is buffered after a PDP context modification.

46.2.2.1.3.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

PDP Context 11 is initiated from MS.

After the first N-PDU is correctly received in acknowledged mode, the last segment of the second N-PDU (N-PDU number=1) is not acked and a PDP context modification is initiated from SS to PDP context 12, i.e.: using SAPI 9 in acknowledged mode.

After the modification procedure is complete, the first SN-DATA PDU received shall have the N-PDU number 1. The N-PDU received shall be the same as the last one before the modification procedure was triggered.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 11.

2

Initiate acknowledged data transfer for 5000 octets, from the MS.

3

MS -> SS

SN-DATA PDU

Verify that the number of octets in the SN-DATA PDU does not exceed N201-I.

Verify that the first SN-DATA PDU received has M=1, T=0, F=1, X = 0, DCOMP = PCOMP = 0, N-PDU number = 0.

4

Verify that the last segment of the first N-PDU received has M=0, T=0, and F=0.

The last segment of last N-PDU may be not segmented; the F bit shall not be checked.

5

Receive the next N-PDU, N-PDU = 1 by following steps 3 and 4. Do not acknowledge the last segment of the N-PDU.

6

{PDP Context Modification}

Macro. Initiate PDP context modification procedure from the SS. Use PDP context 12 (i.e.: using SAPI 9 in acknowledged mode)

7

SS->MS

DISC

Initiate the release of LLC link by sending DISC on SAPI 3 and receive UA or DM from MS.

8

MS->SS

UA or DM

9

SS->MS

SABM

Initiate the establishment of LLC link by sending SABM on SAPI 9 and receive UA from MS.

10

MS->SS

UA

11

MS -> SS

SN-DATA PDU

Verify that the number of octets in the SN-DATA PDU does not exceed N201-I.

Verify that the first SN-DATA PDU received has M=1, T=0, F=1, X = 0, DCOMP = PCOMP = 0.

Verify that the N-PDU received has N-PDU number = 1.

12

Verify that the last segment of every N-PDU received has M=0, T=0, and F=0.

The last segment of last N-PDU may be not segmented; the F bit shall not be checked.

13

Verify that for the subsequent N-PDUs, the N-PDU number is incremented properly

14

Repeat steps 11 to 13 until data transfer is completed.

46.2.2.1.4 Reset indication during unacknowledged mode

46.2.2.1.4.1 Conformance Requirement

Upon receipt of the LL-RESET.indication, the SNDCP layer shall:

– reset all SNDCP XID parameters to their default values;

– in the MS, for every NSAPI using unacknowledged peer-to-peer LLC operation, set the Send N-PDU number (unacknowledged) to 0.

Reference

3GPP TS 04.65, subclause 5.1.2.1.

46.2.2.1.4.2 Test purpose

To verify that the MS resets the Send N-PDU number to 0 on link reset during an unacknowledged mode data transfer.

46.2.2.1.4.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

PDP Context 8 is initiated from MS.

An XID command is sent with reset from SS during unacknowledged data transfer, after receiving N-PDU number 2 from MS. The next N-PDU number from MS shall be 0.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 8.

2

Initiate unacknowledged data transfer using sufficient amount of data (for example 150000 octets) to be sure that at step 8 the MS still has available N-PDUs for transmission subsequent to XID procedure at step 6 and step 7.

3

MS -> SS

SN-UNITDATA PDU

Verify that the number of octets in the SN-UNITDATA PDU does not exceed N201-U.

Verify that the first SN-UNITDATA PDU received has M=1, T=1, F=1, X = 0, DCOMP = PCOMP = 0,N-PDU number = 0, sequence number = 0.

4

Verify that the last segment of the first N-PDU received has M=0, T=1, and F=0.

5

Receive the N-PDUs from the MS until N-PDU number becomes 2

6

SS->MS

XID

Initiate the XID command from SS with reset

Discard all UI frames received.

7

MS->SS

XID

XID response

8

MS -> SS

SN-UNITDATA PDU

Verify that the number of octets in the SN-UNITDATA PDU does not exceed N201-U.

Verify that the first SN-UNITDATA PDU received after link reset has M=1, T=1, F=1, X = 0, DCOMP = PCOMP = 0,N-PDU number = 0, segment number = 0.

46.2.2.1.5 Reset indication during acknowledged mode

46.2.2.1.5.1 Conformance Requirement

Upon receipt of the LL-RESET.indication, the SNDCP layer shall:

– reset all SNDCP XID parameters to their default values;

– for every NSAPI using acknowledged peer-to-peer LLC operation, enter the recovery state and suspend the transmission of SN-PDUs until an SNSM-SEQUENCE.indication primitive is received for the NSAPI.

Reference

3GPP TS 04.65, subclause 5.1.2.1.

46.2.2.1.5.2 Test purpose

To verify that the MS suspends the data transfer in acknowledged mode on link reset and resume when indicated by the SS.

46.2.2.1.5.3 Method of test

Initial conditions

Two cells , cell A and B need to be supported. B is in a routing area (in a new SGSN) and location area different from that of A. The power level of cell A shall be higher than that of cell B so that the MS selects cell A.

Specific PICS statements:

PIXIT statements:

Test procedure

PDP Context 13 is initiated from MS.

Acknowledge the first 2 N-PDUs received from MS during the data transfer.

Initiate an inter SGSN Routing Area Update procedure from MS. An XID command is sent with reset from SS, after receiving N-PDU number N from MS. Specify the Receive N-PDU number to be 3 in the Routing Area Update Accept message. Verify that the data transfer is resumed and the MS sends the complete N-PDU with N-PDU number 3.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 13.

2

Initiate acknowledged data transfer for 7000 octets, from the MS.

3

MS -> SS

SN-DATA PDU

Verify that the number of octets in the SN-DATA PDU does not exceed N201-I.

Verify that the first SN-DATA PDU received has M=1, T=0, F=1, X = 0, DCOMP = PCOMP = 0,N-PDU number = 0.

4

Verify that the last segment of the first N-PDU received has M=0, T=0, and F=0.

5

Receive the N-PDUs from the MS until N-PDU number becomes 1 and acknowledge all the segments completely.

6

Receive the N-PDUs 2 and 3 from the MS and do not acknowledge the last SN-PDU of N-PDU 3..

7

{Inter-SGSN Routing Area Update}

Macro. Initiate a cell change requesting the MS to move to cell B.

Initiate an inter SGSN Routing Area Update procedure from SS.

Send the Receive N-PDU number as 3 in the Routing Area Update Accept message.

Note: After changing the signal strength and before receiving the RAU REQUEST, MS may send some more SN-DATA PDUs. These PDUs are not acknowledged in cell A.

8

SS->MS

SABM

9

MS->SS

UA

10

MS -> SS

SN-DATA PDU

Verify that the number of octets in the SN-DATA PDU does not exceed N201-I.

Verify that the first SN-DATA PDU received has M=1, T=0, F=1, X = 0, DCOMP = PCOMP = 0, N-PDU number = 3.

Last N-PDU may be not segmented; in which case the M bit shall not be checked.

11

Repeat step 10 until data transfer is completed.

46.2.2.1.6 Inter SGSN (with NAS container / new Routing Area / SGSN indicated Reset) PS Handover / Synchronized cell case / successful

46.2.2.1.6.1 Conformance Requirement

If during PS handover the MS is requested to perform a Reset of LLC layer parameters and layer‑3 parameters (see 3GPP TS 24.008 [8a]), the MS shall perform the actions described above and shall send the XID response on one of the active SAPIs once the PS handover procedure has been successfully completed.

If Reset of LLC layer parameters and layer-3 parameters without old XID indicator has been performed, following the sending of the XID response each active LLE in the MS shall:

– set timer T100; and

– not initiate any XID negotiation procedure while T100 is running.

3GPP TS 44.064, subclause 8.5.3.1.

46.2.2.1.6.2 Test purpose

To verify that the MS triggered by a Packet Switch Handover to move to a different SGSN will handle the different types of LLC reset contained in the NAS container.

46.2.2.1.6.3 Method of test

Initial conditions

Cells A and B need to be supported. Cell B is in a routing area (in a new SGSN) and location area different from that of Cell A. The power level of Cell A shall be higher than that of Cell B so that the MS selects Cell A.

Specific PICS statements:

PIXIT statements:

Test procedure

PDP Context 13 is initiated from MS.

Acknowledge the first 2 N-PDUs received from MS during the data transfer.

Initiate an inter SGSN Routing Area Update procedure from MS triggered by a PSHO including the NAS container (same GEA used) after receiving N-PDU number N from MS. Specify the Receive N-PDU number to be 3 in the Routing Area Update Accept message. Verify that the data transfer is resumed and the MS sends the complete N-PDU with N-PDU number 3.

The procedure is run twice, the only difference being k, the old XID field in the {Inter-SGSN Routing Area Update – with PSHO} macro:

Sequence k=0, the MS shall perform a Reset of LLC and SNDCP without old XID indicator

Sequence k=1, the MS shall perform a Reset of LLC and SNDCP with old XID indicator

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 13.

2

Initiate acknowledged data transfer for 7000 octets, from the MS.

3

MS -> SS

SN-DATA PDU

Verify that the number of octets in the SN-DATA PDU does not exceed N201-I.

Verify that the first SN-DATA PDU received has M=1, T=0, F=1, X = 0, DCOMP = PCOMP = 0,N-PDU number = 0.

4

Verify that the last segment of the first N-PDU received has M=0, T=0, and F=0.

5

Receive the N-PDUs from the MS until N-PDU number becomes 1 and acknowledge all the segments completely.

6

Receive the N-PDUs 2 and 3 from the MS and do not acknowledge the last SN-PDU of N-PDU 3.

7

{Inter-SGSN Routing Area Update – with PSHO}

Macro parameter:

Old XID : K parameter according to tested sequence.

Send the Receive N-PDU number as 3 in the Routing Area Update Accept message.

8

SS->MS

SABM

9

MS->SS

UA

10

MS -> SS

SN-DATA PDU

Verify that the number of octets in the SN-DATA PDU does not exceed N201-I.

Verify that the first SN-DATA PDU received has M=1, T=0, F=1, X = 0, DCOMP = PCOMP = 0, N-PDU number = 3.

Last N-PDU may be not segmented; in which case the M bit shall not be checked.

11

Repeat step 10 until data transfer is completed.

46.2.2.2 Segmentation

46.2.2.2.1 LLC link re-establishment on reception of SN-DATA PDU with F=0 in ack mode in the Receive First Segment state

46.2.2.2.1.1 Conformance Requirement

Receive First Segment state:

– If an SN-DATA PDU is received with the F bit set to 0, the SN-DATA PDU shall be discarded, and the acknowledged LLC operation shall be re-established for the SAPI used.

Reference

3GPP TS 04.65, subclause 6.7.4.1.

46.2.2.2.1.2 Test purpose

To verify that the MS re-establishes the LLC SAPI on reception of an SN-DATA PDU with F=0 as the first segment in the acknowledged mode data transfer.

46.2.2.2.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

PDP Context 13 is initiated from MS.

An acknowledged mode data transfer is started from SS with the first SN_DATA PDU with F=0.

Verify that the MS shall re-establish the LLC SAPI 11.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 13.

2

Initiate acknowledged data transfer for 5000 octets, from the SS.

3

SS -> MS

SN-DATA PDU

Send the first SN-DATA PDU with M=1, T=0, F=0, X = 0, DCOMP = PCOMP = 0,N-PDU number = 0 .

4

MS->SS

SABM

MS re-establishes the LLC SAPI 11

5

SS->MS

UA

6

SS -> MS

SN-DATA PDU

Send the first SN-DATA PDU with M=1, T=0, F=1, X = 0, DCOMP = PCOMP = 0, N-PDU number = 0

7

Repeat step 6 until data transfer is completed. Verify that all SN-DATA PDUs are acknowledged.

46.2.2.2.2 LLC link re-establishment on receiving second segment with F=1 and with different PCOMP and DCOMP values in the acknowledged mode data transfer

46.2.2.2.2.1 Conformance Requirement

Receive Subsequent Segment state:

– If an SN-DATA PDU is received with the F bit set to 1, and if DCOMP, PCOMP or N-PDU number is different from those in the first segment, then the SN-DATA PDU and all previous segments belonging to the same N‑PDU shall be discarded, and the acknowledged LLC operation shall be re-established for the SAPI used.

Reference

3GPP TS 04.65, subclause 6.7.4.2.

46.2.2.2.2.2 Test purpose

To verify that the MS re-establishes the LLC SAPI on reception of the second SN-DATA PDU with F=1 and with PCOMP and DCOMP values different from those of the previous segment, in the second segment in acknowledged mode data transfer.

46.2.2.2.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

PDP Context 13 is initiated from MS.

AN acknowledged mode data transfer is started from SS with the first SN_DATA PDU with F=1. Send the second SN‑DATA PDU from SS with F=1 and with PCOMP and DCOMP values different from those in the first segment.

Verify that the MS shall re-establish the LLC SAPI 11.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 13.

2

Initiate acknowledged data transfer for 5000 octets, from the SS.

3

SS -> MS

SN-DATA PDU

Send the first SN-DATA PDU with M=1, T=0, F=1, X = 0, DCOMP = PCOMP = 0,N-PDU number = 0.

4

SS->MS

SN-DATA PDU

Send the second SN-DATA PDU with M=1, T=0, F=1, X = 0, DCOMP = PCOMP = 1,N-PDU number = 0.

5

MS->SS

SABM

Re-establishment of LLC link on SAPI 11.

6

SS->MS

UA

7

SS -> MS

SN-DATA PDU

Send the first SN-DATA PDU with M=1, T=0, F=1, X = 0, DCOMP = PCOMP = 0, N-PDU number = 0

8

Repeat step 7 until data transfer is completed. Verify that all SN-DATA PDUs are acknowledged.

46.2.2.2.3 Single segment N-PDU from MS

46.2.2.2.3.1 Conformance Requirement

– The F bit in the SNDCP header shall be set to 1 for the first segment, and 0 for all subsequent segments. For unacknowledged peer-to-peer LLC operation, DCOMP and PCOMP shall be included in the header when the F bit is set to 1, and shall not be included when the F bit is set to 0. For acknowledged peer-to-peer LLC operation, DCOMP, PCOMP and N-PDU number shall be included in the header when the F bit is set to 1, and shall not be included when the F bit is set to 0.

– The M bit in the SNDCP header shall be set to 0 for the last segment, and 1 for all previous segments. If only one SN-PDU is generated for an N-PDU, the F bit shall be set to 1 and the M bit set to 0.

Reference

3GPP TS 04.65, subclause 6.7.1.1.

46.2.2.2.3.2 Test purpose

To verify that for a single segment N-PDU, the MS shall send the SN_UNITDATA PDU with F=1 and M=0 during unacknowledged data transfer.

46.2.2.2.3.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

PDP Context 10 is initiated from MS.

An unacknowledged mode data transfer is started from MS for a data size less than N201-U. Verify that the MS sends the SN-UNITDATA PDU with M=0 and F=1.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 10.

2

Initiate unacknowledged data transfer for 1 LLC frame (<= N201-U octets), from the MS.

3

MS -> SS

SN-UNITDATA PDU

Verify that the single SN-UNITDATA PDU is received with M=0 and F=1.

46.2.2.3 Link Release

46.2.2.3.1 LLC link release on receiving DM from the SS during link establishment

46.2.2.3.1.1 Conformance Requirement

If the originator of the establishment procedure receives an LL-RELEASE.indication with Cause "DM received", it shall inform the SM sub-layer using the SNSM-STATUS.request primitive with Cause "DM received". SM shall then deactivate all PDP contexts for that SAPI requiring acknowledged peer-to-peer LLC operation.

Reference

3GPP TS 04.65, subclause 6.2.1.4.

46.2.2.3.1.2 Test purpose

To verify that in MS, the LLC SAPI is released and the PDP context is deactivated on reception of DM response from SS during link establishment.

46.2.2.3.1.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

PDP Context 13 is initiated from MS.

A DM response is sent from SS, after receiving a SABM from the MS for link establishment. The MS shall release the LLC SAPI 11 and the PDP context for the NSAPI shall be deactivated.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 13.

2

MS -> SS

SABM

SABM sent for link establishment during PDP context activation

3

SS->MS

DM

Initiate a DM response with F=1 from the SS.

4

Verify that the MS initiates PDP Context Deactivation.

46.2.2.4 XID negotiation

46.2.2.4.1 Response from MS on receiving XID request from the SS

46.2.2.4.1.1 Conformance Requirement

The XID negotiation is a one-step procedure; i.e., the initiating end proposes parameter values, and the responding end either accepts these or offers different values in their place according to the XID negotiation rules described in the present document; the rules limit the range of parameter values as well as the sense of negotiation. The initiating end accepts (or rejects) the values in the response; this concludes the negotiation.

A bit set to 0 means that the compression entity is not applicable to the corresponding NSAPI. A bit set to 1 means that the compression entity is applicable to the corresponding NSAPI.

Reference

3GPP TS 04.65, subclause 6.8.1.

46.2.2.4.1.2 Test purpose

To verify that:

– the MS which does not support compression, responds with applicable NSAPI field with 0 for an XID request from the SS with some compression entity;

– the MS which supports compression responds with the applicable NSAPI field set to 1 for an XID request from the SS with some compression entity.

46.2.2.4.1.3 Method of test

Initial conditions

Specific PICS statements:

– MS supporting compression has compression turned on (TSPC_AddInfo_GPRS_Data_Compr and/or TSPC_AddInfo_GPRS_Header_Compr).

– Support of GPRS header compression algorithm type RFC 1144 (TSPC_AddInfo_GPRS_Header_Compr_Type_RFC1144)

– Support of GPRS header compression algorithm type RFC 2507 (TSPC_AddInfo_GPRS_Header_Compr_Type_RFC2507)

– Support of ROHC algorithm type RFC 3241 (TSPC_AddInfo_ROHC_Type_RFC3241)

– Support of ROHC algorithm type RFC 3242 (TSPC_AddInfo_ROHC _Type_RFC3242)

– Support of ROHC algorithm type RFC 3408 (TSPC_AddInfo_ROHC _Type_RFC3408)

– Support of ROHC algorithm type RFC 3095 (TSPC_AddInfo_ROHC _Type_RFC3095)

PIXIT statements:

Test procedure

PDP Context 10 is initiated from MS. The MS supporting compression will also trigger an XID negotiation. Modify the PDP Context to PDP Context 9 from the SS.

After PDP context modification, trigger compression by sending an XID Request from SS including a L3-parameter with some compression entity for the NSAPI assigned for the PDP context.

The MS which does not support compression or has a lack of resources shall respond with XID response setting the applicable NSAPI field set to 0, indicating that compression is not supported/wanted.

The MS which support compression and has compression turned on shall respond with XID response setting the applicable NSAPI field set to 1, indicating that compression is supported. The MS may choose to not include an SNDCP XID parameter in its response (implicit response), which is equivalent to responding with the value proposed by the SS.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 10. The MS supporting compression will also trigger an XID negotiation.

2

{PDP Context Modification}

Macro. Initiate PDP Context Modification from the SS. The new context is PDP Context 9. If the MS supports compression, SS triggers an XID negotiation in order to remove the PDP Context from the Applicable NSAPIs of the compression entities negotiated in step 1.

3

SS -> MS

XID Request

In the layer3 XID parameters, send a PCOMP entity with parameter type = 2, entity number = 1 and algorithm type, which the MS supports or 0 if the MS does not have support of header compression, a DCOMP entity with parameter type = 1, entity number = 1 and algorithm type = 0. In the applicable NSAPI field, set the bit for the NSAPI assigned for the PDP context.

A4

MS -> SS

XID Response

Verify that the MS which does not support compression, has compression turned off or has a lack of resources responds with the assigned NSAPI field set to 0.

B4

MS -> SS

XID Response

Verify that the MS which supports compression and has compression turned on responds either with the assigned NSAPI field set to 1 or without including the relevant L3 XID parameter (implicit response).

5

Initiate unacknowledged data transfer for 5000 octets, from the MS.

6

MS -> SS

SN-UNITDATA PDU

Verify that the number of octets in the SN-UNITDATA PDUs does not exceed N201-U.

A7

For mobiles which do not support compression, verify that the first SN-UNITDATA PDU received has M=1, T=1, F=1, X = 0, DCOMP = PCOMP = 0,N-PDU number = 0.

B7

For mobiles which support compression such that the SN-UNITDATA-PDU needs to be segmented, verify that the first SN-UNITDATA PDU received has M=1, T=1, F=1, X = 0, DCOMP = the negotiated value (assuming that data is compressible), PCOMP = the negotiated value (assuming that data contains an valid TCP/IP header) or 0 (data did not contain a valid TCP/IP header), N-PDU number = 0.

C7

For mobiles which support compression such that the SN-UNITDATA-PDU does not need to be segmented, verify that the first SN-UNITDATA PDU received has M=0, T=1, F=1, X = 0, DCOMP = the negotiated value (assuming that data is compressible), PCOMP = the negotiated value (assuming that data contains an valid TCP/IP header) ) or 0 (data did not contain a valid TCP/IP header), N-PDU number = 0. Go to step 9.

A8, B8

Verify that the last segment of the first N-PDU received has M=0, T=1, and F=0.

The last segment of last N-PDU may be not segmented; the F bit shall not be checked.

9

Verify that for the subsequent N-PDUs, the N-PDU number is incremented properly

10

Repeat step 6 to 9 until data transfer is complete.

46.2.2.4.2 Response from MS on receiving an XID request from the SS with an unassigned entity number

46.2.2.4.2.1 Conformance Requirement

In the originating SNDCP XID block, if an unassigned entity number is included with the P bit set to 0, then the Applicable NSAPIs field in the response shall be set to 0.

Reference

3GPP TS 04.65, subclause 6.8.3.

46.2.2.4.2.2 Test purpose

To verify that in the originating SNDCP XID block, if an unassigned entity number is included with the P bit set to 0, the Applicable NSAPIs field in the response shall be set to 0.

46.2.2.4.2.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

PDP Context 10 is initiated from MS.

Send an XID command from the SS with P bit set to 0, with an unassigned entity number.

The MS shall respond with XID response setting the applicable NSAPI field set to 0, indicating that compression is not supported.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 10.

2

SS -> MS

XID

In the layer3 XID parameters, send a PCOMP entity with parameter type = 2. Set the P bit to 0 and the entity number to a number not assigned.

3

MS -> SS

XID

Verify that the MS responds with the assigned NSAPI field set to 0.

46.2.2.4.3 Response from MS on receiving an XID response from the SS with unrecognised type field

46.2.2.4.3.1 Conformance Requirement

If the responding SNDCP XID block includes a parameter with unrecognised Type field, unsupported length, an out‑of‑range value or a value violating the sense of negotiation, a parameter type 1 or 2 which violates the rules in subclause 6.8.1, a parameter with duplicated instances, contains prohibited changes (see subclauses 6.5.1.2 and 6.6.1.2) to the parameters of compression entities used with acknowledged peer-to-peer LLC operation when the SNDCP XID block is sent on LL-XID primitives, or a compression field with the P bit set to 1, then the originator shall ignore the block and reinitiate the negotiation.

Reference

3GPP TS 04.65, subclause 6.8.3.

46.2.2.4.3.2 Test purpose

To verify that in the XID response, if an unrecognised type field is specified, the originator shall ignore the block and reinitiate XID negotiation.

46.2.2.4.3.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

PDP Context 11 is initiated from MS.

In the response to SABM, in the UA, send SNDCP parameter type = 30.

The MS shall resend the SABM command or send an XID command.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 11.

2

MS -> SS

SABM

3

SS -> MS

UA

Include an SNDCP XID parameter with parameter type = 30.

4

MS -> SS

XID Command

Or

SABM command

Verify that the MS sends an XID Command or resends the SABM command

46.2.2.5 LLC link release on receiving "Invalid XID response" from the network during link establishment procedure

46.2.2.5.1 Conformance Requirement

If the originator of the establishment procedure receives an LL-RELEASE.indication with Cause "Invalid XID response", it shall inform the SM sub-layer using the SNSM-STATUS.request primitive with Cause "Invalid XID response". SM shall then deactivate all PDP contexts for that SAPI.

Reference

3GPP TS 04.65, subclause 6.2.1.4.

3GPP TS 04.64, subclause 8.5.3.3.

46.2.2.5.2 Test purpose

To verify that in the MS, the PDP context is deactivated on reception of "Invalid XID response" from network during link establishment.

46.2.2.5.3 Method of test

Initial conditions

Specific PICS statements:

PIXIT statements:

Test procedure

Activation of PDP Context 13 is initiated from MS.

The MS sends a SABM from the MS for link establishment.

The SS responds to the SABM with a UA with Invalid XID information field.

The MS shall ignore this response and re-transmit the SABM N200 times.

The SS shall respond with the UA with Invalid XID information, N200 times.

Verify that the MS releases the LLC SAPI and the PDP context for the SAPI is deactivated.

Maximum duration of the test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

{PDP Context Activation}

Macro. Initiate PDP context activation from the MS. Use PDP context 13.

2

MS -> SS

SABM

SABM sent for link establishment during PDP context activation

3

SS->MS

UA

In response to the SABM , SS sends UA with an Invalid XID information field.

MS shall ignore this response and Re-transmit the SABM N200 times.

4

Repeat steps 2 and 3 N200 times. (Send UA with Invalid XID parameters in response to SABM received N200 times.)

5

{PDP Context De-Activation}

Verify that the MS initiates PDP Context Deactivation.