SD-Core Roadmap work items
Below is the list of features with high priority
- Specification (3GPP) upgrade of 5G Core (SD-Core)
- SBI interface
- PFCP interface (N4)
- NAS interface (N1)
- NGAP interface (N2)
- GTPu interface (N3, N6, N9)
- gNBSim support
- data support
- handover support
- UI support in gNBSim
- Upgrade mongodb and kafka to latest versions
TLS support on SBI interface(completed)- Dashboard for CI/CD repo health
- Scalable SD-Core
- Performance Results for UPF
- CD tool (gitops) integration for community members
- Creation of NFs per Slice
- UPF support based on Slice Id & DNN. Same UPF may support multiple DNNs but same slice Id.
Details about Specification Upgrade
- Specification upgrade:
This has multiple dimensions. I shall list the tasks required to do the specification upgrade
- Service Based Interface Update
- Take new openAPI files from specification
- Generating the golang code for openAPI
- Created golang code using theopenAPIimage/container for one yaml file. I need to automate the process for all yaml files
- Can do this for release 17 files and for release 18 files. Which release should we target? I think we should target R18. What do you think? Here are the release timelines: https://www.3gpp.org/specifications-technologies/releases
- Use newly generateopenAPImodels in at least 1 or 2 Network Functions
- PFCP Specification update.
- Impacts UPF & SMF
- UPF currently uses go-pfcp project and SMF uses local pfcp code. We should plan to move to go-pfcp as standard way.
- NAS specification upgrade
- Impacts SMF, AMF network functions
- Impacts simulator like gNBSim
- Impacts the testing with real gNodeB, mobiles.
- NGAP specification upgrade
- Impacts AMF network function
- Created golang code (asn1 → proto → go) but the resulting GO code looks very different to the structure of the current ngap repository. What is the appropriate process to follow?
- ngap repository uses/calls
aper
repository. Does the aper repository also needs to be updated?
- Impacts simulator like gNBSim
- Impacts the testing with real gNodeB
- Impacts AMF network function
- gtpu specification upgrade (low priority)
- Impacts UPF network function
- Impacts optionally SMF
- Impacts gNBSim
- impacts the testing with real gNodeB
- Service Based Interface Update
- gNodeB Simulator changes. Only critical features listed below
- gNodeB handover Xn handover
- gNodeB handover N2 handover
- Data support
- Enable all profiles by default?
- Upgrade mongodb and kafka to latest versions
- Latest versions are mongodb 15.6.7 and kafka 29.3.3
- mongdb was updated from 13.6.4 to 13.16.4 and kafka was upgraded from 20.0.4 to 23.0.7, which are the newest versions that do not require any change in the SD-Core
- Dashboard for CI/CD repo health
- Ajay Lotan Thakur please provide specifics of what you have in mind about this ("dashboard")
- Aspects to complete for CI/CD (in general) are: 1) Make mandatory (required) to pass all GHAs before a PRs is merged; 2) Publish "latest" image to DockerHub?; 3) Does it make sense to have "three" places/registries where images are published (DockerHub, Opennetworking, Aetherproject)? This needs to be improved
- Scalable SD-Core
- ??
- Performance Results for UPF