maki/openairinterface5g
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Handover doc: mention ssb_PositionsInBurst_Bitmap config

Browse Source
This commit is contained in:
Rakesh Mundlamuri
2026-02-25 08:58:33 +01:00
committed by Robert Schmidt
parent 4e9a853696
commit af438ef5e5
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/handover-tutorial.md
+5
View File
@@ -104,6 +104,9 @@ information further below.
A number of remarks: A number of remarks:
1. DU0 and DU1 should use different SSBs, i.e., make sure that
`ssb_PositionsInBurst_Bitmap` is set to send SSB in different slots in the
configurataion files of DU0 (e.g., set to 1) and DU1 (e.g., set to 2).
1. It is important that you start DU0, UE, DU1 in order, and having UE connect 1. It is important that you start DU0, UE, DU1 in order, and having UE connect
to DU0 before starting DU1. This is because we don't employ any channel to DU0 before starting DU1. This is because we don't employ any channel
emulation, and the UE could not decode the SIB1 of DU0 to connect. emulation, and the UE could not decode the SIB1 of DU0 to connect.
@@ -433,6 +436,8 @@ a core-network-based handover.
We assume: We assume:
* `ssb_PositionsInBurst_Bitmap` set to different values for gNB-PCI0 and
gNB-PCI1 as described further above.
* Two independent gNBs connected to the same 5GC via N2 interface. * Two independent gNBs connected to the same 5GC via N2 interface.
* A UE initially connected to gNB-PCI0, which will be handed over to gNB-PCI1. * A UE initially connected to gNB-PCI0, which will be handed over to gNB-PCI1.
* Handover is triggered by either a decision based measurement event (e.g. A3) * Handover is triggered by either a decision based measurement event (e.g. A3)