Edge computing topology information exposure
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.
1. An edge computing (EC) entity for managing an EC system, the EC entity comprising one or more processors coupled to a memory, which, alone or in combination, are configured to execute a method comprising:
obtaining topology information of the EC system;
exposing the topology information to a network exposure function (NEF) or a policy control function (PCF) of a third generation partnership project (3GPP) system by using an interface between the EC system and the 3GPP system; and
exposing, as the topology information, a weight or a priority of each of a plurality of edge data centers (EDCs) in the EC system to the NEF or the PCF of the 3GPP system by using the interface between the EC system and the 3GPP system,
wherein the EC system belongs to a non-3GPP system.
2. The EC entity according to claim 1 , wherein the method further comprises exposing, as the topology information, a topology of all EDCs in the EC system to the 3GPP system.
3. The EC entity according to claim 1 , wherein the topology information comprises at least one of:
a load of at least one EDC in the EC system,
a load on at least one link to the at least one EDC in the EC system,
an availability of the at least one EDC in the EC system,
a location of the at least one EDC in the EC system,
an address or identification of the at least one EDC in the EC system, or
multiple access information of the EC system.
4. The EC entity according to claim 1 , wherein the method further comprises determining the weight or the priority of an EDC of the plurality of EDCs based on a capacity or a load of the EDC in the EC system compared to other EDCs in the EC system.
5. The EC entity according to claim 1 , wherein the method further comprises determining the weight of an EDC of the plurality of EDCs dynamically or with a determined spatial or temporal validity.
6. The EC entity according to claim 1 , wherein the method further comprises exposing, as the topology information, a determined selection algorithm for selecting a plurality of EDCs to the 3GPP system.
7. The EC entity according to claim 6 , wherein the determined selection algorithm includes a round robin algorithm, user equipment proximity based algorithm, or an algorithm based on service differentiation.
8. The EC entity according to claim 1 , wherein the method further comprises exposing the topology information via an interface to:
a management entity of the 3GPP system, or
an application function (AF) of the 3GPP system.
9. The EC entity according to claim 1 , wherein the method further comprises providing topology information updates to the 3GPP system to:
an application function (AF) of the 3GPP system, or
the NEF of the 3GPP system.
10. A mobile communication core (MCC) entity for a MCC system, the MCC entity comprising one or more processors coupled to a memory, which, alone or in combination, are configured to execute a method comprising:
receiving topology information of an edge computing (EC) system from an EC entity of the EC system;
providing the topology information to a network exposure function (NEF) or a policy control function (PCF) of the MCC system by using an interface between the EC system and the MCC system; and
providing, as the topology information, a weight or a priority of each of a plurality of edge data centers (EDCs) in the EC system to the NEF or the PCF of the MCC system by using the interface between the EC system and the MCC system, and
wherein the MCC system is different from the EC system,
wherein the MCC system belongs to a third generation partnership project (3GPP) system and the EC system belongs to a non-3GPP system.
11. The MCC entity according to claim 10 , wherein the MCC entity is a MCC system management entity or is an application function (AF) of the MCC system.
12. The MCC entity according to claim 10 ,
wherein the method further comprises providing the topology information together with one or more data network access identifiers (DNAIs) to the NEF or the PCF, and
wherein each of the DNAIs is related to an EDC in the EC system.
13. The MCC entity according to claim 10 , wherein the method further comprising providing the topology information together with one or more data network access identifiers (DNAIs) to the PCF via a network data analytics function (NWDAF).
14. A method for an edge computing (EC) system, the method comprising:
obtaining topology information of the EC system; and
exposing the topology information to a network exposure function (NEF) or a policy control function (PCF) of a third generation partnership project (3GPP) system by using an interface between the EC system and the 3GPP system, and exposing, as the topology information, a weight or a priority of each of a plurality of edge data centers (EDCs) in the EC system to the NEF or the PCF of the 3GPP system by using the interface between the EC system and the 3GPP system, wherein the 3GPP system is a mobile communication core (MCC) system that is different from the EC system,
wherein the EC system belongs to a non-3GPP system.
15. A method for a mobile communication core (MCC) system, the method comprising:
receiving topology information of an edge computing (EC) system;
providing the topology information to a network exposure function (NEF) or a policy control function (PCF) of the MCC system by using an interface between the EC system and the MCC system; and
providing, as the topology information, a weight or a priority of each of a plurality of edge data centers (EDCs) in the EC system to the NEF or the PCF of the MCC system by using the interface between the EC system and the MCC system,
wherein the MCC system is different from the EC system, and
wherein the MCC system belongs to a third generation partnership project (3GPP) system and the EC system belongs to a non-3GPP system.
16. The MCC entity according to claim 10 , wherein the topology information comprises:
a load of at least one EDC in the EC system,
a load on at least one link to the at least one EDC in the EC system,
an availability of the at least one EDC in the EC system,
a location of the at least one EDC in the EC system,
an address or identification of the at least one EDC in the EC system, and
multiple access information of the EC system.