T 1 S 000098

TSG-T Working Group1 SWG SIG meeting #11 TSGT1S- 000098
Harpenden , UK 5-7 June, 2000
Agenda Item:
Source: NEC
Title: Update on section 11. Session Management in 3G TS 34.123 1,

section 11.4 Error Handling Procedures
Document for: Discussion
Introduction
The SM Clause that we are proposing in this document is an update of clause 8.4 in 3G TS 34.123-1 v1.0.0
to align test specification with current core specs and GSM test specification.
Summary
Changes since T1S 000046 was discussed are:

The last test in T1S 000046 document, 8.4.4 Unknown or Unforeseen Transaction Identifier/Non-
semantical Mandatory Information Element Errors covers all error handling procedures. Since there are
currently theree or four cases to be tested, having them all tested in the same test makes the test
difficult to understand and maintain. There are still errors in this test in GSM, so I propose to split it in
a number of smaller tests which will be easier to maintain.
Proposal
NEC is proposing not to put the section 11.4 Error Handling Procedures in current version of TS34.123-1 and
to add it later after having it discussed and approved at one of following meetings.
References
[1] 3G TS 34.123-1 V1.0.0 (1999-12) ; User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification.
[2] GSM 11.10-1 V7.0.0 ; Mobile Station (MS) conformance specification; Part 1:Conformance specification
(Draft EN 300 607-1 V7.0.0 (1999-07))
[3] 3G TS 24.008 V3.3.0;(2000-01); Mobile radio interface layer 3 specification, Core Network Protocols
Stage 3)
[4] 3G TS 24.007 v3.2.0 (1999-12); Mobile radio interface signalling layer 3 ; General aspects
[5] 3G TS 27.060 v3.3.0 Release 1999; Mobile Station (MS) supporting Packet Switched Services
[6] 3G TS 23.060 v3.2.1 (2000-10) ; General Packet Radio Service (GPRS); Service description; Stage 2
[7] Tdoc SMG7 GPRS 011/00 ver 2.0 ; ETSI SMG7 GPRS, Oulu 14-17 March 2000
[8] TSGT1S-000046 TSG-T Working Group 1 SWG SIG meeting #10, Yokohama, Japan, 17-19 April 2000
11.4 Error Handling Procedures

11.4.1 Unknown or Unforeseen Transaction Identifier/Non-semantical
Mandatory Information Element Errors
11.4.1 Error cases

(Editors note: This test is likely to change due to changes introduced in core specification.)
11.4.1.1 Conformance requirement
11.4.1.1.1 Definition and applicability

This test is applicable for UE supporting PS domain services.
11.4.1.1.2 Conformance requirement
The mobile station shall ignore a session management message with TI EXT bit = 0. Otherwise, the following
procedures shall apply:
The UE 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 UE 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 UE 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 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 UE shall proceed as follows:
If the message was a SM message the SM-STATUS message with cause # 96 invalid mandatory information shall be
returned.
Reference
3G TS 24.008 sections subclause 8.3.2 and 8.5.

3G TS 24.007 section 11.4.2.
11.4.1.1.3 Test purpose
To test the behaviour of the UE when Session Management messages with unknown or unforeseen transaction
identifiers or non-semantical mandatory information element errors occurare received.
11.4.1.1.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
3GPP
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Related ICS/IXIT statements
-
Test procedure
A PDP context activation is requested by the SS with the transaction identifier set to 1. The UE shall not respond to
this request.
A PDP context is then activated from the UE and accepted from SS. 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 UE. The UE shall reply with
a SM STATUS message with cause #81 invalid transaction identifier value and transaction identifier same as one used
in deactivate message.
A modify message is then sent from the SS with a different transaction identifier to the one used in the activate request
message sent by the UE. The UE shall reply with a SM STATUS message with cause #81 invalid transaction identifier
value and transaction identifier same as one used in modify message.
A modify request message is then sent from the SS with transaction identifier equal to the one used in the activate
request message sent by the UE. The UE shall reply with a modify accept message.
Two invalid accept messages are then sent by the SS with T3380 seconds between them. After a further T3380 seconds
a valid accept message is sent by the SS.
A deactivate message is then sent from the SS with the transaction identifier set to 111. The UE shall reply with a SM
STATUS message with transaction identifier set to 111.
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 UE. The UE shall reply with a SM STATUS message with cause #81 invalid transaction
identifier value.
Three invalid modification messages are then sent to the UE in turn. The UE shall respond each time with a SM-
STATUS message with cause # 96 invalid mandatory information.
3GPP
Expected sequence
Step Direction Message Comments

