5G MEC/Slice BP Architecture
...
The 5G MEC BP mainly consists of two network elements,
Edge Edge connector, deployed in the cloud to enable flexible traffic offloading from the aspects of control interaction with mobile network exposed capabilities, and to subscribe the edge slice between UE and edge application.
Edge gateway (GW), deployed close to the 4G/5G network edge to enable the traffic offloadingfrom the aspects of data plane with local traffic routing, traffic management, etc.
...
5G MEC BP users need to use the Kubernetes Master to onboard an application to the Edge Node. BP support supports applications that can run in a docker container. Docker image tar.gz. The image source can be a docker registry or HTTPS image repository. The image repository can be an external image server or one that can be deployed on the controller. The figure below shows the steps involved in application onboarding.
...
- Edge Node Enrollment: Edge Node enrollment is supported using K8s cluster join.
- Dataplane Service: Steers traffic towards applications running on the Edge Node or the Local Break-out Port.
- Using OVN/OVS as Dataplane - recommended dataplane data plane when incoming and outgoing flows are based on pure IP
- Implemented using kube-ovn
- Provides IP 5-tuple based flow filtering and forwarding
- Same Interface can be used for Inter-App, management, Internet and Dataplane interface
- Application Authentication: Ability to authenticate Edge compute application deployed from Controller so that application can avail/call Edge Application APIs. Only applications that intend to call the Edge Application APIs need to be authenticated. TLS certificate based Authentication is implemented.
...