 Hello everyone. Welcome to our lightning talk on multi-access networking in Kubernetes Edge Cloud. I'm Anurag and I'm with my colleagues, Sudhir. We'll be talking through the sessions and have a demo at then. Next slide, please. In this talk, we'll be introducing multi-access edge computing in 5G for IoT devices in enterprise and industrial use cases. 5G is built to connect large number of IoT devices. Some will be intelligent devices and some others will be only sensors. These connections can be over 5G wireless network called NR or a non-3GPP network such as Wi-Fi. The network traffic and workload requirements will need an agile infrastructure. Openness, now called Smart Edge Open, uses Kubernetes to provide such an agile infrastructure and uses a standard way of extending the platform capability. Cloud network applications that are built on microservices architecture for Kubernetes can benefit from these enhancements. Namely orchestration to schedule workload on correct target and networking enhancements to route the traffic to and from the correct application service. Next slide, please. The untrusted non-3GPP interworking function that integrates 5G core network to Wi-Fi is shown here. There is a control pane interface to the access and mobility management function or AMF over N2. And then there is a user pane interface to the user pane function or UPF over N3. Other enhancements in the wireless LAN side, they are not in focus of our discussion today, so they're not shown here. Next slide, please. To understand the integration of Wi-Fi, let's first look at one of the 5G building blocks in OpenNet, the application function. It sits on the control pane and interacts with the 3GPP 5G core network in order to provide services, for example, to support the application influence on traffic routing, access to network exposure function or the NEF as it's called, interaction with 5G policy framework for policy control. Based on operator deployment, application functions considered to be trusted by the operator, they can be allowed to interact directly with the relevant network functions. If the application function is not allowed by the operator to access directly the trusted network functions, then it can use external exposure functions such as network exposure functions, as we mentioned earlier, to interact with relevant network functions. The functionality and the purpose of application functions are defined in the relevant GPP specifications. Next slide, please. This slide shows how we integrate N3IWs with AF in OpenNESS to provide multi-access edge connectivity. OpenNESS microservices showing integration of network functions are marked here accordingly. With that, I would like to hand over presentation to my colleague Sudhir over to you, Sudhir. Thank you, Anurag. This is Sudhir here. So as Anurag explained in this slide, what is an application function and where N3IW is present. So this slide shows how the application function talks to the 5G control plane and how the N3IW talks to the access mobility function and the UPF. Together with N3IW and 5G and the LTE access to the devices, it makes the edge networks a truly multi-access edge computing. So let's look into that. What is actually in there in the AF and what it provides? So this OpenNESS application function provides APIs for traffic influencing. So the OpenNESS AF interacts to the UDR, PCF, the policy control function, binding support function and the session management function of the 5G code networks through the network exposure function. The OpenNESS provides a reference network exposure function or it's an also it can work with a third party network exposure function. Through the traffic influence, OpenNESS AF can influence the traffic steering to the edge locations. The influence can be based on the traffic information or you can influence about the traffic for a single device, a group of devices or ready devices. And you can also have temporal validity which says at what time or duration you want the traffic steering to be enabled. And the most important one is a spatial validity condition. So this is where the N3IWF can come into picture. So through the AF, you can tell to the core network which global RAN node ID, whether it is an N3IWF ID or a G node ID through which you want to steer the traffic to the edge location. In addition to that, OpenNESS also provides APIs for PFD management of packet flow description management by accessing to the UDR and SMF through the network exposure functions. The PFD helps the UPF to accurately identify an application. Having seen about the AF APIs, let us see where AF gets deployed in an OpenNESS Kubernetes cluster. The picture on the right side is the Kubernetes control plane where we have the AF microservice running as a pod. And this AF microservice communicates with the network either through the network exposure function which can be the OpenNESS reference network exposure function or it can be a third party network function. And also from the control plane when you deploy the N3IWF function. So this picture shows where the N3IWF would be running on the worker node. So this N3IWF here, when you deploy it, you generate an N3IWF ID which the application function is aware of that. And this N3IWF ID is using the traffic steering APIs. So now we have seen where AF6 and what N3IWF is there in this location. Let's look at what support the OpenNESS Kubernetes cluster provides for deploying an N3IWF pod. So in this picture, you can see here that the N3IWF can be deployed as a cloud network function. So to deploy the N3IWF for CNF, you need some good capabilities from the edge node which is features like MULTUS and SRIOV. So as we know, MULTUS allows a pod to provide multiple network interfaces. And SRIOV allows you to have multiple network interfaces for the same thing. And the next one is the huge pages which provides the CNF to have to better optimize with the memory management. And then for accelerators for IPsec, you have QAT. QAT accelerator support on the OpenNESS edge cluster. And in order to detect all of this so that your N3IWF pod is placed on the right edge cluster, we need to have the OpenNESS edge cluster provides the feature of the node feature discovery, NFD. So having seen AF and N3IWF, I think any presentation would not end with a good demo. So let's look how an N3IWF is deployed on the OpenNESS edge cluster. I'll switch over to the demo here. In this demo here, you can see a screen which has three terminals. The left side one is the terminal where the N3IWF would be deployed. The right topmost one is the terminal where a simulated device would be deployed. And the bottom most right terminal is the place where the 5G code network is deployed. So let's start first deploying with the N3IWF network. Okay, here if you see, you have a reference N3IWF package. So which has all the required deployment files. So at this point, we do it through the helm. We install the N3IWF and once the N3IWF is installed, we'll see that the N3IWF pod is up and running. So now let's enter into the N3IWF pod. This is an optional step. You can automate the starting of the N3IWF containers, the N3IWF containers. So here we are first starting the high performance data plane, which is based on Fido's VPP. And then so it shows what are the interfaces which gets created. We have two virtual functions here. And then now let's switch over to the starting of the control plane, 5G control plane. This is based on a open source 5G network called as Free5GC. Okay, so now let me start the control plane on the N3IWF side. So now the N3IWF control plane is up. Okay, and if you see, it's already made a connection with the 5G network. Meanwhile, let me start the UE. So right post windows shows the UE part here. Let me first trigger the, before triggering the registration, let me do a ping to see if the networks are reachable. So I am doing a ping and the network is reachable here. So now I've done the registration. At this point, if you see the UE is successfully registered with the 5G core. Okay, now I'm establishing a PDU connection, a data connection with the 5G core network. And then I'll send some data to the 5G network. So this is a ping data which I'm sending, which is going to the 5G network. And after the ping data part, I'll release the data connection and then trigger the UED registration. So at this point, I'm terminating the UE part here. So this demo shows for you how the N3IWF is deployed an openness edge cluster. And we could have a simulated UE and with the 5G network. How we could and simulated UE and the 5G network demonstration of the N3IWF running on the openness edge cluster.