UE SS
1 REQUEST PDP CONTEXT Request the activation of a PDP context with the
ACTIVATION transaction identifier flag set to 1
2 SS Wait 30 seconds to ensure UE does not request
context activation
3 UE Initiate a context request
4 ACTIVATE PDP CONTEXT Activate a PDP context from the UE
REQUEST
5 ACTIVATE PDP CONTEXT Unknown IE encoded as comprehension
ACCEPT required
6 SM STATUS Cause set to #96
7 SS Wait T3380 seconds 10%
8 ACTIVATE PDP CONTEXT Activate a PDP context from the UE (auto-
REQUEST generated)
9 ACTIVATE PDP CONTEXT Out of sequence IE encoded as comprehension
ACCEPT required
10 SM STATUS Cause set to #96
11 SS Wait T3380 seconds 10%
REQUEST generated)
135 ACTIVATE PDP CONTEXT Accept the PDP context
ACCEPT
14 DEACTIVATE PDP CONTEXT TI set to 111
REQUEST
15 SM STATUS TI set to 111
166 DEACTIVATE PDP CONTEXT Try to deactivate the context with a different
REQUEST transaction identifier to that used to activate the
context
177 SM STATUS Cause set to # 81 invalid transaction identifier
value and transaction identifier received in
DEACTIVATE PDP CONTEXT REQUEST
18 MODIFY PDP CONTEXT Request the modification of the PDP context
REQUEST
19 SM STATUS Cause set to # 96
208 MODIFY PDP CONTEXT Try to modify the context with the transaction
REQUEST (NETWORK TO UE identifier different to that used to activate the
DIRECTION) contextRequest the modification of the PDP
context
219 SM STATUS Cause set to # 81 invalid transaction identifier
value and received transaction identifier in
MODIFY PDP CONTEXT
REQUEST(NETWORK TO UE DIRECTION)#
96
2210 MODIFY PDP CONTEXT Try to modify the context with transaction
REQUEST (NETWORK TO UE identifier used to activate the context and QoS
DIRECTION) acceptable to UERequest the modification of the
PDP context
2311 SM STATUSMODIFY PDP Cause set to # 96Accept PDP context
CONTEXT ACCEPT (UE TO modification
NETWORK DIRECTION)
11.4.1.1.5 Test requirements

TBD.
3GPP
11.5.2 Unknown or unforeseen message type
11.4.2.1 Definition and applicability

If a UE receives a SM message with message type not defined for the PD or not implemented by the receiver, it shall
return a status message SM STATUS with cause #97 message type non-existent or not implemented.
If the UE receives a SM message not compatible with the protocol state, the SM-STATUS message with cause #98
Message type not compatible with protocol state shall be returned.
Reference
3G TS 24.008 subclause 8.4.

11.4.2.3 Test purpose
To test the behaviour of the UE when:
- messages with message type element not defined for the PD or not implemented by the receiver
errors occur.
- The UE receives a SM message not compatible with the protocol state.
11.4.2.4 Method of test
Initial conditions
System Simulator:
User Equipment:
-
Test procedure
A PDP context is activated from the UE. The SS sends back a Session Management message with an unknown message
type. The UE shall reply with a SM STATUS message with the cause set to #97 Message type non-existent or not
implemented. After T3380 seconds the UE shall send another ACTIVATE PDP CONTEXT REQUEST message. The
SS sends a MODIFY PDP CONTEXT REQUEST message with the same transaction identifier. The UE shall reply with
SM STATUS message with the cause set to #98 Message type not compatible with protocol state.
Expected sequence

