Distributed enablement and control of computing operations in network

Abstract

There are provided measures for enabling and controlling the distribution of computing operations in a network. The measures exemplarily include generating a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane functional entity or a first local user plane functional entity and / or detecting a downlink packet received from a session anchor user plane functional entity or a second local user plane functional entity, wherein the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header comprising information about traffic routing to a network entity providing a proxy computing operation, and wherein the first action rule further involves forwarding a packet detected according to the first detection rule, and generating a second detection rule and a second action rule associated with the second detection rule, where the second detection rule involves detecting a packet received from a network entity providing a proxy computing operation and removing a second external header from the packet detected according to the second detection rule, wherein the second action rule involves forwarding packets detected according to the second detection rule.

Description

Technical Field

[0001] Various example embodiments of the subject disclosure relate to enabling and controlling the distribution of computing operations in a network. More specifically, various example embodiments relate to measures (including methods, apparatus, and computer program products) for enabling and controlling the distribution of computing operations in a network. Background Art

[0002] A communication system can be viewed as a facility that enables communication sessions between two or more entities (eg, communication devices, base stations, and / or other nodes) by providing carrier waves between the entities involved in the communication path.

[0003] The communication system may be a wireless communication system. Examples of wireless systems include public land mobile networks (PLMNs) operating based on radio standards (e.g., standards provided by 3GPP), satellite-based communication systems, and different wireless local networks. The wireless local network may, for example, be implemented as a wireless local area network (WLAN). Wireless systems may typically be divided into cells and are therefore often referred to as cellular systems.

[0004] Communication systems and associated equipment typically operate in accordance with a given standard or specification, which specifies what the various entities associated with the system are allowed to do and how it should be achieved. Communication protocols and / or parameters applied to the connection are also typically defined. An example of a set of standards is the so-called 5G standard. Summary of the invention

[0005] Various example embodiments are intended to address at least some of the problems and / or issues and disadvantages explicitly described herein or otherwise apparent to one skilled in the relevant art.

[0006] Several aspects of various example embodiments are detailed below.

[0007] According to one aspect, a method is provided, comprising generating a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane functional entity or a first local user plane functional entity and / or detecting a downlink packet received from a session anchor user plane functional entity or a second local user plane functional entity, wherein the first action rule involves adding a first external header to the packet detected according to the first detection rule, the first external header including information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule, and generating a second detection rule and a second action rule associated with the second detection rule, wherein the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header from the packet detected according to the second detection rule, and wherein the second action rule involves forwarding the packet detected according to the second detection rule.

[0008] According to one aspect, a method is provided, comprising receiving a request from a session management function entity, the request comprising a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header comprising information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule, the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header indicating a packet destination from the packet detected according to the second detection rule, and wherein the second action rule involves forwarding the packet detected according to the second detection rule.

[0009] According to one aspect, a method is provided, comprising receiving a configuration message, the configuration message comprising packet detection information, packet processing information and packet forwarding information, wherein the packet detection information defines detecting a packet received from a local user plane function entity, the packet processing information defines removing a first external header indicating a packet destination from a packet detected according to the packet detection information and a computational processing to be performed on data of the packet, and wherein the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane function entity as a destination.

[0010] According to one aspect, a method is provided, comprising generating configuration information related to a proxy computing operation, the configuration information comprising packet detection information, packet processing information, and packet forwarding information, wherein the packet detection information defines detecting a packet received from a local user plane function entity, the packet processing information defines removing a first external header from a packet detected according to the packet detection information and computing processing to be performed on data of the packet, and wherein the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane function entity as a destination.

[0011] According to one aspect, a method is provided, comprising generating information related to a proxy computing operation, and sending a request message including the information related to the proxy computing operation, wherein the information related to the proxy computing operation comprises an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about service routing to the network entity providing the proxy computing operation.

[0012] According to one aspect, a device is provided, comprising a generating circuit, which is configured to generate a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, wherein the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header including information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule, and generating a second detection rule and a second action rule associated with the second detection rule, wherein the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header from the packet detected according to the second detection rule, wherein the second action rule involves forwarding the packet detected according to the second detection rule.

[0013] According to one aspect, an apparatus is provided, comprising a receiving circuit configured to receive a request from a session management function entity, the request comprising a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header comprising information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule, the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header indicating a packet destination from the packet detected according to the second detection rule, and wherein the second action rule involves forwarding the packet detected according to the second detection rule.

[0014] According to one aspect, an apparatus is provided, comprising a receiving circuit, the receiving circuit being configured to receive a configuration message, the configuration message comprising packet detection information, packet processing information, and packet forwarding information, wherein the packet detection information defines detecting a packet received from a local user plane function entity, the packet processing information defines removing a first external header indicating a packet destination from a packet detected according to the packet detection information and a computational processing to be performed on data of the packet, and wherein the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane function entity as a destination.

[0015] According to one aspect, an apparatus is provided, comprising a generating circuit, the generating circuit being configured to generate configuration information related to a proxy computing operation, the configuration information comprising packet detection information, packet processing information, and packet forwarding information, wherein the packet detection information defines detecting a packet received from a local user plane function entity, the packet processing information defines removing a first external header from a packet detected according to the packet detection information and computing processing to be performed on data of the packet, and wherein the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane function entity as a destination.

[0016] According to one aspect, a device is provided, comprising a generating circuit configured to generate information related to a proxy computing operation, and a sending circuit configured to send a request message including the information related to the proxy computing operation, wherein the information related to the proxy computing operation includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about service routing to the network entity providing the proxy computing operation.

[0017] According to one aspect, a device is provided, comprising at least one processor and at least one memory, the memory storing instructions, which when executed by the at least one processor cause the device to at least perform generating a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, wherein the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header comprising information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule, and generating a second detection rule and a second action rule associated with the second detection rule, wherein the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header from the packet detected according to the second detection rule, wherein the second action rule involves forwarding the packet detected according to the second detection rule.

[0018] According to one aspect, an apparatus is provided, comprising at least one processor and at least one memory, the memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least perform receiving a request from a session management function entity, the request comprising a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header comprising information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule, the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header indicating a packet destination from the packet detected according to the second detection rule, and wherein the second action rule involves forwarding the packet detected according to the second detection rule.

[0019] According to one aspect, a device is provided, comprising at least one processor and at least one memory, wherein the memory stores instructions, which, when executed by the at least one processor, cause the device to at least perform receiving a configuration message, the configuration message comprising packet detection information, packet processing information, and packet forwarding information, wherein the packet detection information defines detecting a packet received from a local user plane function entity, the packet processing information defines removing a first external header indicating a packet destination from a packet detected according to the packet detection information and a computational processing to be performed on data of the packet, and wherein the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane function entity as a destination.

[0020] According to one aspect, a device is provided, comprising at least one processor and at least one memory, wherein the memory stores instructions, which, when executed by the at least one processor, cause the device to at least perform generation of configuration information related to a proxy computing operation, wherein the configuration information comprises packet detection information, packet processing information, and packet forwarding information, wherein the packet detection information defines detection of a packet received from a local user plane function entity, the packet processing information defines removal of a first external header from a packet detected according to the packet detection information and computing processing to be performed on data of the packet, and wherein the packet forwarding information defines adding a second external header to the packet, wherein the second external header indicates the local user plane function entity as a destination.

[0021] According to one aspect, a device is provided, comprising at least one processor and at least one memory, wherein the memory stores instructions, which, when executed by the at least one processor, cause the device to at least generate information related to a proxy computing operation and send a request message including the information related to the proxy computing operation, wherein the information related to the proxy computing operation includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about service routing to the network entity providing the proxy computing operation.

[0022] According to one aspect, a device is provided, comprising means for generating a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane functional entity or a first local user plane functional entity and / or detecting a downlink packet received from a session anchor user plane functional entity or a second local user plane functional entity, wherein the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header comprising information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule, and means for generating a second detection rule and a second action rule associated with the second detection rule, wherein the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header from the packet detected according to the second detection rule, wherein the second action rule involves forwarding the packet detected according to the second detection rule.

[0023] According to one aspect, an apparatus is provided, comprising a component for receiving a request from a session management function entity, the request comprising a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header comprising information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule, the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header indicating a packet destination from the packet detected according to the second detection rule, and wherein the second action rule involves forwarding the packet detected according to the second detection rule.

[0024] According to one aspect, an apparatus is provided, comprising means for receiving a configuration message, the configuration message comprising packet detection information, packet processing information and packet forwarding information, wherein the packet detection information defines detecting a packet received from a local user plane function entity, the packet processing information defines removing a first external header indicating a packet destination from a packet detected according to the packet detection information and a computational processing to be performed on data of the packet, and wherein the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane function entity as a destination.

[0025] According to one aspect, an apparatus is provided, comprising a component for generating configuration information related to a proxy computing operation, the configuration information comprising packet detection information, packet processing information, and packet forwarding information, wherein the packet detection information defines detecting a packet received from a local user plane function entity, the packet processing information defines removing a first external header from a packet detected according to the packet detection information and computing processing to be performed on data of the packet, and wherein the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane function entity as a destination.

[0026] According to one aspect, an apparatus is provided, comprising a component for generating information related to a proxy computing operation, and a component for sending a request message including the information related to the proxy computing operation, wherein the information related to the proxy computing operation includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about service routing to the network entity providing the proxy computing operation.

[0027] According to one aspect, a computer program product is provided, comprising a computer executable computer program code, which, when executed on a computer (e.g., a computer of a device according to any one of the above-mentioned exemplary aspects related to the device of the present disclosure), is configured to cause the computer to execute a method according to any one of the above-mentioned exemplary aspects related to the method of the present disclosure.

[0028] Such a computer program product may include (or be embodied as) a (tangible) computer-readable (storage) medium or the like on which a computer-executable computer program code is stored, and / or the program may be directly loaded into the internal memory of the computer or its processor.

[0029] Any of the above aspects or other aspects described herein can effectively enable and control the distribution of computing operations in a network, thereby solving at least part of the difficulties and / or problems and shortcomings described herein or otherwise apparent to technicians in the relevant field in view of the present subject disclosure.

[0030] In some example embodiments, enabling and controlling the distribution of computing operations in a network is provided. More specifically, measures and mechanisms are provided for achieving enabling and controlling the distribution of computing operations in a network.

[0031] Thus, improvements may be achieved through methods, apparatus, and computer program products that enable / implement the enabling and control of distribution of computing operations in a network. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In the following, some example embodiments will be described in more detail by way of non-limiting and illustrative examples with reference to the accompanying drawings, in which:

[0033] Figure 1 is a block diagram illustrating an apparatus according to some example embodiments,

[0034] Figure 2 is a block diagram illustrating an apparatus according to some example embodiments,

[0035] Figure 3 is a block diagram illustrating an apparatus according to some example embodiments,

[0036] Figure 4 is a block diagram illustrating an apparatus according to some example embodiments,

[0037] Figure 5 is a block diagram illustrating an apparatus according to some example embodiments,

[0038] Figure 6 is a block diagram illustrating an apparatus according to some example embodiments,

[0039] Figure 7 is a block diagram illustrating an apparatus according to some example embodiments,

[0040] Figure 8 is a block diagram illustrating an apparatus according to some example embodiments,

[0041] Fig. 9 is a block diagram illustrating an apparatus according to some example embodiments,

[0042] Fig.10 is a schematic diagram of a process according to some example embodiments,

[0043] Fig.11 is a schematic diagram of a process according to some example embodiments,

[0044] Fig.12 is a schematic diagram of a process according to some example embodiments,

[0045] Fig.13 is a schematic diagram of a process according to some example embodiments,

[0046] Fig.14 is a schematic diagram of a process according to some example embodiments,

[0047] Fig.15 A schematic diagram showing an example of a system environment with signaling variants,

[0048] Fig.16 A schematic diagram showing an example of a system environment with signaling variants according to some example embodiments,

[0049] Fig.17 shows a schematic diagram of a signaling sequence according to some example embodiments,

