In the last few months I needed to make a lot of changes to this
project.I need to implement 5G core but I wanted to make sure that this
didn't affect the 4G source code much. As such, I changed BuildTool from
autotools to MESON and freeDiameter library is applied with new version
1,3,2. So, the project name is changed from NextEPC to Open5GS. These
things are almost finished today.
There are a few things left to do now, including implement GTP path
management before developing 5G core, which will not have a major impact on
the master branch.
Thanks a lot!
On Sat, Nov 2, 2019 at 5:50 AM Spencer Sevilla <sevilla(a)cs.washington.edu>
I admin a couple of small-scale networks, one with ~20 users and one with
~100. They are basic, data-only LTE networks, and do not provide any voice
services, 2g fallback, or interconnect at all. One has two eNBs and the
other has one. We currently use the OAI EPC, but are very interested in
moving over to NextEPC for reasons of stability.
I’ve tested NextEPC in our lab (with only two phones and an SDR) and it
seems to work great. I’ve looked through the code, implemented a feature or
two, and it is much much cleaner than OAI. I’ve also heard widely good
reports of some other deployments.
Anything I should know, or any major issues I should be aware of before I
go ahead and deploy the current master branch? I don’t mind finding/fixing
a couple of bugs and will certainly commit any fixes upstream, just more
asking about any already known fundamental problems, features
unimplemented, or reasons I should postpone a rollout.