... | ... | @@ -55,14 +55,16 @@ standard-compliant GTP-U implementation which. |
|
|
|
|
|
# Usage
|
|
|
|
|
|
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
|
|
|
configuratio parameters. A sample configuration to run everything on the same
|
|
|
PC is [cu.lte.conf](f1-sample-conf/cu.lte.conf) and
|
|
|
[du.lte.band7.conf](f1-sample-conf/du.lte.band7.conf) and only the EPC need to
|
|
|
be changed. The basic structure for both files is unchanged; notable differences
|
|
|
to a monolithic deployment are the following:
|
|
|
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:
|
|
|
|
|
|
* 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
|
... | ... | |