[0050] Fig.18 A schematic diagram showing an example of a system environment with signaling variants according to some example embodiments,

[0051] Fig.19 shows a schematic diagram of a signaling sequence according to some example embodiments,

[0052] Fig. 20 A schematic diagram showing a signaling sequence according to some example embodiments, and

[0053] Fig.21 is a block diagram alternatively illustrating an apparatus according to some example embodiments. DETAILED DESCRIPTION

[0054] The subject disclosure is described herein with reference to specific non-limiting and illustrative examples. It will be appreciated by those skilled in the art that the subject disclosure is by no means limited to these examples and can be applied more broadly.

[0055] It should be noted that the subject disclosure and its various example embodiments relate to specifications used as non-limiting and illustrative examples of certain network configurations and deployments. That is, the subject disclosure and its various example embodiments are described in relation to 3GPP specifications used as non-limiting and illustrative examples of certain network configurations and deployments. Therefore, the description of such example embodiments provided herein particularly relates to terms directly related thereto. Such terms are used only in the context of non-limiting and illustrative examples and are not intended to limit the subject disclosure in any way. Instead, any other communication or communication-related system deployment, etc., may also be used.

[0056] Hereinafter, various exemplary embodiments and implementations of the subject disclosure and its various aspects are described using several variants and / or alternatives. It is generally noted that, subject to certain constraints, all of the variants and / or alternatives may be provided individually or in any combination (including combinations of individual features of the various variants and / or alternatives).

[0057] As used herein, “at least one of: ” and “at least one of ” and similar expressions, where a list of two or more elements is connected by “and” or “or”, mean at least any one element, or at least any two or more elements, or at least all elements.

[0058] The subject disclosure relates generally to the distribution of computing operations in a network, and more particularly to enabling in-network computing associated with applications in a 5th generation (5G) system (5GS) user plane (UP). As further detailed herein, one or more challenges may arise because traffic flow control sufficient to allow distributed computing operations is not specified. Therefore, enabling and controlling the distribution of computing operations in a network may provide advantages and improvements for certain use cases.

[0059] According to some example embodiments, measures and mechanisms are provided for (enabling / implementing) enabling and controlling the distribution of computing operations in a network.

[0060] Due to performance, data privacy, or network efficiency requirements, complex computing tasks can be split into several smaller computing operations, each of which can be executed on a different computing node in the network.

[0061] Executing one or more computing operations within the mobile network operator's domain helps to exploit the edge-cloud continuum, e.g., the availability of specific computing capabilities in different parts of the network (far edge, edge, aggregation, central cloud).

[0062] On the one hand, there are already some use cases that use a set or sequence of computing operations to complete a task. One example is artificial intelligence (AI) / machine learning (ML) model splitting. Here, the process related to the AI / ML model is split into two or more computing operations, which are performed by the user equipment (UE) and the network nodes in the network, thereby reducing resource consumption on the UE side, such as computing power and energy.

[0063] Another example is combinatorial learning. Multiple computing tasks can be combined into a computing chain / graph, with each task as a computing operation to reuse the processed intermediate data. In addition, due to hardware requirements or data privacy, sensitive data or intermediate results can only be processed on a given host or in a specific region. Furthermore, the computing operation processing of sensitive data or intermediate results is limited to being deployed on a given host or in the required region.

[0064] On the other hand, many activities related to the design of sixth generation (6G) networks consider computational metrics to enhance, for example, routing decisions. In the context of network and computing integration (INC), the best application service instance to host computing operations can be selected. Traffic steering based on computational metrics is being studied in the IETF WG Computing-Aware Networking (CAN), later renamed computing-aware traffic steering (CATS). As a further development of the current research activities, data should be computed / processed not only on a single cloud node, but also on multiple nodes in a parallel or sequential manner, such as distributed / ubiquitous computing. This means that in the case of selecting service instances for INC or traffic steering for CAN / CATS, the edge node should not be the final destination of the data traffic. The packet data should / can be first computed on one or more local clouds with specific capabilities / hardware support, and then the mobile network user plane (UP) can further process the packet data (e.g., packet routing, lawful interception, etc.) in the same protocol data unit (PDU) session.

[0065] There are already multiple studies and standards that involve directing traffic to a local cloud hosting compute operations through an intermediate user plane function (I-UPF) or to a central / remote data network (DN) through one or more user plane functions (UPFs).

[0066] Fig.15 A schematic diagram showing an example of a system environment with signaling variants, in particular showing N6 and N9 class connections defined by the 3rd Generation Partnership Project (3GPP) and connections over a public network.

[0067] Specifically, Fig.15 The computing operations on the UP and the local cloud related to the known edge computing reference architecture are shown in FIG. The local cloud can be a local server or edge server controlled by a third party / network operator.

[0068] Based on the current 5G System (5GS) architecture defined by 3GPP, two types of connections may exist in a PDU session.

[0069] 1.) Class N6 connection ( Fig.15 The dash in the figure): The local (PDU Session Anchor (PSA)) UPF acts as a PSAUPF to the local cloud so that business data can be routed to the computing operations deployed on the local cloud. However, after the data is calculated by the computing operations, the data cannot be further forwarded to the (central) data network (DN) through the PSA UPF because there is no definition of a connection from the local cloud to the DN through the UP.

[0070] 2.) Class N9 connection ( Fig.15 The local (PSA) UPF forms a UPF chain together with the intermediate UPF (I-UPF) and the PSA UPF so that the business data can be routed to the DN. However, the data cannot be redirected to the computational operations near the local (PSA) UPF for computation first, but can only be forwarded directly to the (central) DN.

[0071] Available through the public network ( Fig.15 The dot-dash line in the figure) (e.g., the Internet) is used for traffic routing. However, the public network is not controlled by the network operator, and UPF functions cannot be applied on this path, for example, they must be applied before sending the traffic to local / edge computing operations (e.g., lawful interception, quality of service (QoS) enforcement, traffic usage reporting, and downlink (DL) buffering), as well as the functions of anchor points that may not support UE mobility and session and service continuity (SSC). This may result in transmission failures, lack of QoS guarantees, etc.

[0072] Fig.16 A schematic diagram showing an example of a system environment with signaling variants according to some example embodiments, and in particular showing the connection between a local cloud and a DN to route traffic through a user plane.

[0073] That is, according to some example embodiments, at least the following aspects are solved and effects are achieved.

[0074] 1.) How to support routing of UE application services to the local DN and further to the cloud server located in the central DN.

[0075] 2.) How to direct UE application traffic (eg UL traffic) to a local (processing) server to allow local processing of the data / traffic before sending to the final destination server.

[0076] 3.) How to direct DL traffic related to a specific application (from the corresponding application server in the DN) and destined for the UE to be routed through the local (processing) application server first.

[0077] 4.) How trusted and / or untrusted third-party application functions (AFs) can impact the local processing of specific application traffic.

[0078] Specifically, some example embodiments aim to route traffic between local / edge computing operations and (central) DNs via the 5GS user plane to enable application-related in-network computing in mobile networks.

[0079] There is no mechanism defined in 3GPP that allows application-dependent local / edge computing operations located outside the management domain of the Mobile Network Operator (MNO) (e.g., on edge cloud nodes) to be integrated into the user plane path of the mobile (core) network, see Fig.16 More specifically, while the current 3GPP specifications allow local access to a DN or edge application server (EAS), for example, a PDU session is anchored and terminated when accessing a DN "locally", there is no way to direct the service to such a local computing node, and after completing the computing task (e.g., "local computing operation"), send the service back to the core network user plane, towards the central UPF or PSA UPF (where the remaining mobile network UP processing will preferably be performed), and further towards the "central" access to the DN.

[0080] Thus, in short, according to some example embodiments, UE UL and DL application traffic can be directed to be first processed locally (e.g., on an application server or edge application server controlled by a public land mobile network (PLMN) or deployed by a trusted third party) and then directed to a central application server (or in the case of DL traffic to the UE, e.g., first to a central application server and then to a local application server), thereby ensuring the desired QoS.

[0081] The mentioned application may be, for example, video analysis services from business / camera surveillance.

[0082] This involves a method for "interconnecting local / edge computing operations with (central) DN via a user plane" to enable application-related in-network computing in the 5GS user plane, for example, a method for routing traffic between a local cloud and a DN via the user plane of an operator network.

[0083] Using methods and means according to some example embodiments, data packets are encapsulated by a local (PSA) UPF together with routing information for local / edge computing operations to perform computing operations on local / edge servers, and are (re)encapsulated by a local (PSA) UPF together with a GTP-U header to continue user plane forwarding after the local / edge computing operations are performed.

[0084] Some example embodiments particularly address interconnection in Fig.16 Indicated by dashed lines.

[0085] A local cloud is a server located at the edge of the network. It can be a local server owned by a network operator or a local server controlled by a trusted third party, on which computing operations are deployed. Therefore, computing operations deployed on local servers are labeled as local computing operations.

[0086] The local cloud can also be a conventional edge server on which edge applications acting as computing operations are deployed. Therefore, the computing operations deployed on the edge servers are marked as edge computing operations.

[0087] Therefore, some example embodiments may be viewed as focusing on two scenarios:

[0088] Scenario 1): interconnecting local computing operations deployed on a local server deployed by the PLMN or a trusted third party through a user plane path with the DN through the user plane; and

[0089] Scenario 2): The edge computing operations on the edge server are interconnected with the DN through the user plane.

[0090] According to some example embodiments, particularly in relation to scenario 1, an application function (AF) based on its internal trigger generates and provides information to the 5GC to enable identification of local computing operations for specific edge services or applications. According to some example embodiments, the information includes a local operation access identifier (LOAI) and routing information for the local computing operation. The information is then stored in a database repository, such as a unified data management (UDM) / unified data repository (UDR), and then provided to the SMF, for example, through PCC rules.

[0091] According to some example embodiments, particularly in relation to scenarios 1 and 2, based on the received information provided by the AF, the SMF and / or the intermediate SMF (I-SMF) generates new packet detection rules (PDRs) and forwarding action rules (FARs). According to some example embodiments, the SMF then configures these PDRs and FARs to the local (PSA) UPF via, for example, the N4 interface. In addition, according to some example embodiments, the configuration context of local / edge computing operations related to packet processing and security is defined by the computing operations controller ( Fig.19 16 in the previous step).

