...
We have accomplished the first task of linking ONAP slicing flow to Altran 5GC (New Slice creation and activation). We still need to test the new slice configuration (using UE/gnb simulator), and we are in the process of doing this (using Altran's simulator tool).
Current ONAP + Altran 5GC + Kaloom UPF Demo Setup
We were also told that the UNH lab is now connected to the lab in Montreal, so we can start moving to this.
...
1. Test the new slices using UE/gnb simulator (in progress)
2. Test Altran 5GC slicing deployment in Montreal lab (make sure we can accomplish the same thing we did locally in UNH servers)
3. Integration with Kaloom UPF (later)
4. Depending on the community's decision, switch to Rebaca's ABoT simulator
Question: When to integratiointegrate with Magma? This will happen with the SBP/Magma integration. Question about the Lab in Montreal. Kader/Sandeep can help connect with CENGN.
Emulator Discussion
2 Options proposed for Emulator:
Context: While we are doing an E2E demo, we need an emulator for showing features on the core. Starting with Altran, looking for additional capabilities from Rebaca.
Scenario 1:
Two gNB will be created from the Orchestrator. One gNB’s UE will start registration followed by PDU session creation with a slice (NSSAI - application specific value) . The other UE’s from another gNB can register with a different NSSAI and create another PDU session. The DNN may be different for different slice types (applications).
The 5GC core may select different NFs (say different SMF,UPF) for different slices. These NFs will be selected via NSSF and NRF in 5GC.
Then from two gNB’ (UE simulator) , traffic will be sent for two different PDU session over N3 tunnel.
5GC UPF should act differently for different slice specific traffic
Scenario 2:
The same test can be gone with a single gNB. First one UE will register with a slice (NSSAI -sst) value and create a PDU session. Traffic will be sent for that slice over N3. We can check that slice related traffic is transmitted properly via relevant NFs. Then the UE deregister.
Again the same UE is registered with a different slice (NSSAI – sst) and create PDU session . Again send data over N3 for the new PDU session and check N3 traffic.
Both scenarios ready, Abot install in the environment. After Altran core, we should be able to report, what's working and what's not.
5G Super Blueprint
- 5G Super Blueprint FAQ
- Update on Basic Governance
Heather presented an update of our philosophy and approach to the work. There was a question around inclusion of proprietary components. Things like a compliance program have hard and fast rules, this demo represents more of a community building effort bases on who shows up to contribute (folks signing up to create something in the course of 6-12 months that demo something). We are building something to inspire others. Feedback received that the blueprint needs to be repeatable. The whitepaper until development will match, mirror the work. Challenge will be have something longer term that we can build on. Question of the charter was discussed, option 1, keep it a POC, Option 2, make it legally binding. Maybe, a middle way... mission, vision, mandate to get us started. Decision making traditionally has been around who shows up to make this work. A questions was raised about architecture.
- ONAP Enterprise Working Group Update / Magma Integration
...