[TVM Regression] No Response for TAU Request

[arun-magma]

Tested magma Build: 1.7.0-1646792286-35f8c481

Issue: No Response for TAU Request
Expectation: TAU Accept

AGW TA Config:

TAU TCs which has no TAU Accept initiated by AGW are listed below:

02_Generic_TAU_with_Change_in_TA_on_Connected_Mode

02_Generic_TAU_with_Change_in_TA_on_Connected_Mode_220309_132014-1.pcapng.zip

05_Periodic_TAU_with_change_in_TA_in_Idle_Mode

05_Periodic_TAU_with_change_in_TA_in_Idle_Mode_220309_132145-1.pcapng.zip

08_TAU_for_connected_UEs_in_initialUE_Active_Flag

08_TAU_for_connected_UEs_in_initialUE_Active_Flag_220309_132317-1.pcapng.zip

09_TAU_for_connected_UEs_in_initialUE_Inactive_Flag

09_TAU_for_connected_UEs_in_initialUE_Inactive_Flag_220309_132443-1.pcapng.zip

[rsarwad]

Tracking area accept is not sent on v1.7. I imported the PR, #11795 on v1.7. With this change different issue is observed.
on reception of Attach Request in initial ue message, mme gets the context based on GUTI and finds that UE is in connected mode and also has valid s1ap_id_key. So mme_app initiates UE context release but s1ap fails to find the ue_ref_p and message gets dropped.
So I am suspecting cleanup is not happening correctly.
On sctpd service restart, TAU test cases are working fine.
I am further analyzing the issue

[rsarwad]

The issue would be fixed from PRs, #11795 and #12275

[arun-magma]

Hi @ssanadhya : Like to know if this above PRs get merged as part of 1.7 rel ?

[ssanadhya]

Hi @ssanadhya : Like to know if this above PRs get merged as part of 1.7 rel ?

@arun-magma , the above PRs will be part of release 1.7.1

[ssanadhya]

Hi @ssanadhya : Like to know if this above PRs get merged as part of 1.7 rel ?

@arun-magma , the above PRs will be part of release 1.7.1

@tmdzk, could you please update this issue once the above PRs have been backported to v1.7 branch.

[ssanadhya]

@arun-magma , @rsarwad , please note that the TSC discussed whether we should try to backport fixes to 1.7 (and create 1.7.1) or make them all part of 1.8, and the consensus was to make them all part of release 1.8. No backporting is needed. Closing this issue since fix is already in master.