[0092] According to some example embodiments, particularly in relation to scenarios 1 and 2, a traffic routing process is provided that is jointly performed by a local (PSA) UPF and a local / edge computing operation. Based on the received PDR and FAR provided by the SMF and / or I-SMF, the local (PSA) UPF forwards the matching packets to the local / edge computing operation instead of forwarding them to the central DN ( Fig. 20 In addition, the local / edge compute operation forwards the computed packets back to the local (PSA) UPF ( Fig. 20 According to some example embodiments, the local (PSA) UPF then forwards the calculated / processed packet to the central DN ( Fig. 20or forwarded to the UE in the case of DL traffic.

[0093] As described herein, the terms “local cloud” and “DN” refer to “local DN” and “central DN” respectively, and “computing operation” refers to “APP service” in certain contexts.

[0094] In the absence of a connection between the local cloud and the "central" DN via the operator's network, according to some example embodiments, the interconnection method of the user plane via the operator's network is to support further mobile UP processing after performing local computing operations related to the application. With this interconnection method according to some example embodiments, the following service routing can be advantageously achieved:

[0095] -The UL traffic related to the application is first routed to the local / edge computing operation hosted on the local / edge server, and then further routed to other computing operations in another local cloud or DN. Optionally, when routing to the local / edge computing operation, the UL traffic can also be replicated by the local (PSA) UPF to be anchored to the PSA UPF at the same time.

[0096] -DL traffic related to applications entering the 5GS from the "central" DN via N6 is first routed to the local / edge computing operation in the local / edge server for local computation before being forwarded to the UE (within the same PDU session). In some example embodiments, when routing to the local / edge computing operation, the DL traffic may also be selectively replicated by the local (PSA) UPF for simultaneous forwarding to the UE.

[0097] Although the methods and components are intended for both UL and DL traffic, the methods and components according to some example embodiments may also be flexibly used for only UL or DL ​​traffic.

[0098] Some example embodiments are described in more detail below.

[0099] Figure 1is 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 generation circuit 11. In some example embodiments, the apparatus may be configured to operate as a session management function (intermediate session management function) entity. For example, the apparatus may be configured to perform one or more functions of a session management function (intermediate session management function) entity. The generation circuit 11 generates a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, wherein the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header including information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule. The generation circuit 11 (or another generation circuit) generates a second detection rule and a second action rule associated with the second detection rule, wherein the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second outer header from the packet detected according to the second detection rule, wherein the second action rule involves forwarding the packet detected according to the second detection rule. Fig.10 is a schematic diagram of a process according to some example embodiments. Figure 1 The device can perform Fig.10 method, but not limited to this method. Fig.10 The method can be Figure 1 The present invention is performed by a device, but is not limited to being performed by the device.

[0100] like Fig.10As shown, a process according to some example embodiments includes the operation of generating (S101) a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, wherein the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header including information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule, and the operation of generating a second detection rule and a second action rule associated with the second detection rule, wherein the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header from the packet detected according to the second detection rule, wherein the second action rule involves forwarding the packet to which the second detection rule is sent.

[0101] Figure 2 is a block diagram illustrating an apparatus according to some example embodiments. Specifically, Figure 2 Shows Figure 1 Thus, according to Figure 2 The device may further include a sending circuit 21, a receiving circuit 22, a selecting circuit 23 and / or a specifying circuit 24.

[0102] In an example embodiment, Figure 1 At least some functions of the device shown in (or 2) can be shared between two physically separated devices forming an operating entity. Therefore, the device can be regarded as describing an operating entity including one or more physically separated devices for performing at least some of the processes.

[0103] according to Fig.10 A variation of the process shown in , providing example additional operations, which are essentially independent of each other. According to this variation, the example method according to some example embodiments may include an operation of sending a request to a third local user plane functional entity associated with the network entity providing the proxy computing operation, the request including the first detection rule, the first action rule, the second detection rule, and the second action rule.

[0104] according to Fig.10 A variation of the illustrated process provides exemplary additional operations that are essentially independent of each other. According to this variation, an example method according to some example embodiments may include an operation of receiving a confirmation response.

[0105] according to Fig.10 A variation of the illustrated process provides exemplary additional operations that are essentially independent of each other. According to this variation, the example method according to some example embodiments may include an operation of selecting the third local user plane functional entity based on a network access identifier of the network entity providing the proxy computing operation.

[0106] according to Fig.10 A variation of the illustrated process provides exemplary additional operations that are essentially independent of each other. According to this variation, an example method according to some example embodiments may include an operation of receiving a proxy computing operation interconnect initiation message, the proxy computing operation interconnect initiation message including the network access identifier of the network entity providing the proxy computing operation, and the information about traffic routing to the network entity providing the proxy computing operation.

[0107] According to a further example embodiment, the network access identifier of the network entity providing the proxy computing operations is a data network access identifier, and the information about traffic routing to the network entity providing the proxy computing operations is an edge application server network address of the network entity providing the proxy computing operations.

[0108] According to a further example embodiment, the proxy computing operation interconnect initiation message comprises an identifier of the proxy computing operation, and the network access identifier of the network entity providing the proxy computing operation is a local operation access identifier, and the information about traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0109] according to Fig.10 A variation of the process shown in , providing example additional operations, which are essentially independent of each other. According to this variation, the example method according to some example embodiments may include an operation that specifies at least one of the following:

[0110] The intermediate user plane functional entity, or

[0111] the first local user plane functional entity, or

[0112] The session anchor user plane functional entity, or

[0113] the second local user plane functional entity, or

[0114] The network entity that provides the proxy computing operation.

[0115] Figure 33 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 functional entity, comprising a receiving circuit 31. In some example embodiments, the apparatus may be configured to operate as a local (protocol data unit session anchor) user plane functional entity. For example, the apparatus may be configured to perform one or more functions of a local (protocol data unit session anchor) user plane functional entity. The receiving circuit 31 receives a request from a session management functional entity, the request comprising a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule. Wherein, the first detection rule involves detecting an uplink packet received from an intermediate user plane functional entity or a first local user plane functional entity and / or detecting a downlink packet received from a session anchor user plane functional entity or a second local user plane functional entity. In addition, the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header comprising information about a service route to a network entity providing a proxy computing operation, and the first action rule also involves forwarding the packet detected according to the first detection rule. In addition, the second detection rule involves detecting packets received from the network entity providing the proxy computing operation and removing a second outer header indicating a destination of the packet from the packets detected according to the second detection rule. Further, the second action rule involves forwarding the packets detected according to the second detection rule. Fig.11 is a schematic diagram of a process according to some example embodiments. Figure 3 The device can perform Fig.11 method, but not limited to this method. Fig.11 The method can be Figure 3 The present invention is performed by a device, but is not limited to being performed by the device.

[0116] like Fig.11As shown, the process according to some example embodiments includes an operation of receiving (S111) a request from a session management function entity, the request including a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule. Here, the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity. In addition, the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header including information about a service route to a network entity providing a proxy computing operation, and the first action rule also involves forwarding the packet detected according to the first detection rule. In addition, the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation, and removing a second external header indicating a packet destination from the packet detected according to the second detection rule. In addition, the second action rule involves forwarding the packet detected according to the second detection rule.

[0117] Figure 4 is a block diagram illustrating an apparatus according to some example embodiments. Specifically, Figure 4 Shows Figure 3 Thus, according to Figure 4 The apparatus may further include a sending circuit 41 , a matching circuit 42 , an application circuit 43 , an adding circuit 44 , a forwarding circuit 45 , a removing circuit 46 and / or a copying circuit 47 .

[0118] In an example embodiment, Figure 3 At least some functions of the device shown in (or 4) can be shared between two physically separated devices forming an operating entity. Therefore, the device can be regarded as describing an operating entity including one or more physically separated devices for performing at least some of the processes.

[0119] according to Fig.11 A variation of the process shown in , provides example additional operations, which are essentially independent of each other. According to this variation, the example method according to some example embodiments may include an operation of sending a confirmation response.

[0120] according to Fig.11 A variation of the process shown in , providing example additional operations, which are essentially independent of each other. According to this variation, the example method according to some example embodiments may include an operation of receiving a packet, an operation of matching the packet with at least one of the following:

[0121] the first detection rule, or

[0122] The second detection rule,

[0123] If the packet matches the first detection rule, the first action rule is applied to the operation of the packet, and if the packet matches the second detection rule, the second action rule is applied to the operation of the packet.

[0124] according to Fig.11 A variation of the process shown in , provides example details of an application operation (applying the first action rule to the packet), which operations themselves are essentially independent of each other. Such an example application operation (applying the first action rule to the packet) according to some example embodiments may include an operation of adding the first outer header to the packet, and an operation of forwarding the packet.

[0125] according to Fig.11 A variation of the process shown in , provides example details of an application operation (applying the second action rule to the packet), which operations themselves are essentially independent of each other. Such an example application operation (applying the second action rule to the packet) according to some example embodiments may include an operation of removing the second outer header from the packet, and an operation of forwarding the packet.

[0126] according to Fig.11 A variation of the process shown in , providing example additional operations, which themselves are essentially independent of each other. According to such a variation, the example method according to some example embodiments may include (before applying any of the first action rule and the second action rule to the packet) an operation of copying the packet as a duplicated packet, and an operation of forwarding the duplicated packet to the original destination of the packet.

[0127] Figure 5is 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 computing operation (server) entity, including a receiving circuit 51. In some example embodiments, the apparatus may be configured to operate as a local / edge computer operation (server) entity. For example, the apparatus may be configured to perform one or more functions of a local / edge computer operation (server) entity. The receiving circuit 31 receives a configuration message, the configuration message comprising packet detection information, packet processing information, and packet forwarding information. Here, the packet detection information defines detection of packets received from a local user plane functional entity. In addition, the packet processing information defines the removal of a first external header indicating a packet destination from a packet detected according to the packet detection information and a computational processing to be performed on the data of the packet. In addition, the packet forwarding information defines the addition of a second external header to the packet, the second external header indicating the local user plane functional entity as a destination. Fig.12 is a schematic diagram of a process according to some example embodiments. Figure 5 The device can perform Fig.12 method, but not limited to this method. Fig.12 The method can be Figure 5 The present invention is performed by a device, but is not limited to being performed by the device.

[0128] like Fig.12 As shown, the process according to some example embodiments includes an operation of receiving (S121) a configuration message, the configuration message including packet detection information, packet processing information and packet forwarding information. Here, the packet detection information defines detecting a packet received from a local user plane function entity. In addition, the packet processing information defines removing a first external header indicating a packet destination and a computational processing to be performed on data of the packet from a packet detected according to the packet detection information. In addition, the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane function entity as a destination.

[0129] Figure 6 is a block diagram of an apparatus according to some example embodiments. Specifically, Figure 6 Shows Figure 5 Thus, according to Figure 6 The apparatus may further include a transmitting circuit 61 , a matching circuit 62 , a processing circuit 63 , a removing circuit 64 , an executing circuit 65 and / or an adding circuit 66 .

[0130] In an example embodiment, Figure 5At least some functions of the device shown in (or 6) can be shared between two physically separated devices forming an operating entity. Therefore, the device can be regarded as describing an operating entity including one or more physically separated devices for performing at least some of the processes.

[0131] according to Fig.12 A variation of the process shown in , provides exemplary additional operations, which are essentially independent of each other. According to this variation, the example method according to some example embodiments may include an operation of sending a configuration confirmation response.

[0132] according to Fig.12 A variation of the process shown in , providing exemplary additional operations, which are essentially independent of each other. According to this variation, the example method according to some example embodiments may include an operation of receiving a packet, an operation of matching the packet with the packet detection information, and an operation of processing the packet as a processed packet if the packet matches the packet detection information. In addition, this example processing operation (processing the packet) according to some example embodiments may include an operation of removing the first outer header from the packet, an operation of performing the computational processing on the data of the packet, and an operation of adding the second outer header to the packet.

[0133] according to Fig.12 A variation of the process shown in , provides example additional operations, which are essentially independent of each other. According to this variation, the example method according to some example embodiments may include an operation of sending the processed packet.

[0134] Figure 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 computing operation controller entity, including a generating circuit 71. In some example embodiments, the apparatus may be configured to operate as a computing operation controller entity. For example, the apparatus may be configured to perform one or more functions of a computing operation controller entity. The generating circuit 71 generates configuration information related to a proxy computing operation, the configuration information including packet detection information, packet processing information, and packet forwarding information. Here, the packet detection information defines detecting a packet received from a local user plane functional entity. In addition, the packet processing information defines removing a first external header from a packet detected according to the packet detection information and computing processing to be performed on the data of the packet. In addition, the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane functional entity as a destination. Fig.13 is a schematic diagram of a process according to some example embodiments. Figure 7 The device can perform Fig.13method, but not limited to this method. Fig.13 The method can be Figure 7 The present invention is performed by a device, but is not limited to being performed by the device.

[0135] like Fig.13 As shown, the process according to some example embodiments includes an operation of generating (S131) ​​configuration information related to the proxy computing operation, the configuration information including packet detection information, packet processing information and packet forwarding information. Here, the packet detection information defines detecting a packet received from a local user plane function entity. In addition, the packet processing information defines removing a first external header from a packet detected according to the packet detection information and a computing process to be performed on the data of the packet. In addition, the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane function entity as a destination.

[0136] Figure 8 is a block diagram illustrating an apparatus according to some example embodiments. In particular, Figure 8 Shows Figure 7 A variation of the device shown. Figure 8 The device may therefore also include a transmitting circuit 81 and / or a receiving circuit 82.

[0137] In an example embodiment, Figure 7 At least some functions of the device shown in (or 8) can be shared between two physically separated devices forming an operating entity. Therefore, the device can be regarded as describing an operating entity including one or more physically separated devices for performing at least some of the processes.

[0138] according to Fig.13 A variation of the illustrated process provides exemplary additional operations that are essentially independent of each other. According to this variation, the example method according to some example embodiments may include an operation of sending a configuration message to a network entity providing the proxy computing operation, the configuration message including the configuration information.

[0139] according to Fig.13 A variation of the illustrated process provides exemplary additional operations that are essentially independent of each other. According to this variation, an example method according to some example embodiments may include an operation of receiving a configuration confirmation response.

[0140] according to Fig.13A variation of the illustrated process provides example additional operations that are inherently independent of one another. According to this variation, an example method according to some example embodiments may include an operation of generating information related to a proxy computing operation, and an operation of sending a request message including the information related to the proxy computing operation, wherein the information related to the proxy computing operation includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about traffic routing to the network entity providing the proxy computing operation.

[0141] According to a further example embodiment, the network access identifier of the network entity providing the proxy computing operation is a local operations access identifier and the information about traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0142] 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 including a generation circuit 91 and a transmission circuit 92. In some example embodiments, the apparatus may be configured to operate as an application function entity. For example, the apparatus may be configured to perform one or more functions of an application function entity. The generation circuit 91 generates information related to a proxy computing operation. The transmission circuit 92 transmits a request message including the information related to the proxy computing operation. Here, the information related to the proxy computing operation includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about a service route to the network entity providing the proxy computing operation. Fig.14 is a schematic diagram of a process according to some example embodiments. Fig. 9 The device can perform Fig.14 method, but not limited to this method. Fig.14 The method can be Fig. 9 The present invention is performed by a device, but is not limited to being performed by the device.

[0143] like Fig.14 As shown, the process according to some example embodiments includes an operation of generating (S141) information related to a proxy computing operation, and an operation of sending (S142) a request message including the information related to the proxy computing operation. Here, the information related to the proxy computing operation includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about a service routing to the network entity providing the proxy computing operation.

[0144] In an example embodiment, Fig. 9At least some of the functions of the apparatus shown may be shared between two physically separate devices forming one operational entity. Thus, the apparatus may be viewed as depicting an operational entity comprising one or more physically separate devices for performing at least some of the described processes.

[0145] According to a further example embodiment, the network access identifier of the network entity providing the proxy computing operation is a local operations access identifier and the information about traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0146] Some of the example embodiments summarized and specified above are explained below in more specific terms.

