An edge computing (EC) entity belongs to an EC system, and a mobile communication core MCC entity belongs to a MCC system, like a 3GPP system. The EC entity is configured to obtain topology information of the EC system, and expose the topology information to another network, in particular to a MCC system. The MCC entity is configured to receive topology information of an EC system from the EC entity, and provide the topology information to a network exposure function (NEF) or to a policy control function (PCF) of the MCC system.

Embodiments herein provide methods of sidelink communication between nodes including resource selection, congestion control, and/or resource signaling. Other embodiments may be described and claimed.

Embodiments are directed towards embodiments are directed toward systems and methods for user plane function (UPF) and network slice load balancing within a 5G network. Example embodiments include systems and methods for load balancing based on current UPF load and thresholds that depend on UPF capacity; UPF load balancing using predicted throughput of new UE on the network based on network data analytics; UPF load balancing based on special considerations for low latency traffic; UPF load balancing supporting multiple slices, maintaining several load-thresholds for each UPF and each slice depending on the UPF and network slice capacity; and UPF load balancing using predicted central processing unit (CPU) utilization and/or predicted memory utilization of new UE on the network based on network data analytics.

A method, system, and storage medium are provided. The method may include receiving, by a network repository function (NRF), registration information of each of a plurality of network functions (NFs), determining, by the NRF, load balance prioritization information for the plurality of NFs based on the received registration information, and transmitting, by the NRF to a service mesh control plane, the load balance prioritization information. The service mesh control plane may be configured to perform load balancing on the plurality of NFs based on the load balance prioritization information.

This invention flexibly controls the number of user planes in a communication system. In a communication system, a base station is in a local area network and at least one user plane function arranged in a cloud are connected. A determination is made as to whether or not a new user plane function should be added, taking into consideration: the traffic amount, from the maximum traffic amount using the local area network, of user data transferred by the at least one user plane function using the local area network; and an anticipated traffic amount of a new user plane function.

Embodiments are directed towards embodiments are directed toward systems and methods for user plane function (UPF) and network slice load balancing within a 5G network. Example embodiments include systems and methods for load balancing based on current UPF load and thresholds that depend on UPF capacity; UPF load balancing using predicted throughput of new UE on the network based on network data analytics; UPF load balancing based on special considerations for low latency traffic; UPF load balancing supporting multiple slices, maintaining several load-thresholds for each UPF and each slice depending on the UPF and network slice capacity; and UPF load balancing using predicted central processing unit (CPU) utilization and/or predicted memory utilization of new UE on the network based on network data analytics.

An apparatus and system are provided to provide the progress and result of lifecycle management (LCM) processes of an edge application server (EAS) virtual network function (VNF) in a cloud. The lifecycle management process information is included in the Network Resource Models (NRMs). An identifier to identify the management service (MnS) consumer initiating the LCM process is included in an EASFunction Information Object Class (IOC), which represents properties of the EAS VNF, and another IOC, which represents requirements to deploy the EAS VNF. The IOC containing the LCM process information permits the consumer to correlate the LCM result with the LCM request. LCM solutions are presented to deploy and terminate EAS VNFs in the cloud using the LCM process information to report the progress and result of the LCM process.

An apparatus and system are provided to provide the progress and result of lifecycle management (LCM) processes of an edge application server (EAS) virtual network function (VNF) in a cloud. The lifecycle management process information is included in the Network Resource Models (NRMs). An identifier to identify the management service (MnS) consumer initiating the LCM process is included in an EASFunction Information Object Class (IOC), which represents properties of the EAS VNF, and another IOC, which represents requirements to deploy the EAS VNF. The IOC containing the LCM process information permits the consumer to correlate the LCM result with the LCM request. LCM solutions are presented to deploy and terminate EAS VNFs in the cloud using the LCM process information to report the progress and result of the LCM process.

A virtualization system (1) comprising a baseband processing arrangement (11,12). The virtualization system is configured to provide a plurality of virtual machines (41,42), each virtual machine having an allocation of baseband processing capacity provided by the baseband processing arrangement for serving remote radio units (6). The virtualization system is configured to dynamically re-allocate baseband processing capacity between virtual machines (41,42) based on at least one parameter related to radio domain requirements of the remote radio units (6).

The present invention relates to Edge Computing (EC) systems. The invention presents an EC entity of an EC system, and a Mobile Communication Core (MCC) entity for a MCC system, like a 3GPP system. The EC entity is configured to obtain topology information of the EC system, and expose the topology information to another network, in particular to a MCC system. The MCC entity is configured to receive topology information of an EC system from the EC entity, and provide the topology information to a Network Exposure Function (NEF) or to a Policy Control Function (PCF) of the MCC system.