## 5.5.1.2.8 Abnormal cases on the network side - Initial Registration (SINTESIO)
## 5.5.1.2.8 Abnormal cases on the network side - Initial Registration (SINTESIO)
[BPIN] Those TOs were identified but they may not be for the first round of implementation
[KSCH] How does "the first round of implementation" correspond to the roadmap distributed?
[KSCH] What is the guideline/rule to assign TPs to the different implementation rounds? Maybe we should give potentail users a chance to know what could be expected by when.
- TP_5GNAS_AMF_REG_ABN_01
- TP_5GNAS_AMF_REG_ABN_01
- Verify that the IUT retransmits the REGISTRATION ACCEPT message and restarts timer T3550 upon the first four expirations.
- Verify that the IUT retransmits the REGISTRATION ACCEPT message and restarts timer T3550 upon the first four expirations.
@@ -147,9 +143,6 @@
- Validate that the AMF rejects a REGISTRATION REQUEST message with invalid or unacceptable UE security capabilities by sending a REGISTRATION REJECT message.
- Validate that the AMF rejects a REGISTRATION REQUEST message with invalid or unacceptable UE security capabilities by sending a REGISTRATION REJECT message.
## 5.5.2.3.5 Abnormal cases in the network side (SINTESIO)
## 5.5.2.3.5 Abnormal cases in the network side (SINTESIO)
[BPIN] Those TOs were identified but they may not be for the first round of implementation
[KSCH] see above.
- TP_5GNAS_AMF_DRG_ABN_01
- TP_5GNAS_AMF_DRG_ABN_01
- Verify that the IUT retransmits DEREGISTRATION REQUEST message after timer T3522 expiration four times (i.e. on the fifth expiry of timer T3522, the de-registration procedure shall be aborted).
- Verify that the IUT retransmits DEREGISTRATION REQUEST message after timer T3522 expiration four times (i.e. on the fifth expiry of timer T3522, the de-registration procedure shall be aborted).
