Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…

 

6.5  5GSM status procedureWord‑p. 568

6.5.1  GeneralWord‑p. 568

The purpose of the sending of the 5GSM STATUS message is to report at any time certain error conditions detected upon receipt of 5GSM protocol data. The 5GSM STATUS message can be sent by both the network and the UE (see example in Figure 6.5.1.1).
Reproduction of 3GPP TS 24.501, Fig. 6.5.1.1: 5GSM status procedure
Up

6.5.2  5GSM status received in the UEWord‑p. 568

If the 5GSM entity of the UE receives a 5GSM STATUS message the UE shall take different actions depending on the received 5GSM cause value:
#47 PTI mismatch.
The UE shall abort any ongoing 5GSM procedure related to the received PTI value and stop any related timer.
#81 invalid PTI value.
The UE shall abort any ongoing 5GSM procedure related to the received PTI value and stop any related timer.
#97 Message type non-existent or not implemented.
The UE shall abort any ongoing 5GSM procedure related to the PTI or PDU session ID and stop any related timer.
On receipt of a 5GSM STATUS message with any other 5GSM cause value no state transition and no specific action shall be taken as seen from the radio interface, i.e. local actions are possible.
Up

6.5.3  5GSM status received in the SMFWord‑p. 568

If the SMF receives a 5GSM STATUS message the SMF shall take different actions depending on the received 5GSM cause value:
#43 invalid PDU session identity.
The SMF shall abort any ongoing 5GSM procedure related to the PTI or PDU session ID, stop any related timer and locally release the PDU session indicated in the 5GSM STATUS message.
#47 PTI mismatch.
The SMF shall abort any ongoing 5GSM procedure related to the received PTI value and stop any related timer.
If the PTI indicated in the 5GSM STATUS message is related to a PDU SESSION ESTABLISHMENT ACCEPT message, the SMF shall perform a local release of the PDU session indicated in the PDU SESSION ESTABLISHMENT ACCEPT message.
#81 invalid PTI value.
The SMF shall abort any ongoing 5GSM procedure related to the received PTI value and stop any related timer.
#96 invalid mandatory information.
The SMF shall abort any ongoing 5GSM procedure related to the PTI or PDU session ID and stop any related timer.
#97 message type non-existent or not implemented.
The SMF shall abort any ongoing 5GSM procedure related to the PTI or PDU session ID and stop any related timer.
The local actions to be taken by the SMF on receipt of a 5GSM STATUS message with any other 5GSM cause value are implementation dependent.
Up

6.6  Miscellaneous proceduresWord‑p. 569

6.6.1  Exchange of extended protocol configuration optionsWord‑p. 569

The UE and the SMF can exchange protocol configuration options via 5GSM procedures.
The protocol configuration options shall be exchanged via the Extended protocol configuration options IE.

6.6.2  Remote UE report procedure |R17|Word‑p. 569

6.6.2.1  GeneralWord‑p. 569

The purpose of the 5G ProSe remote UE report procedure is for a UE acting as 5G ProSe layer-3 UE-to-network relay to notify the network that a 5G ProSe remote UE is connected to the 5G ProSe layer-3 UE-to-network relay UE or disconnected from the 5G ProSe layer-3 UE-to-network relay UE as specified in TS 23.304.

6.6.2.2  Remote UE report procedure initiationWord‑p. 569

In order to initiate the 5G ProSe remote UE report procedure, the UE shall create a REMOTE UE REPORT message.
The UE shall include information of newly connected or disconnected 5G ProSe remote UEs to the network in the REMOTE UE REPORT message by setting the values of the Remote UE context connected IE or the Remote UE context disconnected IE to the 5G ProSe remote UE identities that are being connected or disconnected, respectively.
The UE shall set the PDU session ID IE to the value of the PDU session associated with the 5G ProSe remote UE connected to the 5G ProSe layer-3 UE-to-network relay UE or disconnected from the 5G ProSe layer-3 UE-to-network relay UE.
The UE shall allocate a PTI value currently not used and shall set the PTI IE of the REMOTE UE REPORT message to the allocated PTI value.
The UE shall transport the REMOTE UE REPORT message and the PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, and the UE shall start timer T3586 (see example in Figure 6.6.2.2.1).
Reproduction of 3GPP TS 24.501, Fig. 6.6.2.2.1: Remote UE report procedure
Up

6.6.2.3  Remote UE report procedure accepted by the networkWord‑p. 570

Upon receipt of the REMOTE UE REPORT message, the SMF shall send a REMOTE UE REPORT RESPONSE message to the UE. The SMF shall include the PTI from the REMOTE UE REPORT message.
Upon receipt of the REMOTE UE REPORT RESPONSE message, the UE shall stop timer T3586 and enter the state PROCEDURE TRANSACTION INACTIVE.

6.6.2.4  Abnormal cases in the UEWord‑p. 570

The following abnormal cases can be identified:
  1. Expiry of timer T3586:
    On the first expiry of the timer T3586, the UE shall resend the REMOTE UE REPORT message and shall reset and restart timer T3586. This retransmission is repeated two times, i.e. on the third expiry of timer T3586, the UE shall abort the procedure and release any resources for this procedure.
Up

6.6.2.5  Abnormal cases on the network sideWord‑p. 570

No abnormal cases have been identified.

Up   Top   ToC