... | ... | @@ -6,14 +6,14 @@ standardized in TS 38.470 - 38.473 for 5G NR. Note that though there will be |
|
|
the V1 interface destined for LTE, OAI implements the F1 interface in the LTE
|
|
|
modem.
|
|
|
|
|
|
The code can be found in branch `feature-127-protocol-split`.
|
|
|
The code is merged into `develop`.
|
|
|
|
|
|
# Control plane status (F1-C)
|
|
|
|
|
|
The current implementation is still based on R15.2. It is possible to connect
|
|
|
and disconnect UEs, i.e. especially the disconnect works reliably after a
|
|
|
detach request. As in the current develop branch, a UE is not correctly freed
|
|
|
if synchronization is lost.
|
|
|
detach request. A UE might however not be correctly freed if synchronization
|
|
|
is lost.
|
|
|
|
|
|
The following messages are currently implemented:
|
|
|
|
... | ... | @@ -58,13 +58,13 @@ standard-compliant GTP-U implementation lter. |
|
|
Working F1 configuration files: [`cu.lte.conf`](f1-sample-conf/cu.lte.conf),
|
|
|
[`du.lte.band7.conf`](f1-sample-conf/du.lte.band7.conf)
|
|
|
|
|
|
Check out the branch `feature-127-protocol-split` and compile using the
|
|
|
`build_oai` script as normal. Support for F1AP will be installed. Then, the
|
|
|
same lte-softmodem executable is used to start CU and DU, subject to
|
|
|
configuration parameters, i.e. start your EPC as normal, then run one instance
|
|
|
of the lte-softmodem as [CU](f1-sample-conf/cu.lte.conf) and one as
|
|
|
[DU](f1-sample-conf/du.lte.band7.conf). The basic structure for both files is
|
|
|
unchanged; notable differences to a monolithic deployment are the following:
|
|
|
Build using the `build_oai` script as normal. Support for F1AP will be
|
|
|
installed. Then, the same lte-softmodem executable is used to start CU and DU,
|
|
|
subject toconfiguration parameters, i.e. start your EPC as normal, then run
|
|
|
one instanceof the lte-softmodem as [CU](f1-sample-conf/cu.lte.conf) and one
|
|
|
as [DU](f1-sample-conf/du.lte.band7.conf). The basic structure for both files
|
|
|
is unchanged; notable differences to a monolithic deployment are the
|
|
|
following:
|
|
|
|
|
|
* CU: `tr_s_preference` in the eNodeB configuration is set to `f1`, and there
|
|
|
is configuration for local and remote addresses which I believe are only used
|
... | ... | |