WO2024027917A1 - Application-level payload data processing at the user plane - Google Patents

Abstract

The present disclosure relates to providing an application via a network, for instance, from an application server to user equipment (UE). The disclosure is concerned with processing of application-level payload data included in data packets of a flow related to the application. The disclosure provides various entities, which help to enable the processing of the application-level payload data in the network by one or more user plane entities. The one or more user plane entities may be configured by a controller for being able to process the application-level payload data. The UE may indicate that data packets of the flow are intended for being application-level processed by one or more user entities, and the application server can determine, whether data packets of the flow have been processed in this way in the network.

Description

APPLICATION-LEVEL PAYLOAD DATA PROCESSING AT THE USER PLANE

TECHNICAL FIELD

The present disclosure relates to applications provided via a network, for instance, from an application server to user equipment (UE) via a mobile communication network. The disclosure is concerned with processing of application-level payload data, which is included in data packets of flows related to the applications. The disclosure provides various entities that contribute to enabling the processing of the application-level payload data in the user plane of the network by one or more user plane entities.

BACKGROUND

Communication network flows ensure the connectivity between end-points, and allow the transmission of data between them, typically in the form of data packets. The concept of quality of service flows (QoS-Flows), as used in 5^th generation (5G) networks, allows to account for varying requirements of different applications in terms of latency, reliability, and capacity.

Within a QoS-Flow, for instance via a QoS profile associated to it, packet-loss and delay can be defined, which the application can tolerate, as well as the amount of bandwidth the application requires. The data packets belonging to a given QoS-Flow are then treated by user plane (UP) entities (e.g., gNBs and user plane functions (UPFs) in 5G networks), as defined by the corresponding QoS profile. For example, data packets can be buffered, prioritized, scheduled, etc., in different ways.

However, any of these treatments of the data packets relates to communication only (pure communication flows). The data packets are not modified in the network during the transmission, so that data sent in the data packets by a source corresponds to data received at a destination (assuming that no packet-loss occurs).

SUMMARY

This disclosure is based further on the following considerations of the inventors.

The concept of In-network Computing (INC) implies that computations are carried out in network devices on data packets, as they are traversing the network device(s), e.g., in a router, switch, or network function (NF). In this case, the data sent by a source is modified intentionally and in a well-defined manner during transmission. Consequently, the data sent by a source differs from the data received at a destination. For example, INC may be used for traffic aggregation, data caching, or in-network responses to domain name service (DNS) requests. INC may also provide benefits for a variety of use-cases, among others in terms of fulfilling the challenging requirements of future applications, such as augmented reality (AR) applications.

AR devices (especially in the mobile context) have some requirements (design goals), which often conflict with each other. In particular, the design of powerful, yet comfortably wearable AR devices, not incurring in overheating, is an ongoing challenge. AR devices should be usable wireless, without an external, wired power supply. To still achieve a long battery life-time, large batteries would be required, which conflicts with the design goal of lightweight devices. Further, applications running on AR devices require partially complex computations, which again drains the battery and can cause heating.

FIG. 1 illustrates an example of AR application tasks executed in AR devices. The first gray box on the left denotes the AR devices (UE) and applications running on them. It shows a haptic glove, a racket and ball, and an AR glass with integrated headphones. The haptic glove performs an intelligent filtering of sensory information, and the racket can detect whether the ball was hit or missed. The AR glasses act as a designated device for synchronizing the flows belonging to the different modalities of the user (haptic feedback via the glove and the racket, audio, and video). This can be done, for example, via tethering, where the AR glasses act as a hotspot to which the glove and the racket connect. The access network (AN;) connects the devices with the core network. Via the data network, the data - pre-processed at the AR devices - is transmitted to the application server and vice-versa. Due to the computations for the AR application tasks carried out on the AR devices, their batteries drain fast.

Thus, AR devices need to be as simple as possible, and the computations carried out on them must be reduced to a minimum. For example, complex tasks could be performed by AR applications hosted on servers at the service provider side, but this solution has also two major downsides: • Increased load on the network: The data generated with AR applications is immersive and the transmission of all data to a remote server for processing can easily overload the network

• Non-compliance with the applications’ (near) real-time requirements: Transmitting the immersive amount of data to the remote server can cause latencies that exceed the application’s tolerable delay.

Considering the above, that both the execution of application tasks at the UE side and at the service provider side are not viable, an objective of this disclosure is to enable the execution of application tasks, for instance for AR, in the network devices.

This and other objectives are achieved by the solutions of this disclosure as described in the enclosed independent claims. Advantageous implementations are further defined in the dependent claims.

A first aspect of this disclosure provides a user plane entity for a mobile communication network, the user plane entity being configured to: receive one or more data packets of a flow from user equipment, UE, connected to the mobile communication network, and/or receive one or more data packets of the flow from a further user plane entity or a data network entity or an application server, wherein the flow is related to an application; execute at least one computation on application-level payload data in the one or more data packets of the flow; and forward the one or more data packets of the flow, to a further user plane entity or a data network entity or an application server, and/or forward the one or more data packets of the flow to the UE, wherein the one or more forwarded data packets include the processed application-level payload data.

The execution of the one or more computations can be carried out on the uplink (on applicationlevel payload data traveling from UE to data network/application server) and can also be carried out on the downlink (on application-level payload data traveling from the application server/data network to the UE).

Since the user plane entity of the first aspect is able to process application-level payload data in the data packets of the flow related to the application, by executing the at least one computation on it, the execution of application tasks is possible in the network devices of the mobile communication network. Thus, the at least one computation does neither have to be performed by the UE, nor the application server.

The application may, for example, be an AR application and the application tasks an AR application tasks. The application-level payload data may comprise data necessary for executing the application.

In an implementation form of the first aspect, the user plane entity is further configured to execute no computation on the application-level payload data in the one or more data packets of the flow, if the one or more data packets are not intended for being processed by user plane entities.

For instance, there may be “default” flows, on which no computation is carried out (e.g. if no computation is specified. In this case, the computation to carry out is void).

In an implementation form of the first aspect, the user plane entity is further configured to access a payload of the one or more data packets of the flow to obtain the application-level payload data; execute the at least one computation on the obtained application-level payload data; and include the processed application-level payload data into the one or more data packets of the flow, before forwarding the one or more data packets.

Normally, the user plane entities do not access a payload of application-related data packets. In this disclosure, they may be provided access to the payload, to take over application-related processing tasks.

In an implementation form of the first aspect, the user plane entity is configured to replace the application-level payload data in the one or more data packets of the flow by the processed application-level payload data, before forwarding the one or more data packets.

In most cases, the application-level payload data may be replaced. In some cases, however, it is also possible to add the processed application-level payload data to the non-processed application-level payload data before forwarding the data packets. In an implementation form of the first aspect, the flow is associated with a flow profile, the flow profile indicating one or more computations for the one or more data packets of the flow; and the user plane entity is configured to execute the at least one computation according to the flow profile.