[0147] That is, according to some example embodiments, particularly with respect to scenario 1, an information tuple is constructed to identify a local computing operation deployed on a local server. The information tuple of the local computing operation includes three information elements (IEs):

[0148] - Application ID used to identify the computing operation,

[0149] - a newly defined Local Operation Access Identifier (LOAI) for indicating access to a local server where a local compute operation with an application ID can be found (e.g., a compute operation server), and

[0150] -Routing information for newly defined local compute operations for business routing.

[0151] According to some example embodiments, the AF is responsible for generating an information tuple, and the information tuple may be exposed to the SMF. Subsequently, the traffic may be influenced to be routed to a local computing operation, such as in a PDU session establishment or in a PDU session modification.

[0152] According to some example embodiments, particularly in relation to scenario 2, known EAS discovery and (re)discovery procedures may be used (instead).

[0153] Using information tuples (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, local / edge computing operations can be integrated into the user plane with the help of session interruption of I-UPF and local (PSA) UPF. According to some example embodiments, the local (PSA) UFP and local / edge computing operations (servers) are configured with external header creation and removal to ensure that data packets can be routed to the local / edge computing operations for calculation and then routed back to the user plane towards the PSA UPF.

[0154] Compute operation controllers can provide additional configuration context for local / edge compute operations.

[0155] According to some example embodiments, traffic routing between local / edge computing operations and DNs through a user plane is specified. The specified process details how the local (PAS) UPF and local / edge computing operations process traffic based on the above configuration.

[0156] As described above, "Generate an information tuple for local computing operations affecting AF services" is specified.

[0157] According to some example embodiments, particularly in relation to scenario 1, the local computing operation is identified by an application identifier (application ID). A new IE local operation access identifier (LOAI) is defined to access the local computing operation. The new IE routing information of the local computing operation is used to provide a destination address for routing the service to the local computing operation. These three IEs constitute an information tuple of the local computing operation to affect the service routing. According to some example embodiments, the detailed information of the three IEs is listed in Table 1 below.

[0158] Table 1:

[0159]

[0160] These IEs in Table 1 may be pre-configured in the 5GC, for example in the PCF, and / or provided by the AF.

[0161] If provided by the AF, the AF requests service routing that affects local computing operations by generating an information tuple that can later be exposed to the SMF.

[0162] Fig.17 A schematic diagram of a signaling sequence according to some example embodiments is shown, and in particular, an information tuple for generating a local computing operation for AF service impact is shown.

[0163] Fig.17 The call flow shown in may be based on a service function chain that handles AF requests to affect traffic routing and / or sessions not identified by a UE address, such as specified in 3GPP TS 23.502 V18.1.1.

[0164] according to Fig.17 In step 0a, the PCF subscribes to the modification requested by the AF from the UDR.

[0165] according to Fig.17In step 0b-1, the V-SMF supporting HR-SBO subscribes to the notification requested by the AF by calling the Nnef_TrafficInfluenceData_Subscribe service from the V-NEF.

[0166] according to Fig.17 In step 0b-2, the V-NEF subscribes to notifications of AF requests from the V-UDR.

[0167] according to Fig.17 In step 1, according to some example embodiments, the AF calls the Nnef_TrafficInfluence_Create service operation to create a new request. The content of this AF request is shown in Table 1 above: a newly defined information tuple for service routing, including an application ID, LOAI, and routing information based on local computing operations. The request may also include an AF transaction ID and may include other data keys. Other data keys may include data keys defined in Section 5.2.6.7 "Nnef_TrafficInfluence Service" in 3GPP TS23.502V18.1.1.

[0168] according to Fig.17 In step 2, according to some example embodiments, the AF sends its request together with an information tuple of the local computing operation to the NEF.

[0169] according to Fig.17 According to some example embodiments, the NEF stores the information tuple requested by the AF in the UDR. The NEF responds to the AF.

[0170] according to Fig.17 In steps 4a and 4b, according to some example embodiments, the PCF subscribed to the modification requested by the AF receives a Nudr_DM_Notify data change notification from the UDR. The information is related to the information tuple of the local computing operation. The V-UDR notifies the subscribed V-NEF of the AF service impact request information.

[0171] according to Fig.17 In step 5a, according to some example embodiments, the PCF updates the SMF in the affected PDU session with the policy information of the corresponding new local computing operation by calling Npcf_SMPolicyControl_UpdateNotify. The PCF includes the service steering information in the relevant PCC rules. The process of notifying the report request and service experience analysis may be similar to step 5 in section 4.3.6.2 of 3GPP TS23.502V18.1.1.

[0172] according to Fig.17 In step 5b, the V-NEF notifies the subscribed V-SMF of the AF service impact request information.

[0173] according to Fig.17 In step 6, 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 section 4.3.6.2 of 3GPP TS 23.502 V18.1.1.

[0174] according to Fig.17 In step 7, according to some example embodiments, the SMF may decide whether it is necessary to send the target LOAI or the common LOAI to the AMF to trigger the SMF / I-SMF (re)selection, and then notify the AMF of the target LOAI information or the common LOAI information of the current PDU session or the next PDU session through the Nsmf_PDUSession_SMContextStatusNotify (Nsmf_PDU session_SM context status notification) service operation.

[0175] According to some example embodiments, in particular example embodiments related to scenario 2, in order to identify and discover edge servers and edge computing operations, the "Edge Application Server (EAS) (Re)Discovery" process similar to that defined in Section 6.2.3 of TS23.548 V18.1.1 may be reused to replace Fig.17 The (re)discovery can be performed by a 5GC NF (e.g., EASDF, DNS server / resolver, or AP).

[0176] Alternatively, the EAS information may also be provided by a corresponding application function, which may be performed, for example, using the existing procedures described in TS 23.548 V18.1.1.

[0177] As mentioned above, "interconnecting local / edge computing operations in the user plane" is specified.

[0178] According to some example embodiments, in particular with respect to scenario 1, the service steering information for local computing operations may be generated according to the procedure defined above ("Generating an information tuple for local computing operations impacted by AF services"). According to some example embodiments, in particular with respect to scenario 2, the service steering information for edge computing operations may be generated by an EAS (re)discovery procedure similar to those defined in Section 6.2.3 of TS23.548V18.1.1 or by service impact information provided by the AF, for example, as described in Section 5.6.7 of TS23.501V18.1.1 and Section 4.3.6.3 of TS23.502V18.1.1. In both cases, the PCF includes the service steering information in the relevant PCC rules.

[0179] According to some example embodiments, local / edge computing operations may then be interconnected in the user plane via PDU session establishment or modification.

[0180] Fig.19 A schematic diagram of a signaling sequence according to some example embodiments is shown, and in particular a configuration for interconnecting local / edge computing operations in a PDU session is shown.

[0181] Fig.19 The call flow shown in may be based on 3GPP TS 23.502 V18.1.1 Section 4.3.2 “PDU Session Establishment” and Section 4.3.3 “PDU Session Modification”.

[0182] exist Fig.19 In step 1 of , the interconnection between the local / edge computing and the DN can be implemented during the establishment of a new PDU session (option A) or added to an existing PDU session (option B). Therefore, there are at least two options to initiate the configuration of the interconnection:

[0183] -Option A: You can reuse TS23.502V18.1.1 Figure 4 .3.2.2.1-1 PDU session establishment step 1-10b.

[0184] -Option B: You can reuse TS23.502V18.1.1 Figure 4 .3.3.2-1 PDU Session Modification Step 1b.

[0185] exist Fig.19 In step 2, according to some example embodiments, the PCF invokes the Npcf_SMPolicyControl_UpdateNotify service operation to initiate the interconnection. In scenario 1, the PCC rule contains an information tuple of a local computing operation, such as Fig.17In scenario 2, the PCC rules contain DNAI and / EAS IP for local computing operations, such as defined in Section 6.2.3 of TS23.548 V18.1.1. The PCF sends the PCC rules to the SMF.

[0186] exist Fig.19 In steps 3 to 5, according to some example embodiments, when the SMF cannot provide service for the target LOAI (scenario 1) or DNAI (scenario 2), or when the existing I-SMF is not needed, the SMF calls the Nsmf_PDUSession_SMContextStatusNotify (Nsmf_PDU session_SM context status notification) service operation. The content of the message includes the target LOAI (scenario 1) or DNAI (scenario 2) information. If I-SMF selection is expected, the AMF selects a new I-SMF that can serve the target LOAI (scenario 1) or DNAI (scenario 2). The AMF sends a Nsmf_PDUSession_CreateSMContext (Nsmf_PDU session_Create SM context) request to the new I-SMF. These steps can be based on steps 2a-4a of section 4.23.5.4 of TS23.502V18.1.1, and extended to use LOAI instead of DNAI for scenario 1.

[0187] exist Fig.19 In step 6, 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).

[0188] exist Fig.19 In steps 7 to 12 of , according to some example embodiments, the I-UPF is inserted as an uplink classifier (UL-CL) or branching point (BP) based on the target LOAI (scenario 1) or DNAI (scenario 2) information. These steps can be based on step 6 of section 4.23.5.4 of TS23.502V18.1.1 and extended for scenario 1 using LOAI instead of DNAI.

[0189] exist Fig.19 In step 13, according to some example embodiments, the I-SMF creates two new packet detection rules (PDRs) to classify data packets traveling to and from local / edge computing operations on the local (PSA) UPF, and correspondingly creates two new forwarding action rules (FARs) to route traffic between the local (PSA) UPF and the local / edge computing operations.

[0190] According to some example embodiments, the parameter settings for PDR and FAR are as defined in Table 2 and Table 3.

