Changes

NGAP: Add UESecurityCapabilities IE to PathSwitchRequestAcknowledge

This IE is now used by Open5GS, so add it to the receive template.

This fixes C5G_Tests.TC_handover_inter_ngran_xn.

Note that there is also a pull request to fix the location of this IE in
Open5GS. (https://github.com/open5gs/open5gs/pull/4589) Without this fix
the test case will fail.

Change-Id: Ic46f201db3dcf84a7d62fb1cd17c839ef540e8bb

C5G: Release UE Context before sending Service request

A recent fix in Open5GS rejects RAN_UE_NGAP_ID in InitialUEMessage. This
causes all tests to fail that send a subsequent InitialUEMessage with
the same RAN_UE_NGAP_ID.

Release the UE Context before re-using the RAN_UE_NGAP_ID, because the
connection handler can only handle one context at a time.

Note that the AMF_UE_NGAP_ID is incremented by Open5GS for every
context.

This fixes:
    TC_ue_service_request_cm_idle_inact_sess
    TC_ue_service_request_cm_idle_ul_data
    TC_ue_service_request_cm_idle_unknown_sess_active

Related: Open5GS Issues #4481
Change-Id: If6fae56487aebd810c51cbab170d95d5dec7e138

RemsimServer Tests: give the remsim server some time to update the slotmap

The check of the slotmap can race if it is requests straight away,
because the slotmap might be still in the slotmap list as long the
bankd hasn't responded yet.

Change-Id: I6784e05380d844aa4bb9cde2bbe648ff37bee91b

remsim: server: add a client timeout test

1. Connect to the server
2. Don't answer to IPA PINGs
3. Server closes the connection
4. Client reconnects
5. Older server versions will crash

Related: OS#6957
Change-Id: Iec52d3ce229c2ab84ab0ff9d8dbbff59b7f3fbd9

stp: Make TCAP tests more realistic

* Use a TCAP id outside of the TCAP routing range for the M3UA TCAP id.
* Test both directions IPA -> M3UA and M3UA -> IPA.
* Test TCAP routing with a different called address answering

Change-Id: Ia807c2b26e5188b700365650311cabc0f9095674
Related: SYS#5423

cosmetic: Rename TCAP Being->Begin

Change-Id: I19de8da6ee72a04365896c7fb7730be4f3ea01d4

RAN_Emulation: Fix error: CLIENT multiple conns requires explicit addressing

Fixes fynamic test error during HNBGW_Tests.TC_sccp_cr_limit:
Dynamic test case error: Port CLIENT has more than one active connections. Message can be sent on it only with explicit addressing.

Related: SYS#7600
Change-Id: Icb038e041bd5e82f95141e1814571d7c7f75878b

RAN_Emulation: Proper operation indication in RANAP_Connect prim to upper layers

Change-Id: Id39c68a0408fdc90304d8089dd200274eb843a8d

RAN_Emulation: rename f_handle_userData() -> f_handle_userData_BSSAP()

To match its counterpart f_handle_userData_RANAP().

Change-Id: I9e07cd99d2ca01942aae671175753517d5d40572

cosmetic: bsc-nat: MSC_Simulation.ttcn: Fix trailing whitespace

Change-Id: Ie80ad827f7024c977ed7895cbc11417b4de20fe5

RAN_Emulation: Rename RAN_ConnHdlr.BSSAP* ports to RAN_CONN

That port handles a lot more than BSSAP. Naming it BSSAP makes it really
confusing for instance when using it to handle RANAP in the Iu stack.

Change-Id: I75dc5b8b6db912b2eb69311612dbbb0a454374c3

s1gw: correct handling of UE CONTEXT RELEASE REQUEST

By sending a UE CONTEXT RELEASE REQUEST, the eNB is requesting the
MME to terminate the UE context.  This procedure itself does not
terminate the UE context nor the associated E-RABs.  Therefore, the
S1GW should not terminate E-RAB FSMs upon receiving this PDU.

This means that we should not be expecting PFCP sesstion(s)
to be deleted in S1GW_ConnHdlr.f_ConnHdlr_ue_ctx_release_req().

Change-Id: Ibbb6da1f2888995608b980e7479758000e94864e
Related: osmo-s1gw.git If467162e871b7989f0578be30c04d1c32c263c99
Related: SYS#7738, SYS#7599