A flow in this disclosure may be referred to as a Com²P-Flow (described in detail later), which is a network flow on which computations can be carried out (besides offering communication connectivity). In this case, the flow profile may be a Com²P -Profile, which may be a set of descriptions and/or a data structure that contains information to specify the Com²P-Flow behavior (e.g., which computation to carry out, necessary attributes, etc.).

In an implementation form of the first aspect, the user plane entity is configured to store the flow profile.

In an implementation form of the first aspect, the flow profile includes at least one of one or more identifiers, each identifier being for one of the one or more computations; and one or more attributes of the flow, the one or more attributes being configured to support execution of the one or more computations on the application-level payload data of the one or more data packets of the flow.

In an implementation form of the first aspect, the flow is further associated with at least one flow rule; and the user plane entity is configured to execute the at least one computation according to the flow profile and based on the at least one flow rule.

The flow rule may be referred to as a Com²P-Rule, which specifies one or more rules on how to apply the Com²P-Profile(s) to the Com²P-Flow(s).

In an implementation form of the first aspect, the flow is further associated with a QoS profile and one or more QoS rules; and the user plane entity is configured to execute the at least one computation and/or to forward the one more data packets of the flow according to the QoS profile and the one or more QoS rules.

Thus, QoS requirements can be met and controlled. In an implementation form of the first aspect, the user plane entity comprises at least one logical component configured to perform the at least one computation.

For instance, the user plane entity may comprise a processor, which may be configured to perform the at least one computation, and may comprise a memory storing, for example, code or instructions to carry out the at least one computation.

In an implementation form of the first aspect, the user plane entity is further configured to buffer two or more data packets of the flow; and perform the at least one computation jointly on the application-level payload data in the two or more data packets of the flow.

This may be beneficial for performing application-related tasks, which require the applicationlevel payload data of two or more data packets to be present at the same time.

In an implementation form of the first aspect, the user plane entity is configured to execute the at least one computation on a dedicated layer of a user plane protocol stack, wherein the dedicated layer is either placed on top of multiple layers of the user plane protocol stack that are dedicated for communication or is placed between multiple layers of the user plane protocol stack that are dedicated for communication and a protocol data unit layer of the user plane stack.

This may allow integrating the solutions of the present disclosure with the user plane protocol stack of e.g. a 5G network, and allows efficient processing of the application-level payload data in the network.

In an implementation form of the first aspect, the user plane entity is further configured to receive configuration information from a controller, the configuration information indicating the at least one computation.

The user plane entity may thus be configurable. The user plane entity may not have to determine itself, whether or not to perform application-level payload data processing for a certain flow of data packets, but may be configured or re-configured accordingly by the controller.

In an implementation form of the first aspect, the configuration information includes the flow profile and the at least one flow rule. In an implementation form of the first aspect, the configuration information includes a plurality of flow profiles and a plurality of sets of flow rules, each flow profile and each set of flow rules being associated with a particular flow of a plurality of flows.

For instance, the user plane entity can be configured to perform different computations on application-level payload data for data packets belonging to different flows.

In an implementation form of the first aspect, the one or more computations indicated by the flow profile for the one or more data packets of the flow together are a micro-service; and the user plane entity is configured to: store a code for running the one more computations of the micro-service; and apply the micro-service on the flow by using the code.

For instance, the code may comprise code snippets and/or execution scripts. In this way, the user plane entity can carry out the one or more computations quickly and efficiently on the application-level payload data.

In an implementation form of the first aspect, the configuration information includes the code of the micro-service.

In an implementation form of the first aspect, the user plane entity is an AN entity, or is a core network (CN) entity; and/or the controller is an AF or is at least one control plane (CP) entity.

For example, the controller may be a policy control function (PCF) or any other CP function. An AN entity may be a gNB or base station or the like.

A second aspect of this disclosure provides a controller for configuring one or more user plane entities of a mobile communication network, the controller being configured to: send configuration information to the one or more user plane entities, the configuration information indicating one or more computations for execution on application-level payload data included in one or more data packets of a flow, the flow being related to an application.

By configuring the one or more user plane entities, to enable them to process the applicationlevel payload data, INC of application-related data can be enabled. Thus, the UE(s) and the application server, for example, can be relieved of this processing. This leads to the advantages mentioned above.

In an implementation form of the second aspect, the configuration information indicates at least one computation to be performed by the one or more user plane entities.

Notably, not necessarily each of the user plane entities needs to perform a computation. It may be the case that several user plane entities are involved along the path between UE and data network entity or application server, but that only one or more of them is actually carrying out at least one computation.

In an implementation form of the second aspect, the configuration information includes at least one of a flow profile and at least one flow rule of the flow, the flow profile indicates one or more computations for the one or more data packets of the flow, and the flow rule indicates how to execute the one or more computations on the application-level payload data of the one or more data packets of the flow.

In an implementation form of the second aspect, the controller is an application function or is at least one control plane entity.

For instance, the controller may be a PCF.

In an implementation form of the second aspect, the configuration information includes an association of one or more micro-services to the application, the micro-service comprising the one or more computations.

A third aspect of this disclosure provides a UE for connecting to a mobile communication network, the user equipment being configured to: send one or more data packets of a flow to a user plane entity of the mobile communication network, wherein the flow is related to an application; and indicate that the one or more data packets of the flow are intended for processing of application-level payload data in the one or more data packets by one or more user plane entities. By providing the indication, the UE is able to support the implementation of the processing of the application-level payload data in the network, in particular, by the one or more user plane entities.

In an implementation form of the second aspect, the UE is configured to include an indication in a header of the one or more data packets of the flow, in order to indicate that the one or more data packets of the flow are intended for the processing of the application-level payload data in the one or more data packets by the one or more user plane entities.

A fourth aspect of this disclosure provides an application server for providing an application via a mobile communication network to UE, the application server being configured to: receive one or more data packets of a flow, the flow being related to the application; and determine that application-level payload data in the one or more data packets of the flow has been processed by one or more user plane entities of the mobile communication network.

The application server is thus able to identify whether the application-level payload data processing in the user plane is activated or not. The application server can moreover also send data packets of the flow itself, towards the UE via the network, and may indicate that the one or more sent data packets of the flow are intended for processing of application-level payload data by one or more user plane entities.

In an implementation form of the fourth aspect, the application server is configured to determine, based on an indication in a header of the one or more data packets of the flow, that the application-level payload data has been processed by the one or more user plane entities.

A fifth aspect of this disclosure provides a method for a user plane entity of a mobile communication network, the method comprising: receiving one or more data packets of a flow from UE connected to the mobile communication network, and/or receiving one or more data packets from a further user plane entity or a data network entity or an application server, wherein the flow is related to an application; executing at least one computation on applicationlevel payload data in the one or more data packets of the flow; and forwarding the one or more data packets of the flow to a further user plane entity or a data network entity or an application server, and/or forwarding the one or more data packets of the flow to the UE, wherein the one or more forwarded data packets include the processed application-level payload data. The method of the fifth aspect can be extended with implementation forms according to the implementation forms of the user plane entity of the first aspect. The method of the fifth aspect and its implementation forms provide the same advantages as described above for the user plane entity of the first aspect and its respective implementation forms.

