Enablement and control of distribution of compute operations in networks

Abstract

A first detection rule relates to uplink packets received from an intermediate user plane function (I-UPF) entity or a first local UPF, and / or relates to downlink packets received from a session ancho

Description

Technical Field Various example embodiments of this subject disclosure relate to enablement and control of distribution of compute operations in networks. More specifically, the various example embodiments relate to measures (including methods, apparatuses and computer program products) for realizing enablement and control of distribution of compute operations in networks. Background A communication system can be seen as a facility that enables communication sessions between two or more entities such as communication devices, base stations and / or other nodes by providing carriers between the various entities involved in the communications path. The communication system may be a wireless communication system. Examples of wireless systems comprise public land mobile networks (PLMN) operating based on radio standards (such as, those provided by 3GPP), satellite based communication systems and different wireless local networks. A wireless local network may, for example, be implemented as a wireless local area network (WLAN). The wireless systems can typically be divided into cells, and are therefore often referred to as cellular systems. The communication system and associated devices typically operate in accordance with a given standard or specification which sets forth what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and / or parameters which shall be used for the connection are also typically defined. An example of a set of standards are the so-called 5G standards. Summary Various example embodiments aim at addressing at least part of the issues and / or problems and drawbacks either explicitly described herein or otherwise apparent to a person skilled in the relevant arts. Several aspects of the various example embodiments are detailed as follows. According to an aspect, there is provided a method comprising generating a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity ora second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, and generating a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. According to an aspect, there is provided a method comprising receiving, from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header indicative of a packet destination from a packet detected according to said second detection rule, and wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. According to an aspect, there is provided a method comprising receiving a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. According to an aspect, there is provided a method comprising generating configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. According to an aspect, there is provided a method comprising generating proxy computation operation related information, and transmitting a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. According to an aspect, there is provided an apparatus comprising generating circuitry configured to generate a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, and to generate a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. According to an aspect, there is provided an apparatus comprising receiving circuitry configured to receive, from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header indicative of a packet destination from a packet detected according to said second detection rule, and wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. According to an aspect, there is provided an apparatus comprising receiving circuitry configured to receive a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding 6 information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. According to an aspect, there is provided an apparatus comprising generating circuitry configured to generate configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. According to an aspect, there is provided an apparatus comprising generating circuitry configured to generate proxy computation operation related information, and transmitting circuitry configured to transmit a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. According to an aspect, there is provided an apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform generating a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, and generating a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. According to an aspect, there is provided an apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform receiving, from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header 8 indicative of a packet destination from a packet detected according to said second detection rule, and wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. According to an aspect, there is provided an apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform receiving a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. According to an aspect, there is provided an apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform generating configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. According to an aspect, there is provided an apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform generating proxy computation operation related information, and transmitting a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. According to an aspect, there is provided an apparatus comprising means for generating a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity ora first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, and means for generating a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. According to an aspect, there is provided an apparatus comprising means for receiving, from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header indicative of a packet destination from a packet detected according to said second detection rule, and wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. According to an aspect, there is provided an apparatus comprising means for receiving a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. According to an aspect, there is provided an apparatus comprising means for generating configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. According to an aspect, there is provided an apparatus comprising means for generating proxy computation operation related information, and means for transmitting a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. According to an aspect, there is provided a computer program product comprising computer-executable computer program code which, when the program is run on a computer (e.g. a computer of an apparatus according to any one of the aforementioned apparatus-related exemplary aspects of the present disclosure), is configured to cause the computer to carry out the method according to any one of the aforementioned method-related exemplary aspects of the present disclosure. Such computer program product may comprise (or be embodied) a (tangible) computer-readable (storage) medium or the like on which the computerexecutable computer program code is stored, and / or the program may be directly loadable into an internal memory of the computer or a processor thereof. Any one of the above aspects or other aspects described herein enables an efficient enablement and control of distribution of compute operations in networks to thereby address at least part of the issues and / or problems and drawbacks identified herein or otherwise apparent to a person skilled in the relevant arts in view of the subject disclosure. In some example embodiments, there is provided enablement and control of distribution of compute operations in networks. More specifically, there are provided measures and mechanisms for realizing enablement and control of distribution of compute operations in networks. Thus, improvement may be achieved by methods, apparatuses and computer program products enabling / realizing enablement and control of distribution of compute operations in networks. Brief Description of the Drawings In the following, some example embodiments will be described in greater detail, by way of non-limiting and illustrative examples, with reference to the accompanying drawings, in which: FIG. 1 is a block diagram illustrating an apparatus according to some example embodiments, FIG. 2 is a block diagram illustrating an apparatus according to some example embodiments, FIG. 3 is a block diagram illustrating an apparatus according to some example embodiments, FIG. 4 is a block diagram illustrating an apparatus according to some example embodiments, FIG. 5 is a block diagram illustrating an apparatus according to some example embodiments, FIG. 6 is a block diagram illustrating an apparatus according to some example embodiments, FIG. 7 is a block diagram illustrating an apparatus according to some example embodiments, FIG. 8 is a block diagram illustrating an apparatus according to some example embodiments, FIG. 9 is a block diagram illustrating an apparatus according to some example embodiments, FIG. 10 is a schematic diagram of a procedure according to some example embodiments, FIG. 11 is a schematic diagram of a procedure according to some example embodiments, FIG. 12 is a schematic diagram of a procedure according to some example embodiments, FIG. 13 is a schematic diagram of a procedure according to some example embodiments, FIG. 14 is a schematic diagram of a procedure according to some example embodiments, FIG. 15 shows a schematic diagram of an example of a system environment with signaling variants, FIG. 16 shows a schematic diagram of an example of a system environment with signaling variants according to some example embodiments, FIG. 17 shows a schematic diagram of signaling sequences according to some example embodiments, FIG. 18 shows a schematic diagram of an example of a system environment with signaling variants according to some example embodiments, FIG. 19 shows a schematic diagram of signaling sequences according to some example embodiments, FIG. 20 shows a schematic diagram of signaling sequences according to some example embodiments, and FIG. 21 is a block diagram alternatively illustrating apparatuses according to some example embodiments. Detailed Description The subject disclosure is described herein with reference to particular nonlimiting and illustrative examples. A person skilled in the art will appreciate that the subject disclosure is by no means limited to these examples, and may be more broadly applied. It is to be noted that the subject disclosure and its various example embodiments refer to specifications being used as non-limiting and illustrative examples for certain network configurations and deployments. Namely, the subject disclosure and its various example embodiments are described in relation to 3GPP specifications being used as non-limiting and illustrative examples for certain network configurations and deployments. As such, the description of such example embodiments provided herein specifically refers to terminology which is directly related thereto. Such 15 terminology is only used in the context of the non-limiting and illustrative examples, and is not intended to limit the subject disclosure in any way. Rather, any other communication or communication related system deployment, etc. may also be utilized. Hereinafter, various example embodiments and implementations of the subject disclosure and its aspects are described using several variants and / or alternatives. It is generally noted that, according to certain constraints, all of the described variants and / or alternatives may be provided alone or in any combination (also including combinations of individual features of the various variants and / or alternatives). As used herein, "at least one of the following: " and "at least one of " and similar wording, where the list of two or more elements are joined by "and" or "or", mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements. The subject disclosure generally relates to distribution of compute operations in networks, and, more specifically to enabling application related in-network computing in a 5th Generation (5G) system (5GS) user plane (UP). As further detailed herein, one or more issues can arise in that traffic flow control sufficiently allowing distributed compute operations are not specified. Hence, enablement and control of distribution of compute operations in networks may provide advantages and improvements for certain use cases. According to some example embodiments, there are provided measures and mechanisms for (enabling / realizing) enablement and control of distribution of compute operations in networks. Due to requirements of performance, data privacy, or network efficiency, a complex computing task may be split into several smaller compute 16 operations, where each of the operations may be executed at a different compute node in the network. Executing one or several compute operation(s) within a mobile network operator's domain helps exploiting the edge-cloud continuum, e.g., the availability of specific computing capabilities in different parts of the network (far edge, edge, aggregation, central cloud). On the one hand, there have been several use cases using a group or sequence of compute operations to finish a task. One example is artificial intelligence (AI) / machine learning (ML) model split. Here, an AI / ML model-related procedure is split into two or more compute operations to be performed by a user equipment (UE) and network nodes in the network, so that the resource consumption, e.g., computing power and energy, will be reduced on the UE side. Another example is compositional learning. Several computing tasks may be composed to a computing chain / graph, each task as a computing operation, to reuse processed intermediate data. Moreover, sensitive data or intermediate results can only be processed on a given host or in a certain region, due to hardware requirements or data privacy. In turn, the compute operation processing of the sensitive data or intermediate results is limited to be deployed on the given host or in the required region. On the other hand, many activities related to 6th Generation (6G) network design consider computing metrics to enhance, e.g., routing decisions. In the context of integration of network and computing (INC), optimal application service instances hosting the compute operations can be selected. In the IETF WG computing-aware networking (CAN) (later renamed to computing-aware traffic steering (CATS)), traffic steering based on computing metrics are being studied. As a further step beyond the present research activities, data should not only be computed / processed on a single cloud node, but on several nodes in a parallel or sequential manner, e.g., distributed / ubiquitous computing. This means that edge nodes should not be the final destination of data traffic in the case of service instance selection for INC or traffic steering for CAN / CATS. The packet data should / can be first computed on one or several local cloud(s) with specific function / hardware support, then the mobile network user plane (UP) can further process the packet data in the same protocol data unit (PDU) session (e.g., packet routing, lawful intercept, etc.). There have been several studies and standards related to steering traffic via intermediate user plane function (I-UPF) to a local cloud on which a compute operation is hosted, or to a central / remote data network (DN) via one or more user plane function(s) (UPF). FIG. 15 shows a schematic diagram of an example of a system environment with signaling variants, and in particular illustrates N6- and N9-like connections defined by 3rd Generation Partnership Project (3GPP) and the connection via public networks. Specifically, the UP and the compute operations on a local cloud are illustrated in FIG. 15 related to known edge computing reference architectures. The local cloud can be a local server controlled by a third party / network operator or an edge server. Based on the current 5G system (5GS) architecture defined by 3GPP, two types of connections are possible in the PDU session. 1.) N6-like connection (dashed line in FIG. 15): The local (PDU session anchor (PSA)) UPF acts as a PSA UPF to the local cloud, so that traffic data can be routed to the compute operations deployed on the local cloud. However, after data being computed by the compute operations, the data cannot be further forwarded to the (central) data network (DN) via the PSA UPF, since there is no connectivity defined from the local cloud to DN via UP. 2.) N9-like connection (dotted line in FIG. 15): The local (PSA) UPF forms a UPF chain together with intermediate UPF (I-UPF) and PSA UPF, so that traffic data can be routed to DN. However, data cannot be first redirected to the compute operations near the local (PSA) UPF for computing, but directly be forwarded to the (central) DN only. Traffic routing via a public network (dash-dotted line in FIG. 15), e.g., internet, may be possible. However, public networks are out of network operator's control, UPF functions cannot be applied on this path, e.g., they would have to be applied before the traffic is sent to the local / edge compute operation (e.g., lawful intercept, quality of service (QoS) enforcement, traffic usage reporting, and downlink (DL) buffering), and the function of anchor point for UE mobility and session and service continuity (SSC) may not be supported. This may lead to transmission failures, lack of QoS guarantee, etc. FIG. 16 shows a schematic diagram of an example of a system environment with signaling variants according to some example embodiments, and in particular illustrates connectivity between a local cloud and DN, to route traffic via the user plane. Namely, according to some example embodiments, at least the following aspects are addressed and effects achieved. 1.) How to support the routing of UE application traffic to a local DN and further to a cloud server located in the central DN. 2.) How to steer UE application traffic, e.g., UL traffic, to a local (processing) server to allow local-processing of the data / traffic, before sending to the final destination server. 3.) How to steer DL traffic related to a specific application (from a respective application server in the DN) and destined to the UE to be first routed via local (processing) application server. 4.) How a trusted and / or non-trusted third party application function (AF) can influence local processing of specific application traffic. In particular, some example embodiments target to route traffic between local / edge compute operation and the (central) DN via 5GS user plane, to enable application-related in-network computing in mobile networks. There is no mechanism defined in 3GPP that allows for integrating an application-related local / edge compute operation that is located outside the mobile network operator's (MNO) administrative domain (e.g., on an edge cloud node) into the user plane path of the mobile (core) network, see the dashed line in FIG. 16. More specifically, while current 3GPP specifications allow for local access to DN or edge application server (EAS), e.g., the PDU session is anchored and terminated at a "local" access to the DN, it is not possible to steer traffic to such a local compute node and, after completion of the compute task (e.g., the "local compute operation"), send the traffic back into the core network user plane towards the central UPF or PSA UPF (where remaining mobile network UP processing would preferably take place) and further towards the "central" access to the DN. Hence, in brief, according to some example embodiments, UE UL and DL application traffic is enabled to be steered for first processing locally (e.g., at the public land mobile network (PLMN) controlled or trusted third party deployed application server, or edge application server) and then to the central application server(s) (or to the UE in case of DL traffic, e.g., at the central application server first and then at the local application server), thus ensuring required QoS. The mentioned application could be, e.g., a video analytics service from traffic / camera monitoring. This involves a method for "interconnecting a local / edge compute operation and the (central) DN via user plane" to enable application-related in-network computing in the 5GS user plane, e.g., a method to route traffic between the local cloud and the DN via user plane of the operator network. With methods and means according to some example embodiments, data packets are encapsuled with local / edge compute operation's routing information by a local (PSA) UPF for performing the compute operation on a local / edge server, and (re-)encapsuled with GTP-U headers by the local (PSA) UPF to continue user plane forwarding after the local / edge compute operations' performance. The interconnection particularly addressed by some example embodiments is shown as dashed line in FIG. 16. The local cloud is a server located on the network edge. It can be either a network operator owned local server, or a trusted third party controlled local server, on which compute operation(s) is / are deployed. Thus, a compute operation deployed on the local server is denoted as local compute operation. The local cloud can also be a regular edge server, on which an edge application acting as compute operation(s) is deployed. Thus, a compute operation deployed on the edge server is denoted as edge compute operation. Therefore, some example embodiments may be considered as focusing on two scenarios: Scenario 1): Interconnecting a local compute operation deployed on a local server, which is deployed by PLMN or trusted third party via the user plane path, with the DN via the user plane; and Scenario 2): Interconnecting an edge compute operation on an edge server with the DN via the user plane. According to some example embodiments, in particular in relation to Scenario 1, an application function (AF) based on its internal trigger generates and provides information to 5GC to enable identification of the local compute operation, for a specific edge traffic or application(s). According to example some embodiments, the information includes local operation access identifier (LOAI) and routing information for local compute operation. This information is then stored in a database repository, e.g., unified data management (UDM) / unified data repository (UDR) and subsequently provided to SMF, e.g., via PCC rules. According to some example embodiments, in particular in relation to Scenario 1 and 2, based on the received information provided by the AF, the SMF and / or intermediate SMF (I-SMF) generates new packet detection rules (PDRs) and forwarding action rules (FARs). According to example some embodiments, the SMF then configures these PDRs and FARs to the local (PSA) UPF via e.g., N4 interface. Additionally, according to some example embodiments, configuration context for local / edge compute operation related to packet processing and security is defined by a compute operation controller (Step 16 in FIG. 19). According to some example embodiments, in particular in relation to Scenario 1 and 2, a traffic routing procedure is provided, which is jointly performed by the local (PSA) UPF and the local / edge compute operation. Based on the received PDRs and FARs provided by SMF and / or I-SMF, the local (PSA) UPF forwards the matched packets to the local / edge compute operation instead of forwarding to the central DN (Step 3 in FIG. 20). Also, following the configuration context defined by the compute operation controller, the local / edge compute operation forwards the computed packets back to the local (PSA) UPF (Step 4 in FIG. 20). According to some example embodiments, the local (PSA) UPF then forwards the computed / processed packets via the GTP-U tunnel to the central DN (Step 5 in FIG. 20), or to the UE in case of DL traffic. As provided herein, the terms "local cloud" and "DN" refer to "local DN" and "central DN", respectively, and "compute operation" refers to "APP service" in some context. In the absence of connectivity between the local cloud and the "central" DN via the operator's network, the interconnection approach according to some example embodiments through the user plane of the operator's network is to support further mobile UP processing after application-related local compute operations have been executed. With this interconnection approach according to some example embodiments, advantageously, the following traffic routing can be achieved: UL traffic related to an application is first routed to local / edge compute operation(s) hosted on a local / edge server, and then further routed to other compute operation(s) in another local cloud or DN. Optionally, while routing to the local / edge computing operation, UL traffic may also be duplicated by the local (PSA) UPF for simultaneous anchoring to the PSA UPF. DL traffic related to an application coming into the 5GS via N6 from the "central" DN is first routed to local / edge compute operation(s) in a local / edge server for local-computing, and only afterwards forwarded to the UE (within same PDU session). In some example embodiments, when routing to the local / edge computing operation, DL traffic may also be optionally duplicated by the local (PSA) UPF for simultaneous forwarding to the UE. Although methods and means are intended to be utilizable for UL traffic and DL traffic, methods and means according to some example embodiments can flexibly also be used only for UL or for DL traffic. Some example embodiments are specified below in more detail. FIG. 1 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be implemented as a network node or entity 10, such as a session management function (Intermediate session management function) entity, comprising a generating circuitry 11. In some example embodiments, the apparatus may be configured to operate as a session management function (intermediate session management function) entity. For instance, the apparatus may be configured to perform one or more functions of a session management function (intermediate session 23 management function) entity. The generating circuitry 11 generates a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity ora second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule. The generating circuitry 11 (or another generating circuitry) generates a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. FIG. 10 is a schematic diagram of a procedure according to some example embodiments. The apparatus according to FIG. 1 may perform the method of FIG. 10, but is not limited to this method. The method of FIG. 10 may be performed by the apparatus of FIG. 1, but is not limited to being performed by this apparatus. As shown in FIG. 10, a procedure according to some example embodiments comprises an operation of generating (S101) a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, and an operation of generating a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. FIG. 2 is a block diagram illustrating an apparatus according to some example embodiments. In particular, FIG. 2 illustrates a variation of the apparatus shown in FIG. 1. The apparatus according to FIG. 2 may thus further comprise a transmitting circuitry 21, a receiving circuitry 22, a selecting circuitry 23, and / or a specifying circuitry 24. In an example embodiment, at least some of the functionalities of the apparatus shown in FIG. 1 (or 2) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes. According to a variation of the procedure shown in FIG. 10, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of transmitting, towards a third local user plane function entity associated with said network entity providing said proxy computation operation, a request, said request including said first detection rule, said first action rule, said second detection rule, and said second action rule. According to a variation of the procedure shown in FIG. 10, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of receiving an acknowledgement response. According to a variation of the procedure shown in FIG. 10, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of selecting said third local user plane function entity based on a network access identifier of said network entity providing said proxy computation operation. According to a variation of the procedure shown in FIG. 10, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of receiving a proxy computation operation interconnection initiation message, said proxy computation operation interconnection initiation message including said network access identifier of said network entity providing said proxy computation operation and said information on traffic routing towards said network entity providing said proxy computation operation. According to further example embodiments, said network access identifier of said network entity providing said proxy computation operation is a data network access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is an edge application server network address of said network entity providing said proxy computation operation. According to further example embodiments, said proxy computation operation interconnection initiation message includes an identifier of said proxy computation operation, and said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. According to a variation of the procedure shown in FIG. 10, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of specifying at least one of the following: said intermediate user plane function entity, or said first local user plane function entity, or said session anchor user plane function entity, or said second local user plane function entity, or said network entity providing said proxy computation operation. FIG. 3 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be implemented as a network node or entity 30, such as a local (protocol data unit session anchor) user plane function entity, comprising a receiving circuitry 31. In some example embodiments, the apparatus may be configured to operate as a local (protocol data unit session anchor) user plane function entity. For instance, the apparatus may be configured to perform one or more functions of a local (protocol data unit session anchor) user plane function entity. The receiving circuitry 31 receives, from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule. Here, said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity. Further, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and said first action rule further pertains to forwarding of said packet detected according to said first detection rule. Yet further, said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header indicative of a packet destination from a packet detected according to said second detection rule. Yet further, said second action rule pertains to forwarding of said packet detected according to said second detection rule. FIG. 11 is a schematic diagram of a procedure according to some example embodiments. The apparatus according to FIG. 3 may perform the method of FIG. 11, but is not limited to this method. The method of FIG. 11 may be performed by the apparatus of FIG. 3, but is not limited to being performed by this apparatus. As shown in FIG. 11, a procedure according to some example embodiments comprises an operation of receiving (Sill), from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule. Here, said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity. Further, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and said first action rule further pertains to forwarding of said packet detected according to said first detection rule. Yet further, said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header indicative of a packet destination from a packet detected according to said second detection rule. Yet further, said second action rule pertains to forwarding of said packet detected according to said second detection rule. FIG. 4 is a block diagram illustrating an apparatus according to some example embodiments. In particular, FIG. 4 illustrates a variation of the apparatus shown in FIG. 3. The apparatus according to FIG. 4 may thus further comprise a transmitting circuitry 41, a matching circuitry 42, an applying circuitry 43, an adding circuitry 44, a forwarding circuitry 45, a removing circuitry 46, and / or a duplicating circuitry 47. In an example embodiment, at least some of the functionalities of the apparatus shown in FIG. 3 (or 4) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes. According to a variation of the procedure shown in FIG. 11, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of transmitting an acknowledgement response. According to a variation of the procedure shown in FIG. 11, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of receiving a packet, an operation of matching said packet against at least one of the following: said first detection rule, or said second detection rule, an operation of applying said first action rule to said packet, if said packet matches with said first detection rule, and an operation of applying said 29 second action rule to said packet, if said packet matches with said second detection rule. According to a variation of the procedure shown in FIG. 11, example details of the applying operation (applying said first action rule to said packet) are provided, which are inherently independent from each other as such. Such example applying operation (applying said first action rule to said packet) according to some example embodiments may comprise an operation of adding said first outer header to said packet, and an operation of forwarding said packet. According to a variation of the procedure shown in FIG. 11, example details of the applying operation (applying said second action rule to said packet) are provided, which are inherently independent from each other as such. Such example applying operation (applying said second action rule to said packet) according to some example embodiments may comprise an operation of removing said second outer header from said packet, and an operation of forwarding said packet. According to a variation of the procedure shown in FIG. 11, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of (before applying any of said applying said first action rule and said second action rule to said packet) duplicating said packet as a duplicated packet, and an operation of forwarding said duplicated packet to an original destination of said packet. FIG. 5 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be implemented as a network node or entity 50, such as a local / edge compute operation (server) entity, comprising a receiving circuitry 51. In some example embodiments, the apparatus may be configured to operate as a local / edge computer operation (server) entity. For instance, the apparatus may be configured to perform one or more functions of a local / edge computer operation (server) entity. The receiving circuitry 31 receives a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information. Here, said packet detection information defines detection of packets received from a local user plane function entity. Further, said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection information and compute processing to be performed on data of said packet. Yet further, said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. FIG. 12 is a schematic diagram of a procedure according to some example embodiments. The apparatus according to FIG. 5 may perform the method of FIG. 12, but is not limited to this method. The method of FIG. 12 may be performed by the apparatus of FIG. 5, but is not limited to being performed by this apparatus. As shown in FIG. 12, a procedure according to some example embodiments comprises an operation of receiving (S121) a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information. Here, said packet detection information defines detection of packets received from a local user plane function entity. Further, said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection information and compute processing to be performed on data of said packet. Yet further, said packet forwarding Information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. FIG. 6 is a block diagram illustrating an apparatus according to some example embodiments. In particular, FIG. 6 illustrates a variation of the apparatus shown in FIG. 5. The apparatus according to FIG. 6 may thus further comprise a transmitting circuitry 61, a matching circuitry 62, a processing circuitry 63, a removing circuitry 64, a performing circuitry 65, and / or an adding circuitry 66. In an example embodiment, at least some of the functionalities of the apparatus shown in FIG. 5 (or 6) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes. According to a variation of the procedure shown in FIG. 12, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of transmitting a configuration acknowledgement response. According to a variation of the procedure shown in FIG. 12, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of receiving a packet, an operation of matching said packet against said packet detection information, and an operation of processing said packet to a processed packet, if said packet matches with said packet detection information. Further, such example processing operation (processing said packet) according to some example embodiments may comprise an operation of removing said first outer header from said packet, an operation of performing said compute processing on said data of said packet, and an operation of adding said second outer header to said packet. According to a variation of the procedure shown in FIG. 12, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of transmitting said processed packet. FIG. 7 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be implemented as a network node or entity 70, such as a compute operation controller entity, comprising a generating circuitry 71. In some example embodiments, the apparatus may be configured to operate as a compute operation controller entity. For instance, the apparatus may be configured to perform one or more functions of a compute operation controller entity. The generating circuitry 71 generates configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information. Here, said packet detection information defines detection of packets received from a local user plane function entity. Further, said packet processing information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet. Yet further, said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. FIG. 13 is a schematic diagram of a procedure according to some example embodiments. The apparatus according to FIG. 7 may perform the method of FIG. 13, but is not limited to this method. The method of FIG. 13 may be performed by the apparatus of FIG. 7, but is not limited to being performed by this apparatus. As shown in FIG. 13, a procedure according to some example embodiments comprises an operation of generating (S131) configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information. Here, said packet detection information defines detection of packets received from a local user plane function entity. Further, said packet processing information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet. Yet further, said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. FIG. 8 is a block diagram illustrating an apparatus according to some example embodiments. In particular, FIG. 8 illustrates a variation of the apparatus shown in FIG. 7. The apparatus according to FIG. 8 may thus further comprise a transmitting circuitry 81, and / or a receiving circuitry 82. In an example embodiment, at least some of the functionalities of the apparatus shown in FIG. 7 (or 8) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes. According to a variation of the procedure shown in FIG. 13, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of transmitting, towards a network entity providing said proxy computation operation, a configuration message, said configuration message including said configuration information. According to a variation of the procedure shown In FIG. 13, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of receiving a configuration acknowledgement response. According to a variation of the procedure shown in FIG. 13, example additional operations are provided, which are inherently independent from each other as such. According to such variation, an example method according to some example embodiments may comprise an operation of generating proxy computation operation related information, and an operation of transmitting a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of said proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. According to further example embodiments, said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. FIG. 9 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be implemented as a network node or entity 90, such as an application function entity comprising a generating circuitry 91 and a transmitting circuitry 92. In some example embodiments, the apparatus may be configured to operate as an application function entity. For instance, the apparatus may be configured to perform one or more functions of an application function entity. The generating circuitry 91 generates proxy computation operation related information. The transmitting circuitry 92 transmits a request message including said proxy computation operation related information. Here, said proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. FIG. 14 is a schematic diagram of a procedure according to some example embodiments. The apparatus according to FIG. 9 may perform the method of FIG. 14, but is not limited to this method. The method of FIG. 14 may be performed by the apparatus of FIG. 9, but is not limited to being performed by this apparatus. As shown in FIG. 14, a procedure according to some example embodiments comprises an operation of generating (S141) proxy computation operation related information, and an operation of transmitting (S142) a request message including said proxy computation operation related information. Here, said proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. In an example embodiment, at least some of the functionalities of the apparatus shown in FIG. 9 may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes. According to further example embodiments, said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. Some example embodiments outlined and specified above are explained below in more specific terms. Namely, according to some example embodiments, in particular in relation to Scenario 1, an information tuple is built to identify a local compute operation, which is deployed on a local server. The local compute operation's information tuple consists of three information elements (IE): - an application ID to identify the compute operation, - a newly defined local operation access identifier (LOAI) to indicate the access to the local server, at which the local compute operation with the application ID can be found (e.g., compute operation server), and - a newly defined routing information of the local compute operation for traffic routing. According to example some embodiments, an AF is responsible for generating the information tuple, and the information tuple can be exposed to an SMF. In turn, the traffic can be influenced to be routed to the local compute operation, e.g., in a PDU session establishment or in a PDU session modification. According to some example embodiments, in particular in relation to Scenario 2, known EAS discovery and (re-)discovery procedures can be used (instead). With the information tuple (Scenario 1) or data network access identifier (DNAI) / edge application server (EAS) internet protocol (IP) address (Scenario 2) as policy and charging control (PCC) rules, the local / edge compute operation can be integrated into the user plane with the help of I-UPF's session breakout and local (PSA) UPF. According to some example embodiments, the local (PSA) UFP and the local / edge compute operation (server) are configured with outer header creation and removal to ensure that data packets can be routed to the local / edge compute operation for computing and later to be routed back into the user plane towards PSA UPF. Other configuration context of the local / edge compute operation may be provided by a compute operation controller. According to some example embodiments, traffic routing between the local / edge compute operation and DN via the user plane are specified. The specified procedure is detailed as to how traffic is processed by the local (PAS) configuration. As summarized above, "generation of local compute operation's information 5 tuple for AF traffic influence" is specified. According to some example embodiments, in particular in relation to Scenario 1, a local compute operation is identified by an application identifier (application ID). A new IE local operation access identifier (LOAI) is defined 10 to access to the local compute operation. A new IE routing information of the local compute operation is utilized to provide a destination address for routing traffic to the local compute operation. These tree IEs compose the information tuple of the local compute operation to influence traffic routing. The details of the three IEs according to some example embodiments are listed in Table 15 1 below. Table 1: Information Element Description Category Application ID Provide an identifier of the local operation, as defined in TS 23.203 V17.2.0. Mandatory LOAI Identify the access to a local server, at which the local compute operation with the application ID can be found. It is similar to DNAI defined in 3GPPTS 23.501 V18.1.0 Clause 5.6.7, but for identifying local compute operation instead of (local) DN. Mandatory Routing Information Information to route traffic to the local compute operation. It can be IP address of the local compute operation. Mandatory This IEs in Table 1 could be pre-configured in 5GC, e.g., in the PCF, and / or provided by AF. In case this is provided by the AF, the AF requests to influence traffic routing to the local compute operation by generating the information tuple, which later can be exposed to SMF. FIG. 17 shows a schematic diagram of signaling sequences according to some example embodiments, and in particular illustrates generating local compute operation's information tuple for AF traffic influence. The call flow illustrated in FIG. 17 may be based on processing AF requests to influence traffic routing and / or service function chaining for sessions not identified by a UE address as e.g., specified in 3GPPTS 23.502 V18.1.1. According to a Step 0a of FIG. 17, PCF(s) subscribe(s) to modification of AF requests from UDR. According to a Step Ob-1 of FIG. 17, a V-SMF supporting HR-SBO subscribes to notification of AF request by invoking Nnef_TrafficInfluenceData_Subscribe service from V-NEF. According to a Step Ob-2 of FIG. 17, the V-NEF subscribes to notification of AF request from V-UDR. According to a Step 1 of FIG. 17, according to some example embodiments, the AF invokes a Nnef_TrafficInfluence_Create service operation to create a new request. Content of this AF request is illustrated in Table 1 above: newly defined information tuple for traffic routing, including application ID, LOAI, and routing information, which are based on the local compute operation. The request may also contain an AF transaction ID and may contain other data keys. Other data keys may include those defined in Clause 5.2.6.7 "Nnef Trafficinfluence service" in 3GPPTS 23.502 V18.1.1. According to a Step 2 of FIG. 17, according to some example embodiments, the AF sends its request with the local compute operation's information tuple to the NEF. According to Steps 3a and 3b of FIG. 17, according to some example embodiments, the NEF stores the AF requested information tuple in the UDR. The NEF responds to AF. According to Steps 4a and 4b of FIG. 17, according to some example embodiments, the PCF(s) that have subscribed to modifications of AF requests receive(s) a Nudr_DM_Notify notification of data change from the UDR. The information relates to the local compute operation's information tuple. The V-UDR notifies the subscribed V-NEF of the AF traffic influence request information. According to a Step 5a of FIG. 17, according to some example embodiments, the PCF updates the SMF in the impacted PDU sessions with corresponding new local compute operation's policy information by invoking Npcf_SMPolicyControl_UpdateNotify. PCF includes traffic steering information in the relevant PCC rules. The procedures of notification reporting request, service experience analytics may be similar to step 5 in Clause 4.3.6.2 of in 3GPP TS 23.502 V18.1.1. According to a Step 5b of FIG. 17, the V-NEF notifies the subscribed V-SMF of the AF traffic influence request information. According to a Step 6 of FIG. 17, according to some example embodiments, the SMF takes appropriate actions to reconfigure the user plane of the PDU session, which may be similar to step 6 described in Clause 4.3.6.2 of in 3GPP TS 23.502 V18.1.1. According to a Step 7 of FIG. 17, according to some example embodiments, the SMF may decide whether it is required to send the target LOAI or the common LOAI to the AMF for triggering SMF / I-SMF (re)selection and then inform the target LOAI information or the common LOAI information for the current PDU session or for the next PDU session to AMF via Nsmf_PDUSession_SMContextStatusNotify service operation. According to some example embodiments, in particular in relation to Scenario 2, to identify and discover the edge server and edge compute operation, an "edge application server (EAS) (re-)discovery" processing similar to that defined in TS 23.548 V18.1.1 Clause 6.2.3 may be reused to replace the procedures in FIG. 17. The (re-)discovery can be performed via 5GC NFs, e.g., EASDF, DNS server / resolver, or AP. Alternatively, the EAS information may also be provided by a respective application function, which may be performed, for example, using the existing procedure as described in TS 23.548 V18.1.1. As summarized above, "interconnecting a local / edge compute operation in the user plane" is specified. According to some example embodiments, in particular in relation to Scenario 1, the traffic steering information of a local compute operation can be generated following the procedure defined above ("generation of local compute operation's information tuple for AF traffic influence"). According to some example embodiments, in particular in relation to Scenario 2, the traffic steering information of an edge compute operation can be generated by EAS (re-)discovery procedures similar to those defined in TS 23.548 V18.1.1 Clause 6.2.3 or via the AF provided traffic influence information e.g., as specified in Clause 5.6.7 of TS 23.501 V18.1.1 and clause 4.3.6.3 of TS 23.502 V18.1.1. In both scenarios, PCF includes traffic steering information in the relevant PCC rules. According to some example embodiments, the local / edge compute operation can then be interconnected in the user plane via PDU session establishment or modification. FIG. 19 shows a schematic diagram of signaling sequences according to some example embodiments, and in particular illustrates configuration to interconnect local / edge compute operation in a PDU Session. The call flow illustrated in FIG. 19 may be based on Clause 4.3.2 "PDU Session Establishment" and Clause 4.3.3 "PDU Session Modification" in 3GPP TS 23.502 V18.1.1. In a Step 1 of FIG. 19, the interconnection of a local / edge computing with DN can be realized during a new PDU Session establishment (Option A) or be added in an existing PDU session (Option B). Therefore, there are at least two options that the configuration of the interconnection may be initiated: - Option A: The PDU session establishment Step l-10b of FIG. 4.3.2.2.1-1 in TS 23.502 V18.1.1 can be reused. - Option B: The PDU Session modification Step lb of FIG. 4.3.3.2-1 in TS 23.502 V18.1.1 can be reused. In a Step 2 of FIG. 19, according to some example embodiments, the PCF invokes a Npcf_SMPolicyControl_UpdateNotify service operation to initiate the interconnection. In Scenario 1, PCC rules contain the local compute operation's information tuple, as defined in Step 5a in FIG. 17. In Scenario 2, PCC rules contain the local compute operation's DNAI and / EAS IP, e.g., as defined in TS 23.548 V18.1.1 Clause 6.2.3. The PCF sends the PCC rules to SMF. In Steps 3 to 5 of FIG. 19, according to some example embodiments, the SMF invokes a Nsmf_PDUSession_SMContextStatusNotify service operation, when the SMF cannot serve the target LOAI (Scenario 1) or DNAI (Scenario 2), or when an existing I-SMF is not needed. The content of the message includes the target LOAI (Scenario 1) or DNAI (Scenario 2) information. If the I-SMF selection is expected, the AMF selects a new I-SMF which can serve the target LOAI (Scenario 1) or DNAI (Scenario 2). AMF sends a Nsmf_PDUSession_CreateSMContext request to the new I-SMF. These steps may be based on Step 2a - 4a of Clause 4.23.5.4 in TS 23.502 V18.1.1, with the extension of using LOAI instead of DNAI for Scenario 1. In a Step 6 of FIG. 19, according to some example embodiments, the I-SMF selects a local (PSA) UPF selection based on the target LOAI (Scenario 1) or DNAI (Scenario 2). In Steps 7 to 12 of FIG. 19, according to some example embodiments, an I-UPF is inserted as uplink classifier (UL-CL) or Branch Point (BP) based on the target LOAI (Scenario 1) or DNAI (Scenario 2) information. These steps may be based on Step 6 of Clause 4.23.5.4 in TS 23.502 V18.1.1, with the extension of using LOAI instead of DNAI for Scenario 1. In a Step 13 of FIG. 19, according to some example embodiments, the I-SMF creates two new packet detection rules (PDRs) to classify data packets to and from the local / edge compute operation on the local (PSA) UPF, and, accordingly, two new forwarding action rules (FARs) to route traffic between local (PSA) UPF and the local / edge compute operation. According to some example embodiments, the parameters of the PDRs and FARs are set as defined in Table 2 and 3. Table 2: PDR and FAR for traffic routing to the local / edge compute operation. Information Element Attribute Value PDR1 Packet Filter Set UL incoming packets from I-UPF. or a Local (PSA) UPF. DL incoming packets from PSA UPF or a local (PSA) UPF. Forwarding Action Rule ID The FAR ID for packet routing to the local / edge compute operation should be the ID of FAR1. Other parameters Other parameters can be set upon individual needs. FAR1 Action Forwarding. Outer header creation Adding outer header: Routing Information from the local compute operation's information tuple in Scenario 1 or EAS IP of the edge local compute operation in Scenario 2. Other parameters Other parameters can be set upon individual needs. Table 3: PDR and FAR for traffic routing from the local / edge compute operation. Information Element Attribute Value PDR2 Packet Filter Set Incoming packets from the local / edge compute operation. Forwarding Action Rule ID The FAR ID for packet routing to PSA UPF or the next Local (PSA) UPF should be the ID of FAR2. Outer header removal Remove the outer header added by the local / edge compute operation. Other parameters Other parameters can be set upon individual needs. FAR2 Action Forwarding. Other parameters Other parameters can be set upon individual needs. FIG. 18 shows a schematic diagram of an example of a system environment with signaling variants according to some example embodiments, and in particular illustrated a packet processing flow with the new defined PDRs and FARs. That is, FIG. 18 reflects a packet processing flow for traffic routing to and from the local / edge compute operation. Returning to FIG. 19, in Steps 14 and 15 of FIG. 19, according to some example embodiments, the I-SMF initiates N4 association update. In a Step 16 of FIG. 19, according to some example embodiments, the compute operation controller generates a configuration context. The packet handling by the local / edge compute operation should be defined. In particular, 1. for every incoming packet from local (PSA) UPF, the outer header should be removed; 2. then, the local / edge compute operation can be performed on the packet data; and 3. after performing the local / edge compute operation, an outer header is (to be) added in the way that local (PSA) UPF is identified as the destination address, so that data packets can be forwarded back to local (PSA) UPF. Additionally, other configuration context should be shared to the local / edge compute operation, including encryption keys and other security information to enable the processing on the packets' payload. In a Step 17 and 18 of FIG. 19, according to some example embodiments, the compute operation controller sends the configuration context to the local / edge compute operation. Upon a successful sending, a response is sent from the local / edge compute operation to the compute operation controller. According to some example embodiments, steps 16 to 18 of FIG. 19 may be independent of the remaining procedure illustrated in FIG. 19, thus enabling the compute operation controller to provide the required information to the local / edge compute operation in advance, e.g., during deployment or regular configuration process and / or on request from local / edge compute operation. In a Step 19 of FIG. 19, the remaining configuration of interconnection realized during a new PDU session establishment (Option A) or added in an existing PDU session (Option B) may be performed as follows: - Option A: The PDU session establishment Step 11-21 of FIG. 4.3.2.2.1-1 in TS 23.502 V18.1.1 can be reused. - Option B: The PDU Session modification Step 4-13 of FIG. 4.3.3.2-1 in TS 23.502 V18.1.1 can be reused. In the case that the SMF can serve the target LOAI or DNAI, I-SMF insertion in Steps 3 to 5 in FIG. 19 can be skipped, and, according to some example embodiments, the following procedures related to I-SMF are realized by the SMF. As summarized above, "traffic routing between a local / edge compute operation and DN via user plane" is specified. Based on the configuration procedures defined above ("interconnecting a local / edge compute operation in the user plane"), UL traffic can be continuing forwarded to DN by local (PSA) UPF after first be forwarded and computed by the local / edge compute operation. FIG. 20 shows a schematic diagram of signaling sequences according to some example embodiments, and in particular illustrates traffic routing via the local / edge compute operation in user plane. In FIG. 20, the control plane NFs involved in the configuration procedures are represented by the entity 5G Core (5GC). In a Step 1 of FIG. 20, the interconnecting is initialized during a PDU session establishment or modification, corresponding to Option A and B of the configuration procedures defined above ("interconnecting a local / edge compute operation in the user plane"). In a Step 2 of FIG. 20, according to some example embodiments, the configuration procedures defined above ("interconnecting a local / edge compute operation in the user plane") are realized. - UE sends UL traffic to DN, and - UL traffic from UE to DN is breakouted by the I-UPF using ULCL or BP to local (PSA) UPF. In a Step 3 of FIG. 20, according to some example embodiments, the local (PSA) UPF realizes the PDR.1 and FAR.1 configuration defined above in Table 2, e.g., adding outer header and performing forwarding action. According to some example embodiments, the UL traffic can be optionally duplicated to be simultaneously forwarded to PSA UPF towards DN. According to some example embodiments, the UL traffic with the added header is routed to local / edge compute operation. In a Step 4 of FIG. 20, according to some example embodiments, the local / edge compute operation realizes the configuration context defined in Step 16 of FIG. 19 discussed above, e.g., outer header removal, compute operation performance, and outer header adding. According to some example embodiments, the UL traffic with the re-added header is routed back to local (PSA) UPF. In a Step 5 of FIG. 20, according to some example embodiments, the local (PSA) UPF realizes the PDR2 and FAR2 configuration defined above in Table 3, e.g., removing the added outer header and performing forwarding action. According to some example embodiments, the UL traffic is routed to PSA UPF and further to DN, as the original destination provided by UE. FIG. 20 shows the UL traffic routing. DL traffic can be a regular DL traffic from PSA UPF to UE or similar outer header processing like UL traffic. Multiple local / edge compute operation can be interconnected by building a chain of [local (PSA) UPF, local / edge compute operation] pairs. In the case of multiple pairs, according to some example embodiments, Step 5 of FIG. 20 is changed to modifying the outer header as the next local (PSA) UPF instead of removing the outer header if it is not the last pair towards PSA UPF. The above-described procedures and functions may be implemented by respective functional elements, processors, or the like, as described below. In the foregoing example description of the network entity, only the units that are relevant for understanding the subject disclosure have been described using functional blocks. The network entity may comprise further units that are utilized for its respective operation. However, a description of these units is omitted in the subject disclosure. The arrangement of the functional blocks of the devices is not construed to limit the subject disclosure, and the functions may be performed by one block or further split into sub-blocks. When in the foregoing description it is stated that the apparatus, e.g., network node or entity (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that a (e.g. at least one) processor or corresponding circuitry, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be equivalently implementable by specifically configured circuitry or means for performing the respective function (e.g., the expression "unit configured to" is construed to be equivalent to an expression such as "means for"). In FIG. 21, an alternative illustration of apparatuses according to some example embodiments is depicted. As indicated in FIG. 21, according to some example embodiments, the apparatus (network node or entity) 10' (corresponding to the network node or entity 10) comprises a processor 211, a memory 212 and an interface 213, which are connected by a bus 214 or the like. Further, according to some example embodiments, the apparatus (network node or entity) 30' (corresponding to the network node or entity 30) comprises a processor 211, a memory 212 and an interface 213, which are connected by a bus 214 or the like. Further, according to some example embodiments, the apparatus (network node or entity) 50' (corresponding to the network node or entity 50) comprises a processor 211, a memory 212 and an interface 213, which are connected by a bus 214 or the like. Further, according to some example embodiments, the apparatus (network node or entity) 70' (corresponding to the network node or entity 70) comprises a processor 211, a memory 212 and an interface 213, which are connected by a bus 214 or the like. Further, according to some example embodiments, the apparatus (network node or entity) 90' (corresponding to the network node or entity 90) comprises a processor 211, a memory 212 and an interface 213, which are connected by a bus 214 or the like. The apparatus 10', 30', 50', 70', 90' may be connected via link 215 with another apparatus, e.g. another apparatus out of apparatuses 10', 30', 50', 70', 90', respectively. The processor 211 and / or the interface 213 may also include a modem or the like to facilitate communication over a (hardwire or wireless) link, respectively. The interface 213 may include a suitable transceiver coupled to one or more antennas or communication means for (hardwire or wireless) communications with the linked or connected device(s), respectively. The interface 213 is generally configured to communicate with at least one other apparatus, e.g., the interface thereof. In some example embodiments, the memory 212 may store respective programs assumed to include program instructions or computer program code that, when executed by the respective processor, cause the respective electronic device or apparatus to operate in accordance with any one or more of the example embodiments described herein. In some example embodiments, the memory 212 may store instructions that, when executed by the respective processor, cause the respective electronic device or apparatus to operate in accordance with any one or more of the example embodiments described herein. In general terms, the respective devices / apparatuses (and / or parts thereof) may represent means for performing respective operations and / or exhibiting respective functionalities, and / or the respective devices (and / or parts thereof) may have functions for performing respective operations and / or exhibiting respective functionalities. When in the subsequent description it is stated that the processor (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that at least one processor, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be equivalently implementable by specifically configured means for performing the respective function (e.g., the expression "processor 50 configured to [cause the apparatus to] perform xxx-ing" is construed to be equivalent to an expression such as "means for xxx-ing"). According to some example embodiments, an apparatus representing the network node 10 comprises at least one processor 211, at least one memory 212 including computer program code, and at least one interface 213 configured for communication with at least another apparatus. The processor (e.g., the at least one processor 211, with the at least one memory 212 and the computer program code) is configured to perform generating a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity ora second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule (thus the apparatus comprising corresponding means for generating), and to perform generating a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. According to some example embodiments, an apparatus representing the network node 30 comprises at least one processor 211, at least one memory 212 including computer program code, and at least one interface 213 configured for communication with at least another apparatus. The processor (e.g., the at least one processor 211, with the at least one memory 212 and the computer program code) is configured to perform receiving, from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header indicative of a packet destination from a packet detected according to said second detection rule, and wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule (thus the apparatus comprising corresponding means for receiving). According to some example embodiments, an apparatus representing the network node 50 comprises at least one processor 211, at least one memory 212 including computer program code, and at least one interface 213 configured for communication with at least another apparatus. The processor (e.g., the at least one processor 211, with the at least one memory 212 and the computer program code) is configured to perform receiving a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection 52 information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination (thus the apparatus comprising corresponding means for receiving). According to some example embodiments, an apparatus representing the network node 70 comprises at least one processor 211, at least one memory 212 including computer program code, and at least one interface 213 configured for communication with at least another apparatus. The processor (e.g., the at least one processor 211, with the at least one memory 212 and the computer program code) is configured to perform generating configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination (thus the apparatus comprising corresponding means for generating). According to some example embodiments, an apparatus representing the network node 90 comprises at least one processor 211, at least one memory 212 including computer program code, and at least one interface 213 configured for communication with at least another apparatus. The processor (e.g., the at least one processor 211, with the at least one memory 212 and the computer program code) is configured to perform generating proxy computation operation related information (thus the apparatus comprising corresponding means for generating), and to perform transmitting a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation (thus the apparatus comprising corresponding means for transmitting). For further details regarding the operability / functionality of the individual apparatuses, reference is made to the above description in connection with any one of FIGS. 1 to 20, respectively. For the purpose of the subject disclosure as described herein, it should be noted that - method steps likely to be implemented as software code portions and being run using a processor at a network server or network entity (as examples of devices, apparatuses and / or modules thereof, or as examples of entities including apparatuses and / or modules therefore), are software code independent and can be specified using any known or future developed programming language as long as the functionality defined by the method steps is preserved; - generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the example embodiments and its modification in terms of the functionality implemented; - method steps and / or devices, units or means likely to be implemented as hardware components at the above-defined apparatuses, or any module(s) thereof, (e.g., devices carrying out the functions of the apparatuses according to the embodiments as described above) are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components; - devices, units or means (e.g. the above-defined network entity or network register, or any one of their respective units / means) can be implemented as individual devices, units or means, but this does not exclude that they can be implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved; - an apparatus like the user equipment and the network entity / network register may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution / being run on a processor; - a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example. In general, it is to be noted that respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and / or software, respectively, if it is only adapted to perform the described functions of the respective parts. The mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device. Generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the subject disclosure. Devices and means can be implemented as individual devices, but this does not exclude that they can be implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person. Software in the sense of the subject description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means / portions or embodied in a signal or in a chip, potentially during processing thereof. The subject disclosure also covers any combination of method steps and operations described above, and any conceivable combination of nodes, apparatuses, modules or elements described above, as long as the abovedescribed concepts of methodology and structural arrangement are applicable. In view of the above, there are provided measures for enablement and control of distribution of compute operations in networks. Such measures may comprise generating a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, and generating a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. Even though the subject disclosure is described above with reference to its various example embodiments according to the accompanying drawings, it is to be understood that the subject disclosure is not restricted thereto. Rather, it is apparent to those skilled in the art that the subject disclosure can be modified in many ways without departing from the scope of the various example embodiments as disclosed herein. At least the following Items are covered by the above disclosure: Item 1. A method comprising generating a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, and generating a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. Item 2. The method according to Item 1, further comprising transmitting, towards a third local user plane function entity associated with said network entity providing said proxy computation operation, a request, said request including said first detection rule, said first action rule, said second detection rule, and said second action rule. Item 3. The method according to Item 2, further comprising selecting said third local user plane function entity based on a network access identifier of said network entity providing said proxy computation operation. Item 4. The method according to Item 3, further comprising receiving a proxy computation operation interconnection initiation message, said proxy computation operation interconnection initiation message including said network access identifier of said network entity providing said proxy computation operation and said information on traffic routing towards said network entity providing said proxy computation operation. Item 5. The method according to Item 4, wherein said network access identifier of said network entity providing said proxy computation operation is a data network access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is an edge application server network address of said network entity providing said proxy computation operation, or said proxy computation operation interconnection initiation message includes an Identifier of said proxy computation operation, and said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. Item 6. The method according to any of Items 1 to 5, further comprising specifying at least one of the following: said intermediate user plane function entity, or said first local user plane function entity, or said session anchor user plane function entity, or said second local user plane function entity, or said network entity providing said proxy computation operation. Item 7. A method comprising receiving, from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header indicative of a packet destination from a packet detected according to said second detection rule, and wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. Item 8. The method according to Item 7, further comprising transmitting an acknowledgement response. Item 9. The method according to Item 7 or 8, further comprising receiving a packet, matching said packet against at least one of the following: said first detection rule, or said second detection rule, applying said first action rule to said packet, if said packet matches with said first detection rule, and applying said second action rule to said packet, if said packet matches with said second detection rule. Item 10. The method according to Item 9, wherein in relation to said applying said first action rule to said packet, the method further comprises adding said first outer header to said packet, and forwarding said packet. Item 11. The method according to Item 9 or 10, wherein in relation to said applying said second action rule to said packet, the method further comprises removing said second outer header from said packet, and forwarding said packet. Item 12. The method according to any of Items 9 to 11, further comprising before applying any of said applying said first action rule and said second action rule to said packet, duplicating said packet as a duplicated packet, and forwarding said duplicated packet to an original destination of said packet. receiving a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. Item 14. The method according to Item 13, further comprising transmitting a configuration acknowledgement response. Item 15. The method according to Item 13 or 14, further comprising receiving a packet, matching said packet against said packet detection information, and processing said packet to a processed packet, if said packet matches with said packet detection information, wherein in relation to said processing said packet, the method further comprises removing said first outer header from said packet, performing said compute processing on said data of said packet, and adding said second outer header to said packet. Item 16. The method according to Item 15, further comprising transmitting said processed packet. generating configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. Item 18. The method according to Item 17, further comprising transmitting, towards a network entity providing said proxy computation operation, a configuration message, said configuration message including said configuration information. Item 19. The method according to Item 17 or 18, further comprising generating proxy computation operation related information, and transmitting a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of said proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. Item 20. The method according to Item 19, wherein said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said 62 proxy computation operation is a network address of said network entity providing said proxy computation operation. Item 21. A method comprising generating proxy computation operation related information, and transmitting a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. Item 22. The method according to Item 21, wherein said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. Item 23. An apparatus comprising generating circuitry configured to generate a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, and to generate a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. Item 24. The apparatus according to Item 23, further comprising transmitting circuitry configured to transmit, towards a third local user plane function entity associated with said network entity providing said proxy computation operation, a request, said request including said first detection rule, said first action rule, said second detection rule, and said second action rule. Item 25. The apparatus according to Item 24, further comprising selecting circuitry configured to select said third local user plane function entity based on a network access identifier of said network entity providing said proxy computation operation. Item 26. The apparatus according to Items 25, further comprising receiving circuitry configured to receive a proxy computation operation interconnection initiation message, said proxy computation operation interconnection initiation message including said network access identifier of said network entity providing said proxy computation operation and said information on traffic routing towards said network entity providing said proxy computation operation. Item 27. The apparatus according to Item 26, wherein said network access identifier of said network entity providing said proxy computation operation is a data network access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is an edge application server network address of said network entity providing said proxy computation operation, or said proxy computation operation interconnection initiation message includes an identifier of said proxy computation operation, and said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. Item 28. The apparatus according to any of Items 23 to 27, further comprising specifying circuitry configured to specify at least one of the following: said intermediate user plane function entity, or said first local user plane function entity, or said session anchor user plane function entity, or said second local user plane function entity, or said network entity providing said proxy computation operation. Item 29. An apparatus comprising receiving circuitry configured to receive, from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header indicative of a packet destination from a packet detected according to said second detection rule, and wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. Item 30. The apparatus according to Item 29, further comprising transmitting circuitry configured to transmit an acknowledgement response. Item 31. The apparatus according to Item 29 or 30, further comprising receiving circuitry configured to receive a packet, matching circuitry configured to match said packet against at least one of the following: said first detection rule, or said second detection rule, and applying circuitry configured to apply said first action rule to said packet, if said packet matches with said first detection rule, and to apply said second action rule to said packet, if said packet matches with said second detection rule. Item 32. The apparatus according to Item 31, further comprising adding circuitry configured to add said first outer header to said packet, and forwarding circuitry configured to forward said packet. Item 33. The apparatus according to Item 31 or 32, further comprising removing circuitry configured to remove said second outer header from said packet, and forwarding circuitry configured to forward said packet. Item 34. The apparatus according to any of Items 31 to 33, further comprising duplicating circuitry configured to, before applying any of said applying said first action rule and said second action rule to said packet, duplicate said packet as a duplicated packet, and forwarding circuitry configured to forward said duplicated packet to an original destination of said packet. Item 35. An apparatus comprising receiving circuitry configured to receive a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. Item 36. The apparatus according to Item 35, further comprising transmitting circuitry configured to transmit a configuration acknowledgement response. Item 37. The apparatus according to Item 35 or 36, further comprising receiving circuitry configured to receive a packet, matching circuitry configured to match said packet against said packet detection information, processing circuitry configured to process said packet to a processed packet, if said packet matches with said packet detection information, removing circuitry configured to remove said first outer header from said packet, performing circuitry configured to perform said compute processing on said data of said packet, and adding circuitry configured to add said second outer header to said packet. Item 38. The apparatus according to Item 37, further comprising transmitting circuitry configured to transmit said processed packet. Item 39. An apparatus comprising generating circuitry configured to generate configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. Item 40. The apparatus according to Item 39, further comprising transmitting circuitry configured to transmit, towards a network entity providing said proxy computation operation, a configuration message, said configuration message including said configuration information. Item 41. The apparatus according to Item 39 or 40, further comprising generating circuitry configured to generate proxy computation operation related information, and transmitting circuitry configured to transmit a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of said proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. Item 42. The apparatus according to Item 41, wherein said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. Item 43. An apparatus comprising generating circuitry configured to generate proxy computation operation related information, and transmitting circuitry configured to transmit a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. Item 44. The apparatus according to Item 43, wherein said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. Item 45. An apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: generating a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, and generating a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. Item 46. The apparatus according to Item 45, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: transmitting, towards a third local user plane function entity associated with said network entity providing said proxy computation operation, a request, said request including said first detection rule, said first action rule, said second detection rule, and said second action rule. Item 47. The apparatus according to Item 46, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: selecting said third local user plane function entity based on a network access identifier of said network entity providing said proxy computation operation. Item 48. The apparatus according to Item 47, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: receiving a proxy computation operation interconnection initiation message, said proxy computation operation interconnection initiation message including said network access identifier of said network entity providing said proxy computation operation and said information on traffic routing towards said network entity providing said proxy computation operation. Item 49. The apparatus according to Item 48, wherein said network access identifier of said network entity providing said proxy computation operation is a data network access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is an edge application server network address of said network entity providing said proxy computation operation, or said proxy computation operation interconnection initiation message includes an identifier of said proxy computation operation, and said network access identifier of said network entity providing said proxy computation operation is a local operation access Identifier, and said Information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. the instructions, when executed by the at least one processor, cause the apparatus at least to perform: specifying at least one of the following: said intermediate user plane function entity, or said first local user plane function entity, or said session anchor user plane function entity, or said second local user plane function entity, or said network entity providing said proxy computation operation. Item 51. An apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: receiving, from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header indicative of a packet destination from a packet detected according to said second detection rule, and wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. Item 52. The apparatus according to Item 51, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: transmitting an acknowledgement response. Item 53. The apparatus according to Item 51 or 52, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: receiving a packet, matching said packet against at least one of the following: said first detection rule, or said second detection rule, applying said first action rule to said packet, if said packet matches with said first detection rule, and applying said second action rule to said packet, if said packet matches with said second detection rule. Item 54. The apparatus according to Item 53, wherein in relation to said applying said first action rule to said packet, the instructions, when executed by the at least one processor, cause the apparatus at least to perform: adding said first outer header to said packet, and forwarding said packet. Item 55. The apparatus according to Item 53 or 54, wherein in relation to said applying said second action rule to said packet, the instructions, when executed by the at least one processor, cause the apparatus at least to perform: removing said second outer header from said packet, and forwarding said packet. the instructions, when executed by the at least one processor, cause the apparatus at least to perform: before applying any of said applying said first action rule and said second action rule to said packet, duplicating said packet as a duplicated packet, and forwarding said duplicated packet to an original destination of said packet. Item 57. An apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: receiving a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. Item 58. The apparatus according to Item 57, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: transmitting a configuration acknowledgement response. Item 59. The apparatus according to Item 57 or 58, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: receiving a packet, matching said packet against said packet detection information, and processing said packet to a processed packet, if said packet matches with said packet detection information, wherein in relation to said processing said packet, the instructions, when executed by the at least one processor, cause the apparatus at least to perform: removing said first outer header from said packet, performing said compute processing on said data of said packet, and adding said second outer header to said packet. Item 60. The apparatus according to Item 59, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: transmitting said processed packet. Item 61. An apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: generating configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing Information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. Item 62. The apparatus according to Item 61, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: transmitting, towards a network entity providing said proxy computation operation, a configuration message, said configuration message including said configuration information. Item 63. The apparatus according to Item 61 or 62, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: generating proxy computation operation related information, and transmitting a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of said proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. Item 64. The apparatus according to Item 63, wherein said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. Item 65. An apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: generating proxy computation operation related information, and transmitting a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. Item 66. The apparatus according to Item 65, wherein said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. Item 67. An apparatus comprising means for generating a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, and means for generating a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. Item 68. The apparatus according to Item 67, further comprising means for transmitting, towards a third local user plane function entity associated with said network entity providing said proxy computation operation, a request, said request including said first detection rule, said first action rule, said second detection rule, and said second action rule. Item 69. The apparatus according to Item 68, further comprising means for selecting said third local user plane function entity based on a network access identifier of said network entity providing said proxy computation operation. Item 70. The apparatus according to Item 69, further comprising means for receiving a proxy computation operation interconnection initiation message, said proxy computation operation interconnection initiation message including said network access identifier of said network entity providing said proxy computation operation and said information on traffic routing towards said network entity providing said proxy computation operation. Item 71. The apparatus according to Item 70, wherein said network access identifier of said network entity providing said proxy computation operation is a data network access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is an edge application server network address of said network entity providing said proxy computation operation, or said proxy computation operation interconnection initiation message includes an identifier of said proxy computation operation, and said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. Item 72. The apparatus according to any of Items 67 to 71, further comprising means for specifying at least one of the following: said intermediate user plane function entity, or said first local user plane function entity, or said session anchor user plane function entity, or said second local user plane function entity, or said network entity providing said proxy computation operation. Item 73. An apparatus comprising means for receiving, from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header indicative of a packet destination from a packet detected according to said second detection rule, and wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule. Item 74. The apparatus according to Item 73, further comprising means for transmitting an acknowledgement response. Item 75. The apparatus according to Item 73 or 74, further comprising means for receiving a packet, means for matching said packet against at least one of the following: said first detection rule, or said second detection rule, means for applying said first action rule to said packet, if said packet matches with said first detection rule, and means for applying said second action rule to said packet, if said packet matches with said second detection rule. Item 76. The apparatus according to Item 75, further comprising means for adding said first outer header to said packet, and means for forwarding said packet. Item 77. The apparatus according to Item 75 or 76, further comprising means for removing said second outer header from said packet, and means for forwarding said packet. Item 78. The apparatus according to any of Items 75 to 77, further comprising means for duplicating, before applying any of said applying said first action rule and said second action rule to said packet, said packet as a duplicated packet, and means for forwarding said duplicated packet to an original destination of said packet. Item 79. An apparatus comprising means for receiving a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. Item 80. The apparatus according to Item 79, further comprising means for transmitting a configuration acknowledgement response. Item 81. The apparatus according to Item 79 or 80, further comprising means for receiving a packet, means for matching said packet against said packet detection information, and means for processing said packet to a processed packet, if said packet matches with said packet detection information, means for removing said first outer header from said packet, means for performing said compute processing on said data of said packet, and means for adding said second outer header to said packet. Item 82. The apparatus according to Item 81, further comprising means for transmitting said processed packet. Item 83. An apparatus comprising means for generating configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information, wherein said packet detection information defines detection of packets received from a local user plane function entity, said packet processing information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and wherein said packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination. Item 84. The apparatus according to Item 83, further comprising means for transmitting, towards a network entity providing said proxy computation operation, a configuration message, said configuration message including said configuration information. Item 85. The apparatus according to Item 83 or 84, further comprising means for generating proxy computation operation related information, and means for transmitting a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of said proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. Item 86. The apparatus according to Item 85, wherein said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. Item 87. An apparatus comprising means for generating proxy computation operation related information, and means for transmitting a request message including said proxy computation operation related information, wherein said proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation. Item 88. The apparatus according to Item 87, wherein said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation. Item 89. A computer program product comprising computer-executable computer program code which, when the program is run on a computer, is configured to cause the computer to carry out the method according to any one of Items 1 to 6, 7 to 12, 13 to 16, 17 to 20, or 21 to 22. Item 90. The computer program product according to Item 89, wherein the computer program product comprises a computer-readable medium on which the computer-executable computer program code is stored, and / or wherein the program Is directly loadable into an internal memory of the computer or a processor thereof. List of acronyms and abbreviations 3GPP Third Generation Partnership Project 5GC 5G core 5GS 5G system AF application function AMF access management function BP branch point CAN computing-aware networking CATS computing-aware traffic steering CF computing function CHF charging function CU center (centralized) unit DN data network DNAI data network access identifier DU distributed unit EC edge cloud FAR forwarding action rule INC integration of network and computing I-UPF intermediate user plane function I-SMF intermediate session management function LOAI local operation access identifier NAS non-access stratum NEF network exposure function PCC policy and charging control PCF policy control and charging function PDR packet detection rule PDU protocol data unit PSA PDU session anchor RAN radio access network RU radio unit SMF session management function UE user equipment ULCL uplink classifier UPF user plane function

Claims

1. An apparatus comprisingmeans for generating a first detection rule and a first action rule associated with said first detection rule, wherein said first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity or a second local user plane function entity, wherein said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule, andmeans for generating a second detection rule and a second action rule associated with said second detection rule, wherein said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header from a packet detected according to said second detection rule, wherein said second action rule pertains to forwarding of said packet detected according to said second detection rule.

2. The apparatus according to claim 1, further comprisingmeans for transmitting, towards a third local user plane function entity associated with said network entity providing said proxy computation operation, a request, said request including said first detection rule, said first action rule, said second detection rule, and said second action rule.

3. The apparatus according to claim 2, further comprisingmeans for selecting said third local user plane function entity based on a network access identifier of said network entity providing said proxy computation operation.

4. The apparatus according to claim 3, further comprisingmeans for receiving a proxy computation operation interconnection initiation message, said proxy computation operation interconnection initiation message including said network access identifier of said network entity providing said proxy computation operation and said information on traffic routing towards said network entity providing said proxy computation operation.

5. The apparatus according to claim 4, whereinsaid network access identifier of said network entity providing said proxy computation operation is a data network access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is an edge application server network address of said network entity providing said proxy computation operation, orsaid proxy computation operation interconnection initiation message includes an identifier of said proxy computation operation, and said network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation.

6. The apparatus according to any of claims 1 to 5, further comprising means for specifying at least one of the following:said intermediate user plane function entity, orsaid first local user plane function entity, orsaid session anchor user plane function entity, orsaid second local user plane function entity, orsaid network entity providing said proxy computation operation.

7. An apparatus comprisingmeans for receiving, from a session management function entity, a request, said request including a first detection rule, a first action rule associated with said first detection rule, a second detection rule, and a second action rule associated with said second detection rule, whereinsaid first detection rule pertains to detection of uplink packets received from an intermediate user plane function entity or a first local user plane function entity and / or detection of downlink packets received from a session anchor user plane function entity ora second local user plane function entity, said first action rule pertains to addition of a first outer header to a packet detected according to said first detection rule, said first outer header including information on traffic routing towards a network entity providing a proxy computation operation, and wherein said first action rule further pertains to forwarding of said packet detected according to said first detection rule,said second detection rule pertains to detection of packets received from said network entity providing said proxy computation operation and removal of a second outer header indicative of a packet destination from a packet detected according to said second detection rule, and whereinsaid second action rule pertains to forwarding of said packet detected according to said second detection rule.

8. The apparatus according to claim 7, further comprisingmeans for transmitting an acknowledgement response.

9. The apparatus according to claim 7 or 8, further comprisingmeans for receiving a packet,means for matching said packet against at least one of the following:said first detection rule, or said second detection rule,means for applying said first action rule to said packet, if said packet matches with said first detection rule, andmeans for applying said second action rule to said packet, if said packet matches with said second detection rule.

10. The apparatus according to claim 9, further comprising means for adding said first outer header to said packet, and means for forwarding said packet.

11. The apparatus according to claim 9 or 10, further comprising means for removing said second outer header from said packet, and means for forwarding said packet.

12. The apparatus according to any of claims 9 to 11, further comprising means for duplicating, before applying any of said applying said first action rule and said second action rule to said packet, said packet as a duplicated packet, andmeans for forwarding said duplicated packet to an original destination of said packet.

13. An apparatus comprisingmeans for receiving a configuration message, said configuration message including packet detection information, packet processing information, and packet forwarding information, whereinsaid packet detection information defines detection of packets received from a local user plane function entity,said packet processing information defines removal of a first outer header indicative of a packet destination from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and whereinsaid packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination.

14. The apparatus according to claim 13, further comprisingmeans for transmitting a configuration acknowledgement response.

15. The apparatus according to claim 13 or 14, further comprisingmeans for receiving a packet,means for matching said packet against said packet detection information, andmeans for processing said packet to a processed packet, if said packet matches with said packet detection information,means for removing said first outer header from said packet,means for performing said compute processing on said data of said packet, andmeans for adding said second outer header to said packet.

16. The apparatus according to claim 15, further comprisingmeans for transmitting said processed packet.

17. An apparatus comprisingmeans for generating configuration information related to a proxy computation operation, said configuration information including packet detection information, packet processing information, and packet forwarding information, whereinsaid packet detection information defines detection of packets received from a local user plane function entity,said packet processing information defines removal of a first outer header from a packet detected according to said packet detection information and compute processing to be performed on data of said packet, and whereinsaid packet forwarding information defines addition of a second outer header to said packet, said second outer header being indicative of said local user plane function entity as a destination.

18. The apparatus according to claim 17, further comprisingmeans for transmitting, towards a network entity providing said proxy computation operation, a configuration message, said configuration message including said configuration information.

19. The apparatus according to claim 17 or 18, further comprisingmeans for generating proxy computation operation related information, andmeans for transmitting a request message including said proxy computation operation related information, whereinsaid proxy computation operation related information includes an identifier of said proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation.

20. The apparatus according to claim 19, whereinsaid network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation.

21. An apparatus comprisingmeans for generating proxy computation operation related information, andmeans for transmitting a request message including said proxy computation operation related information, whereinsaid proxy computation operation related information includes an identifier of a proxy computation operation, a network access identifier of a network entity providing said proxy computation operation, and information on traffic routing towards said network entity providing said proxy computation operation.

22. The apparatus according to claim 21, whereinsaid network access identifier of said network entity providing said proxy computation operation is a local operation access identifier, and said5 information on traffic routing towards said network entity providing said proxy computation operation is a network address of said network entity providing said proxy computation operation.91

Images