[0191] Table 2: PDR and FAR for traffic routing to local / edge computing operations.

[0192]

[0193]

[0194] Table 3: PDR and FAR for traffic routing from local / edge computing operations.

[0195]

[0196] Fig.18 A schematic diagram of an example of a system environment with signaling variations according to some example embodiments is shown, and in particular, a packet processing flow with newly defined PDR and FAR is shown. That is, Fig.18 Reflects the packet processing flow for traffic routing to and from local / edge computing operations.

[0197] return Fig.19 ,exist Fig.19 In steps 14 and 15, according to some example embodiments, the I-SMF initiates an N4 association update.

[0198] exist Fig.19 In step 16, according to some example embodiments, the computing operation controller generates a configuration context. The grouping processing of local / edge computing operations should be defined. Specifically,

[0199] 1. For each incoming packet from the local (PSA) UPF, the outer header should be removed;

[0200] 2. Local / edge computing operations can then be performed on the packetized data; and

[0201] 3. After performing the local / edge computing operation, an outer header is added in a way that identifies the local (PSA) UPF as the destination address so that the data packet can be forwarded back to the local (PSA) UPF.

[0202] Additionally, other configuration context should be shared to local / edge compute operations, including encryption keys and other security information, to enable processing of the packetized payload.

[0203] exist Fig.19 In steps 17 and 18, according to some example embodiments, the computing operation controller sends the configuration context to the local / edge computing operation. After the sending is successful, a response is sent from the local / edge computing operation to the computing operation controller.

[0204] According to some example embodiments, Fig.19Steps 16 to 18 can be independent of Fig.19 The remaining processes shown in , thereby enabling the computing operation controller to provide the required information to the local / edge computing operation in advance, for example, during the deployment or regular configuration process and / or upon request of the local / edge computing operation.

[0205] exist Fig.19 In step 19 of , the remaining configuration of the interconnection implemented during new PDU Session establishment (option A) or added in an existing PDU Session (option B) can be performed as follows:

[0206] -Option A: You can reuse TS23.502V18.1.1 Figure 4 .3.2.2.1-1 PDU session establishment steps 11-21.

[0207] -Option B: You can reuse TS23.502V18.1.1 Figure 4 .3.3.2-1 PDU session modification step 4-13.

[0208] In the case that the SMF can serve the target LOAI or DNAI, it can be skipped Fig.19 The I-SMF in steps 3 to 5 is inserted, and according to some example embodiments, the following processes related to the I-SMF are implemented by the SMF.

[0209] As mentioned above, it is specified that "traffic routing is performed between local / edge computing operations and DNs through the user plane."

[0210] Based on the configuration process defined above ("Interconnecting local / edge computing operations in the user plane"), UL traffic can continue to be forwarded to the DN by the local (PSA) UPF after first being forwarded and calculated by the local / edge computing operations.

[0211] Fig. 20 A schematic diagram of a signaling sequence according to some example embodiments is shown, and in particular traffic routing through local / edge computing operations in a user plane is shown.

[0212] exist Fig. 20 In the present invention, the control plane NF involved in the configuration process is represented by the physical 5G core (5GC).

[0213] exist Fig. 20 In step 1 of , interconnection is initialized during PDU session establishment or modification, corresponding to options A and B of the configuration procedure defined above ("interconnecting local / edge computing operations in the user plane").

[0214] exist Fig. 20In step 2 of , according to some example embodiments, the configuration process defined above (“interconnecting local / edge computing operations in the user plane”) is implemented.

[0215] -UE sends UL traffic to DN, and

[0216] -UL traffic from UE to DN is interrupted by I-UPF to local (PSA) UPF using ULCL or BP.

[0217] exist Fig. 20 In step 3, according to some example embodiments, the local (PSA) UPF implements the PDR1 and FAR1 configurations defined above in Table 2, for example, adds an outer header and performs forwarding actions.

[0218] According to some of the example embodiments, UL traffic may optionally be replicated to be simultaneously forwarded to the PSA UPF towards the DN.

[0219] According to some example embodiments, UL traffic with added headers is routed to local / edge computing operations.

[0220] exist Fig. 20 In step 4, according to some example embodiments, the local / edge computing operation implements the above Fig.19 The configuration context defined in step 16 of , e.g., external header removal, computation operation execution, and external header addition.

[0221] According to some of the example embodiments, the UL traffic with the re-added header is routed back to the local (PSA) UPF.

[0222] exist Fig. 20 In step 5, according to some example embodiments, the local (PSA) UPF implements the PDR2 and FAR2 configurations defined in Table 3 above, for example, removes the added outer header and performs forwarding actions.

[0223] According to some of the example embodiments, UL traffic is routed to the PSA UPF and further routed to the DN which is the original destination provided by the UE.

[0224] Fig. 20 UL traffic routing is shown. DL traffic can be regular DL traffic from PSA UPF to UE, or similar outer header processing like UL traffic. Multiple local / edge computing operations can be interconnected by building a chain of [local (PSA) UPF, local / edge computing operation] pairs. In the case of multiple pairs, according to some example embodiments, Fig. 20 Step 5 of is changed to modify the outer header to the next local (PSA) UPF instead of removing it when the outer header is not the last pair towards the PSA UPF.

[0225] The above processes and functions can be implemented by corresponding functional elements, processors, etc., as described below.

[0226] In the aforementioned example description of the network entity, only units relevant to understanding the present subject disclosure are described using functional blocks. The network entity may include further units for its corresponding operations. However, the description of these units is omitted in the present subject disclosure. The arrangement of the functional blocks of the device should not be interpreted as limiting the present subject disclosure, and the functions may be performed by one block or further split into sub-blocks.

[0227] When it is stated in the foregoing description that a device (e.g., a network node or entity (or some other component)) is configured to perform certain functions, this should be interpreted as equivalent to the following description: (e.g., at least one) processor or corresponding circuitry, possibly in cooperation with a computer program code stored in a memory of the corresponding device, is configured to cause the device to perform at least the above-mentioned functions. In addition, such functions should be interpreted as being equivalently implementable by specially configured circuits or components for performing the corresponding functions (e.g., the expression "a unit configured to..." should be interpreted as being equivalent to expressions such as "components for...").

[0228] exist Fig.21 In FIG. 1 , an alternative diagram of an apparatus according to some example embodiments is depicted. Fig.21 As shown, according to some example embodiments, the device (network node or entity) 10' (corresponding to the network node or entity 10) includes a processor 211, a memory 212, and an interface 213, which are connected via a bus 214 or the like. In addition, according to some example embodiments, the device (network node or entity) 30' (corresponding to the network node or entity 30) includes a processor 211, a memory 212, and an interface 213, which are connected via a bus 214 or the like. In addition, according to some example embodiments, the device (network node or entity) 50' (corresponding to the network node or entity 50) includes a processor 211, a memory 212, and an interface 213, which are connected via a bus 214 or the like. In addition, according to some example embodiments, the device (network node or entity) 70' (corresponding to the network node or entity 70) includes a processor 211, a memory 212, and an interface 213, which are connected via a bus 214 or the like. Furthermore, according to some example embodiments, device (network node or entity) 90' (corresponding to network node or entity 90) includes a processor 211, a memory 212, and an interface 213, which are connected via a bus 214, etc. Devices 10', 30', 50', 70', 90' may be connected to another device via a link 215, such as another device of devices 10', 30', 50', 70', 90', respectively.

[0229] The processor 211 and / or the interface 213 may also include a modem or the like to communicate via a (hardwired or wireless) link, respectively. The interface 213 may include an appropriate transceiver coupled to one or more antennas or communication components for communicating (hardwired or wireless) with a linked or connected device, respectively. The interface 213 is typically configured to communicate with at least one other device (e.g., an interface thereof).

[0230] In some example embodiments, the memory 212 may store corresponding programs, which are assumed to include program instructions or computer program codes, which, when executed by a corresponding processor, cause a corresponding electronic device or device to operate according to any one or more example embodiments described herein. In some example embodiments, the memory 212 may store instructions, which, when executed by a corresponding processor, cause a corresponding electronic device or device to operate according to one or more example embodiments described herein.

[0231] Generally speaking, the corresponding devices / apparatuses (and / or parts thereof) may represent components for performing corresponding operations and / or demonstrating corresponding functions, and / or the corresponding devices (and / or parts thereof) may have functions for performing corresponding operations and / or demonstrating corresponding functions.

[0232] When it is stated in the subsequent description that a processor (or some other component) is configured to perform certain functions, this should be interpreted as equivalent to the following description: at least one processor, possibly in cooperation with computer program code stored in a memory of a corresponding device, is configured to cause the device to perform at least the above functions. In addition, such functions should be interpreted as being equivalently implementable by components specifically configured to perform the corresponding functions (for example, the expression "a processor configured to [cause the device] to perform xxx" is interpreted as being equivalent to expressions such as "components for xxx").

[0233] According to some of the example embodiments, the apparatus representing the network node 10 comprises at least one processor 211, at least one memory 212 comprising computer program code, and at least one interface 213 configured for communicating with at least another apparatus. The processor (e.g., at least one processor 211, having at least one memory 212 and computer program code) is configured to execute generating a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, wherein the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header comprising information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule (therefore the device includes corresponding components for generating), and executing generating a second detection rule and a second action rule associated with the second detection rule, wherein the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header from the packet detected according to the second detection rule, wherein the second action rule involves forwarding the packet detected according to the second detection rule.

[0234] According to some of the example embodiments, the apparatus representing the network node 30 comprises at least one processor 211, at least one memory 212 comprising computer program code, and at least one interface 213 configured for communicating with at least another apparatus. The processor (e.g., at least one processor 211, and at least one memory 212 and computer program code) is configured to execute receiving a request from a session management function entity, the request comprising a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header comprising information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule, the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header indicating a packet destination from the packet detected according to the second detection rule, and wherein the second action rule involves forwarding the packet detected according to the second detection rule (therefore the apparatus comprises corresponding components for receiving).

[0235] According to some example embodiments, the apparatus representing the network node 50 comprises at least one processor 211, at least one memory 212 comprising computer program code, and at least one interface 213 configured for communication with at least another apparatus. The processor (e.g., at least one processor 211, and at least one memory 212 and computer program code) is configured to perform receiving a configuration message, the configuration message comprising packet detection information, packet processing information, and packet forwarding information, wherein the packet detection information defines detecting a packet received from a local user plane function entity, the packet processing information defines removing a first external header indicating a packet destination from a packet detected according to the packet detection information and a computational processing to be performed on data of the packet, wherein the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane function entity as a destination (therefore the apparatus comprises corresponding components for receiving).

[0236] According to some example embodiments, the apparatus representing the network node 70 comprises at least one processor 211, at least one memory 212 comprising computer program code, and at least one interface 213 configured for communication with at least another apparatus. The processor (e.g., at least one processor 211, and at least one memory 212 and computer program code) is configured to perform generation of configuration information related to proxy computing operations, the configuration information comprising packet detection information, packet processing information, and packet forwarding information, wherein the packet detection information defines detection of packets received from a local user plane function entity, the packet processing information defines removal of a first external header from a packet detected according to the packet detection information and computing processing to be performed on data of the packet, and wherein the packet forwarding information defines adding a second external header to the packet, the second external header indicating the local user plane function entity as a destination (therefore the apparatus comprises corresponding components for generating).

[0237] According to some example embodiments, the apparatus representing the network node 90 includes at least one processor 211, at least one memory 212 including computer program code, and at least one interface 213 configured to communicate with at least another apparatus. The processor (e.g., at least one processor 211, and at least one memory 212 and computer program code) is configured to perform generating proxy computing operation related information (therefore, the apparatus includes corresponding components for generating), and to perform sending a request message including the proxy computing operation related information, wherein the proxy computing operation related information includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about traffic routing to the network entity providing the proxy computing operation (therefore, the apparatus includes corresponding components for sending).

