School of Specs 24.501v20.0.0

3GPP 24.501 v20.0.0 — the document's own text

7.3.1 Procedure transaction identity

Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).

The following network procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in a 5GSM message:

  • In case the network receives a PDU SESSION MODIFICATION COMPLETE, a PDU SESSION RELEASE COMPLETE message or a PDU SESSION MODIFICATION COMMAND REJECT message in which the PTI value is an assigned or unassigned value that does not match any PTI in use, the network shall respond with a 5GSM STATUS message including 5GSM cause #47 "PTI mismatch".
  • In case the network receives a PDU SESSION AUTHENTICATION COMPLETE message or a SERVICE-LEVEL AUTHENTICATION COMPLETE message in which the PTI value is an assigned value, the network shall respond with a 5GSM STATUS message including 5GSM cause #81 "invalid PTI value".
  • In case the network receives a PDU SESSION ESTABLISHMENT REQUEST message, a PDU SESSION MODIFICATION REQUEST message or a PDU SESSION RELEASE REQUEST message in which the PTI value is an unassigned value, the network shall respond with a 5GSM STATUS message including 5GSM cause #81 "invalid PTI value".
  • In case the network receives a 5GSM message in which the PTI value is a reserved value, the network shall ignore the message.

The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in a 5GSM message:

  • In case the UE receives a PDU SESSION MODIFICATION COMMAND message or a PDU SESSION MODIFICATION REJECT message in which the PTI value is an assigned value that does not match any PTI in use:
    • if the UE detects that this PDU SESSION MODIFICATION COMMAND message is a network retransmission of an already accepted request (see clause 6.3.2.3), the UE shall respond with a PDU SESSION MODIFICATION COMPLETE message;
    • if the UE detects that this PDU SESSION MODIFICATION COMMAND message is a network retransmission of an already rejected request (see clause 6.3.2.4), the UE shall respond with a PDU SESSION MODIFICATION COMAND REJECT message; or
    • otherwise, the UE shall respond with a 5GSM STATUS message including 5GSM cause #47 "PTI mismatch".
  • In case the UE receives a PDU SESSION RELEASE COMMAND message or a PDU SESSION RELEASE REJECT message in which the PTI value is an assigned value that does not match any PTI in use:
    • if the UE detects that this PDU SESSION RELEASE COMMAND message is a network retransmission of an already accepted request (see clause 6.3.3.3), the UE shall respond with a PDU SESSION RELEASE COMPLETE message; or
    • otherwise, the UE shall respond with a 5GSM STATUS message including 5GSM cause #47 "PTI mismatch".
  • In case the UE receives a PDU SESSION ESTABLISHMENT ACCEPT message or a PDU SESSION ESTABLISHMENT REJECT message in which the PTI value is an assigned value that does not match any PTI in use:
    • the UE shall respond with a 5GSM STATUS message including 5GSM cause #47 "PTI mismatch".
  • In case the UE receives a PDU SESSION AUTHENTICATION COMMAND message, a PDU SESSION AUTHENTICATION RESULT message or a SERVICE-LEVEL AUTHENTICATION COMMAND message in which the PTI value is an assigned value, the UE shall respond with a 5GSM STATUS message including 5GSM cause #81 "invalid PTI value".
  • In case the UE receives a PDU SESSION ESTABLISHMENT ACCEPT message, a PDU SESSION ESTABLISHMENT REJECT message, a PDU SESSION MODIFICATION REJECT message or a PDU SESSION RELEASE REJECT message in which the PTI value is an unassigned value, the UE shall ignore the message.
  • In case the UE receives a 5GSM message in which the PTI value is a reserved value, the UE shall ignore the message.