Multi-slice support for MEC-enabled 5G deployments

1. A system configured to track network slicing operations within a Fifth Generation (5G) communication network, the system comprising:

memory; and

processing circuitry coupled to the memory, the processing circuitry configured to:

determine a network slice instance (NSI) associated with a quality of service (QoS) flow of a user equipment (UE), the NSI communicating data for a network function virtualization (NFV) instance of a Multi-Access Edge Computing (MEC) system within the 5G communication network;

retrieve latency information for a plurality of communication links used by the NSI, the plurality of communication links including a first set of non-MEC communication links associated with a radio access network (RAN) of the 5G communication network and a second set of MEC communication links associated with the MEC system;

generate a slice configuration policy based on the retrieved latency information and slice-specific attributes of the NSI; and

reconfigure network resources of the 5G communication network used by the NSI based on the generated slice configuration policy.

2. The system of claim 1 , wherein the NFV instance is provided by a MEC application associated with the QoS flow, the MEC application executing on virtual resources of a network function virtualization infrastructure (NFVI) of the MEC system.

3. The system of claim 2 , wherein the MEC system comprises an MEC host executing the NFV instance.

4. The system of claim 3 , wherein the slice configuration policy comprises a virtual machine (VM) allocation and handoff policy and to reconfigure the network resources, the processing circuitry is configured to:

allocate additional network resources of the 5G communication network to the MEC host based on the VM allocation and handoff policy.

5. The system of claim 4 , wherein to reconfigure the network resources, the processing circuitry is further configured to:

perform a VM handoff to relocate the MEC application to execute on virtual resources of a second NFVI of the MEC system based on the VM allocation and handoff policy.

6. The system of claim 2 , wherein the first set of non-MEC communication links comprises:

a communication links between the UE and the RAN;

a communication link associated with an N3 interface between the RAN and a MEC data plane of the MEC system, the MEC data plane performing a user plane function of the 5G communication network; and

a communication link associated with an N6 interface between the MEC data plane and a local data network including the virtual resources of the NFVI.

7. The system of claim 6 , wherein the second set of MEC communication links comprises at least one communication link associated with an Mp1 interface of the MEC application.

8. The system of claim 7 , wherein the at least one communication link associated with the Mp1 interface is a communication link between the MEC application and an MEC application programming interface (API) within an MEC platform of the MEC system.

9. The system of claim 8 , wherein the latency information includes processing delay associated with obtaining radio network information (RNI) or location information by the MEC API, based on a request from the MEC application associated with the QoS flow.

10. The system of claim 1 , wherein the processing circuitry is configured to:

retrieve a first portion of the latency information associated with the first set of communication links from a service coordinating entity of the 5G communication network.

11. The system of claim 10 , wherein the service coordinating entity of the 5G communication network is an Operations Support System (OSS) of the 5G communication network.

12. The system of claim 10 , wherein the processing circuitry is configured to:

retrieve a second portion of the latency information associated with the second set of communication links from a service coordinating entity of the MEC system.

13. The system of claim 12 , wherein the service coordinating entity of the MEC system is a Multi-Access Edge Orchestrator (MEAO) of the MEC system.

14. A computing device in a Multi-Access Edge Computing (MEC)-enabled Fifth Generation (5G) communication network, the device comprising:

a network interface card (NIC); and

processing circuitry coupled to the NIC, the processing circuitry configured to perform operations to:

determine a network slice instance (NSI) associated with a quality of service (QoS) flow of a user equipment (UE), the NSI communicating data for a network function virtualization (NFV) instance of a Multi-Access Edge Computing (MEC) system within the 5G communication network;

retrieve via the NIC, latency information for a plurality of communication links used by the NSI, the plurality of communication links including a first set of non-MEC communication links associated with a radio access network (RAN) of the 5G communication network and a second set of MEC communication links associated with the MEC system;

generate a slice configuration policy based on the retrieved latency information and slice-specific attributes of the NSI; and