[0238] For more details on the operability / functionality of the individual devices, refer to the Figures 1 to 20 Any of the above descriptions related to .

[0239] For purposes of the subject disclosure described herein, it should be noted that:

[0240] - the method steps, which may be implemented as software code portions and executed using a processor at a network server or network entity (as an example of a device, apparatus and / or its modules, or as an example of an entity including apparatus and / or modules), are independent of the software code and may be specified using any known or future developed programming language as long as the functionality defined by the method steps is preserved;

[0241] - generally, any method step is suitable for implementation in software or hardware form without changing the idea of ​​the exemplary embodiment and its modification in terms of the implemented functions;

[0242] - the method steps and / or devices, units or parts that may be implemented as hardware components at the above-defined apparatus or any module thereof (e.g., a device that performs the functions of the apparatus according to the above-described embodiments) are hardware-independent and may be implemented using any known or future-developed hardware technology or any hybrid of these technologies, such as MOS (metal oxide semiconductor), CMOS (complementary MOS), BiMOS (bipolar MOS), BiCMOS (bipolar CMOS), ECL (emitter coupled logic), TTL (transistor-transistor logic), etc., for example using ASIC (application specific IC (integrated circuit)) components, FPGA (field programmable gate array) components, CPLD (complex programmable logic device) components or DSP (digital signal processor) components;

[0243] - devices, units or components (e.g. a network entity or a network register as defined above, or any of their corresponding units / components) may be implemented as separate devices, units or components, but this does not exclude that they may be implemented in a distributed manner throughout the system, as long as the functionality of the device, unit or component is preserved;

[0244] - Apparatuses such as user equipment and network entities / network registers may be represented by a semiconductor chip, a chipset or a (hardware) module comprising such a chip or chipset; however, this does not exclude the possibility that the functionality of the apparatus or module is not implemented by hardware but as software in a (software) module (e.g. a computer program or computer program product comprising executable software code portions for execution / running on a processor);

[0245] - A device may be considered as an apparatus or a component of a plurality of apparatuses, whether they cooperate in functionality or are functionally independent of each other but located, for example, in the same device housing.

[0246] Generally, it should be noted that the corresponding functional blocks or elements according to the above aspects can be implemented by any known components, whether hardware or software, respectively, as long as they are only suitable for performing the functions of the respective components. The mentioned method steps can be implemented in separate functional blocks or separate devices, or one or more method steps can be implemented in a single functional block or a single device.

[0247] Generally, any method step is suitable for implementation as software or hardware without changing the idea of ​​the subject disclosure. Devices and components can be implemented as separate devices, but this does not exclude that they can be implemented in a distributed manner throughout the system, as long as the functionality of the device is preserved. This and similar principles should be considered to be known to those skilled in the art.

[0248] The software in the subject description includes software code, which includes code components or portions or a computer program or computer program product for performing corresponding functions, and software (or computer program or computer program product) embodied on a tangible medium (such as a computer readable (storage) medium) on which the corresponding data structure or code components / portions are stored, or embodied in a signal or chip (possibly during processing).

[0249] The subject disclosure also covers any combination of the above method steps and operations, and any conceivable combination of the above nodes, devices, modules, or elements, as long as the concepts of the above methods and structural arrangements are applicable.

[0250] In view of the above, measures for enabling and controlling the distribution of computing operations in a network are provided. Such measures may include generating a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane functional entity or a first local user plane functional entity and / or detecting a downlink packet received from a session anchor user plane functional entity or a second local user plane functional entity, wherein the first action rule involves adding a first external header to a packet detected according to the first detection rule, the first external header including information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule also involves forwarding the packet detected according to the first detection rule, and generating a second detection rule and a second action rule associated with the second detection rule, wherein the second detection rule involves detecting a packet received from the network entity providing the proxy computing operation and removing a second external header from the packet detected according to the second detection rule, wherein the second action rule involves forwarding the packet detected according to the second detection rule.

[0251] Although the subject disclosure is described above with reference to its various exemplary embodiments according to the accompanying drawings, it should be understood that the subject disclosure is not limited thereto. On the contrary, it is obvious that those skilled in the art can modify the subject disclosure in many ways without departing from the scope of the various exemplary embodiments disclosed herein.

[0252] The above disclosure covers at least the following items:

[0253] Item 1. A method comprising

[0254] generating a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, wherein the first action rule involves adding a first outer header to a packet detected according to the first detection rule, the first outer header comprising information about a traffic route to a network entity providing a proxy computing operation, and wherein the first action rule further involves forwarding the packet detected according to the first detection rule, and

[0255] A second detection rule and a second action rule associated with the second detection rule are generated, wherein the second detection rule involves detecting packets received from the network entity providing the proxy computing operation and removing a second outer header from packets detected according to the second detection rule, wherein the second action rule involves forwarding the packets detected according to the second detection rule.

[0256] Item 2. The method according to Item 1 further includes

[0257] A request is sent to a third local user plane functional entity associated with the network entity providing the proxy computing operation, the request including the first detection rule, the first action rule, the second detection rule, and the second action rule.

[0258] Item 3. The method according to Item 2 further includes

[0259] The third local user plane functional entity is selected based on a network access identifier of the network entity providing the proxy computing operation.

[0260] Item 4. The method according to Item 3 further includes

[0261] A proxy computing operation interconnect initiation message is received, the proxy computing operation interconnect initiation message including the network access identifier of the network entity providing the proxy computing operation and the information on traffic routing to the network entity providing the proxy computing operation.

[0262] Item 5. The method according to Item 4, wherein

[0263] the network access identifier of the network entity providing the proxy computing operation is a data network access identifier, and the information about traffic routing to the network entity providing the proxy computing operation is an edge application server network address of the network entity providing the proxy computing operation, or

[0264] The proxy computing operation interconnect initiation message includes an identifier of the proxy computing operation, and the network access identifier of the network entity providing the proxy computing operation is a local operation access identifier, and the information about traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0265] Item 6. The method according to any one of Items 1 to 5, further comprising

[0266] Specify at least one of the following:

[0267] The intermediate user plane functional entity, or

[0268] the first local user plane functional entity, or

[0269] The session anchor user plane functional entity, or

[0270] the second local user plane functional entity, or

[0271] The network entity that provides the proxy computing operation.

[0272] Item 7. A method comprising

[0273] A request is received from a session management function entity, the request comprising a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule, wherein

[0274] The first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity,

[0275] the first action rule involves adding a first outer header to a packet detected according to the first detection rule, the first outer header comprising information about a traffic route to a network entity providing a proxy computing operation, and wherein the first action rule further involves forwarding the packet detected according to the first detection rule,

[0276] The second detection rule involves detecting packets received from the network entity providing the proxy computing operation and removing a second outer header indicating a destination of the packet from the packets detected according to the second detection rule, and wherein

[0277] The second action rule relates to forwarding the packet detected according to the second detection rule.

[0278] Item 8. The method according to Item 7 further includes

[0279] Send a confirmation response.

[0280] Item 9. The method according to Item 7 or 8, further comprising

[0281] Receive packets,

[0282] Match the group with at least one of the following:

[0283] the first detection rule, or

[0284] The second detection rule,

[0285] If the packet matches the first detection rule, applying the first action rule to the packet, and

[0286] If the packet matches the second detection rule, the second action rule is applied to the packet.

[0287] Item 10. The method according to Item 9, wherein

[0288] With respect to said applying said first action rule to said packet, said method further comprises:

[0289] adding the first outer header to the packet, and

[0290] The packet is forwarded.

[0291] Item 11. The method according to Item 9 or 10, wherein

[0292] With respect to said applying said second action rule to said packet, the method further comprises

[0293] removing the second outer header from the packet, and

[0294] The packet is forwarded.

[0295] Item 12. The method according to any one of Items 9 to 11, further comprising

[0296] before applying any of the first action rule and the second action rule to the packet, copying the packet as a copied packet, and

[0297] The copied packet is forwarded to the original destination of the packet.

[0298] Item 13. A method comprising

[0299] Receive a configuration message, the configuration message including packet detection information, packet processing information and packet forwarding information, wherein

[0300] The packet detection information defines detecting packets received from a local user plane function entity,

[0301] The packet processing information defines removal of a first outer header indicating a packet destination from a packet detected according to the packet detection information and a calculation process to be performed on data of the packet, and wherein

[0302] The packet forwarding information defines adding a second outer header to the packet, the second outer header indicating the local user plane function entity as a destination.

[0303] Item 14. The method according to Item 13 further includes

[0304] Send configuration confirmation response.

[0305] Item 15. The method according to Item 13 or 14, further comprising

[0306] Receive packets,

[0307] matching the packet with the packet detection information, and

[0308] If the packet matches the packet detection information, the packet is processed as a processed packet, wherein

[0309] With respect to said processing said packet, the method further comprises

[0310] removing the first outer header from the packet,

[0311] performing said computational processing on said data of said group, and

[0312] The second outer header is added to the packet.

[0313] Item 16. The method according to Item 15 further includes

[0314] The processed packets are transmitted.

[0315] Item 17. A method comprising

[0316] Generate configuration information related to the proxy computing operation, the configuration information including packet detection information, packet processing information and packet forwarding information, wherein

[0317] The packet detection information defines detecting packets received from a local user plane function entity,

[0318] The packet processing information defines the removal of the first outer header from the packet detected according to the packet detection information and the computational processing to be performed on the data of the packet, and wherein

[0319] The packet forwarding information defines adding a second outer header to the packet, the second outer header indicating the local user plane function entity as a destination.

[0320] Item 18. The method according to Item 17 further includes

[0321] A configuration message is sent to a network entity that provides the proxy computing operation, the configuration message including the configuration information.

[0322] Item 19. The method according to Item 17 or 18, further comprising:

[0323] Generate information about proxy compute operations, and

[0324] Sending a request message including information related to the proxy computing operation, wherein

[0325] The proxy computing operation related information includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about traffic routing to the network entity providing the proxy computing operation.

[0326] Item 20. The method according to Item 19, wherein

[0327] The network access identifier of the network entity providing the proxy computing operation is a local operations access identifier, and the information regarding traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0328] Item 21. A method comprising:

[0329] Generate information about proxy compute operations, and

[0330] Sending a request message including information related to the proxy computing operation, wherein

[0331] The proxy computing operation related information includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about traffic routing to the network entity providing the proxy computing operation.

[0332] Item 22. A method according to Item 21, wherein the network access identifier of the network entity providing the proxy computing operation is a local operation access identifier, and the information about the service routing to the network entity providing the proxy computing operation is the network address of the network entity providing the proxy computing operation.

[0333] Item 23. A device comprising:

[0334] Generate a circuit that is configured as:

[0335] generating a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, wherein the first action rule involves adding a first outer header to a packet detected according to the first detection rule, the first outer header comprising information about a traffic route to a network entity providing a proxy computing operation, and wherein the first action rule further involves forwarding the packet detected according to the first detection rule, and

[0336] A second detection rule and a second action rule associated with the second detection rule are generated, wherein the second detection rule involves detecting packets received from the network entity providing the proxy computing operation and removing a second outer header from packets detected according to the second detection rule, wherein the second action rule involves forwarding the packets detected according to the second detection rule.

[0337] Item 24. The device according to Item 23 further includes

[0338] A sending circuit is configured to send a request to a third local user plane functional entity associated with the network entity providing the proxy computing operation, the request comprising the first detection rule, the first action rule, the second detection rule and the second action rule.

[0339] Item 25. The device according to Item 24 further includes

[0340] The selection circuit is configured to select the third local user plane functional entity based on a network access identifier of the network entity providing the proxy computing operation.

[0341] Item 26. The device according to Item 25 further includes

[0342] A receiving circuit is configured to receive a proxy computing operation interconnect initiation message, wherein the proxy computing operation interconnect initiation message includes the network access identifier of the network entity providing the proxy computing operation and the information on traffic routing to the network entity providing the proxy computing operation.

[0343] Item 27. The device according to Item 26, wherein