A sixth aspect of this disclosure provides a method for configuring one or more user plane entities of a mobile communication network, the method comprising sending configuration information to the one or more user plane entities, the configuration information indicating one or more computations for execution on application-level payload data included in one or more data packets of a flow, the flow being related to an application.

The method of the sixth aspect can be extended with implementation forms according to the implementation forms of the controller of the second aspect. The method of the sixth aspect and its implementation forms provide the same advantages as described above for the controller of the second aspect and its respective implementation forms.

A seventh aspect of this disclosure provides a method for a UE connected to a mobile communication network, the method comprising: sending one or more data packets of a flow to a user plane entity of the mobile communication network, wherein the flow is related to an application; and indicating that the one or more data packets of the flow are intended for processing of application-level payload data in the one or more data packets by one or more user plane entities.

The method of the seventh aspect can be extended with implementation forms according to the implementation forms of the UE of the third aspect. The method of the seventh aspect and its implementation forms provide the same advantages as described above for the UE of the third aspect and its respective implementation forms.

An eight aspect of this disclosure provides a method for an application server providing an application via a mobile communication network to user equipment, UE, the method comprising: receiving one or more data packets of a flow, the flow being related to the application; and determining that application-level payload data in the one or more data packets of the flow has been processed by one or more user plane entities of the mobile communication network.

The method of the eighth aspect can be extended with implementation forms according to the implementation forms of the application server of the fourth aspect. The method of the eighth aspect and its implementation forms provide the same advantages as described above for the application server of the fourth aspect and its respective implementation forms.

A ninth aspect of this disclosure provides a computer program comprising instructions, which, when the program is executed by a computer, cause the computer to perform the method according to one of the fifth, sixth, seventh or eighths aspect.

The solutions of this disclosure allow carrying out application-related computations in the UP. This, for example, may solve the problem of not wanting to process the application-level data at AR devices - due to their simple design and battery saving requirements - but also not at a remote (e.g., multi-access edge computing (MEC)) application server - due to the increased network load and real-time requirements of the applications. According to this disclosure, application tasks can be offloaded from the AR device or application server to the user plane entities.

The solutions of this disclosure may be based on the following:

• An existing agreement between a mobile network operator (MNO) of the network and an application provider (AP), which allows the MNO to operate on the application-level payload data.

• The user plane entities having access to the application-level payload data. That means that the traffic is not encrypted, or all credentials for decryption are available, or advanced techniques are used, such as homomorphic encryption, which still allow to operate on the application-level payload data.

Although this disclosure is motivated by the presented AR use-case (to keep the devices simple and to achieve the application’s delay requirements), it has high potential for several other usecases. For example:

• Vehicular networks: Similar to AR, there are very stringent delay requirements and potentially huge amount of generated data (e.g. from cameras mounted on the vehicle). With the proposed solution, data flows from vehicles could be processed at the AN and other user plane entities for early data processing, thus reducing the network traffic load and delay.

• Vertical networks: If the network is fully owned by the vertical, it can provide full flexibility in terms of the computations carried out on the flows. The solution could, for example, be used for out-of-control sensor detection in industrial environments.

• Online bidding (e.g. for advertisement placement on web-pages). For example, the bidding action could be initiated before the user’s request for a web-page reaches the server hosting that web-page. Similar as with the in-network DNS approach, the user plane entity identifies based on the traffic flow the DNS/HTTP request for a webserver/webpage. This automatically triggers to start the online-bidding process for placing ads to the requested web-page, before the user’s request even reaches the webserver.

• In general, the solution could be applied to anything, where edge computing is used today.

The solution could also be used for enforcing data-privacy by involving the MNO as a third party. For example, self-driving cars constantly screen the environment via a couple of integrated cameras. To ensure that this sensitive kind of information is not processed at the server (and potentially used for other purposes than automatized driving), the MNO could be in charge for object detection and masking (e.g. the faces of pedestrians). For instance, not just offloading application-related tasks to the network, but offloading privacy-related responsibilities to another party.

In general, the solution’s applicability is not limited to the UP of mobile networks. It can be used in a similar fashion in a home network (on personal WiFi routers), as well as in other data networks.

It has to be noted that all devices, elements, units and means described in the present application could be implemented in the software or hardware elements or any kind of combination thereof. All steps which are performed by the various entities described in the present application as well as the functionalities described to be performed by the various entities are intended to mean that the respective entity is adapted to or configured to perform the respective steps and functionalities. Even if, in the following description of specific embodiments, a specific functionality or step to be performed by external entities is not reflected in the description of a specific detailed element of that entity which performs that specific step or functionality, it should be clear for a skilled person that these methods and functionalities can be implemented in respective software or hardware elements, or any kind of combination thereof.

BRIEF DESCRIPTION OF DRAWINGS

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

FIG. 1 shows AR application tasks executed in AR devices (glove, racket, ear-phones and AR glasses), leading to fast battery drainage of the AR devices.

FIG. 2 shows a concept of offloading application tasks to user plane entities, which enables reducing the complexity of AR devices and their energy consumption.

FIG. 3 shows various entities according to this disclosure, and their potential interaction.

FIG. 4 shows an example of communication and compute flows among various entities according to this disclosure.

FIG. 5 shows an exemplary enhancement of a user plane entity according to this disclosure with additional computational resources and compute logics.

FIG. 6 shows a programmability of the UP via a controller according to this disclosure, to define the UP path and Com²P-Flow behavior

FIG. 7 shows an exemplary system architecture according to this disclosure.

FIG. 8 shows a controller and a user plane entity according to this disclosure, and an interface between them.

FIG. 9 shows an exemplary enhancement of a user plane entity according to this disclosure, in particular, its protocol stack, with a layer dedicated for computations of application-level payload data.

FIG. 10 shows an overview of a UP programmability via a controller according to this disclosure.

FIG. 11 shows a definition of a Com²P-Flow behavior via pre-defined micro-services.

FIG. 12 shows a programming of the UP via a controller according to this disclosure, by means of code deployment for defining new, customized micro-services.

FIG. 13 shows an enhancement of UPFs and AN by means of adding a computational layer (C-Layer) to the protocol stack.

FIG. 14 show the introduction of a new direct interface for direct communication between an AF and a UPF. FIG. 15 shows the use of a sequence of existing 5G NFs and interfaces.

FIG. 16 shows the connecting of a UPF to a SBI via a new interface.

FIG. 17 shows the introduction of a new NF connecting AF and UPF with new interfaces.

FIG. 18 shows a programming and usage of Com²P -Flows for 5G/B5G networks.

FIG. 19 shows an authentication AF-PCF via NEF.

FIG. 20 shows a Com²P-Flow establishment.

FIG. 21 shows a method for a user plane entity, according to this disclosure.

FIG. 22 shows a method for a controller, according to this disclosure.

FIG. 23 shows a method for a UE, according to this disclosure.

FIG. 24 shows a method for an application server, according to this disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

FIG.2 illustrates a difference provided by this disclosure compared to FIG. 1. According to this disclosure, network entities can be used and programmed to execute one or more computations on application-level payload data of application-related data packets. In this way, the network entities can perform application tasks, in the example FIG. 1 and FIG. 2, AR application tasks.

