hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.4.3.1.2 Test purpose
|
To test the behaviour of the MS when the network does not reply to a DEACTIVATE PDP CONTEXT REQUEST message from the MS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.4.3.1.3 Method of test
|
Specific PICS statements:
-
PIXIT statements:
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Test procedure
A PDP context is activated by the user and accepted by the SS. A context deactivation is then requested by the user. The MS shall send a DEACTIVATE PDP CONTEXT REQUEST message five times with T3390 ±10% seconds between each message. T3390 +10 % seconds after the fifth message the SS shall send a MODIFY PDP CONTEXT REQUEST message for the deactivated context and the MS shall reply with SM STATUS with cause set to #81 'Transaction identifier not known'.
Maximum duration of test
5 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
Initiate a context activation
2
MS -> SS
ACTIVATE PDP CONTEXT REQUEST
Activate a PDP context
3
SS -> MS
ACTIVATE PDP CONTEXT ACCEPT
Accept the PDP context
4
MS
Initiate a context deactivation
5
MS -> SS
DEACTIVATE PDP CONTEXT REQUEST
Request a deactivation of a PDP context
6
SS
T3390 ±10% seconds
7
MS -> SS
DEACTIVATE PDP CONTEXT REQUEST
Request a deactivation of a PDP context
8
SS
T3390 ±10% seconds
9
MS -> SS
DEACTIVATE PDP CONTEXT REQUEST
Request a deactivation of a PDP context
10
SS
T3390 ±10% seconds
11
MS -> SS
DEACTIVATE PDP CONTEXT REQUEST
Request a deactivation of a PDP context
12
SS
T3390 ±10% seconds
13
MS -> SS
DEACTIVATE PDP CONTEXT REQUEST
Request a deactivation of a PDP context
14
SS
Wait T3390 +10% seconds
15
SS -> MS
MODIFY PDP CONTEXT REQUEST
Try to modify the deactivated context.
16
MS -> SS
SM STATUS
Cause set to #81
Specific message contents
As default except:
Activate PDP Context Request
Information Element
Value/remark
Transaction identifier
In the range 0-6
Transaction identifier flag
0
NSAPI
In the range 5-15
Requested LLC SAPI
3, 5, 9 or 11
Requested QoS
Arbitrarily chosen
Requested PDP address
Arbitrarily chosen
Activate PDP Context Accept
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
1
Negotiated LLC SAPI
As above
Negotiated QoS
As above
Radio priority level
Arbitrarily chosen
Spare half octet
0
Deactivate PDP Context Request
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
0
SM cause
Regular Deactivation
Modify PDP Context Request
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
1
Radio priority level
As above
Spare half octet
0
Requested LLC SAPI
As above
New QoS
As above
SM Status
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
0
SM Cause
#81
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.4.3.2 Collision of MS and network initiated PDP context deactivation requests
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.4.3.2.1 Conformance requirement
|
If the MS and the network initiated PDP context deactivation requests collide, the MS and the network shall each reply with the message DEACTIVATE PDP CONTEXT ACCEPT and shall stop timer T3390 and T3395, respectively.
Reference
3GPP TS 04.08 / 3GPP TS 24.008 subclause 6.1.3.3.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.4.3.2.2 Test purpose
|
To test the behaviour of the MS when there is a collision between an MS initiated and a network initiated context deactivation.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.4.3.2.3 Method of test
|
Specific PICS statements:
-
PIXIT statements:
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Test procedure
A PDP context is activated by the user and accepted by the SS. A context deactivation is then requested by the user. Upon receipt of the DEACTIVATE PDP CONTEXT REQUEST message the SS sends a DEACTIVATE PDP CONTEXT REQUEST message. The MS shall reply with only one DEACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of this message the SS sends a DEACTIVATE PDP CONTEXT ACCEPT message.
Maximum duration of test
5 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
Initiate a context activation
2
MS -> SS
ACTIVATE PDP CONTEXT REQUEST
Activate a PDP context
3
SS -> MS
ACTIVATE PDP CONTEXT ACCEPT
Accept the PDP context
4
MS
Initiate a context deactivation
5
MS -> SS
DEACTIVATE PDP CONTEXT REQUEST
Request a deactivation of a PDP context
6
SS -> MS
DEACTIVATE PDP CONTEXT REQUEST
Request a deactivation of a PDP context
7
MS -> SS
DEACTIVATE PDP CONTEXT ACCEPT
Accept the PDP context deactivation
8
SS -> MS
DEACTIVATE PDP CONTEXT ACCEPT
Accept the PDP context deactivation
Specific message contents
As default except:
Activate PDP Context Request
Information Element
Value/remark
Transaction identifier
In the range 0-6
Transaction identifier flag
0
NSAPI
In the range 5-15
Requested LLC SAPI
3, 5, 9 or 11
Requested QoS
Arbitrarily chosen
Requested PDP address
Arbitrarily chosen
Activate PDP Context Accept
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
1
Negotiated LLC SAPI
As above
Negotiated QoS
As above
Radio priority level
Arbitrarily chosen
Spare half octet
0
Deactivate PDP Context Request (used in step 5)
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
0
SM cause
Regular Deactivation
Deactivate PDP Context Request (used in step 6)
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
1
SM cause
Regular Deactivation
Deactivate PDP Context Accept (used in step 7)
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
0
Deactivate PDP Context Accept (used in step 8)
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.4.4 PDP context deactivation initiated by the network / Tear down indicator
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.4.4.1 Conformance requirement
|
The PDP context deactivation may be initiated by the MS or by the network. The tear down indicator information element may be included in the DEACTIVATE PDP CONTEXT REQUEST message in order to indicate whether only the PDP context associated with this specific TI or all active PDP contexts sharing the same PDP address as the PDP context associated with this specific TI shall be deactivated. If the tear down indicator information element is not included in the DEACTIVATE PDP CONTEXT REQUEST message, only the PDP context associated with this specific TI shall be deactivated.
The Tear down indicator IE is included in the message in order to indicate whether only the PDP context associated with this specific TI or all active PDP contexts sharing the same PDP address as the PDP context associated with this specific TI shall be deactivated.
Reference
3GPP TS 24.008 subclauses 6.1.3.4, 8.3.2 (b) and 9.5.14.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.4.4.2 Test purpose
|
To test the behaviour of the MS upon receipt of a DEACTIVATE PDP CONTEXT REQUEST message from the network including Tear down indicator IE.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.4.4.3 Method of test
|
Specific PICS statements:
-
PIXIT statements:
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Test procedure
A PDP context is activated by the user and accepted by the SS. A Secondary PDP context is activated by the user and accepted by the SS. A DEACTIVATE PDP CONTEXT REQUEST message is then sent by the SS indicating the TI of second PDP context and including Tear down indicator IE. The MS shall reply with a DEACTIVATE PDP CONTEXT ACCEPT message. The SS shall then send a MODIFY PDP CONTEXT REQUEST including the TI of second PDP context and the MS shall reply with an SM STATUS message with cause #81 'transaction identifier not known'. The SS shall then send a MODIFY PDP CONTEXT REQUEST including the TI of the first PDP context and the MS shall reply with an SM STATUS message with cause #81 'transaction identifier not known'.
Maximum duration of test
5 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
Initiate a context activation
2
MS -> SS
ACTIVATE PDP CONTEXT REQUEST
Activate a PDP context
3
SS -> MS
ACTIVATE PDP CONTEXT ACCEPT
Accept the PDP context
4
MS
Initiate a secondary PDP context activation
5
MS -> SS
ACTIVATE SECONDARY PDP CONTEXT REQUEST
Request a Secondary PDP context activation
6
SS -> MS
ACTIVATE SECONDARY PDP CONTEXT ACCEPT
Accept the Secondary PDP context activation
7
SS -> MS
DEACTIVATE PDP CONTEXT REQUEST
Request a deactivation of a PDP context. Include TI of second PDP context and Tear down indicator flag set to 1.
8
MS -> SS
DEACTIVATE PDP CONTEXT ACCEPT
Accept the PDP context deactivation.
TI is the same as step 7.
9
SS -> MS
MODIFY PDP CONTEXT REQUEST
Send a modify request including the TI of second PDP context.
10
MS -> SS
SM STATUS
Cause set to #81
11
SS -> MS
MODIFY PDP CONTEXT REQUEST
Send a modify request including the TI of first PDP context.
12
MS -> SS
SM STATUS
Cause set to #81
Specific message contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.5 Unknown or Unforeseen Transaction Identifier/Non-semantical Mandatory Information Element Errors
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.5.1 Error cases
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.5.1.1 Conformance requirement
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.5.1.1.1 Conformance requirement for release 98 and earlier MS
|
The mobile station shall reject a session management message other than SM-STATUS received with TI value "111" by immediately sending an SM-STATUS message with TI value "111". For a session management message received with TI different from "111", the following procedures shall apply:
- Whenever any session management message except REQUEST PDP CONTEXT ACTIVATION or SM-STATUS is received by the MS specifying a transaction identifier which is not recognised as relating to an active context or to a context that is in the process of activation or deactivation or has been [recently] deactivated, the MS shall send a SM-STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value and remain in the PDP-INACTIVE state.
- When a REQUEST PDP CONTEXT ACTIVATION message is received with a transaction identifier flag set to "1", this message shall be ignored.
When on receipt of a message:
- an "imperative message part" error; or
- a "missing mandatory IE" error;
is diagnosed or when a message containing:
- a syntactically incorrect mandatory IE; or
- an IE unknown in the message, but encoded as "comprehension required"; or
- an out of sequence IE encoded as "comprehension required";
is received, the mobile station shall proceed as follows:
- If the message was an SM message the SM-STATUS message with cause # 96 "invalid mandatory information" shall be returned.
- If a mobile station receives a GMM message or SM message with message type not defined for the PD or not implemented by the receiver, it shall return a status message (GMM STATUS or SM STATUS depending on the protocol discriminator) with cause #97 'message type non-existent or not implemented'.
- If the mobile station receives a message not compatible with the protocol state, the mobile station shall ignore the message except for the fact that, if an RR connection exists, it returns a status message (STATUS, MM STATUS depending on the protocol discriminator) with cause #98 "Message type not compatible with protocol state". When the message was a GMM message the GMM-STATUS message with cause #98 "Message type not compatible with protocol state" shall be returned. When the message was a SM message the SM-STATUS message with cause #98 'Message type not compatible with protocol state' shall be returned.
- Other syntactic errors.
This subclause applies to the analysis of the value part of an information element. It defines the following terminology:
- An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as 'reserved', or if its value part violates syntactic rules given in the specification of the value part. However it is not a syntactical error that a type 4 standard IE specifies in its length indicator a greater length than possible according to the value part specification: extra bits are ignored.
Reference
3GPP TS 04.08 subclauses 8.3.2 and 8.5.
3GPP TS 04.07 subclause 11.4.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.5.1.1.2 Conformance requirement for release 99 and later MS
|
The mobile station and network shall ignore a session management message with TI EXT bit = 0. Otherwise, the following procedures shall apply:
- Whenever any session management message except REQUEST PDP CONTEXT ACTIVATION or SM-STATUS is received by the MS specifying a transaction identifier which is not recognized as relating to an active context or to a context that is in the process of activation or deactivation, the MS shall send a SM-STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value including the extension octet and remain in the PDP-INACTIVE state.
- When REQUEST PDP CONTEXT ACTIVATION message is received with a transaction identifier flag set to "1", this message shall be ignored.
When on receipt of a message,
- an "imperative message part" error; or
- a "missing mandatory IE" error;
is diagnosed or when a message containing:
- a syntactically incorrect mandatory IE; or
- an IE unknown in the message, but encoded as "comprehension required" (see 3GPP TS 24.007); or
- an out of sequence IE encoded as "comprehension required" (see 3GPP TS 24.007) is received,
the mobile station shall proceed as follows:
If the message is not one of the messages listed in subclauses 8.5.1, 8.5.2, 8.5.3, 8.5.4 and 8.5.5 a) or b), the mobile station shall ignore the message except for the fact that, if an RR connection exists, it shall return a status message (STATUS, MM STATUS depending on the protocol discriminator) with cause # 96 "Invalid mandatory information". If the message was a GMM message the GMM-STATUS message with cause #96 " Invalid mandatory information" shall be returned. If the message was an SM message the SM-STATUS message with cause # 96 "invalid mandatory information" shall be returned.
- the network shall proceed as follows:
When the message is not one of the messages listed in subclause 8.5.3 b), c), d) or e) and 8.5.5 a) or c), the network shall either:
- try to treat the message (the exact further actions are implementation dependent), or
- ignore the message except that it should return a status message (STATUS, or MM STATUS (depending on the protocol discriminator), GMM STATUS, or SM STATUS) with cause # 96 "Invalid mandatory information".
This subclause applies to the analysis of the value part of an information element. It defines the following terminology:
- An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as 'reserved', or if its value part violates syntactic rules given in the specification of the value part. However it is not a syntactical error that a type 4 standard IE specifies in its length indicator a greater length than possible according to the value part specification: extra bits are ignored.
Reference
3GPP TS 24.008 subclauses 6.1, 8.3.2, 8.5 and 9.5.2.1.
3GPP TS 24.007 subclause 11.4.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.5.1.2 Test Purpose
|
To test the behaviour of the MS when messages with unknown or unforeseen transaction identifiers or non-semantical mandatory information element errors occur.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
45.5.1.3 Method of test
|
Specific PICS statements:
- MS Higher Layer Release (TSPC_MS_HIGHER_LAYER_RELEASE)
PIXIT statements:
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Test procedure
A PDP context activation is requested by the SS with the transaction identifier set to '1'. The MS shall not respond to this request.
A PDP context is then activated from the MS. An invalid accept message is then sent by the SS. The MS shall then send an SM STATUS message. After the MS has sent an ACTIVATE PDP CONTEXT REQUEST message the SS sends a MODIFY PDP CONTEXT REQUEST message with the same transaction identifier. The MS shall reply with an SM STATUS message with the cause set to #98 'Message type not compatible with protocol state'.
After T3380 has expired 10% seconds the MS shall send another ACTIVATE PDP CONTEXT REQUEST message. The SS sends back a Session Management message with an unknown message type. The MS shall reply with an SM STATUS message with the cause set to #97 'Message type non-existent or not implemented'.
After a further T3380 has expired the MS shall send another ACTIVATE PDP CONTEXT REQUEST message 10% seconds. Another invalid accept message is sent by the SS.
After a further T3380 has expired 10% seconds a valid accept message with QoS length greater than 3 is sent by the SS. This shall be accepted by the MS.
A deactivate message is then sent from the SS coded with the extension mechanism for TI. Therefore the TIO value is set to 111 and the transaction identifier extension TIE is set to an unused value greater than 6(no reserved value) . A MS implemented release 98 or earlier should reply with an SM STATUS message with transaction identifier set to '111'. A Rel.99 MS shall reply with an SM STATUS message with cause #81 'invalid transaction identifier value'.
A deactivate message is then sent from the SS with a different transaction identifier to the one used in the activate request message sent by the MS. The MS shall reply with an SM STATUS message with cause #81 'invalid transaction identifier value'.
Two invalid modification messages are then sent to the MS in turn. The MS shall respond each time with an SM-STATUS message with cause # 96 "invalid mandatory information".
Maximum duration of test
5 minutes.
Expected sequence
Step
Direction
Message
Comments
1
SS -> MS
REQUEST PDP CONTEXT ACTIVATION
Request the activation of a PDP context with the transaction identifier flag set to "1"
2
SS
Wait 30 seconds to ensure MS does not request context activation
3
MS
Initiate a context request
4
MS -> SS
ACTIVATE PDP CONTEXT REQUEST
Activate a PDP context from the MS
5
SS -> MS
ACTIVATE PDP CONTEXT ACCEPT
Unknown IE encoded as 'comprehension required'
6
MS -> SS
SM STATUS
Cause set to #96
7
MS -> SS
ACTIVATE PDP CONTEXT REQUEST
Activate a PDP context from the MS (auto-generated)
This message shall be sent within T3380 seconds ±10% from the last ACTIVATE PDP CONTEXT REQUEST message
8
SS -> MS
MODIFY PDP CONTEXT REQUEST
Request the modification of the PDP context
9
MS -> SS
SM STATUS
Cause set to #98 'Message type not compatible with protocol state'.
10
MS -> SS
ACTIVATE PDP CONTEXT REQUEST
Activate a PDP context from the MS (auto-generated)
This message shall be sent within T3380 seconds ±10% from the last ACTIVATE PDP CONTEXT REQUEST message
11
SS -> MS
UNKNOWN MESSAGE
Message with unknown message type
12
MS -> SS
SM STATUS
Cause set to #97 'message type non-existent or not implemented'.
13
MS -> SS
ACTIVATE PDP CONTEXT REQUEST
Activate a PDP context from the MS (auto-generated)
This message shall be sent within T3380 seconds ±10% from the last ACTIVATE PDP CONTEXT REQUEST message
14
SS -> MS
ACTIVATE PDP CONTEXT ACCEPT
Out of sequence IE encoded as 'comprehension required'
15
MS -> SS
SM STATUS
Cause set to #96
16
MS -> SS
ACTIVATE PDP CONTEXT REQUEST
Activate a PDP context from the MS (auto-generated)
This message shall be sent within T3380 seconds ±10% from the last ACTIVATE PDP CONTEXT REQUEST message
17
SS -> MS
ACTIVATE PDP CONTEXT ACCEPT
Accept the PDP context
-
Step 18A, 19A is performed for release 98 and earlier MS and step 18B, 19B for release 99 and later MS implementation
18A
SS -> MS
DEACTIVATE PDP CONTEXT REQUEST
TI set to "111"
18B
SS -> MS
DEACTIVATE PDP CONTEXT REQUEST
TIO=111 and TIE=not used value greater than 6
19A
MS -> SS
SM STATUS
TI set to "111", cause value not checked
19B
MS->SS
SM STATUS
with cause #81 "invalid transaction identifier value
20
SS -> MS
DEACTIVATE PDP CONTEXT REQUEST
Try to deactivate the context with a different transaction identifier to that used to activate the context
21
MS -> SS
SM STATUS
Cause set to # 81
22
SS -> MS
MODIFY PDP CONTEXT REQUEST
Request the modification of the PDP context
23
MS -> SS
SM STATUS
Cause set to # 96
24
SS -> MS
MODIFY PDP CONTEXT REQUEST
Request the modification of the PDP context
25
MS -> SS
SM STATUS
Cause set to # 96
Specific message contents
As default except:
Request PDP Context Activation
Information Element
Value/remark
Transaction identifier
In the range 0-6
Transaction identifier flag
1
Offered PDP address
Arbitrarily chosen
Activate PDP Context Request
Information Element
Value/remark
Transaction identifier
In the range 0-6
Transaction identifier flag
0
NSAPI
In the range 5-15
Requested LLC SAPI
3, 5, 9 or 11
Requested QoS
Arbitrarily chosen
Requested PDP address
Arbitrarily chosen
Activate PDP Context Accept (used in step 5)
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
1
Negotiated LLC SAPI
As above
Negotiated QoS
As above
Radio priority level
Arbitrarily chosen
Spare half octet
0
PDP address
Arbitrarily chosen
'Comprehension required IE'
0Fh NOTE: first four bits encoded as 'comprehension required'
Activate PDP Context Accept (used in step 14)
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
1
Negotiated LLC SAPI
As above
Negotiated QoS
As above
Radio priority level
Arbitrarily chosen
Spare half octet
0
PDP address
omitted
'Comprehension required IE'
07h NOTE: first four bits encoded as 'comprehension required'
Protocol configuration options
Minimum length with Configuration protocol of 'PPP'
Activate PDP Context Accept (used in step 17)
Information Element
Value/remark
Transaction identifier
As above
Transaction identifier flag
1
Negotiated LLC SAPI
As above
Negotiated QoS
As above but
For R97 and R98 : Length set to 5 and 2 extra octets set to 0 after the normal QoS octets
For R99 and Rel-4 : Length set to 13 and 2 extra octets set to 0 after the normal QoS octets
For Rel-5 and later: Length set to 16 and 2 extra octets set to 0 after the normal QoS octets
For Rel-7 and later: Length set to 18 and 2 extra octets set to 0 after the normal QoS octets
Radio priority level
Arbitrarily chosen
Spare half octet
0
PDP address
Arbitrarily chosen
Deactivate PDP Context Request (used in step 18)
Information Element
Value/remark
Transaction identifier
111
Transaction identifier flag
1
SM cause
24h, regular deactivation
Deactivate PDP Context Request (used in step 20)
Information Element
Value/remark
Transaction identifier
In the range 0-6, but different from the TI in the Activate PDP Context Request message
Transaction identifier flag
1
SM cause
24h, regular deactivation
Modify PDP Context Request (used in step 22)
Information Element
Value/remark
Transaction identifier
As in step 17
Transaction identifier flag
1
Radio priority level
As above
Spare half octet
0
Requested LLC SAPI
As above
New QoS
This IE will NOT be present
Modify PDP Context Request (used in step 24)
Information Element
Value/remark
Transaction identifier
As in step 17
Transaction identifier flag
1
Radio priority level
As above
Spare half octet
0
Requested LLC SAPI
Fh, NOTE: this is a reserved value
New QoS
Arbitrary value
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46 LLC and SNDCP Tests
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1 LLC Tests
|
This subclause contains the test case requirements for Logical Link Control (LLC) procedures in the General Packet Radio Service (GPRS).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2 Test cases
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.1 Unacknowledged data transfer
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.1.1 Data transmission in protected mode
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.1.1.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.
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 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. 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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.1.2 Data transmission in unprotected mode
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.1.3 Reception of I frame in ADM
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2 Acknowledged data transfer
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.1 Link establishment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.1.1 Link establishment from MS to SS
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.1.1.2 Test purpose
|
To test the establishment of acknowledged mode data transfer from the MS to the SS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.1.2 Link establishment from SS to MS
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.1.3 Loss of UA frame
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.1.3.2 Test purpose
|
To test the MS response to the loss of a UA frame during link establishment.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.1.4 Total loss of UA frame
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.1.5 DM response
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.2 MS sends I+S frames
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.2.1 Checking N(S)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.2.1.2 Test purpose
|
To verify that the MS handles the send sequence number N(S) correctly.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.2.2 Busy condition at the peer, with RR sent for resumption of transmission
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.2.3 Busy condition at the peer, with ACK sent for resumption of transmission
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.2.4 SACK frame
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.3 Reception of I + S frames at the MS
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.3.1 Checking N(R)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.3.1.2 Test purpose
|
To verify that the MS transmits acknowledgements with the correct N(R).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.3.2 MS handling busy condition during bi-directional data transfer
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.3.3 SACK frame
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.3.4 ACK frame
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.4 Link Reestablishment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.4.1 Reestablishment due to reception of SABM
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.4.2 Reestablishment due to N200 failures
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
46.1.2.2.4.3 Reestablishment due to reception of DM
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.