[0344] the network access identifier of the network entity providing the proxy computing operation is a data network access identifier, and the information about traffic routing to the network entity providing the proxy computing operation is an edge application server network address of the network entity providing the proxy computing operation, or

[0345] The proxy computing operation interconnect initiation message includes an identifier of the proxy computing operation, and the network access identifier of the network entity providing the proxy computing operation is a local operation access identifier, and the information about traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0346] Item 28. The device according to any one of Items 23 to 27, further comprising

[0347] Specifying circuitry configured to specify at least one of the following:

[0348] The intermediate user plane functional entity, or

[0349] the first local user plane functional entity, or

[0350] The session anchor user plane functional entity, or

[0351] the second local user plane functional entity, or

[0352] The network entity that provides the proxy computing operation.

[0353] Item 29. A device comprising

[0354] A receiving circuit is configured to receive a request from a session management function entity, the request comprising a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule, wherein

[0355] The first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity,

[0356] the first action rule involves adding a first outer header to a packet detected according to the first detection rule, the first outer header comprising information about a traffic route to a network entity providing a proxy computing operation, and wherein the first action rule further involves forwarding the packet detected according to the first detection rule,

[0357] The second detection rule involves detecting packets received from the network entity providing the proxy computing operation and removing a second outer header indicating a destination of the packet from the packets detected according to the second detection rule, and wherein

[0358] The second action rule relates to forwarding the packet detected according to the second detection rule.

[0359] Item 30. The device according to Item 29 further includes

[0360] A transmitting circuit is configured to transmit an acknowledgment response.

[0361] Item 31. The device according to Item 29 or 30, further comprising

[0362] a receiving circuit configured to receive a packet,

[0363] A matching circuit configured to match the packet to at least one of:

[0364] the first detection rule, or

[0365] the second detection rule, and

[0366] application circuit, which is configured as

[0367] If the packet matches the first detection rule, applying the first action rule to the packet, and

[0368] If the packet matches the second detection rule, the second action rule is applied to the packet.

[0369] Item 32. The device according to Item 31 further includes

[0370] adding circuitry configured to add the first outer header to the packet, and

[0371] A forwarding circuit is configured to forward the packet.

[0372] Item 33. The device according to Item 31 or 32 further includes

[0373] removing circuitry configured to remove the second outer header from the packet, and

[0374] A forwarding circuit is configured to forward the packet.

[0375] Item 34. The device according to any one of Items 31 to 33, further comprising

[0376] a copy circuit configured to copy the packet into a copied packet before applying any one of the first action rule and the second action rule to the packet, and

[0377] A forwarding circuit is configured to forward the copied packet to an original destination of the packet.

[0378] Item 35. A device comprising

[0379] A receiving circuit is configured to receive a configuration message, wherein the configuration message includes packet detection information, packet processing information and packet forwarding information, wherein

[0380] The packet detection information defines detecting packets received from a local user plane function entity,

[0381] The packet processing information defines removal of a first outer header indicating a packet destination from a packet detected according to the packet detection information and a calculation process to be performed on data of the packet, and wherein

[0382] The packet forwarding information defines adding a second outer header to the packet, the second outer header indicating the local user plane function entity as a destination.

[0383] Item 36. The device according to Item 35 further includes

[0384] A sending circuit is configured to send a configuration confirmation response.

[0385] Item 37. The device according to Item 35 or 36 further includes

[0386] a receiving circuit configured to receive a packet,

[0387] a matching circuit configured to match the packet with the packet detection information,

[0388] a processing circuit configured to process the packet as a processed packet if the packet matches the packet detection information,

[0389] a removal circuit configured to remove the first outer header from the packet,

[0390] an execution circuit configured to perform the computational processing on the data of the group, and

[0391] Adding circuitry is configured to add the second outer header to the packet.

[0392] Item 38. The device according to Item 37 further includes

[0393] A transmitting circuit is configured to transmit the processed packet.

[0394] Item 39. A device comprising

[0395] A generating circuit is configured to generate configuration information related to the proxy computing operation, the configuration information including packet detection information, packet processing information and packet forwarding information, wherein

[0396] The packet detection information defines detecting packets received from a local user plane function entity,

[0397] The packet processing information defines the removal of the first outer header from the packet detected according to the packet detection information and the computational processing to be performed on the data of the packet, and wherein

[0398] The packet forwarding information defines adding a second outer header to the packet, the second outer header indicating the local user plane function entity as a destination.

[0399] Item 40. The device according to Item 39 further includes

[0400] The sending circuit is configured to send a configuration message to a network entity providing the proxy computing operation, wherein the configuration message includes the configuration information.

[0401] Item 41. The device according to Item 39 or 40, further comprising:

[0402] generating circuitry configured to generate information related to the proxy computing operation; and

[0403] A sending circuit is configured to send a request message including information related to the proxy computing operation, wherein

[0404] The proxy computing operation related information includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about traffic routing to the network entity providing the proxy computing operation.

[0405] Item 42. The device according to Item 41, wherein

[0406] The network access identifier of the network entity providing the proxy computing operation is a local operations access identifier, and the information regarding traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0407] Item 43. A device comprising:

[0408] generating circuitry configured to generate information related to the proxy computing operation; and

[0409] A sending circuit is configured to send a request message including information related to the proxy computing operation, wherein

[0410] The proxy computing operation related information includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about traffic routing to the network entity providing the proxy computing operation.

[0411] Item 44. The device according to Item 43, wherein

[0412] The network access identifier of the network entity providing the proxy computing operation is a local operations access identifier, and the information regarding traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0413] Item 45. A device comprising

[0414] at least one processor, and

[0415] at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform:

[0416] generating a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, wherein the first action rule involves adding a first outer header to a packet detected according to the first detection rule, the first outer header comprising information about a traffic route to a network entity providing a proxy computing operation, and wherein the first action rule further involves forwarding the packet detected according to the first detection rule, and

[0417] A second detection rule and a second action rule associated with the second detection rule are generated, wherein the second detection rule involves detecting packets received from the network entity providing the proxy computing operation and removing a second outer header from packets detected according to the second detection rule, wherein the second action rule involves forwarding the packets detected according to the second detection rule.

[0418] Item 46. The device according to Item 45, wherein

[0419] The instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0420] A request is sent to a third local user plane functional entity associated with the network entity providing the proxy computing operation, the request including the first detection rule, the first action rule, the second detection rule, and the second action rule.

[0421] Item 47. The device according to Item 46, wherein

[0422] The instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0423] The third local user plane functional entity is selected based on a network access identifier of the network entity providing the proxy computing operation.

[0424] Item 48. The device according to Item 47, wherein

[0425] The instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0426] A proxy computing operation interconnect initiation message is received, the proxy computing operation interconnect initiation message including the network access identifier of the network entity providing the proxy computing operation and the information on traffic routing to the network entity providing the proxy computing operation.

[0427] Item 49. The device according to Item 48, wherein

[0428] the network access identifier of the network entity providing the proxy computing operation is a data network access identifier, and the information about traffic routing to the network entity providing the proxy computing operation is an edge application server network address of the network entity providing the proxy computing operation, or

[0429] The proxy computing operation interconnect initiation message includes an identifier of the proxy computing operation, and the network access identifier of the network entity providing the proxy computing operation is a local operation access identifier, and the information about traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0430] Item 50. A device according to any one of Items 45 to 49, wherein

[0431] The instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0432] Specify at least one of the following:

[0433] The intermediate user plane functional entity, or

[0434] the first local user plane functional entity, or

[0435] The session anchor user plane functional entity, or

[0436] the second local user plane functional entity, or

[0437] The network entity that provides the proxy computing operation.

[0438] Item 51. A device comprising

[0439] at least one processor, and

[0440] at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform:

[0441] A request is received from a session management function entity, the request comprising a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule, wherein

[0442] The first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity,

[0443] the first action rule involves adding a first outer header to a packet detected according to the first detection rule, the first outer header comprising information about a traffic route to a network entity providing a proxy computing operation, and wherein the first action rule further involves forwarding the packet detected according to the first detection rule,

[0444] The second detection rule involves detecting packets received from the network entity providing the proxy computing operation and removing a second outer header indicating a destination of the packet from the packets detected according to the second detection rule, and wherein

[0445] The second action rule relates to forwarding the packet detected according to the second detection rule.

[0446] Item 52. The device according to Item 51, wherein

[0447] The instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0448] Send a confirmation response.

[0449] Item 53. An apparatus according to Item 51 or 52, wherein

[0450] The instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0451] Receive packets,

[0452] Match the group with at least one of the following:

[0453] the first detection rule, or

[0454] The second detection rule,

[0455] If the packet matches the first detection rule, applying the first action rule to the packet, and

[0456] If the packet matches the second detection rule, the second action rule is applied to the packet.

[0457] Item 54. An apparatus according to Item 53, wherein

[0458] With respect to the applying the first action rule to the packet, the instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0459] adding the first outer header to the packet, and

[0460] The packet is forwarded.

[0461] Item 55. An apparatus according to Item 53 or 54, wherein

[0462] With respect to the applying the second action rule to the packet, the instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0463] removing the second outer header from the packet, and

[0464] The packet is forwarded.

[0465] Item 56. A device according to any one of Items 53 to 55, wherein

[0466] The instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0467] before applying any of the first action rule and the second action rule to the packet, copying the packet as a copied packet, and

[0468] The copied packet is forwarded to the original destination of the packet.

[0469] Item 57. A device comprising

[0470] at least one processor, and

[0471] at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform:

[0472] Receive a configuration message, the configuration message including packet detection information, packet processing information and packet forwarding information, wherein

[0473] The packet detection information defines detecting packets received from a local user plane function entity,

[0474] The packet processing information defines removal of a first outer header indicating a packet destination from a packet detected according to the packet detection information and calculation processing to be performed on data of the packet, and wherein

[0475] The packet forwarding information defines adding a second outer header to the packet, the second outer header indicating the local user plane function entity as a destination.

[0476] Item 58. The device according to Item 57, wherein

[0477] When the instructions are executed by the at least one processor, the device is caused to at least perform:

[0478] Send configuration confirmation response.

[0479] Item 59. An apparatus according to Item 57 or 58, wherein

[0480] The instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0481] Receive packets,

[0482] matching the packet with the packet detection information, and

[0483] If the packet matches the packet detection information, the packet is processed as a processed packet, wherein

[0484] With respect to said processing said packet, said instructions, when executed by said at least one processor, cause said apparatus to at least perform removing said first outer header from said packet,

[0485] performing said computational processing on said data of said group, and

[0486] The second outer header is added to the packet.

[0487] Item 60. The device according to Item 59, wherein

[0488] The instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0489] The processed packets are transmitted.

[0490] Item 61. A device comprising

[0491] at least one processor, and

[0492] at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform:

[0493] Generate configuration information related to the proxy computing operation, the configuration information including packet detection information, packet processing information and packet forwarding information, wherein

[0494] The packet detection information defines detecting packets received from a local user plane function entity,

[0495] The packet processing information defines the removal of the first outer header from the packet detected according to the packet detection information and the computational processing to be performed on the data of the packet, and wherein

[0496] The packet forwarding information defines adding a second outer header to the packet, the second outer header indicating the local user plane function entity as a destination.

[0497] Item 62. The device according to Item 61, wherein

[0498] The instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0499] A configuration message is sent to a network entity that provides the proxy computing operation, the configuration message including the configuration information.

[0500] Item 63. An apparatus according to Item 61 or 62, wherein

[0501] The instructions, when executed by the at least one processor, cause the apparatus to at least perform:

[0502] Generate information about proxy compute operations, and

[0503] Sending a request message including information related to the proxy computing operation, wherein

[0504] The proxy computing operation related information includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about traffic routing to the network entity providing the proxy computing operation.

[0505] Item 64. An apparatus according to Item 63, wherein

[0506] The network access identifier of the network entity providing the proxy computing operation is a local operations access identifier, and the information regarding traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0507] Item 65. A device comprising

[0508] at least one processor, and