In FIG. 2, the first gray box shows involved UEs 320 according to this disclosure, here AR devices similar to FIG. 1. Compared to FIG. 1, however, one or more computations on application-level payload data are not performed at the UEs 320, but instead, by means of programming the UP, one or more user plane entities 300 (e.g., AN device(s) 201 or UPF(s) 202 in the CN) can carry out one or more computations to perform AR application tasks, like information filtering, pattern detection, and flow synchronization, while simultaneously forwarding the data packets. The processed data packets may be then sent via the data network to an application server 330 according to this disclosure. The user plane entities 300 and the UE(s) 320 may be programmed via a controller 310 according to this disclosure with configuration information 302, as denoted by the dashed lines.

FIG. 3 shows more generally various entities that may participate in enabling the processing of the application-level data in the UP. These entities may be applied for the scenario of FIG. 2, but are not limited to this scenario. In particular, FIG. 3 shows a user plane entity 300 according to this disclosure, a UE 320 according to this disclosure, a controller 310 according to this disclosure, and an application server 330 according to this disclosure. The user plane entity 300 may be in a mobile communication network, and is configured to receive one or more data packets 301 of a flow from the UE 320 connected to the mobile communication network. Additionally or alternatively, the user plane entity 300 is configured to receive one or more data packets 301 of the flow from a further user plane entity 300, or from a data network entity, or from an application server 330 (indicated by the dotted break in the arrow). The application server 330 is thereby configured to provide an application 303 via the mobile communication network to the UE 320. The flow of the data packets 301 is related to the application 303.

The UE 320 is accordingly configured to send the one or more data packets 301 of the flow to the user plane entity 300. The UE 320 is also configured to indicate that the one or more data packets 301 of the flow are intended for processing of the application-level payload data included in the one or more data packets 301 by one or more user plane entities 300 of the network.

The shown user plane entity 300 is further configured to execute at least one computation on the application-level payload data in the one or more data packets 301 of the flow. Then, the user pane entity 300 is configured to forward the one or more data packets 301 of the flow, for example, to a further user plane entity 300, or to a data network entity, or to the application server 330.

The application server 330 is accordingly configured to receive one or more data packets 301 of the flow. The application server 330 is further configured to determine that application-level payload data in the one or more data packets 301 of the flow has been processed by one or more user plane entities 300 of the mobile communication network, for instance, by the shown user plane entity 300. The application server 330 can also send data packets 301 of the flow towards the mobile communication network, where these data packets 301 may be received by the control plane entity 300. Thereby, like the UE 320, the application server 330 may indicate that the one or more data packets 301 of the flow are intended for processing of the applicationlevel payload data included in the one or more data packets 301 by one or more user plane entities 300 of the network.

The control plane entity 300 may be configured to execute at least one computation on application-level payload data in the one or more data packets 301 of the flow coming from the application server 330, and to forward the one or more data packets 301 of the flow to the UE 320, wherein the one or more forwarded data packets 301 include the processed applicationlevel payload data.

The controller 310 is adapted to configure one or more user plane entities 300 of the mobile communication network, for instance, the shown user plane entity 300. The controller 310 is, to this end, configured to send configuration information 302 to the one or more user plane entities 300. The configuration information 302 indicates one or more computations for execution on application-level payload data included in the one or more data packets 301 of the flow related to the application the application 303.

Each entity 300, 310, 320, and 330 may respectively comprise a processor or processing circuitry (not shown) configured to perform, conduct or initiate the various operations of the respective entity 300, 310, 320, 330 described herein. The processing circuitry may comprise hardware and/or the processing circuitry may be controlled by software. The hardware may comprise analog circuitry or digital circuitry, or both analog and digital circuitry. The digital circuitry may comprise components such as application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), digital signal processors (DSPs), or multi-purpose processors. Each entity 300, 310, 320, 330 may further respectively comprise memory circuitry, which stores one or more instruction(s) that can be executed by the processor or by the processing circuitry, in particular under control of the software. For instance, the memory circuitry may comprise a non-transitory storage medium storing executable software code which, when executed by the processor or the processing circuitry, causes the various operations of the entity 300, 310, 320, 330 to be performed. In one embodiment, the processing circuitry comprises one or more processors and a non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code which, when executed by the one or more processors, causes the respective entity 300, 310, 320, 330 to perform, conduct or initiate the operations or methods described herein.

According to the above, in-network (i.e., by one or more user plane entities 300) execution of one or more computations, e.g., AR application tasks, on application-level payload data of data packets 301 is implemented. Besides ensuring the connectivity and data transfer between two end points (e.g., the UE 320 and the application server 330), the application-level payload data can thus be processed along the user plane entities 300. This means that the application-level payload data sent from one endpoint of the connection (e.g. the UE 320), differs from the (processed) application-level payload data received by the other endpoint (e.g. the application server 330).

The flow(s) according to this disclosure may be so called Communication and Compute Flows (Com²P -Flows), which may be defined and may allow computations to be carried out on the application-level payload data of the data packets 301 as they traverse the user plane entities 300. Each flow may be associated with a flow profile, for instance, a Com²P-Flow may be associated with a Com²P -Profile. The flow profile may specify the treatment of the flow with respect to the at least one computation to carry out.

If no computation to carry out is specified in the flow profile, a default treatment of the associated flow may be to not carry out any computation on data packets 301 of the flow in the one or more user plane entities 300 (e.g., the computation is void).

FIG. 4 illustrates the concept of Com²P -Flows according to this disclosure. The UE 320 (here acting as the source of the flow) sends the data packets 301 towards the AN, e.g., to an AN entity, which may be the first user plane entity 300 along the connection/path. The data packets 301 in this case traverse one or more further user plane entities 300, where they may be processed, before leaving the mobile communication network and entering the DN 402. The processed data packets 301 of the flow are further received by the application server 330 (here the destination of the flow). The Com²P-Flow spans the connection from the UE 320 until leaving the mobile CN and entering the DN 402. The Com²P-Flow is associated with a Com²P- Profile 401, which specifies the computations to be executed on its belonging data packets 301.

Analogues, the UE 320 can also act as the destination of the Com²P-Flow, such that the one or more computations are carried out on the way from the application server 330 to the UE 320. Although the Com²P-Flow spans the connection between the UE 320 until reaching the DN 402, both of the connection end-points, i.e., the UE 320 and also the application server 330 (located within the DN 402), may beneficially be aware of the usage of Com²P -Flows. For instance, the UE 320 and the application server 330 may know, which one or more computations of a set of computations they carry out themselves, and which at least one computation of the set of computations is offloaded to the user plane entities 300.

Depending on whether Com²P -Flows are utilized or not, a different treatment of the application packets 301 within the UE 320 of application server 330 may be required. Some adaptations to the application 303 may be done to conform to the Com²P-Flows. For instance, to signal on application-level between the UE 302 and the application server 330 (i.e., the two application end-points in this case), or to include additional information usable by the network entities, e.g., in the form of new header information.

