Reviewed TOs moved under Revieved Section

- TP_5GNAS_AMF_UPR_ABN_01

    - Verify that the IUT sends correctly a PDU SESSION RELEASE REJECT after receiving a PDU SESSION RELEASE REQUEST with a wrong PDU Sesiion ID by the UE and not accepts the session release with reason #43 (Invalid PDU session identity).

# TP objectives ideas

## 5.6.1.1

- TP_5GNAS_AMF_SRP_ACC_01

    - Verify that the IUT sends a SERVICE ACCEPT message after receiving a SERVICE REQUEST message by the UE, that was initated by a paging request to the UE in 5GMM-IDLE mode over 3GPP access.

## 6.4.3.2, 6.4.3.4 (FF)

- TP_5GNAS_AMF_UPR_ACC_01

    - Verify that the IUT handles correctly a PDU session release by sending a PDU SESSION RELEASE COMAND with cause #36 (regular deactivation) after receiving a PDU SESSION RELEASE REQUEST by the UE with cause #36 (regular deactivation).

## 6.3.3.2 Network-requested PDU session release procedure initiation (FF)

Note: possible to test? In this case the IUT can't be triggered with a (interface) message.

[KSCH] Potential Tigger is also the UE originateed PDU SESSION RELEASE REQUEST, besides others e.g. O&M Disable SMF 

[KSCH] There are several procedures, which can't be triggered with an interfce message. We should not restrict the environment in that way, as the overall test coverage would be reduced drastically. As mentioned above an O&M Interface has to be supported for other reasons as well. 

## 5.4.6 5GMM status procedure (SINTESIO)

    - Verify that the IUT handles correctly a PDU session release by sending a PDU SESSION RELEASE COMAND with cause #36 (regular deactivation) after receiving a PDU SESSION RELEASE REQUEST by the UE with cause #36 (regular deactivation).## 5.4.6 5GMM status procedure (SINTESIO)

## 5.4.6.2 5GMM status received in the UE

- TP_5GNAS_AMF_EST_STA_01

    - Verify that IUT is able to trigger 5GMM STATUS message with all mandatory IEs. 

    - Verify that IUT proceeds with both procedures in case if the network receives a SERVICE REQUEST message before the ongoing generic UE configuration update

procedure has been completed

# TP objectives ideas

## 6.3.3.2 Network-requested PDU session release procedure initiation (FF)

Note: possible to test? In this case the IUT can't be triggered with a (interface) message.

[KSCH] Potential Tigger is also the UE originateed PDU SESSION RELEASE REQUEST, besides others e.g. O&M Disable SMF 

[KSCH] There are several procedures, which can't be triggered with an interfce message. We should not restrict the environment in that way, as the overall test coverage would be reduced drastically. As mentioned above an O&M Interface has to be supported for other reasons as well. 

[KSCH] General Remark on Test Coverage

Potential Proedures to be tested - for the sake of total test coverage

- 5.6.1 Service request procedure (a) to l) 12 different types - some are covered) [BPIN 5.6.1.1 Done]