Patent Description:
Towards 5th Generation mobile technology (<NUM>) substantial efforts are made, in order to enable next generation communication systems. The <NUM> endeavor is particularly driven by diversified use cases and scenarios. These range from high bandwidth to ultra-low latency and high reliability use cases. To support such use cases, EC is regarded as an important building block.

As per 3GPP SA1 TR <NUM> (see http://www. <NUM>), MEC is identified as being important for critical low latency applications, e.g. automation and Vehicle-to-Anything (V2X). This is due to the very low latencies offered by deploying smaller Edge Data Centers (EDCs) of a MEC close to User Equipment (UE), e.g. close to vehicles or robots. Also non-3GPP platforms and architectures are getting more mature, e.g.: ETSI MEC (www. org Multi Access Edge Computing), ONAP (www. org), Openstack, etc. These platforms allow more on-demand deployment of EC systems close to 3GPP access points (e.g. Radio Access Networks (RANs)).

3GPP TS <NUM> defines how the <NUM> system supports EC, particularly through:.

The focus of the present invention is specifically around the AF influence on the traffic routing. The standard implementation defines how the AF can conventionally trigger the (re)routing of traffic towards a local EDC. Currently, this rerouting is performed via an AF request sent to the PCF by specifying a list of Data Network Access Identifiers (DNAIs). A DNAI is an identifier to reach a Data Network Name (DNN) hosting MEC nodes that host EDCs, which serve edge computing traffic. That is, each DNAI is related to an EDC in the MEC system.

One issue of this current standard implementation is that the AF sends only limited information about the EDCs, namely basically only the list of DNAIs. This limits the amount of information available to the 3GPP system, and leads to the following problems:.

Accordingly, the use of a simple DNAI list to request traffic (re)routing is the reasons for the above problems, and is thus not enough to handle complex EC/MEC scenarios, particularly for verticals (e.g. V2X).

<CIT> discloses systems and method for creating slices at a cell edge to provide computing services.

So far, this has been addressed intensive manual configuration and/or deployment specific implementations. However, this has the disadvantage that the configuration or implementation cannot be reused. Currently no topology information or dynamic load information can be conveyed from a large number of EDCs, as there is no standardized interface for this.

The present invention thus aims to improve interactions between an EC system and another network, particularly a MCC system like a 3GPP system. The objective of the invention is in particular to realize more efficient EC enabled network systems. The invention intends to provide more information about the EC to the other network, in order to facilitate a more efficient and better selection process at the other network.

It is noted that in embodiments of the invention, the EC system is specifically a MEC system.

The objective of the present invention is achieved by the solution provided in the enclosed independent claims.

In particular the present disclosure proposes topology information exposure from the EC system towards the other network (e.g. MCC or 3GPP system). Thereby, three levels of topology information exposure are used: full exposure, weighted exposure, and algorithmic exposure. These three levels can be used as per the deployment scenarios. An implementation of the invention may specifically base on a management system access of the MCC system, as well as an AF access towards the MCC system.

In a first aspect of the invention, the entity is configured to expose, as the topology information, a determined selection algorithm for selecting EDCs to the other network.

For instance, a desired selection criterion may be exposed in this way, e.g. Round Robin, shortest path etc. The other network is accordingly provided clear instructions for efficiently selecting one or more EDCs.

Notably, it is also possible that the entity is configured to expose, as the topology information, a full topology of all EDCs, or a weight or priority off each EDC, together with the determined selection algorithm for selecting the EDCs.

In a further implementation form of the first aspect, the determined selection algorithm includes a Round Robin algorithm, UE proximity based algorithm, and/or an algorithm based on service differentiation.

Generally, the selection algorithm may be a UE profile based algorithm, wherein UE location is an example of a UE profile. The algorithm could also be a time based algorithm.

In a further implementation form of the first aspect, the entity is configured to expose the topology information via an interface to a management entity of the other network, a NEF of the other network, or an AF of the other network.

In a further implementation form of the first aspect, the entity is configured to provide topology information updates to the other network, particularly via an interface to an AF of the other network, or an NEF of the other network.

Topology updates reflect topology changes of the EC system. The topology updates may be provided by exposing complete new topology information. However, the topology updates may also be provided incrementally with respect to previously exposed topology information.

A second aspect of the invention provides a 3GPP MCC system comprising an MCC entity, wherein the MCC entity is configured to receive topology information of an EC system from an EC entity, and provide the topology information to a NEF or a PCF of the 3GPP system. In particular, the MCC entity is configured to receive, as the topology information, a determined selection algorithm for selecting EDCs.

From the NEF or PCF, the topology information can be further provided to the SMF, which can then make a decision about which EDCs to select. According to the invention, the decision making entity in the MCC has sufficient information about the topology of the EC system, e.g. about the locations and load of the EDCs. Overall, by receiving the topology information from the EC system, a better and more efficient selection can be made at the 3GPP MCC system.

In an implementation form of the second aspect, the MCC entity is a 3GPP MCC system management entity or is an AF of the 3GPP MCC system.

In a further implementation form of the second aspect, the MCC entity is configured to provide the topology information together with one or more DNAIs to the NEF or PCF, wherein each DNAI is related to a DC in the EC system.

Thus, the selection of the EDCs (DC in EC system) can be made based on DNAIs and topology information.

In a further implementation form of the second aspect, the MCC entity is configured to provide the topology information together with one or more DNAIs to the PCF via a Network Data Analytics Function (NWDAF) of the MCC entity, wherein the NWDAF is further configured to process the topology information based on the history or combine it with other information from the networks, e.g. UE location statistic, before providing it to the PCF.

A third aspect of the invention provides a method for an EC system, the method comprising obtaining topology information of the EC system, and exposing the topology information to another network, in particular to a 3GPP MCC system.

In the third aspect, the method comprises exposing, as the topology information, a determined selection algorithm for selecting EDCs to the other network.

In a further implementation form of the third aspect, the determined selection algorithm includes a Round Robin algorithm, UE proximity based algorithm, and/or an algorithm based on service differentiation.

In a further implementation form of the third aspect, the method comprises exposing the topology information via an interface to a management entity of the other network, a NEF of the other network, or an AF of the other network.

In a further implementation form of the third aspect, the method comprises providing topology information updates to the other network, particularly via an interface to an AF of the other network, or an NEF of the other network.

Accordingly, the method of the third aspect and its implementation forms achieve all advantages and effects of the entity of the first aspect and its respective implementation forms.

A fourth aspect of the present invention provides a method for a 3GPP MCC system, the method comprising: receiving, by an MCC entity, topology information of an EC system; providing, by the MCC entity, the topology information to a NEF or a PCF of the MCC system; sending, by the NEF or the PCF, the received topology information to an SMF of the 3GPP MCC system; and selecting, by the SMF, one or more EDCs based on the received topology information. The method comprises receiving, by the MCC entity, a determined selection algorithm for selecting EDCs as the topology information.

In an implementation form of the fourth aspect, the MCC entity is a 3GPP MCC system management entity or is an AF of the 3GPP MCC system.

In a further implementation form of the fourth aspect, the method comprises providing the topology information together with one or more DNAIs to the NEF or PCF, wherein each DNAI is related to an EDC in the EC system.

In a further implementation form of the fourth aspect, the method comprises providing the topology information together with one or more DNAIs to the PCF via a NWDAF.

Accordingly, the method of the fourth aspect and its implementation forms achieve all advantages and effects of the entity of the second aspect and its respective implementation forms.

The above described aspects and implementation forms of the invention will be explained in the following description of specific embodiments in relation to the enclosed drawings, in which.

<FIG> shows an EC entity <NUM> according to an embodiment of the invention. The EC entity <NUM> is particularly configured to manage an EC system <NUM>, in particular, an MEC system. It may thus be located in the EC system <NUM>. The entity <NUM> may, for instance, be a management entity of the EC system, i.e. may be implemented by a Mobile Edge Computing Management System (MEC MS). It may also be implemented by a Mobile Edge Orchestrator or a Mobile Edge Platform Manager.

The EC entity <NUM> of <FIG> is configured to obtain topology information <NUM> of the EC system <NUM>. The topology information <NUM> may, for example, be generated by the EC entity <NUM>, or may be received from another dedicated topology information generation entity, or retrieved from a storage maintaining (pre)defined topology information <NUM> about the EC system <NUM>. Further, the EC entity <NUM> is configured to expose (dotted line) the topology information <NUM> to another network <NUM>, wherein the other network <NUM> is a MCC system like a 3GPP system, e.g. a <NUM> system. The entity <NUM> may specifically expose the topology information <NUM> by sending it to the other network <NUM>, or by sharing it with the other network <NUM> such that the other network <NUM> can retrieve it from the entity <NUM> or some memory.

<FIG> shows a MCC entity <NUM> according to an embodiment of the invention. The MCC entity <NUM> is particularly suitable for a MCC system <NUM> like a 3GPP system. The MCC entity <NUM> may be a MCC system management entity, e.g. may be a 3GPP Management System (3GPP MS) or may be an AF.

The MCC entity <NUM> is configured to receive (dotted line) topology information <NUM> of an EC system <NUM> from an EC entity <NUM>, for instance from the EC entity <NUM> shown in <FIG> and described above. The MCC entity <NUM> may then provide the received topology information <NUM> further to a NEF <NUM> or a PCF <NUM>, which may again provide it further to a decision taking entity of the MCC system <NUM>, e.g. a SMF. That is, the MCC entity <NUM> is configured to distribute the topology information <NUM> in the MCC system <NUM>.

<FIG> shows an architecture and interaction of an EC system <NUM>, particularly a MEC system, and a 3GPP system (5GS) as the other network <NUM>. A standard architecture is assumed for both the MEC system <NUM> (e.g. based on ETSI standard) and the 3GPP system <NUM>. In <FIG>, a communication service customer (which can e.g. be a vertical customer) may be interested in deploying an MEC application near its UE <NUM> (for example, a car in case the vertical is a car manufacturer).

Three actions may be taken done by the communication service customers:.

<FIG> shows a simplified architecture of a MEC system <NUM> and a 3GPP system <NUM> that work together. In particular, a high-level architecture of each of the two systems <NUM> and <NUM> is shown. The invention provides interfaces ("MEC Topology exposure") that enable the topology information <NUM> exposure from the MEC system <NUM> towards the 3GPP system <NUM>. The topology information <NUM> exposure is first being conveyed from the MEC system <NUM> (e.g. from an MEC entity <NUM>, like the Mobile Edge Orchestrator or the Mobile Edge platform manager, or another entity in the MEC system <NUM>) over a new interface MEC-3GPP to the AF (which acts in <FIG> as the MCC entity shown in <FIG> and is thus labelled <NUM>), which in turns uses existing interfaces N5 towards the NEF <NUM> (for an untrusted AF <NUM>) or existing interfaces N5 towards the PCF <NUM> (for a trusted AF <NUM>) to forward the topology information <NUM>. In order to route traffic from a certain UE <NUM> to an EDC <NUM> (i.e. a local DN for EC), the SMF <NUM> advantageously knows the locations of the applications. Such locations are represented using the identifiers called DNAI. These DNAIs are sent from the AF <NUM> to the PCF/NEF <NUM>/<NUM>. For a full detailed description of the technologies defined in 5GS, reference is made to 3GPP Sec TS <NUM> Section <NUM>. According to the invention, the information exchanged between the MEC system <NUM> and the 3GPP AF <NUM>, as well as the information exchanged between the AF <NUM> and NEF/PCF <NUM>/<NUM>, is extended, particularly by additionally including the topology information <NUM> of the MEC system <NUM>. The benefit is a much better interworking of the two systems <NUM> and <NUM>, and a better quality of service, due to a more efficient EDC <NUM> selection process at the 3GPP system <NUM>.

Three schemes to enhance the MEC system/3GPP system <NUM>/<NUM> interaction by including said topology information <NUM> are envisaged. These schemes are based on different topology information <NUM> exposure levels:.

<FIG> shows a message flow diagram in an architecture and for an interaction of a MEC system <NUM> and a 3GPP system <NUM>. In particular, <FIG> shows the basic architectural message flow diagram. It is proposed to allow the MEC MS <NUM> (which acts in <FIG> as the EC entity of <FIG> and is thus labelled <NUM>) to expose the topology information <NUM> to the AF(which acts in <FIG> as the MCC entity shown in <FIG> and is thus labelled <NUM>). The topology information <NUM> exposure can have any of the three levels explained above, i.e.: full topology exposure, limited topology exposure with weighted DNAI selection, or algorithmic exposure. The AF <NUM> itself forwards those topology information <NUM> to the NEF <NUM> or PCF <NUM> (trusted AF <NUM>) when it requests the rerouting of UE <NUM> traffic to a certain DNAI. The topology information <NUM> is used by the SMF <NUM> upon creation of a new PDU session. The topology information <NUM> can be used by the PCF <NUM> to better handle complex EC platform architectures as well as dynamic and mobile UEs <NUM> and applications.

<FIG> shows a sequence diagram of a topology information <NUM> exposure from an MEC system <NUM> towards a 3GPP (<NUM>) system <NUM>. In particular, <FIG> shows the message flows for the topology information <NUM> exposure. Notably, the topology information <NUM> can again have the three levels explained above, which are hereafter described in more detail.

The first level topology information <NUM> exposure is the full topology information exposure. For instance, in the case the operator is managing both the 3GPP system <NUM> and the MEC system <NUM>, the operator may wish to have full topology information <NUM> exposure for a best matching of UE requirements with MEC network capacities. In this case, it is proposed that the topology information <NUM> exposure may include the following metrics.

The second level topology information <NUM> exposure is the limited/weighted topology information <NUM> exposure. In case the 3GPP system operator is the not the same as the MEC system operator, both operators may desired a limited topology information <NUM> exposure. Here, it is suggested to use a weighted exposure to reflect the capacity of different MEC EDCs <NUM>.

Such a weighted exposure could look like:
(DNAI1, weight: <NUM>%), (DNAI2, weight: <NUM>%), (DNAI3, weight: <NUM>%).

The different weights are assumed to be defined by the EC management system and its provider to reflect desired traffic distribution among the different EDCs <NUM>. How those weights are calculated is left for the EC provider implementation. However, it may be assumed that such a weight is influenced by the capacity and/or load of the different EDCs <NUM>. The weights could be static or dynamic. In case of dynamic weights, the weights are expected to change e.g. depending on the load of the different EDCs <NUM>. Therefore, using the proposed solution, the EC system <NUM> can convey different EDC <NUM> sizes and/or capacities and/or achieve a lazy load reporting. The reported weights can be defined for certain spatial or temporal validity so that to have different load patterns in different geo location or at different times of the day.

The third level topology information <NUM> exposure is an algorithmic topology information exposure. This again addresses the case, in which two different operators are managing the MEC and 3GPP systems <NUM> and <NUM>. As the final selection of the DNAI is typically performed by the SMF <NUM>, the MEC system <NUM> conventionally has little control on the algorithm used for the DNAI selection. Here it is proposed to allow the MEC system <NUM> to convey the required selection algorithm required. This allows specific selection patterns or even service differentiation. Such selection criteria can be: Round Robin, UE proximity, service differentiation (based on QCI).

<FIG> shows an architecture and interaction of a MEC system <NUM> and a 3GPP system <NUM>. In particular, <FIG> shows a first exemplary embodiment. In this exemplary embodiment, the MEC MS (which acts in <FIG> as the EC entity of <FIG> and is thus labelled <NUM>) sends topology information <NUM> to the PCF <NUM> over the 3GPP MS (which acts in <FIG> as the MCC entity of <FIG> and is thus labelled <NUM>). The MEC MS <NUM> uses the new interface MEC-3GPP to send the topology information <NUM> to the 3GPP MS <NUM>. The MEC MS <NUM> acts accordingly as an AF, an updates are sent to NEF <NUM>.

<FIG> shows a sequence diagram of a topology information <NUM> exposure from an MEC system <NUM> towards a 3GPP system <NUM>. In particular, <FIG> relates to the first exemplary embodiment shown in <FIG>. The following steps are performed:.

<FIG> shows an architecture and interaction of a MEC system <NUM> and a 3GPP system <NUM>. In particular, <FIG> shows a second exemplary embodiment. The first exemplary embodiment of <FIG> and <FIG> may not optimally work, if the vertical has a dynamic but proprietary way of choosing the best DNN. In the second exemplary embodiment, the MEC MS (which acts in <FIG> as the EC entity of <FIG> and is thus labelled <NUM>) sends topology information <NUM> to the PCF <NUM> via the AF (which acts in <FIG> as the MCC entity of <FIG> and is thus labelled <NUM>) deployed by the vertical running proprietary images. The MEC MS <NUM> uses the new interface MEC_3GPP to send the topology information <NUM> to the AF <NUM>. The AF <NUM> uses the existing interface N5 to send the topology information <NUM> further to the NEF <NUM>.

<FIG> shows a sequence diagram of a topology information <NUM> exposure from an MEC system <NUM> towards a 3GPP system <NUM>. In particular, <FIG> relates to the second exemplary embodiment shown in <FIG>. The following steps are performed:.

The first and second exemplary embodiments of <FIG> may not be dynamic enough as the PCF <NUM> is only normally accessed during new PDU setup. Thus, in a third exemplary embodiment, the MEC MS <NUM> may sends dynamic/urgent topology information <NUM> updates to the SMF <NUM> with or without an AF.

<FIG> shows a sequence diagram of a topology information <NUM> exposure from an MEC system <NUM> towards a 3GPP system <NUM>. In particular, <FIG> relates to the third exemplary embodiment with an AF. The following steps are performed:.

<FIG> shows a sequence diagram of a topology information <NUM> exposure from an MEC system <NUM> towards a <NUM> system <NUM>. In particular, <FIG> relates to the third exemplary embodiment without AF. The following steps are performed:.

<FIG> shows an architecture and interaction of a MEC system <NUM> and a 3GPP system <NUM>. In particular, <FIG> shows a fourth exemplary embodiment. In this exemplary embodiment, the MEC MS (which acts in <FIG> as the EC entity of <FIG> and is thus labelled <NUM>) sends historical and/or dynamic topology information <NUM> to the PCF/SMF <NUM>/<NUM> via a NWDAF <NUM> with an AF (which acts in <FIG> as the MCC entity of <FIG> and is thus labelled <NUM>). However, it is also possible without AF. The MEC MS <NUM> sends the topology information <NUM> over a new interface MEC_3GPP to the AF <NUM>. The AF <NUM> sends the topology information <NUM> over existing interface N5 to the NEF <NUM>. The NEF <NUM> forwards the topology information <NUM> over existing interface Nx to the NWDAF <NUM>, which again forwards it over existing interface Nx to the PCF <NUM>.

As mentioned, in the fourth embodiment, the MEC MS <NUM> may particularly send historical and/or dynamic topology information <NUM> to the NWDAF <NUM> for analytics. The historical topology information <NUM> can be used by a NF following the request/response methods.

<FIG> shows in (a) - (c) sequence diagrams that relate to the fourth exemplary embodiment shown in <FIG>. <FIG> shows historical topology information <NUM> sent from the AF <NUM> to the NWDAF <NUM>. <FIG> shows an example, in which the SMF <NUM> is using the historical topology information <NUM> about load and latency to select the DNAI. Another example is shown in <FIG>, in which dynamic topology information <NUM> about high load and unavailability are sent to the NWDAF <NUM> to be conveyed to any NF using the subscribe/notify methods. The following steps are performed:.

In all of the above embodiments, also a multi-MEC operator scenario is possible. In case there are multiple MEC providers, there is a need for the AF <NUM> to receive MEC topology information <NUM> from multiple MEC MS <NUM>. In this case the AF <NUM> has the additional tasks of aggregating the topology information <NUM> from the different operators. The topology information <NUM> aggregation in the AF <NUM> has the tasks of combining the list (DNAI, topology information <NUM>) from the different sources, and use the collective information for further processing as described above.

<FIG> shows a method <NUM> according to an embodiment of the invention, particularly a method for an EC system <NUM>. The method <NUM> may, for instance, be carried out by the EC entity <NUM> shown in <FIG>. The method <NUM> comprises a step <NUM> of obtaining topology information <NUM> of the EC system <NUM>. Further, the method <NUM> comprises a step <NUM> of exposing the topology information <NUM> to another network <NUM>, particularly to a MCC system like a 3GPP system.

<FIG> shows a method <NUM> according to an embodiment of the invention, particularly a method for a MCC system <NUM>. The method <NUM> may, for instance, be carried out by the MCC entity <NUM> shown in <FIG>. The method <NUM> comprises a step <NUM> of receiving topology information <NUM> of an EC system <NUM>. Further, the method <NUM> comprises a step <NUM> of providing the topology information <NUM> to a NEF <NUM> or PCF <NUM> of the MCC system <NUM>.

Claim 1:
Edge Computing, EC, entity (<NUM>) for managing a Multiple-access Edge Computing, MEC, system (<NUM>), the EC entity (<NUM>) being configured to
obtain topology information (<NUM>) of the MEC system (<NUM>), and
expose the topology information (<NUM>) to another network (<NUM>), wherein the other network (<NUM>) is a Third Generation Partnership Project, 3GPP, mobile communication core MCC, system, comprising a MCC Entity (<NUM>),
wherein the EC entity (<NUM>) is characterized to be configured to expose, as the topology information (<NUM>), a determined selection algorithm for selecting Edge Data Centers, EDCs (<NUM>) to the MCC entity (<NUM>).