Section: 6.3.2 Principles of address handling for ESM procedures
Content: Transaction related procedures use the procedure transaction identity as address parameter in the ESM message header. When the UE or the network initiates a transaction related procedure, it shall include a valid procedure transaction identity value in the message header and set the EPS bearer identity to "no EPS bearer identity assigned". When the ProSe UE-to-network relay initiates the transaction related procedure remote UE report, it shall include a valid procedure transaction identity value in the message header and set the EPS bearer identity to a valid EPS bearer identity value. If the response message is again a transaction related message, e.g. a PDN CONNECTIVITY REJECT, PDN DISCONNECT REJECT, BEARER RESOURCE ALLOCATION REJECT, BEARER RESOURCE MODIFICATION REJECT, ESM INFORMATION REQUEST message or ESM DUMMY MESSAGE from the network or an ESM INFORMATION RESPONSE message or ESM DUMMY MESSAGE from the UE, the sending entity shall include the procedure transaction identity value received with the request message and set the EPS bearer identity to "no EPS bearer identity assigned" (see examples in figures 6.3.2.1, 6.3.2.1a and 6.3.2.2). If the response message is the transaction related message REMOTE UE REPORT RESPONSE message from the network, the network shall include the procedure transaction identity value received with the request message and set the EPS bearer identity to the EPS bearer identity value received from the ProSe UE-to-network relay (see example in figure 6.3.2.2a). If an ESM DUMMY MESSAGE is sent in response to a received ESM DUMMY MESSAGE, the sending entity shall include the received procedure transaction identity value in the message header and set the EPS bearer identity to "no EPS bearer identity assigned". Figure 6.3.2.1: Transaction related procedure initiated by the UE and rejected by the network Figure 6.3.2.1a: Transaction related procedure initiated by the UE and responded by a network initiated transaction related request Figure 6.3.2.2: Transaction related procedure initiated by the network Figure 6.3.2.2a: Transaction related procedure initiated by the UE EPS bearer context related procedures use the EPS bearer identity as address parameter in the ESM message header. When the network initiates an EPS bearer context related procedure, it shall include a valid EPS bearer identity value in the message header. The procedure transaction identity value shall be set as follows: - If the EPS bearer context related procedure was triggered by the receipt of a transaction related request message from the UE, the network shall include the procedure transaction identity value received with the transaction related request message in the message header of the EPS bearer context related request message (see example in figure 6.3.2.3). - If the procedure was triggered network-internally, the network shall set the procedure transaction identity value in the message header of the EPS bearer context related request message to "no procedure transaction identity assigned" (see example in figure 6.3.2.4). - If the procedure was triggered by the transport of user data via the control plane, the network shall set the procedure transaction identity value in the message header of the EPS bearer context related request message to "no procedure transaction identity assigned" (see example in figure 6.3.2.5). In the response message of the EPS bearer context related procedure, the UE shall include the EPS bearer identity value received from the network and set the procedure transaction identity value to "no procedure transaction identity assigned". When the UE initiates an EPS bearer context related procedure and the procedure was triggered by the transport of user data via the control plane, it shall include a valid EPS bearer identity value and set the procedure transaction identity value to "no procedure transaction identity assigned" in the message header (see example in figure 6.3.2.6). Figure 6.3.2.3: EPS bearer context related procedure triggered by a transaction related request Figure 6.3.2.4: EPS bearer context related procedure triggered network-internally Figure 6.3.2.5: EPS bearer context related procedure triggered by network for the transport of user data via the control plane Figure 6.3.2.6: EPS bearer context related procedure triggered by UE for the transport of user data via the control plane