11.4 Unknown or Unforeseen Transaction Identifier/Non-semantical Mandatory Information Element Errors
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
11.4.1 Error cases
11.4.1.1 Definition
11.4.1.2 Conformance requirement
The mobile station 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 UE 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 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 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, except DEACTIVATE PDP CONTEXT REQUEST and REQUEST PDP CONTEXT ACTIVATION, the SM-STATUS message with cause # 96 "invalid mandatory information" shall be returned.
a) If the message is a DEACTIVATE PDP CONTEXT REQUEST, a DEACTIVATE PDP CONTEXT ACCEPT message shall be returned. All resources allocated for that context shall be released.
b) If the message is a REQUEST PDP CONTEXT ACTIVATION, a REQUEST PDP CONTEXT REJECT 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 clause 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 clauses 8.3.2, 8.4 and 8.5.
3GPP TS 24.007 clause 11.4.2.
11.4.1.3 Test purpose
To test the behaviour of the UE when messages with unknown or unforeseen transaction identifiers or non-semantical mandatory information element errors occur.
11.4.1.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Related ICS/IXIT statements
– PS supported yes/no
– Method of context activation
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. An invalid accept messages is sent by the SS. The UE replies with SM STATUS message. After T3380 seconds UE sends second auto generated ACTIVATE PDP CONTEXT REQUEST message. SS again replies with invalid ACTIVATE PDP CONTEXT ACCEPT and UE returns SM STATUS message. After further T3380 seconds UE sends third auto generated ACTIVATE PDP CONTEXT REQUEST message. SS replies with unknown message and UE returns SM STATUS with cause #97 ‘message type non-existent or not implemented’. After T3380 seconds the UE sends next auto generated ACTIVATE PDP CONTEXT REQUEST message, SS replies with MODIFY PDP CONTEXT REQUEST and UE returns SM STATUS with cause #98 ‘message type not compatible with protocol state’. After T3380 seconds the UE sends last auto generated ACTIVATE PDP CONTEXT REQUEST message. SS replies with valid accept message.
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’.
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".
Last MODIFY PDP CONTEXT message sent from SS has TI EXT bit = 0. The UE does not respond to this message.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
|
REQUEST PDP CONTEXT ACTIVATION |
Request the activation of a PDP context with the transaction identifier flag set to "1" |
|
|
2 |
SS |
Wait T3385 seconds to ensure UE does not request context activation |
||
|
3 |
UE |
Initiate a context request |
||
|
4 |
|
ACTIVATE PDP CONTEXT REQUEST |
Activate a PDP context from the UE |
|
|
5 |
|
ACTIVATE PDP CONTEXT ACCEPT |
Unknown IE encoded as ‘comprehension required’ |
|
|
6 |
|
SM STATUS |
Cause set to #96 |
|
|
7 |
SS |
Wait T3380 seconds |
||
|
8 |
|
ACTIVATE PDP CONTEXT REQUEST |
Activate a PDP context from the UE (auto-generated) |
|
|
9 |
|
ACTIVATE PDP CONTEXT ACCEPT |
Out of sequence IE encoded as ‘comprehension required’ |
|
|
10 |
|
SM STATUS |
Cause set to #96 |
|
|
11 |
SS |
Wait T3380 seconds |
||
|
12 |
|
ACTIVATE PDP CONTEXT REQUEST |
Activate a PDP context from the UE (auto-generated) |
|
|
13 |
|
UNKNOWN MESSAGE |
Message with unknown message type |
|
|
14 |
|
SM STATUS |
Cause set to #97 |
|
|
15 |
SS |
Wait T3380 seconds |
||
|
16 |
|
ACTIVATE PDP CONTEXT REQUEST |
Activate a PDP context from the UE (auto-generated) |
|
|
17 |
|
MODIFY PDP CONTEXT REQUEST |
Request modification of PDP context |
|
|
18 |
|
SM STATUS |
Cause set to #98 |
|
|
19 |
SS |
Wait T3380 seconds |
||
|
20 |
|
ACTIVATE PDP CONTEXT REQUEST |
Activate a PDP context from the UE (auto-generated) |
|
|
21 |
|
ACTIVATE PDP CONTEXT ACCEPT |
Accept the PDP context |
|
|
22 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Try to deactivate the context with a different transaction identifier to that used to activate the context |
|
|
23 |
|
SM STATUS |
Cause set to # 81 |
|
|
24 |
|
MODIFY PDP CONTEXT REQUEST(NETWORK TO UE DIRECTION) |
Request the modification of the PDP context (‘New QoS’ mandatory IE missing in the message) |
|
|
25 |
|
SM STATUS |
Cause set to # 96 |
|
|
26 |
|
MODIFY PDP CONTEXT REQUEST(NETWORK TO UE DIRECTION) |
Request the modification of the PDP context (with ‘Requested LLC SAPI’ set to reserved value ‘1100’) |
|
|
27 |
|
SM STATUS |
Cause set to # 96 |
|
|
28 |
|
MODIFY PDP CONTEXT REQUEST(NETWORK TO UE DIRECTION) |
Request the modification of the PDP context (TI EXT bit = 0) |
|
|
29 |
SS |
Wait T3386 seconds to ensure UE does not respond |
||
11.4.1.5 Test requirements
TBD.