... | ... | @@ -31,7 +31,7 @@ All other messages can be assumed to *not* be implemented: |
|
|
* All Paging messages
|
|
|
* All Warning Message transmissions
|
|
|
|
|
|
There are the following notes:
|
|
|
Notes:
|
|
|
|
|
|
* Tested up to four UEs
|
|
|
* The CU can continue to run once the DU stops and does not need to be
|
... | ... | @@ -45,13 +45,13 @@ reason being that work started before 3GPP specified the first revision). |
|
|
The current implementation uses Google Protocol Buffers to encapsulate RLC SDUs
|
|
|
and transports them over a configurable UDP tunnel. It is powerful enough to
|
|
|
sustain at least a steady 70Mbps user data rate which is enough for a single
|
|
|
CU-DU link and a single UE saturating the wireless link over 100RB in SISO
|
|
|
CU-DU link and a single UE saturating the wireless link over 100RB in TM1
|
|
|
(measured with OAI). Protocol Buffers are already used for FlexRAN, so no
|
|
|
changes are necessary here in the build script.
|
|
|
|
|
|
Currently, multiple DUs are not supported in the data plane (as in the control
|
|
|
plane). It is planned to replace this implementation with the
|
|
|
standard-compliant GTP-U implementation which.
|
|
|
standard-compliant GTP-U implementation lter.
|
|
|
|
|
|
# Usage
|
|
|
|
... | ... | |