The Com²P -Profiles 401 may be used to uniquely describe the treatment of their associated Com²P -Flows. Each Com²P-Flow may be associated with a single Com²P -Profile 401 that contains the necessary information to specify the Com²P-Flow treatment of this flow. The flow profile 401 may include:

• One more identifier, which are referring to the computation(s) to be carried out on the Com²P -Flows. The computations are described as micro-services (MS), identified via the micro-service ID (MS-ID).

• Attributes necessary to further describe the Com²P -Flows. That is, specific values needed in addition to the micro-service(s) to carry out the computations properly and any further information/meta-data related to the Com²P-Flow treatment, such as pre-emption capability or priority level.

The UP may be enhanced, as described above, by capabilities to carry out the one or more computations on the application-level payload data of data packets 301. To this end, for example, the user plane entities 300 (e.g., UPF and/or gNB in 5G terms) may be enhanced by:

• A logical component for carrying out the at least one computations specified for the Com²P-Flow packets 301.

• (Virtual) resources needed to be capable of carrying out the at least one computation, including storage, memory, CPU. For example, the user plane entity 300 may perform one or more application-level computations, for example, requiring to buffer a larger number of network-level data packets 301, re-assembling the data packets 301, and finally operate on the retrieved application-level payload data. FIG. 5 denotes an incoming and un- modified data packet 301 entering a certain user plane entity 300. The enhanced computational resources may allow a logical component to process the incoming packet 301 or a bulk of data packets 301 of the flow, on top of its communication- related treatment (e.g., scheduling, and/or prioritizing). The modified data packet 301 is then forwarded and leaves the user plane entity 300.

The user plane entities 300 in this disclosure can be programmed via the controller 310 (e.g., the controller may be an AF in 5G terms), so to specify the behavior of Com²P -Flows, e.g., which computations to carry out on which user plane entities 300 and which flows.

FIG. 6 illustrates, as an example, three UP entities 300 and the controller 310. The controller 310 may define and/or program (denoted as dashed lines) the behavior and UP path of the Com²P -Flows, as well as the one or more computations to carry out in the user plane entities’ 300 logical components.

Not all of the involved user plane entities 300, which are used or defined to connect UE 320 and the application server 330 (two in the example of FIG. 6), necessarily carry out computations on a flow’s data packet 301. It can be the case that although several user plane entities 300 are involved along the path, only one, or a few, user plane entity 300 is actually modifying the application-level payload data.

Programming the UP may involve several dimensions, as denoted in detail later. (1) The definition and deployment of micro-services at the user plane entities 300, e.g., equipping them with the logics to apply on the Com²P -Flows. In this case, the controller 310 is programming the user plane entities 300 in the network, so as to prepare them for the Com²P-Flow usage. (2) Defining a mapping between applications 303 and the micro-services to use on them. In the case of the mapping, only the CP of the mobile network is affected. That is, the mapping between the applications 303 and the micro-services to use is not known by the user plane entities 300 themselves. (3) The Com²P-Flow setup in the network according to the specifications given in the Com²P -Profile. For this part of the programmability, the UE 320 may be included, as well. That is, the UE 320 may be informed about the usage of Com²P- Flows. FIG. 7 illustrates a system architecture, to which the concept of the above-described Com²- Flows applies. A UE 320 is connected via an AN to the mobile CN, where the UE’s traffic (data packets 301) traverses one or more further user plane entities 300. The application traffic can be modified on one or more of the involved user plane entities 300 (including the AN entity). It may then be further routed via the DN 402 to the application server 330. The controller 310 can program the user plane entities 300 via dedicated interfaces 7 to define the treatment of the Com²P -Flows along the UP path.