reconfigure network resources of the 5G communication network used by the NSI based on the generated slice configuration policy.

15. The computing device of claim 14 , wherein the NFV instance is provided by a MEC application associated with the QoS flow, the MEC application executing on virtual resources of a network function virtualization infrastructure (NFVI) of the MEC system.

16. The computing device of claim 15 , wherein the MEC system comprises an MEC host executing the NFV instance, and wherein the computing device comprises a second MEC host configured as a Network Function Virtualization Orchestrator (NFVO) of the MEC system, the NFVO including a NFV slice control function (NFV-SCO) generating the slice configuration policy.

17. The computing device of claim 16 , wherein the slice configuration policy comprises a virtual machine (VM) allocation and handoff policy and to reconfigure the network resources, the processing circuitry is configured to:

allocate additional network resources of the 5G communication network to the MEC host based on the VM allocation and handoff policy.

18. The computing device of claim 14 , wherein the slice-specific attributes of the NSI include one or more of the following:

an end-to-end (E2E) latency requirement associated with communication of data within the NSI;

a minimum available bandwidth requirement for the plurality of communication links of the NSI; and

a communication throughput requirement of at least one of the plurality of communication links of the NSI.

19. The computing device of claim 14 , wherein the processing circuitry is configured to:

select a utility function from a plurality of available utility functions based on a slice service level agreement (SLA) associated with the NSI; and

generate the slice configuration policy further based on minimizing the selected utility function.

20. The computing device of claim 19 , wherein the utility function is one of the following:

a 5G efficiency-centric utility function for minimizing end-to-end (E2E) delay within the 5G communication network;

an MEC efficiency-centric utility function for minimizing E2E delay within the MEC system; and

an overall efficiency utility function for minimizing breaches of the slice SLA.

21. At least one non-transitory machine-readable storage medium comprising instructions, wherein the instructions, when executed by a processing circuitry of a computing device operable a Multi-Access Edge Computing (MEC)-enabled Fifth Generation (5G) communication network, cause the processing circuitry to perform operations that:

determine a network slice instance (NSI) associated with a quality of service (QoS) flow of a user equipment (UE), the NSI communicating data for a network function virtualization (NFV) instance of a Multi-Access Edge Computing (MEC) system within the 5G communication network;

retrieve latency information for a plurality of communication links used by the NSI, the plurality of communication links including a first set of non-MEC communication links associated with a radio access network (RAN) of the 5G communication network and a second set of MEC communication links associated with the MEC system;

generate a slice configuration policy based on the retrieved latency information and slice-specific attributes of the NSI; and

reconfigure network resources of the 5G communication network used by the NSI based on the generated slice configuration policy.

22. The non-transitory machine-readable storage medium of claim 21 , wherein the NFV instance is provided by a MEC application associated with the QoS flow, the MEC application executing on virtual resources of a network function virtualization infrastructure (NFVI) of the MEC system.

23. The non-transitory machine-readable storage medium of claim 22 , wherein the MEC system comprises an MEC host executing the NFV instance, and wherein the computing device comprises a second MEC host configured as a Network Function Virtualization Orchestrator (NFVO) of the MEC system, the NFVO including a NFV slice control function (NFV-SCO) generating the slice configuration policy.

24. The non-transitory machine-readable storage medium of claim 23 , wherein the slice configuration policy comprises a virtual machine (VM) allocation and handoff policy and to reconfigure the network resources, the instructions further causing the processing circuitry to:

allocate additional network resources of the 5G communication network to the MEC host based on the VM allocation and handoff policy; and

perform a VM handoff to relocate the MEC application to execute on virtual resources of a second NFVI of the MEC system based on the VM allocation and handoff policy.

25. The non-transitory machine-readable storage medium of claim 21 , wherein the processing circuitry is configured to:

select a utility function from a plurality of available utility functions based on a slice service level agreement (SLA) associated with the NSI; and

generate the slice configuration policy further based on minimizing the selected utility function.