name: PTI
full_form: Procedure Transaction Identity
context: The following network procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in an ESM message: a) If the network receives a PDN CONNECTIVITY REQUEST message with an unassigned or reserved PTI value, the network shall respond with a PDN CONNECTIVITY REJECT message including ESM cause #81 "invalid PTI value". b) If the network receives a PDN DISCONNECT REQUEST message with an unassigned or reserved PTI value, the network shall respond with a PDN DISCONNECT REJECT message including ESM cause #81 "invalid PTI value". c) If the network receives a BEARER RESOURCE ALLOCATION REQUEST message with an unassigned or reserved PTI value, the network shall respond with a BEARER RESOURCE ALLOCATION REJECT message including ESM cause #81 "invalid PTI value". d) If the network receives a BEARER RESOURCE MODIFICATION REQUEST message with an unassigned or reserved PTI value, the network shall respond with a BEARER RESOURCE MODIFICATION REJECT message including ESM cause #81 "invalid PTI value". e) If the network receives an ESM INFORMATION RESPONSE message which includes an unassigned or reserved PTI value, the network shall ignore the message. If the PTI is an assigned value that does not match the PTI in use for any ongoing transaction related procedure, the network shall respond with an ESM STATUS message including ESM cause #81 "invalid PTI value". f) If the network receives an ESM message other than those listed in items a through e above with a reserved PTI value, the network shall ignore the message. The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in an ESM message: a) If the UE receives a PDN CONNECTIVITY REJECT message in which the PTI value is an unassigned or reserved value, or an assigned value that does not match any PTI in use, the UE shall ignore the message. b) If the UE receives a PDN DISCONNECT REJECT message in which the PTI value is an unassigned or reserved value, or an assigned value that does not match any PTI in use, the UE shall ignore the message. c) If the UE receives a BEARER RESOURCE ALLOCATION REJECT message in which the PTI value is an unassigned or reserved value, or an assigned value that does not match any PTI in use, the UE shall ignore the message. d) If the UE receives a BEARER RESOURCE MODIFICATION REJECT message in which the PTI value is an unassigned or reserved value, or an assigned value that does not match any PTI in use, the UE shall ignore the message. e) If the UE receives an ESM INFORMATION REQUEST message in which the PTI value is an unassigned or reserved value, the UE shall ignore the message. If the PTI is an assigned value that does not match a PTI in use for a pending UE requested PDN connectivity procedure for which the ESM information transfer flag was set in the PDN CONNECTIVITY REQUEST message, the UE shall respond with an ESM STATUS message including ESM cause #47 "PTI mismatch". f) If the UE receives a NOTIFICATION message in which the PTI value is an unassigned value, the UE shall proceed as specified in clause 7.3.2. If the PTI is a reserved value, the UE shall respond with an ESM STATUS message including ESM cause #81 "invalid PTI value". If the PTI is an assigned value that does not match any PTI in use, the UE shall respond with an ESM STATUS message including ESM cause #47 "PTI mismatch". g) If the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message in which the PTI value is an assigned value that does not match any PTI in use, if the UE detects that this request is a network retransmission of an already accepted request (see clause 6.5.1.3) the UE shall respond with an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message. Otherwise, the UE shall respond with an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message including ESM cause #47 "PTI mismatch". h) If the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message which contains a reserved or unassigned PTI value, the UE shall respond with an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message including ESM cause #81 "invalid PTI value". i) If the UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message in which the PTI value is an assigned value that does not match any PTI in use, if the UE detects that this request is a network retransmission of an already accepted request (see clauses 6.5.3.3 and 6.5.4.3) the UE shall respond with an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. Otherwise, the UE shall respond with an ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message including ESM cause #47 "PTI mismatch". j) If the UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message which contains a reserved PTI value, the UE shall respond with an ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message including ESM cause #81 "invalid PTI value". k) If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message in which the PTI value is an assigned value that does not match any PTI in use, if the UE detects that this request is a network retransmission of an already accepted request (see clauses 6.5.3.3 and 6.5.4.3) the UE shall respond with a MODIFY EPS BEARER CONTEXT ACCEPT message. Otherwise, the UE shall respond with a MODIFY EPS BEARER CONTEXT REJECT message including ESM cause #47 "PTI mismatch". l) If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message which contains a reserved PTI value, the UE shall respond with a MODIFY EPS BEARER CONTEXT REJECT message including ESM cause #81 "invalid PTI value". m) If the UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message in which the PTI value is a reserved value or an assigned value that does not match any PTI in use, the UE shall ignore the message. n) If the UE receives an ESM message other than those listed in items a through m with a reserved PTI value or an assigned value that does not match any PTI in use, the UE shall ignore the message.
description: Procedure Transaction Identity (PTI) is a concept used in telecommunications to identify and manage transactions related to network procedures. It is used to ensure that messages are processed correctly and to prevent errors or unforeseen situations. The PTI value is included in ESM messages and is used by the network and UE to determine how to handle the message.
explanation: PTI is classified under the entity type 'Telecommunications Protocol' because it is a standardized concept used in telecommunications protocols to manage transactions related to network procedures. It is an essential component of the ESM protocol, which is used for communication between the network and UE.
section_title: 7.3.1 Procedure transaction identity
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Network Function,O,O,O,O,B-Device,O,O,B-Message,I-Message,I-Message,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O,O,O,O,B-Device,O,O,B-Message,I-Message,I-Message,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O,O,O,O,B-Device,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O,O,O,O,B-Device,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O,O,O,O,B-Device,O,O,B-Message,I-Message,I-Message,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Device,O,B-Network,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,O,O,B-Device,O,O,O,O,B-Message,I-Message,O,O,B-Network Function,O,O,O,O,O,O,O,B-Device,O,O,B-Message,I-Message,O,O,O,B-Parameter,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Device,O,O,O,O,B-Message,I-Message,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O,B-Message,I-Message,O,O,B-Network Function,O,O,O,O,O,O,O,B-Device,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,I-Message,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,B-Device,O,O,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,I-Message,O,O,B-Network Function,O,O,O,O,O,O,O,B-Device,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,I-Message,O,O,O,O,O,O,O,B-Parameter,O,O,B-Device,O,O,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,I-Message,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,B-Device,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,I-Message,O,O,O,B-Device,O,O,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,I-Message,I-Message,O,B-Network Function,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Device,O,O,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,I-Message,I-Message,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,B-Device,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,O,O,O,B-Device,O,O,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,O,O,B-Network Function,O,O,O,O,O,O,O,B-Device,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,O,O,O,O,O,B-Parameter,O,O,B-Device,O,O,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,B-Device,O,O,O,B-Network,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O,O,O,O,B-Device,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O