As denoted in FIG. 8, the following products may be involved in the implementation of the solutions of the present disclosure. (1) The controller 310, which is programming the user plane entity 300 and defining the treatment of the Com²P -Flows (e.g., the AF in 5G terms). (2) The user plane entity 300 with the enhancements of being able to carry out computations (e.g., the gNB and the UPFs in 5G terms). (3) The interface between the controller 310 and the user plane entity 310 via which the programming (sending of configuration information 302 can be carried out.

In the following a general embodiment of this disclosure, usable for 6^th generation (6G) mobile networks, is described. The embodiment includes the evolution from pure communication flows to Com²P -Flows. Enhancements to define the Com²-P -Flows may be similar to the definition of 5G QoS-Flows.

A Com²P-Flow may be identified via a Com²P-Flow ID (C²FI). UP traffic with the same C²FI may receive the same treatment in terms of communication and computation. The C²FI may be communicated from the controller 310 to the UP at Com²P-Flow setup.

A Com²P-Flow may, for example, be characterized by:

• A QoS profile

• One or more QoS rule(s) and optionally QoS Flow level QoS parameters

• One or more UL and DL PHY data rate (PDR)

• A Com²P -Profile, specifying the computations to carry out on the flow (by indicating a micro-service ID and additional Com²P parameters)

• One or more Com²P -Rules The first three points are also present with QoS-Flows in 5G. In addition to the existing characteristics, the Com²P -Flows may be associated with a Com²P -Profile that contains the necessary information to specify the Com²P-Flow treatment, for example:

• Identifier for one or several micro-services to use (Micro-Service Identifier (MS-ID))

■ The MS-ID either refers to a standardized/pre-configured MS or to a customized/dynamic MS

■ The MS-ID can either specify all relevant attributes needed for defining the computation, or additional attributes are specified in the Com²P-Flow

• Attributes to further describe the handling of the Com²P-Flow

■ Depending on the micro-service, a number of additional information may be specified besides the MS-ID (e.g., comparable to specific GBR settings with QoS- Flows). This includes the following (but not limited to):

Dedicated threshold(s) for application-aware packet dropping (e.g. for filtering haptic information from sensory data) Codecs to use (e.g. voice or video compression)

Pattern(s) to be recognized on the Com²P -Flows (e.g. sensor signals or movements from AR devices)

■ Any further information/meta-data related to the Com²P-Flow treatment. This includes, but is not limited to:

Priority level

Pre-emption capability

Reporting specifications

Key(s) for traffic decryption

Com²P -Rules can specify one or more rules on how to apply the Com²P-Profile(s). This may include (but not limited) to the following aspects:

• Usage of the same Com²P -Profile for both on uplink or downlink (corresponding reflective QoS in QoS-Flows)

• In case of defining at least two optional Com²P -Profiles that are appropriate for a Com²P- Flow, the Com²P-Rule may define the dynamic switching between the at least two Com²P -Profiles. That may depend on factors such as the UP entities’ 300 current computational load, or the available end-to-end bandwidth. As mentioned above, this disclosure also provides an enhancement of the user plane entity 300 by means of introducing a logical component for carrying out the one or more computations specified for the Com²P-Flow packets 301. This logical component may be realized as new layer 901 in the UP protocol stack 902, as illustrated in FIG. 9.

The user plane entities 300 may implement the UP protocol stack 902 with a number (n) of layers dedicated for the communication (four in the case of 5G UP protocol stack 902). On top of the layers dedicated for communication, the new layer 901 dedicated for carrying out one or more computations (L n+1) is placed. It corresponds to the logical unit dedicated for carrying out the computations on the packets/flows.

For the user plane entity 300 connecting to the DN (e.g., UPF session anchor in 5G terms), the new computational layer 901 may be placed between the layers 902 dedicated for communication and the PDU-Layer 903.

With respect to the UP programmability, three stages may come into play. A schematic illustration is given in FIG. 10. The controller 310 refers to the controller 310 in FIG. 7. The programmability in FIG. 10 refers to the programmability via dedicated interfaces in FIG. 7.

The three stages of programmability are described in more detail below. FIG. 10 denotes the controller 310, whereby different instances of the controller 310 (CI-1, CI-2, CI-3) or the controller 310 can be responsible for carrying out the different programming tasks. Thereby, the controller 310, or one dedicated controller instance, can be capable of carrying out one of stages of programmability (i.e. (a), (b), (c)), or all of the stages or any of the possible combinations.

On a larger time scale, the controller 310 can define new micro-services, via deploying code like code snippets or execution scripts at the user plane entities 300. Which micro-service to use on which flow is defined/programmed via a mapping that defines the Com²-Profile to use for which service or application (flow). This mapping may be available in the control plane entities, but not in the user plane entities 300. The mapping may be used by the control plane entities during the Com²P-Flow setup in the UP. The programming for the sake of setting up a Com²P-Flow may happen on a short time-scale, e.g., whenever a UE 320 makes use of a Com²P- Flow. Com²P-Flow setup includes the UP path selection, which is among others depending on the user plane entities’ 300 capabilities to support the respective Com²P -Profile. The Com²P-

Flow setup also includes the enforcement of the Com²P -Profile along the UP path

For any of the three programming purposes, the controller 310 (or controller instance) is connected (either via a direct interface or using a sequence of interfaces via the control plane) to the UP. The control commands and information exchanged between the controller 310 and the user plane entities 300 are well-defined by both ends, e.g., by means of a dedicated protocol. The programming may involve several procedures, such as authentication or user plane entity 300 selection.

The controller 310 may define and implement the Com²P-Flow behavior. This may involve:

• Determining the appropriate UP path, i.e., the user plane entities 300 to connect the UE 320 to the DN 402. This determination may include factors such as the location of the UE 320 and the DN 402, the capabilities and current load of the user plane entities 300, as well as UE 320 input parameters.

• Setting up the Com²P-Flow with the appropriate Com²P -Profile (including the microservice to use on that flow)

The controller 310 specifies which flow profile 401, e.g. Com²P -Profile, to use for which application flow(s). This may be depending on various factors, such as (but not limited to):

• The used application/service (e.g. an AR video flow to use micro-service A vs. an AR haptic information flow to use micro-service B)

• The location of the connection end-points (e.g. if server is located in X, use micro-service A or for all UEs in area Y use micro-service B)

• The capabilities of the UE 320

• QoS-parameters (e.g. available bandwidth along the path)

With respect to the availability of micro-services, there are two options:

(1) A set of pre-defined/ standardized micro-services, potentially per default available on all or a dedicated set of UP entities.

As illustrated in FIG. 11, the user plane entities 300 may be equipped with a set of microservices, which they are capable of executing. Each micro-service is identified via a micro- service identifier (MS-ID), which specifies the computation to carry out. Optional attributes allow for further specifying the computation. An attribute value can be standardized and/or predefined, e.g., it has the same value for all computations using that MS-ID. Or the specific attribute value is dedicatedly defined in the flow profile 401, so that the MS-ID is flexibly used with that attribute value. When the controller 310 programs the Com²P-Flow behavior, it may send the following information to the involved user plane entities 300:

• A flow ID, e.g. the C²FI, to identify the flow on which the micro-service should be applied

• The flow profile 401, e.g. Com²P -Profile, which contains the MS-ID and optional attributes

For this option (1), a set of micro-service may be standardized.

(2) The second option for the micro-service availability are custom/additional micro-services, which are defined by the controller and potentially deployed only at a set of user plane entities 300. The deployment of customized micro-services is described in the next subsection. The logic with respect to which micro-service and Com²P -Profile to use for which application 303 may resides in the CP of the mobile network. For instance, the user plane entities 300 are not aware of this mapping, but the usage of the micro-services is delegated by the CP to the user plane entities 300 when performing the Com²P-Flow setup.

The deployment of new, dynamic micro-services is illustrated in FIG. 12. For that, the user plane entities 300 may store and deploy (additionally to the set of pre-defined/standardized of micro-services) newly received code like code snippets or execution scripts, to deploy dynamic micro-services. The controller 310 can describe the intended behavior of the micro-service by means of new execution scripts or code snippets, and deploys these logics at the user plane entities 300. The new micro-service is equipped with an ID and the user plane entities 300 are then capable of operating on the packets/flows according to the new dynamic micro-service.

In the following an embodiment for 5G is described, in particular, for B5G/5G networks.

Regarding the definition of the Com²P-Flows, the same applies as described above for the embodiment for 6G. As shown in FIG. 13, the computational layer (C -Layer) 1301 in the 5G UP protocol stack 1302 may be placed between the GTP-U and the PDU-Layer in case the UPF serves as a PDU session anchor (PSU), i.e. it connects via the N6 to interface to the DN 402. For all other UPFs and the AN, the C-Layer 1301 is placed on top of the GTP-U Layer.

The following provides four possible sub-embodiments for the communication between the controller 310 and the UP for: (a) Setting up the Com²P -Flows, (b) Defining the mapping of which Com²P -Profile to use for which flow, and (c) Defining new micro-services. This part corresponds to the description above regarding FIG. 10, programmability of the 6G embodiment. For realizing the programmability in terms of (a), (b), and (c), any combinations of the four presented options for controller-UPF-communication can be used. For example, the programming for Com²P-Flow setup (i.e. programming stage (c)) may leverage a first option (Option 1), while the programming/deployment of new micro-services (i.e. programming stage (a)) may leverage a second option (Option 2).

Option 1 bases on a new dedicated interface between AF (controller 310) and UPF (user plane entity 300), as shown in FIG. 14. The AF can directly communicate with the UPF via the new interface. The new interface is denoted as N-UPF. The AF has all necessary credentials to program the UPF, and all information needed for setting up the Com²P-Flow in the UP. That is, the full network topology, the capabilities of the UPFs with respect to supported micro-services, their load in terms of CPU/RAM, etc.

Option 2 uses a sequence of existing interfaces, as shown in FIG. 15. The AF (controller 310) cannot directly communicate with the UPF (user plane entity 300). All necessary information for programming are sent from the AF to the PCF via the SBI. The PCF uses existing interfaces to forward the information to the SMF. The SMF performs the respective programming of the UPF via the N4 interface.

A third option (Option 3) may connect the UPF to the SBI, as shown in FIG. 16. The UPF (user plane entity 300) is connected to the SBI via a new interface, the Nupf. In this way, the AF (controller 310) can either directly communicate with the UPF via the SBI, or new sequences of communication between the NFs can be used (e.g. AF>PCF>UPF). A fourth option (Option 4) may base on a proxy-UPF (P-UPF) between AF (controller 310) and UPF (user plane entity 300), as shown in FIG. 17. This option introduces a new NF, referred to as Proxy-UPF (P-UPF). It is connected to the AF via a new interface and to the UPF via another new interface. All programming information and commands are sent to the P-UPF. The P-UPF holds all credentials and information for programming (e.g. UPF capabilities or network topology). From the viewpoint of the AF, the AF might have full access for programming the UP. Still, no information, such as the UPF capability, load, or the network topology need to be exposed to the AF.

The following describes the programmability in terms of setting up the Com²P -Flows (i.e. programming stage (a)) when using option 2 described above. For instance, using a sequence of signaling between existing 5G NFs and interfaces, thus involving the fewest changes compared to 5G systems today. The procedure is similar to that of setting up QoS Flows and described using FIG. 18.

■ The Com²P-Flow mapping has been communicated to the PCF (i.e. via programming stage (b)) at an earlier stage. The AF (also controller 310) can request the usage of a Com²P-Flow for its application 303.

■ The PCF is aware of the Com²P-Flow mapping and selects the appropriate Com²P -Profile for the Com²P-Flow to establish. In addition, the PCF holds any other rules related to the Com²P-Flow setup, such as charging or reporting-related information.

■ The PCF instructs the SMF to setup the Com²P-Flow with the appropriate Com²P -Profile.

■ The SMF has all information concerning all controlled ANs/UPFs. This info used to select the appropriate UP entities that is: Supported QoS-features/Com²P- features (which the SMF obtains via 0AM). Status, e.g. the load of the UPF (which the SMF obtains via NRF).

It then determines an appropriate UP path and programs the UPFs involved via its N4 interface.

■ The AMF configures the AN 201 and the UE 320 for the Com²P-Flow usage with the specified Com²P -Profile. At this point, a connection for communication and computing is established between the UE 320 and the DN 402. FIG. 19 denotes in more detail the first step of FIG. 18, i.e., the request for Com²P-Flow usage. This step may include:

(1) The AF sends the request for using a Com²P-Flow or a micro-service to the NEF

(2) NEF performs the authorization of the Com²P-Flow usage

(3) NEF invokes PCF service to create Com²P- Profile

(4) PCF notifies the NEF of the acceptance of the Com²P-Flow with the specified Com²P- Profile creation request

(5) NEF notifies the AF of the acceptance of Com²P-Flow creation request and its associated Com2P -Profile

The whole procedure for setting up Com²P -Flows is illustrated in FIG. 20.

(1) The AF indicates to the 5GC (PCF) which AF Sessions the Com²P- flow shall apply, and which micro-operations shall be used for the Com²P- Flow.

(2) The 5GC (PCF) creates Com²P- rules to be applied to PDU Sessions as indicated by AF.

(3) At PDU Session Establishment/Modification for the PDU Sessions indicated by AF, SMF retrieve Com²P- rules from PCF and program UPF, AN and UE accordingly, establishing Com²P- flow

(4) UP Data for the Com²P-Flow receive the communication and compute flow as per AF indication

FIG. 21 shows a method 2100 for a user plane entity 300 of a mobile communication network, according to this disclosure. The method 2100 comprises a step 2101 of receiving one or more data packets 301 of a flow from UE 320 connected to the mobile communication network, and/or a step 2101 of receiving one or more data packets 301 from a further user plane entity

300 or a data network entity 402 or an application server 330, wherein the flow is related to an application 302. The method 2100 also comprises a step 2102 of executing at least one computation on application-level payload data in the one or more data packets 301 of the flow. Further, the method 2100 comprises a step 2103 of forwarding the one or more data packets

301 of the flow to a further user plane entity 300 or a data network entity 402 or an application server 330, and/or a step 2103 of forwarding the one or more data packets 301 of the flow to the UE 320, wherein the one or more forwarded data packets 301 include the processed application-level payload data. FIG. 22 shows a method 2200 for configuring one or more user plane entities 300 of a mobile communication network, according to this disclosure. The method 2200 comprises a step 2201 of sending configuration information 302 to the one or more user plane entities 300, the configuration information 302 indicating one or more computations for execution on application-level payload data included in one or more data packets 301 of a flow, the flow being related to an application 303.

FIG. 23 shows a method 2300 for a UE 320 connected to a mobile communication network, according to this disclosure. The method 2300 comprises a step 2301 of sending one or more data packets 301 of a flow to a user plane entity 300 of the mobile communication network, wherein the flow is related to an application 303. The method 2300 also comprises a step 2302 of indicating that the one or more data packets 301 of the flow are intended for processing of application-level payload data in the one or more data packets 301 by one or more user plane entities 300.

FIG. 24 shows a method 2400 for an application server 330 providing an application 303 via a mobile communication network to UE 320, according to this disclosure. The method 2400 comprises a step 2401 of receiving one or more data packets 301 of a flow, the flow being related to the application 303. The method 2400 further comprise a step 2402 of determining that application-level payload data in the one or more data packets 301 of the flow has been processed by one or more user plane entities 300 of the mobile communication network.

The present disclosure has been described in conjunction with various embodiments as examples as well as implementations. However, other variations can be understood and effected by those persons skilled in the art and practicing the claimed matter, from the studies of the drawings, this disclosure and the independent claims. In the claims as well as in the description the word “comprising” does not exclude other elements or steps and the indefinite article “a” or “an” does not exclude a plurality. A single element or other unit may fulfill the functions of several entities or items recited in the claims. The mere fact that certain measures are recited in the mutual different dependent claims does not indicate that a combination of these measures cannot be used in an advantageous implementation.

Claims

1. A user plane entity (300) for a mobile communication network, the user plane entity (300) being configured to: receive one or more data packets (301) of a flow from user equipment, UE, (320) connected to the mobile communication network, and/or receive one or more data packets (301) of the flow from a further user plane entity (300) or a data network entity (402) or an application server (330), wherein the flow is related to an application (303); execute at least one computation on application-level payload data in the one or more data packets (301) of the flow; and forward the one or more data packets (301) of the flow, to a further user plane entity

(300) or a data network entity (402) or an application server (330), and/or forward the one or more data packets (301) of the flow to the UE (320), wherein the one or more forwarded data packets (301) include the processed application-level payload data.

2. The user plane entity (300) according to claim 1, further configured to: execute no computation on the application-level payload data in the one or more data packets (301) of the flow, if the one or more data packets (301) are not intended for being processed by user plane entities (300).

3. The user plane entity (300) according to claim 1 or 2, configured to: access a payload of the one or more data packets (301) of the flow to obtain the application-level payload data; execute the at least one computation on the obtained application-level payload data; and include the processed application-level payload data into the one or more data packets

(301) of the flow, before forwarding the one or more data packets (301).

4. The user plane entity (300) according to one of the claims 1 to 3, configured to: replace the application-level payload data in the one or more data packets (301) of the flow by the processed application-level payload data, before forwarding the one or more data packets (301).

5. The user plane entity (300) according to one of the claims 1 to 4, wherein: the flow is associated with a flow profile (401), the flow profile (401) indicating one or more computations for the one or more data packets (301) of the flow; and the user plane entity (300) is configured to execute the at least one computation according to the flow profile (401).

6. The user plane entity (300) according to claim 5, configured to store the flow profile (401).

7. The user plane entity (300) according to claim 5 or 6, wherein the flow profile (401) includes at least one of: one or more identifiers, each identifier being for one of the one or more computations; and one or more attributes of the flow, the one or more attributes being configured to support execution of the one or more computations on the application-level payload data of the one or more data packets (301) of the flow.

8. The user plane entity (300) according to one of the claims 5 to 7, wherein: the flow is further associated with at least one flow rule; and the user plane entity (300) is configured to execute the at least one computation according to the flow profile (401) and based on the at least one flow rule.

9. The user plane entity (300) according to one of the claims 5 to 8, wherein; the flow is further associated with a quality of service, QoS, profile and one or more QoS rules; and the user plane entity (300) is configured to execute the at least one computation and/or to forward the one more data packets (301) of the flow according to the QoS profile and the one or more QoS rules.

10. The user plane entity (300) according to one of the claims 1 to 9, comprising at least one logical component configured to perform the at least one computation.

11. The user plane entity (300) according to one of the claims 1 to 10, further configured to: buffer two or more data packets (301) of the flow; and perform the at least one computation jointly on the application-level payload data in the two or more data packets (301) of the flow.

12. The user plane entity (300) according to one of the claims 1 to 11, configured to: execute the at least one computation on a dedicated layer (901) of a user plane protocol stack (902), wherein the dedicated layer (901) is either placed on top of multiple layers of the user plane protocol stack (902) that are dedicated for communication or is placed between multiple layers of the user plane protocol stack that are dedicated for communication and a protocol data unit layer (903) of the user plane stack (902).

13. The user plane entity (300) according to one of the claims 1 to 12, further configured to: receive configuration information (302) from a controller (310), the configuration information (302) indicating the at least one computation.

14. The user plane entity (300) according to one of the claims 5 to 13, wherein the configuration information (302) includes the flow profile (401) and the at least one flow rule.

15. The user plane entity (300) according to claim 13 or 14, wherein the configuration information includes a plurality of flow profiles (401) and a plurality of sets of flow rules, each flow profile (401) and each set of flow rules being associated with a particular flow of a plurality of flows.

16. The user plane entity (300) according to one of the claims 5 to 15, wherein the one or more computations indicated by the flow profile (501) for the one or more data packets (301) of the flow together are a micro-service; and the user plane entity (300) is configured to: store a code (1201) for running the one more computations of the micro-service; and apply the micro-service on the flow by using the code (1201).

17. The user plane entity (300) according to claim 15 or 16, wherein the configuration information (302) includes the code of the micro-service.

18. The user plane entity (300) according to one of the claims 1 to 16, wherein: the user plane entity (300) is an access network entity, or is a core network entity; and/or wherein the controller (310) is an application function or is at least one control plane entity.

19. A controller (310) for configuring one or more user plane entities (300) of a mobile communication network, the controller (310) being configured to: send configuration information (302) to the one or more user plane entities (300), the configuration information (302) indicating one or more computations for execution on application-level payload data included in one or more data packets (301) of a flow, the flow being related to an application (303).

20. The controller (310) according to claim 19, wherein the configuration information (302) indicates at least one computation to be performed by the one or more user plane entities (300).

21. The controller (310) according to claim 19 or 20, wherein: the configuration information (302) includes at least one of a flow profile (401) and at least one flow rule of the flow, the flow profile (401) indicates one or more computations for the one or more data packets (301) of the flow, and the flow rule indicates how to execute the one or more computations on the applicationlevel payload data of the one or more data packets (301) of the flow.

22. The controller (310) according to one of the claims 19 to 21, wherein the controller (310) is an application function or is at least one control plane entity (300).

23. The controller (310) according to one of the claims 19 to 22, wherein the configuration information (302) includes an association of one or more micro-services to the application (303), the micro-service comprising the one or more computations.

24. A user equipment, UE, (320) for connecting to a mobile communication network, the user equipment (320) being configured to: send one or more data packets (301) of a flow to a user plane entity (300) of the mobile communication network, wherein the flow is related to an application (303); and indicate that the one or more data packets (301) of the flow are intended for processing of application-level payload data in the one or more data packets (301) by one or more user plane entities (300).

25. The UE (320) according to claim 24 configured to include an indication in a header of the one or more data packets (301) of the flow, in order to indicate that the one or more data packets (301) of the flow are intended for the processing of the application-level payload data in the one or more data packets (301) by the one or more user plane entities (300).

26. An application server (330) for providing an application (303) via a mobile communication network to user equipment, UE, (320) the application server (330) being configured to: receive one or more data packets (301) of a flow, the flow being related to the application; and determine that application-level payload data in the one or more data packets (301) of the flow has been processed by one or more user plane entities (300) of the mobile communication network.

27. The application server (303) according to claim 25, configured to determine, based on an indication in a header of the one or more data packets (301) of the flow, that the applicationlevel payload data has been processed by the one or more user plane entities (300).

28. A method (2100) for a user plane entity (300) of a mobile communication network, the method (2100) comprising: receiving (2101) one or more data packets (301) of a flow from user equipment, UE, (320) connected to the mobile communication network, and/or receiving (2101) one or more data packets (301) from a further user plane entity (300) or a data network entity (402) or an application server (330), wherein the flow is related to an application (300); executing (2102) at least one computation on application-level payload data in the one or more data packets (301) of the flow; and forwarding (2103) the one or more data packets (301) of the flow to a further user plane entity (300) or a data network entity (402) or an application server (330), and/or forwarding (2103) the one or more data packets (301) of the flow to the UE (320), wherein the one or more forwarded data packets (301) include the processed application-level payload data.

29. A method (2200) for configuring one or more user plane entities (300) of a mobile communication network, the method (2200) comprising: sending (2201) configuration information (302) to the one or more user plane entities

(300), the configuration information (302) indicating one or more computations for execution on application-level payload data included in one or more data packets (301) of a flow, the flow being related to an application (303).

30. A method (2300) for a user equipment, UE, (320) connected to a mobile communication network, the method (2300) comprising: sending (2301) one or more data packets (301) of a flow to a user plane entity (300) of the mobile communication network, wherein the flow is related to an application (303); and indicating (2302) that the one or more data packets (301) of the flow are intended for processing of application-level payload data in the one or more data packets (301) by one or more user plane entities (300).

31. A method (2400) for an application server (330) providing an application (303) via a mobile communication network to user equipment, UE, (320) the method (2400) comprising: receiving (2401) one or more data packets (301) of a flow, the flow being related to the application (303); and determining (2402) that application-level payload data in the one or more data packets

(301) of the flow has been processed by one or more user plane entities (300) of the mobile communication network.

32. A computer program comprising instructions which, when the program is executed by a computer, cause the computer to perform the method (2100, 2200, 2300, 2400) according to one of the claims 28 to 31.