hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.3 Collision of commands and responses
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.3.1 Collision of SABM
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.3.3 Collision of SABM and XID commands
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.4 Unsolicited response frames
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.4.1 Unsolicited DM
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.5 FRMR frames
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.5.1 Sending FRMR due to undefined command control field
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.5.2 Sending FRMR due to reception of an S frame with incorrect length
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.5.3 Sending FRMR due to reception of an I frame information field exceeding the maximum length
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.5.4 Frame reject condition during establishment of ABM
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.6 Multiple Connections
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.6.1 Simultaneous acknowledged and unacknowledged data transfer on the same SAPI
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.6.2 Simultaneous acknowledged and unacknowledged data transfer on different SAPIs
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.7 XID Negotiation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.7.1 Negotiation initiated by the SS during ABM, for T200 and N200
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.7.2 Negotiation initiated by the SS during ADM, for N201-I
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.7.3 Negotiation initiated by the SS (using XID, for IOV-UI)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.7.3.3 Method of test
|
Initial conditions
For parameter K = 4 (GEA4) Test USIM has to be plugged into the MS. The MS shall be GPRS attached with ciphering enabled. Encryption GEA3 or GEA4 is used depending on the parameter K.
Specific PICS statements:
- Supported encryption Algorithm: GEA3 (TSPC_Feat_GEA3)
- Supported encryption Algorithm: GEA4 (TSPC_Feat_GEA4)
PIXIT statements:
-
Test procedure
During GPRS attach ciphering GEA3 or GEA4 is activated depending on the parameter 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 parameter 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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.7.4 Negotiation initiated by the SS (during ADM, for N201-U)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.7.5 Negotiation initiated by the SS (during ADM, for IOV-UI)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.7.5.3 Method of test
|
Initial conditions
- For parameter K = 4 (GEA4) Test USIM has to be plugged into the MS.
Specific PICS statements:
- 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 parameter 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:
GEA3 for K=3,
GEA4 for K=4.
3
MS -> SS
UI [Authentication and Ciphering Response]
For K=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 = 3
Present for K = 4
Ciphering Algorithm
Type of Algorithm
GEA/3 for K = 3
GEA/4 for K = 4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.7.7 XID command with unrecognised type field
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.7.7.2 Test purpose
|
To test the MS response to an XID command with an unrecognised type field.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.7.8 XID Response with out of range values
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.2.2 Test cases
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.2.2.1 Data transfer
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.2.2.1.1 Mobile originated normal data transfer with LLC in acknowledged mode
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.2.2.1.3 Usage of acknowledged mode for data transmission before and after PDP Context modification, on different SAPIs
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.2.2.1.4 Reset indication during unacknowledged mode
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.2.2.1.5 Reset indication during acknowledged mode
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.2.2.1.6 Inter SGSN (with NAS container / new Routing Area / SGSN indicated Reset) PS Handover / Synchronized cell case / successful
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.2.2.2 Segmentation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.2.2.2.3 Single segment N-PDU from MS
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.