Bug 3027

Summary:	S1 signalling is done before RRC connection establishment is finished
Product:	ns-3	Reporter:	Manuel Requena <manuel.requena>
Component:	lte	Assignee:	Manuel Requena <manuel.requena>
Status:	RESOLVED FIXED
Severity:	normal	CC:	ns-bugs, tomh
Priority:	P5
Version:	ns-3-dev
Hardware:	All
OS:	All
Bug Depends on:
Bug Blocks:	3022

Description Manuel Requena 2018-12-05 05:31:38 UTC

The eNB sends the S1 signalling (currently, direct calls) to the core network when the RRC connection request is received. This should be done when the 3-way RRC connection establishment is finished, i.e. when the RRC connection setup complete is received that is sent from the UE to the eNB.

As we receive the information of the bearers "immediately", we send this information in the RRC connection setup. This should be done in the RRC connection reconfiguration that we send to the UE once we receive the S1 Initial Context Setup Request from the MME.

With the new epc upgrade in 
https://code.nsnam.org/index.cgi/mrequena/ns-3-dev-epc-upgrade/
the information about the dedicated bearers is not setup correctly.

Comment 1 Tom Henderson 2018-12-06 20:39:57 UTC

Do you intend to push the EPC upgrade and then fix this issue, or hold the EPC upgrade until this is fixed?

Comment 2 Manuel Requena 2018-12-07 07:17:55 UTC

This issue plus the EPC upgrade makes that 3 testsuites fail.
To avoid these fails, I would prefer to fix this issue before pushing the EPC upgrade. I'm working on it now.

Comment 3 Manuel Requena 2019-01-18 11:35:08 UTC

The fix to this issue is part of the commit
https://gitlab.com/nsnam/ns-3-dev/commit/4dd0821ed6b726d033f108703957e4349adb9a02