[0509] at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform:

[0510] Generate information about proxy compute operations, and

[0511] Sending a request message including information related to the proxy computing operation, wherein

[0512] The proxy computing operation related information includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about traffic routing to the network entity providing the proxy computing operation.

[0513] Item 66. The device according to Item 65, wherein

[0514] The network access identifier of the network entity providing the proxy computing operation is a local operations access identifier, and the information regarding traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0515] Item 67. A device comprising:

[0516] means for generating a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule relates to detecting an uplink packet received from an intermediate user plane functional entity or a first local user plane functional entity and / or detecting a downlink packet received from a session anchor user plane functional entity or a second local user plane functional entity, wherein the first action rule relates to adding a first outer header to a packet detected according to the first detection rule, the first outer header comprising information about a traffic route to a network entity providing a proxy computing operation, and wherein the first action rule further relates to forwarding the packet detected according to the first detection rule, and

[0517] Means for generating a second detection rule and a second action rule associated with the second detection rule, wherein the second detection rule relates to detecting packets received from the network entity providing the proxy computing operation and removing a second outer header from packets detected according to the second detection rule, wherein the second action rule relates to forwarding the packets detected according to the second detection rule.

[0518] Item 68. The device according to Item 67 further includes

[0519] Means for sending a request to a third local user plane functional entity associated with the network entity providing the proxy computing operation, the request comprising the first detection rule, the first action rule, the second detection rule, and the second action rule.

[0520] Item 69. The device according to Item 68 further includes

[0521] Means for selecting said third local user plane functional entity based on a network access identifier of said network entity providing said proxy computing operation.

[0522] Item 70. The device according to Item 69 further includes

[0523] Means for receiving a proxy computing operation interconnect initiation message, the proxy computing operation interconnect initiation message comprising the network access identifier of the network entity providing the proxy computing operation and the information on traffic routing to the network entity providing the proxy computing operation.

[0524] Item 71. An apparatus according to Item 70, wherein

[0525] the network access identifier of the network entity providing the proxy computing operation is a data network access identifier, and the information about traffic routing to the network entity providing the proxy computing operation is an edge application server network address of the network entity providing the proxy computing operation, or

[0526] The proxy computing operation interconnect initiation message includes an identifier of the proxy computing operation, and the network access identifier of the network entity providing the proxy computing operation is a local operation access identifier, and the information about traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0527] Item 72. The device according to any one of Items 67 to 71, further comprising:

[0528] A component that specifies at least one of the following:

[0529] The intermediate user plane functional entity, or

[0530] the first local user plane functional entity, or

[0531] The session anchor user plane functional entity, or

[0532] the second local user plane functional entity, or

[0533] The network entity that provides the proxy computing operation.

[0534] Item 73. A device comprising

[0535] means for receiving a request from a session management function entity, the request comprising a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule, wherein

[0536] The first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity,

[0537] the first action rule involves adding a first outer header to a packet detected according to the first detection rule, the first outer header comprising information about a traffic route to a network entity providing a proxy computing operation, and wherein the first action rule further involves forwarding the packet detected according to the first detection rule,

[0538] The second detection rule involves detecting packets received from the network entity providing the proxy computing operation and removing a second outer header indicating a destination of the packet from the packets detected according to the second detection rule, and wherein

[0539] The second action rule relates to forwarding the packet detected according to the second detection rule.

[0540] Item 74. The device according to Item 73 further includes

[0541] Component used to send a confirmation response.

[0542] Item 75. The device according to Item 73 or 74 further includes

[0543] A component for receiving packets,

[0544] means for matching said grouping to at least one of:

[0545] the first detection rule, or

[0546] The second detection rule,

[0547] means for applying the first action rule to the packet if the packet matches the first detection rule, and

[0548] Means for applying the second action rule to the packet if the packet matches the second detection rule.

[0549] Item 76. The device according to Item 75 further includes

[0550] means for adding said first outer header to said packet, and

[0551] Means for forwarding said packet.

[0552] Item 77. The device according to Item 75 or 76 further includes

[0553] means for removing said second outer header from said packet, and

[0554] Means for forwarding said packet.

[0555] Item 78. The device according to any one of Items 75 to 77, further comprising:

[0556] means for copying the packet as a copied packet before applying any of the first action rule and the second action rule to the packet, and

[0557] Means for forwarding the copied packet to the original destination of the packet.

[0558] Item 79. A device comprising

[0559] A component for receiving a configuration message, wherein the configuration message includes packet detection information, packet processing information and packet forwarding information, wherein

[0560] The packet detection information defines detecting packets received from a local user plane function entity,

[0561] The packet processing information defines removal of a first outer header indicating a packet destination from a packet detected according to the packet detection information and a calculation process to be performed on data of the packet, and wherein

[0562] The packet forwarding information defines adding a second outer header to the packet, the second outer header indicating the local user plane function entity as a destination.

[0563] Item 80. The device according to Item 79 further includes

[0564] Component used to send a configuration confirmation response.

[0565] Item 81. The device according to Item 79 or 80 further includes

[0566] A component for receiving packets,

[0567] means for matching said packet with said packet detection information, and

[0568] means for processing the packet as a processed packet if the packet matches the packet detection information,

[0569] means for removing said first outer header from said packet,

[0570] means for performing said computational processing on said grouped data, and

[0571] Means for adding the second outer header to the packet.

[0572] Item 82. The device according to Item 81 further includes

[0573] Means for transmitting said processed packets.

[0574] Item 83. A device comprising

[0575] A component for generating configuration information related to proxy computing operations, wherein the configuration information includes packet detection information, packet processing information, and packet forwarding information.

[0576] The packet detection information defines detecting packets received from a local user plane function entity,

[0577] The packet processing information defines the removal of the first outer header from the packet detected according to the packet detection information and the computational processing to be performed on the data of the packet, and wherein

[0578] The packet forwarding information defines adding a second outer header to the packet, the second outer header indicating the local user plane function entity as a destination.

[0579] Item 84. The device according to Item 83 further includes

[0580] Means for sending a configuration message to a network entity providing the proxy computing operation, the configuration message including the configuration information.

[0581] Item 85. The device according to Item 83 or 84 further includes

[0582] components for generating information about agent compute operations, and

[0583] A component for sending a request message including information related to the proxy computing operation, wherein

[0584] The proxy computing operation related information includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about traffic routing to the network entity providing the proxy computing operation.

[0585] Item 86. An apparatus according to Item 85, wherein

[0586] The network access identifier of the network entity providing the proxy computing operation is a local operations access identifier, and the information regarding traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0587] Item 87. A device comprising

[0588] components for generating information about agent compute operations, and

[0589] A component for sending a request message including information related to the proxy computing operation, wherein

[0590] The proxy computing operation related information includes an identifier of the proxy computing operation, a network access identifier of a network entity providing the proxy computing operation, and information about traffic routing to the network entity providing the proxy computing operation.

[0591] Item 88. The device according to Item 87, wherein

[0592] The network access identifier of the network entity providing the proxy computing operation is a local operations access identifier, and the information regarding traffic routing to the network entity providing the proxy computing operation is a network address of the network entity providing the proxy computing operation.

[0593] Item 89. A computer program product comprising a computer executable computer program code, which, when run on a computer, is configured to cause the computer to perform a method according to any one of Items 1 to 6, 7 to 12, 13 to 16, 17 to 20 or 21 to 22.

[0594] Item 90. The computer program product according to Item 89, wherein the computer program product comprises a computer-readable medium, the computer executable computer program code is stored on the medium, and / or wherein the program can be directly loaded into the internal memory of the computer or its processor.

[0595] List of acronyms and abbreviations

[0596] 3GPP Third Generation Partnership Project

[0597] 5GC 5G Core

[0598] 5GS 5G System

[0599] AF application function

[0600] AMF access management function

[0601] BP branch point

[0602] CAN Computational Perception Network

[0603] CATS computing-aware service guidance

[0604] CF calculation function

[0605] CHF billing function

[0606] CU Center (Centralized) Unit

[0607] DN Data Network

[0608] DNAI Data Network Access Identifier

[0609] DU Distributed Unit

[0610] EC Edge Cloud

[0611] FAR forwarding action rules

[0612] INC Network and Computing Integration

[0613] I-UPF intermediate user plane function

[0614] I-SMF intermediate session management function

[0615] LOAI Local Operation Access Identifier

[0616] NAS non-access layer

[0617] NEF network open function

[0618] PCC policy and charging control

[0619] PCF policy control and charging function

[0620] PDR Group Detection Rules

[0621] PDU protocol data unit

[0622] PSA PDU Session Anchor

[0623] RAN Radio Access Network

[0624] RU Radio Unit

[0625] SMF session management function

[0626] UE User Equipment

[0627] ULCL Uplink Classifier

[0628] UPF user plane function

Claims

1. A method comprising: generating a first detection rule and a first action rule associated with the first detection rule, wherein the first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, wherein the first action rule involves adding a first outer header to a packet detected according to the first detection rule, the first outer header comprising information about a service route to a network entity providing a proxy computing operation, and wherein the first action rule further involves forwarding the packet detected according to the first detection rule, and A second detection rule and a second action rule associated with the second detection rule are generated, wherein the second detection rule involves detecting packets received from the network entity providing the proxy computing operation and removing a second outer header from packets detected according to the second detection rule, wherein the second action rule involves forwarding the packets detected according to the second detection rule.

2. The method according to claim 1, further comprising: A request is sent to a third local user plane functional entity associated with the network entity providing the proxy computing operation, the request including the first detection rule, the first action rule, the second detection rule, and the second action rule.

3. The method according to claim 2, further comprising: The third local user plane functional entity is selected based on a network access identifier of the network entity providing the proxy computing operation.

4. A method comprising A request is received from a session management function entity, the request comprising a first detection rule, a first action rule associated with the first detection rule, a second detection rule, and a second action rule associated with the second detection rule, wherein: The first detection rule involves detecting an uplink packet received from an intermediate user plane function entity or a first local user plane function entity and / or detecting a downlink packet received from a session anchor user plane function entity or a second local user plane function entity, The first action rule involves adding a first outer header to a packet detected according to the first detection rule, the first outer header comprising information about a traffic route to a network entity providing a proxy computing operation, and wherein the first action rule further involves forwarding the packet detected according to the first detection rule, The second detection rule involves detecting packets received from the network entity providing the proxy computing operation and removing a second outer header indicating a destination of the packet from the packets detected according to the second detection rule, and wherein, The second action rule relates to forwarding the packet detected according to the second detection rule.

5. The method according to claim 4, further comprising: Send a confirmation response.

6. The method according to claim 4 or 5, further comprising: Receive packets, Match the group with at least one of the following: The first detection rule, or The second detection rule, If the packet matches the first detection rule, applying the first action rule to the packet, and If the packet matches the second detection rule, the second action rule is applied to the packet.

7. A method comprising: receiving a configuration message, wherein the configuration message includes packet detection information, packet processing information, and packet forwarding information, wherein: The packet detection information defines detecting packets received from a local user plane function entity, The packet processing information defines removal of a first outer header indicating a packet destination from a packet detected according to the packet detection information and calculation processing to be performed on data of the packet, and wherein, The packet forwarding information defines adding a second outer header to the packet, the second outer header indicating the local user plane function entity as a destination.

8. A method comprising: Generate configuration information related to the proxy computing operation, the configuration information including packet detection information, packet processing information and packet forwarding information, wherein: The packet detection information defines detecting packets received from a local user plane function entity, The packet processing information defines removal of a first outer header from a packet detected according to the packet detection information and computational processing to be performed on data of the packet, and wherein, The packet forwarding information defines adding a second outer header to the packet, the second outer header indicating the local user plane function entity as a destination.

9. An apparatus comprising: at least one processor, and At least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least perform the method of any one of claims 1-8.

10. A computer program product, comprising a computer executable computer program code, wherein the computer program code, when executed on a computer, is configured to cause the computer to perform the method according to any one of claims 1 to 8.

Images