3GPP 37.340 says that it is up the secondary node to establish "SRB3", but what exactly does this mean and how is it done?
Simple answer: The establishment of a signaling radio bearer (SRB) 3 in EN-DC mode means that RRC Measurement Reports for NR quality can be sent directly to the SgNB. This enables the 5G node to make intra-SgNB handover decisions and start the handover execution without involving the master eNodeB of the connection.
To
prevent confusion the figure below shows a simplified scenario in which the
Complete/Acknowledgement messages are not mentioned although they will be seen
in the message flow.
A prerequisite
is the successful addition of 5G radio resources as described in an earlier blog post. After this is completed the UE in the example transmits user plane information over
the NR cell with the physical cell ID (PCI) = 12. In the transport network this
cell is identified by NR CGI = xxxx52 (where „xxxx“ stands for a valid PLMN-ID
and gNodeB-ID).
Instead of the X2AP SgNB Modification Required message the information for activating the CSI reference signal measurements can alternatively transported using the X2AP SgNB Addition Request Acknowledge or X2AP SgNB Change Required message.
In
step 2 the UE sends a NR RRC (3GPP 38.331) Measurement Report that indicates a
stronger 5G cell (the neighbor cell with PCI = 11) was measured. It might be a
vendor-specific implementation to send this NR RRC Measurement Report
simultaneously over uplink channels of the LTE radio link where it is carried
by the LTE RRC Uplink Information Transfer MRDC (Multi-RAT Dual Connectivity)
as well as over NR radio links where it is forwarded by the SgNB to the MeNB
embedded in a X2AP RRC Transfer message.
Indeed,
it is the SgNB that makes the handover decision, but since the MeNB is in
charge of the signaling connection the handover command (here: another NR RRC
cG-Config message that orders to switch the 5G radio link to the cell with PCI
= 11) must be transmitted to the MeNB by using another X2AP SgNB Modification
Required message.
Figure: Measurement Configuration, Reporting and Execution for intra-SgNB Handover |
3 comments:
Thanks for the posting.
One thing I'd like to mention though: message sequence charts are much easier to read, IMHO.
Thanks for the feedback. I see your point and will consider this in future graphics.
I believe Step#3 is X2AP::SgNBModificationConfirm.
Post a Comment