UE SS
REQUEST
3 UNKNOWN MESSAGE Message with unknown message type
4 SM STATUS Cause set to #97 message type non-existent or
not implemented.
5 SS T3380 seconds
REQUEST
REQUEST (NETWORK TO UE
DIRECTION)
8 SM STATUS Cause set to #98 message type not compatible
with protocol state.
3GPP
11.4.2.5 Test requirements

TBD.
11.4.3 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
3G TS 24.007 subclause 11.4.2.

To test the behaviour of the UE when syntactically incorrect messages are received.
Initial conditions
System Simulator:
User Equipment:
-
Test procedure
TBD.
Expected sequence
TBD.

TBD.
3GPP
11.4.4 Non-semantical Mandatory Information Element Errors

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 UE shall proceed as follows:
If the message was a SM message the SM-STATUS message with cause # 96 invalid mandatory information shall be
returned.
Reference
3G TS 24.008 subclauses 8.5 and 8.5.5.

To test the behaviour of the UE when messages with non-semantical mandatory information element errors are received
from network.
Initial conditions
System Simulator:
User Equipment:
-
Test procedure
A PDP context is activated from the UE. An invalid accept message with unknown IE encoded as comprehension
required is then sent by the SS. Then UE shall send a SM STATUS message with cause #96. After the UE has sent
another ACTIVATE PDP CONTEXT REQUEST message, the SS sends invalid accept message with out of sequence IE
encoded as comprehension required. The UE shall reply with SM STATUS message with the cause set to #96. After
T3380 seconds the UE shall send another ACTIVATE PDP CONTEXT REQUEST message.
Two invalid modification messages are then sent to the UE in turn. The UE shall respond each time with a SM-STATUS
message with cause # 96 invalid mandatory information.
3GPP
Expected sequence

UE SS
REQUEST
3 ACTIVATE PDP CONTEXT Unknown IE encoded as comprehension
ACCEPT required
4 SM STATUS Cause set to #96 invalid mandatory
information
SS Wait T3380 seconds
ACTIVATE PDP CONTEXT Activate a PDP context from the UE (auto-
REQUEST generated)
7 ACTIVATE PDP CONTEXT Out of sequence IE encoded as comprehension
ACCEPT required
8 SM STATUS Cause set to #96 invalid mandatory
information
9 SS Wait T3380 seconds
REQUEST generated)
11 ACTIVATE PDP CONTEXT Accept the PDP context
ACCEPT
DIRECTION)
13 SM STATUS Cause set to # 96 invalid mandatory
information
DIRECTION)
15 SM STATUS Cause set to # 96 invalid mandatory
information

TBD.
3GPP

T 1 S 000098

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

T 1 S 000098

Încărcat de

Drepturi de autor:

Formate disponibile

TSG-T Working Group1 SWG SIG meeting #11 TSGT1S- 000098

Harpenden , UK 5-7 June, 2000

Title: Update on section 11. Session Management in 3G TS 34.123 1,

Document for: Discussion

Changes since T1S 000046 was discussed are:

11.4 Error Handling Procedures

11.4.1 Error cases

11.4.1.1 Conformance requirement

11.4.1.1.1 Definition and applicability

- an imperative message part error; or

3G TS 24.008 sections subclause 8.3.2 and 8.5.

Step Direction Message Comments

11.4.1.1.5 Test requirements

11.5.2 Unknown or unforeseen message type

11.4.2.1 Definition and applicability

3G TS 24.008 subclause 8.4.

11.4.2.4 Method of test

Step Direction Message Comments

11.4.2.5 Test requirements

11.4.3 Other Syntactic Errors

11.4.3.1 Definition and applicability

11.4.3.2 Conformance requirement

- An IE is defined to be syntactically incorrect in a message if it contains at least one value

3G TS 24.007 subclause 11.4.2.

11.4.3.5 Test requirements

11.4.4 Non-semantical Mandatory Information Element Errors

11.4.4.1 Definition and applicability

- an imperative message part error; or

3G TS 24.008 subclauses 8.5 and 8.5.5.

11.4.4.3 Test purpose

Step Direction Message Comments

11.4.4.5 Test requirements

S-ar putea să vă placă și