TOs ideas: 5GMM, 5GSM, Config update

[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)

## 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. 

## 5.4.6.3 5GMM status received in the network

- TP_5GNAS_AMF_EST_STA_02

    - Verify that IUT is able to receive 5GMM STATUS message from UE and no state transition and no specific action shall be taken.

## 6.5 5GSM status procedure  (SINTESIO)

## 6.5.2 5GSM status received in the UE

- TP_5GNAS_AMF_SST_STA_01

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

## 6.5.3 5GSM status received in the SMF

- TP_5GNAS_AMF_SST_STA_02

    - Verify that IUT is able to receive 5GSM STATUS message from UE and no state transition and no specific action shall be taken.

## 5.4.4.2 Generic UE configuration update procedure initiated by the network (SINTESIO)

- TP_5GNAS_AMF_CNF_COM_01

    - Verify that the IUT initiates the generic UE configuration update procedure by sending the CONFIGURATION UPDATE COMMAND message and not contains Acknowledgment requested bit in the Configuration update indication IE when only the Network Identity and Time Zone (NITZ) parameter is included.

- TP_5GNAS_AMF_CNF_COM_02

    - Verify that the IUT initiates the generic UE configuration update procedure by sending the CONFIGURATION UPDATE COMMAND message containing one or more parameters (e.g., 5G-GUTI, TAI list,...) and containing Configuration update indication IE with Acknowledgement bit set to "acknowledgement requested"

- TP_5GNAS_AMF_CNF_COM_03

    - Verify that the IUT initiates the generic UE configuration update procedure only due to changes to the allowed NSSAI and

these changes require the UE to initiate a registration procedure then IUT sends the CONFIGURATION UPDATE COMMAND message not containing any other parameters except Configuration update indication IE with the Registration requested bit set to "registration requested" and Acknowledgement bit set to "acknowledgement requested" and

## 5.4.4.4 Generic UE configuration update completion by the network (SINTESIO)

- TP_5GNAS_AMF_CNF_REL_01

    - Verify that the IUT initiates the generic UE configuration update procedure by sending the CONFIGURATION UPDATE COMMAND message containing an allowed NSSAI, a configured NSSAI or both and Configuration update indication IE with the Registration requested bit set to "registration requested" and Acknowledgement bit set to "acknowledgement requested".

and then the IUT initiates the release of the N1 NAS signalling connection.

## 5.4.4.6 Abnormal cases on the network side (SINTESIO)

- TP_5GNAS_AMF_CNF_ABN_01

    - Verify that the IUT retransmits the CONFIGURATION UPDATE COMMAND message and restarts timer T3555 upon the first four expirations. (i.e. on

the fifth expiry of timer T3555, the procedure shall be aborted.)

- TP_5GNAS_AMF_CNF_ABN_02

    - Verify that IUT aborts the generic UE configuration update procedure

and progress the de-registration procedure in case if the network receives a DEREGISTRATION REQUEST message before the ongoing generic UE configuration

update procedure has been completed

- TP_5GNAS_AMF_CNF_ABN_03

    - Verify that IUT aborts the generic UE configuration update procedure

and progress the registration procedure for mobility and periodic registration update procedure in case if the network receives a REGISTRATION REQUEST message before the ongoing generic UE configuration

update procedure has been completed

- TP_5GNAS_AMF_CNF_ABN_04

    - 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

[KSCH] General Remark on Test Coverage

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

- 5.4.4 Generic UE configuration update procedure

- 5.4.6 5GMM status procedure

- 5.6.1 Service request procedure (a) to l) 12 different types - some are covered)

- 5.4.4 Generic UE configuration update procedure [BPIN Done]

- 5.4.6 5GMM status procedure  [BPIN Done]

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

- 5.6.2 Paging procedure

- 5.6.3 Notification procedure

- 6.3.2 Network-requested PDU session modification

- 6.5   5GSM status procedure

- 6.5   5GSM status procedure [BPIN Done]

[KSCH] We should specifc what are the restrictions on test coverage and what will be covered in later phases.