Skip to content
[Jenkins]Jenkins
log insign up
Unstable

Changes

Summary

  1. RAN_Emulation: Fix error: CLIENT multiple conns requires explicit (details)
  2. RAN_Emulation: Proper operation indication in RANAP_Connect prim to (details)
  3. RAN_Emulation: rename f_handle_userData() -> f_handle_userData_BSSAP() (details)
  4. cosmetic: bsc-nat: MSC_Simulation.ttcn: Fix trailing whitespace (details)
  5. RAN_Emulation: Rename RAN_ConnHdlr.BSSAP* ports to RAN_CONN (details)
  6. s1gw: correct handling of UE CONTEXT RELEASE REQUEST (details)
Commit fdee8ec40f1cd0495c94deb2f9302ade77097387 by Pau Espin Pedrol
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
The file was modifiedlibrary/RAN_Emulation.ttcnpp
Commit 31a591d58013cea8914272cc4b80970c75c82179 by Pau Espin Pedrol
RAN_Emulation: Proper operation indication in RANAP_Connect prim to upper layers

Change-Id: Id39c68a0408fdc90304d8089dd200274eb843a8d
The file was modifiedlibrary/RAN_Emulation.ttcnpp
The file was modifiedhnbgw/ConnHdlr.ttcn
Commit 800bcff2e165e8ad330c98676d9cd86cba174eda by Pau Espin Pedrol
RAN_Emulation: rename f_handle_userData() -> f_handle_userData_BSSAP()

To match its counterpart f_handle_userData_RANAP().

Change-Id: I9e07cd99d2ca01942aae671175753517d5d40572
The file was modifiedlibrary/RAN_Emulation.ttcnpp
Commit 4b06648221f6d0b8f434b71cf32844b13d9413df by Pau Espin Pedrol
cosmetic: bsc-nat: MSC_Simulation.ttcn: Fix trailing whitespace

Change-Id: Ie80ad827f7024c977ed7895cbc11417b4de20fe5
The file was modifiedbsc-nat/MSC_Simulation.ttcn
Commit 3adb72bff2b66b3f8121b6f8c73bdbe60dfa71b9 by Pau Espin Pedrol
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
The file was modifiedbsc/BSC_Tests_VAMOS.ttcn
The file was modifiedlibrary/RAN_Emulation.ttcnpp
The file was modifiedsgsn/SGSN_Tests.ttcn
The file was modifiedmsc/BSC_ConnectionHandler.ttcn
The file was modifiedbsc/BSC_Tests_LCLS.ttcn
The file was modifiedmsc/MSC_Tests.ttcn
The file was modifiedmsc/MSC_Tests_ASCI.ttcn
The file was modifiedhnbgw/HNBGW_Tests.ttcn
The file was modifiedsgsn/SGSN_Tests_Iu.ttcn
The file was modifiedmsc/MSC_Tests_Iu.ttcn
The file was modifiedbsc/BSC_Tests_ASCI.ttcn
The file was modifiedbsc-nat/MSC_ConnectionHandler.ttcn
The file was modifiedsgsn/BSSGP_ConnHdlr.ttcn
The file was modifiedbsc/BSC_Tests.ttcn
The file was modifiedbsc/MSC_ConnectionHandler.ttcn
The file was modifiedhnbgw/ConnHdlr.ttcn
The file was modifiedbsc-nat/BSC_MS_ConnectionHandler.ttcn
The file was modifiedbsc-nat/BSC_MS_Simulation.ttcn
Commit acd272346c99da2e911333162ace6a733ced428d by laforge
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
The file was modifieds1gw/S1GW_ConnHdlr.ttcn