Enhanced decision-making and configuration for edge computing

Abstract

A network function, element or entity receives S610 a list of candidate data network access identifiers (DNAIs) and, for each candidate DNAI, acquires S620 delay-related information regarding delay be

Description

TECHNICAL FIELD Various example embodiments of this disclosure generally relate to wireless communication technique(s). More specifically (but not exclusively), measures / mechanisms (including, e.g. methods, apparatuses and computer program products) are described for enabling (or otherwise facilitating or realizing) enhancements and / or improvements for edge computing, such as enhanced (e.g., efficient) decision-making and configuration for edge computing. BACKGROUND Examples of mobile or wireless telecommunication technology and systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, fifth generation (5G) radio access technology or new radio (NR) access technology and / or sixth generation (6G) radio access technology. Fifth generation (5G) and sixth generation (6G) wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G and 6G network technology is based on new radio (NR) technology, but the 5G / 6G (or NG) network can also build on E-UTRAN radio. It is estimated that NR may provide bitrates on the order of 10-20 Gbit / s or higher and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (loT). LIST OF ACRONYMS AND ABBREVIATIONS 3 GPP 3rd Generation Partnership Project 5G Fifth Generation 5GC 5G Core 5GS 5G System 6G Sixth Generation 5 AF Application Function AMF Access and mobility Management Function AUSF Authentication Server Function DN Data Network DNAI Data Network Access Identifier 10 E2E End-to-End EAS Edge Application Server EASDF EAS Discovery Function EAS ID EAS Identifier EHE Edge Hosting Environment 15 FQDN Fully Qualified Domain Name HMAC Hashed Message Authentication Code HTTP HyperText Transfer Protocol IP Internet Protocol N3IWF Non-3GPP InterWorking Function 20 NEF Network Exposure Function NFV(I) Network Function Virtualization (Infrastructure) NR New Radio NRF Network Repository Function NSSF Network Slice Selection Function 25 PCF Policy Control Function PDA PDU Session Anchor PDU Packet Data Unit PFCP Packet Forwarding Control Protocol QoS Quality of Service 30 (R)AN (Radio) Access Network SDN Software-Defined Networking SMF Session Management Function STAMP Simple Two-Way Active Measurement Protocol TN GF Trusted Non-3GPP Gateway Function TWAMP Two-Way Active Measurement Protocol UDM Unified Data Management L DP User Datagram Protocol UDR Unified Data Repository UE User Equipment UPF User Plane Function W-AGF Wireless Access Gateway Function SUMMARY Various example embodiments address at least part of issues, problems and / or drawbacks described herein or otherwise recognized by a person skilled in the art in view of this disclosure. Various example embodiments are set out in the claims. Some of the various example embodiments are described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the various example embodiments, nor are they intended to be used to limit the scope of thereof. Other features, aspects, and elements will be recognized by a person skilled in the art in view of this disclosure. According to an example aspect, there is provided a method, comprising: receiving a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, acquiring, based on the delay-related information, access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network, and selecting, based on the access network delays and the data network delays, a target data network access identifier from the list of candidate data network access identifiers and a target edge application server from the at least one candidate edge application server. According to an example aspect, there is provided an apparatus, comprising means for receiving a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, means for acquiring, based on the delay-related information, access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network, and means for selecting, based on the access network delays and the data network delays, a target data network access identifier from the list of candidate data network access identifiers and a target edge application server from the at least one candidate edge application server. According to an example aspect, there is provided an apparatus, comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, acquire, based on the delay-related information, access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network, and select, based on the access network delays and the data network delays, a target data network access identifier from the list of candidate data network access identifiers and a target edge application server from the at least one candidate edge application server. According to an example aspect, there is provided an apparatus, comprising: circuitry configured to receive a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, acquire, based on the delay-related information, access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network, and select, based on the access network delays and the data network delays, a target data network access identifier from the list of candidate data network access identifiers and a target edge application server from the at least one candidate edge application server. According to various developments / modifications, any one of the aforementioned method-related and / or apparatus-related example aspects may include one or more of the following features: the acquiring comprises: obtaining, from the delay-related information, the access network delays, and / or determining, based on assistance information in the delay-related information, the data network delays, the delay-related information comprises, with respect to a candidate edge application server, information indicating the access network delay and assistance information for determining the data network delay, the acquiring comprises: obtaining, from the delay-related information, the access network delay with respect to the candidate edge application server, and / or determining, based on the assistance information, the data network delay with respect to the candidate edge application server, a user plane function entity of the communication network is identified by an IP address on a data network identified by the target data network access identifier, determining a data network delay comprises performing or initiating measurement of the delay between the respective user plane function entity and the respective candidate edge application server using the assistance information, the assistance information comprises information for facilitating measurement of the delay between the respective user plane function entity and the respective candidate edge application server, the measurement facilitating information comprises measurement protocol information about an applicable protocol for the measurement and measurement configuration information about an applicable configuration for the measurement, the measurement protocol information indicates a simple two-way active measurement protocol and / or a two-way active measurement protocol as applicable measurement protocol, the measurement configuration information comprises one or more of protocol configuration information, addressing information, security information and validity information for the measurement and / or a connection for the measurement, the method, functionality, operability or configuration comprises or enables: sending the target data network access identifier and an edge application server identifier of the target edge application server, the method, functionality, operability or configuration comprises or enables: accessing load information with respect to the at least one candidate edge application server, wherein load information indicates a load of the respective candidate edge application server, wherein the target data network access identifier and the target edge application server are selected further based on the load information, the method, functionality, operability or configuration comprises or enables: receiving at least one IP address, each IP address being associated with a user plane function entity, wherein the target data network access identifier and the target edge application server are selected further based on the at least one IP address, the method, functionality, operability or configuration comprises or enables: requesting notification or provisioning of delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay, the requesting is carried out in at least one of a traffic routing influence procedure, a service, operation or procedure for setting up a session with required quality-of-service, a service parameter service, operation or procedure, or an edge application server deployment service, operation or procedure, the method, functionality, operability or configuration is (operable as or in) part of or integrated in a traffic routing influence procedure and / or a user plane management event notification procedure, the method, functionality, operability or configuration is operable at or by an application function entity of the communication network, the list of candidate data network access identifiers and the delay-related information are received from a session management function entity or a network exposure function entity of the communication entity, the target data network access identifier and an edge application server identifier of the target edge application server are sent to a session management function entity or a network exposure function entity of the communication entity, the user equipment is to use an application controlled by an application function entity of the communication network, which is to be delivered by an edge application server of the at least one candidate edge application server, the access network delay is indicative of a delay on N3 and / or N9 reference points, and / or the data network delay is indicative of a delay on a N6 reference point. According to an example aspect, there is provided a method, comprising: sending a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates acquiring access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network. According to an example aspect, there is provided an apparatus, comprising: means for sending a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates acquiring access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network. According to an example aspect, there is provided an apparatus, comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: send a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates acquiring access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network. According to an example aspect, there is provided an apparatus, comprising: circuitry configured to send a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates acquiring access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network. According to various developments / modifications, any one of the aforementioned method-related and / or apparatus-related example aspects may include one or more of the following features: the method, functionality, operability or configuration comprises or enables: receiving a target data network access identifier from the list of candidate data network access identifiers and an edge application server identifier of a target edge application server from the at least one candidate edge application server, the method, functionality, operability or configuration comprises or enables: configuring, based on the target data network access identifier and the edge application server identifier of the target edge application server, a user plane function entity from one or more user plane function entities of the communication network, the delay-related information facilitates: obtaining, from the delay-related information, the access network delays, and / or determining, based on assistance information in the delay-related information, the data network delays, the delay-related information comprises, with respect to a candidate edge application server, information indicating the access network delay and assistance information for determining the data network delay, a user plane function entity of the communication network is identified by an IP address on a data network identified by the target data network access identifier, the delay-related information facilitates determining a data network delay by performing or initiating measurement of the delay between the respective user plane function entity and the respective candidate edge application server using the assistance information, the assistance information comprises information for facilitating measurement of the delay between the respective user plane function entity and the respective candidate edge application server, the measurement facilitating information comprises measurement protocol information about an applicable protocol for the measurement and measurement configuration information about an applicable configuration for the measurement, the measurement protocol information indicates a simple two-way active measurement protocol and / or a two-way active measurement protocol as applicable measurement protocol, the measurement configuration information comprises one or more of protocol configuration information, addressing information, security information and validity information for the measurement and / or a connection for the measurement, the method, functionality, operability or configuration comprises or enables: sending at least one IP address, each IP address being associated with a user plane function entity, the method, functionality, operability or configuration comprises or enables: acquiring assistance information for determining the data network delay with respect to a candidate edge application server, the assistance information for determining the data network delay is acquired from a user plane function entity and / or a network repository function entity of the communication network, the assistance information for determining the data network delay is acquired as part of an association setup or update procedure with a user plane function entity, such as a packet forwarding control protocol association setup or update procedure, and / or a network function discovery service, operation or procedure with a network repository function entity of the communication network, the method, functionality, operability or configuration comprises or enables: receiving a request for notification or provisioning of delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay, the method, functionality, operability or configuration comprises or enables: upon receiving the request, setting a condition for sending the delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay, wherein the delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay are sent when the condition is met, the method, functionality, operability or configuration comprises or enables: upon receiving the request, setting the respective user plane function entity for measurement of the delay between the respective user plane function entity and the respective candidate edge application server, the request is received in at least one of a traffic routing influence procedure, a service for setting up a session with required quality-of-service, a service parameter service, or an edge application server deployment service, the method, functionality, operability or configuration is (configured to be operable in or as) part of or integrated in a traffic routing influence procedure and / or a user plane management event notification procedure, the method, functionality, operability or configuration is operable at or by a session management function entity of the communication network, the list of candidate data network access identifiers and the delay-related information are sent to an application function entity or a network exposure function entity of the communication entity, a target data network access identifier and an edge application server identifier of a target edge application server are received from an application function entity or a network exposure function entity of the communication entity, the user equipment is to use an application controlled by an application function entity of the communication network, which is to be delivered by an edge application server of the at least one candidate edge application server, the user plane function entity is configured as a packet data unit session anchor of a packet data unit session in the communication network and an endpoint of an interface between the communication network and the data network of the target edge application server, the access network delay is indicative of a delay on N3 and / or N9 reference points, and / or the data network delay is indicative of a delay on a N6 reference point. According to an example aspect, there is provided a system comprising at least two of the apparatuses according to any one of the aforementioned apparatus-related example aspects (and / or any development / modification thereof) According to an example aspect, there is provided a computer-readable medium comprising program instructions for causing an apparatus (e.g. an apparatus according to any one of the aforementioned apparatus-related example aspects (and / or any development / modification thereof)) to perform at least a method according to any one of the aforementioned method-related example aspects (and / or any development / modification thereof). According to an example aspect, there is provided a computer program product comprising (computer-executable) computer program code which, when the program code is executed (or run) on a computer or the program is run on a computer (e.g. a computer of an apparatus according to any one of the aforementioned apparatus-related example aspects (and / or any development / modification thereof)), is configured to cause the computer to carry out at least a method according to any one of the aforementioned method-related example aspects (and / or any development / modification thereof). The computer program product may comprise or may be embodied as a (tangible / non-transitory) computer-readable (storage) medium or the like, on which the computer-executable computer program code is stored, and / or the program is directly loadable into an internal memory of the computer or a processor thereof. The term “non-transitory,” as used herein, is a limitation of the medium itself (referring to e.g. a tangible medium, not a signal) as opposed to a limitation on data storage persistency (e.g. RAM vs. ROM). Further developments and / or modifications of the aforementioned example aspects are set out in the following. By way of example embodiments, technique(s) for (e.g. enabling or otherwise facilitating or realizing enhancements and / or improvements for) edge computing, such as enhanced (e.g., efficient) decision-making and configuration for edge computing, may be provided. This summary is intended to provide a brief overview of some of the aspects (and features thereof) according to the various example embodiments of the disclosure. Accordingly, it will be appreciated that the above-described aspects (and features thereof) are merely examples and should not be construed to narrow the scope of the various example embodiments or disclosure in any way. Other features, aspects, and advantages of the disclosure will become apparent from the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS In the following, various example embodiments will be described with reference to the accompanying drawings, in which FIG. 1 shows a schematic diagram of an example (mobile / wireless) communication system or network; FIG. 2 shows a schematic diagram of an example wireless device or entity; FIG. 3 shows a schematic diagram of an example network node or entity; FIG. 4 shows a schematic diagram of an example architecture of a 5G system; FIG. 5 shows a schematic diagram of an example architecture of a 5G system supporting edge computing; FIG. 6 shows a flowchart of an example method or process; FIG. 7 shows a flowchart of an example method or process; FIG. 8 shows a schematic diagram illustrating various delays in an example architecture; FIG. 9 shows a sequence diagram of an example procedure; FIG. 10 shows a sequence diagram of an example procedure; FIG. 11 shows a schematic block diagram illustrating a structure of apparatuses. DETAILED DESCRIPTION Various example embodiments are herein described with reference to particular non-limiting and illustrative examples. A person skilled in the art will appreciate that these various example embodiments are by no means limited to these non-limiting and illustrative examples, and may be more broadly applied. References in the specification to "one embodiment," "an embodiment," "an example embodiment," "some example embodiments," "certain example embodiments," "various example embodiments," and so forth, indicate that the referenced embodiment(s) may include particular feature(s), structure(s), or characteristic(s), but every referenced embodiment or example embodiment may not necessarily include the particular feature(s), structure(s), or characteristic(s). Moreover, such phrases are not necessarily referring to the same embodiment or example embodiment. Further, when particular feature(s), structure(s), or characteristic(s) are described in connection with an embodiment or an example embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with any other embodiments or example embodiments whether or not such combination(s) are explicitly described. It is to be noted that the detailed description, at times, refers to one or more specifications being used as non-limiting and illustrative examples for certain architectures, network configurations and system deployments. More specifically, the detailed description makes reference to 3GPP standards, being used as non-limiting and illustrative examples. As such, the example embodiments provided herein can specifically employ terminology which is directly related thereto. Such terminology is only used in the context of the non-limiting and illustrative examples, and is not intended to limit the example embodiments in any way. Rather, any other system configuration or deployment may be utilized while complying with what is described herein and / or example embodiments are applicable to it. For example, various example embodiments are applicable in any (e.g., mobile / wireless) communication system, such as a 5G / NR system and a next-generation / future system beyond 5G. For example, various example embodiments are applicable in a 3GPP-standardized mobile / wireless communication system of Release 19 onwards. Furthermore, even though reference to 5G / NR is made, other types of access / system / network are supported / covered as well, such as future 3GPP radio / 6G but also non-3GPP access to 3GPP Core (such as e.g. Untrusted non-3GPP access to 3GPP core using e.g. N3IWF, Trusted non-3GPP access to 3GPP core using e.g. TNGF, wireline access to 3GPP core using e.g. W-AGF), or the like. When reference is made to particular terminology specific for any such example system, these references are to be understood / construed to be more generally applicable in a corresponding, similar or equivalent meaning. More specifically, when reference is made to some network function, entity or element of a 5G / NR or 3GPP system, it shall be understood / construed that any network function, entity or element of any system is meant or encompassed, which has or exhibits a corresponding, similar or equivalent characteristic, functionality, purpose or the like. As an illustrative but non-exhaustive example, a reference to an application function or session management function of a 5G / NR or 3GPP communication network shall mean or encompass any network function, entity or element of any communication network, which has or exhibits a characteristic, functionality, purpose or the like, which is corresponding, similar or equivalent to that of the referenced application or session management function, respectively. Hereinafter, various example embodiments are described using several variants and / or alternatives. It is generally to be noted that, according to certain implementations or constraints, all of the described variants and / or alternatives may be provided alone or in any conceivable combination (e.g. also including combinations of individual features of these various variants and / or alternatives). As used herein, the words “comprising” and “including” should be understood as not limiting the example embodiments to consist of only those features that have been mentioned, and example embodiments may also contain, among other things, e.g. features, structures, units, modules, or the like, that have not been specifically mentioned. As used herein, “at least one of the following: ” and “at least one of ” and similar expressions, like “one or more of’, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements. As used herein, the expression “and / or” means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements. As used herein, unless explicitly stated to the contrary, performing a step / operation / functionality “in response to A” does not indicate that the step / operation / functionality is performed immediately after “A” occurs as one or more intervening steps / operations / functionalities may be included therebetween. Analogously, performing a step / operation / functionality “based on A” does not indicate that the step / operation / functionality is performed solely based on “A”, as the referenced step / operation / functionality may be further based on one or more other conditions (such as “B”) in addition to “A”. As used herein, according to various example embodiments, any operations of sending or receiving may comprise actual transmission or communication operations, e.g. transmitting or communicating associated information, data, signals or messages, but may additionally or alternatively comprise related processing operations, e.g. preparing / generating / issuing associated information, data, signals or messages before sending and / or obtaining / handling / processing of associated information, data, signals or messages after receiving. For example, sending an information or data at / by an entity may comprise generating / issuing and / or transmitting / communicating thereof or a corresponding signal or message in / at / by the entity, and receiving a signal or message at / by an entity may comprise obtaining / handling and / or processing thereof or a corresponding information or data in / at / by the entity. As used herein, a signal or message may refer to and / or encompass any kind of corresponding information, data, signal or the like. In the drawings, it is to be noted that lines / arrows interconnecting individual blocks or entities are generally meant to illustrate an operational coupling there-between, which may be a physical and / or logical coupling, which on the one hand is implementation-independent (e.g. wired or wireless) and on the other hand may also comprise an arbitrary number of intermediary functional blocks or entities not shown. In flowcharts or sequence diagrams, the illustrated order of operations or actions is generally non-limiting and illustrative, and any other order of respective operations or actions is conceivable, if feasible. Various example embodiments relate to considerations in a (e.g. mobile / wireless) communication system or network, such as a 5G / NR system and a next-generation / future system beyond 5G. For example, various example embodiments are applicable in a 3GPP-standardized mobile / wireless communication system or network of Release 19 onwards. Such considerations relate to edge computing. Edge computing is a concept that enables (or otherwise facilitates or realizes) services to be hosted close to the service consumers and may provide benefits, such as enhanced (e.g., efficient) service delivery with reduction in end-to-end latency and decreased load on the transport network. With edge computing, a user equipment residing in a communication network can use an application controlled by an application function entity of the communication network, wherein the application is to be delivered by an edge application server of a data network connected to the communication system. Further, such considerations may relate to enhancements and / or improvements for edge computing, such as enhanced (e.g., efficient) decision-making and configuration for edge computing. Before explaining example embodiments in further detail, certain general aspects of a (mobile / wireless) communication system or network are briefly explained with reference to FIGS. 1 to 3 to assist in understanding the technology underlying the described example embodiments. FIG. 1 illustrates an example of a (mobile / wireless) communication system or network 100 that may be used for wireless communications. Communication system or network 100 includes wireless devices or entities, such as UEs 110 (e.g., 110A-110C), and network nodes or entities, such as radio access nodes 120 (e.g., 120A-120B) (e.g., eNBs, gNBs, and so forth), connected to one or more network nodes or entities 130 via an interconnecting network 125. Communication system or network 100 may use any suitable deployment scenarios. UEs 110 within coverage area 115 may each be capable of communicating directly with radio access nodes 120 over a wireless interface. In some example embodiments, UEs 110 may also be capable of communicating with each other via device-to-device (D2D) communication. As an example, UE 110A may communicate with radio access node 120A over a wireless interface. That is, UE 110A may transmit wireless signals to and / or receive wireless signals from radio access node 120A. The wireless signals may contain voice traffic, data traffic, control signals, and / or any other suitable information. As used herein, the term "user equipment" (UE) has the full breadth of its ordinary meaning and may refer to any type of wireless device or entity which can communicate with a network node or entity and / or with another UE in a cellular or mobile or wireless / mobile communication system. Examples of UE are target device, D2D UE, machine type UE or UE capable of machine-to-machine (M2M) communication, personal digital assistant, tablet, mobile terminal, smartphone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, ProSe UE, vehicle-to-vehicle (V2V) UE, V2X UE, machine-type-communication (MTC) UE, eMTC UE, FeMTC UE, UE Cat 0, UE Cat Ml, narrow band loT (NB-Internet-of-Things) UE, UE Cat NB1, and so forth. Example embodiments of a UE are described in more detail below with respect to FIG. 2. In some example embodiments, an area of wireless signal coverage 115 associated with a radio access node 120 may be referred to as a cell. However, particularly with respect to the fifth generation (5G) / New Radio (NR) mobile communication concepts, beams may be used instead of cells and, as such, it is important to note that concepts described herein are equally applicable to both cells and beams. With respect to a beam-based mobile communication system, the radio access node 120 (base station) may transmit a beamformed signal to the UE 110 in one or more transmit directions (transmission beam, Tx beam). The UE 110 may receive the beamformed signal from the base station 120 in one or more receive directions (reception beam, Rx beam). The UE 110 may also transmit a beamformed signal to the base station 120 in one or more directions and the base station 120 may receive the beamformed signal from the UE 110 in one or more directions. The base station 120 and the UE 110 may determine the best receive and transmit directions, e.g., best in the sense of these directions leading to the highest link quality or fulfilling other quality conditions in the most suitable manner, for each of the base station / UE pairs. The interconnecting network 125 may refer to any interconnecting system capable of transmitting audio, video, signals, data, messages, and so forth, or any combination of the preceding. The interconnecting network 125 may include all or a portion of a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network, such as the Internet, a wireline or wireless network, an enterprise intranet, or any other suitable communication link, including combinations thereof. In some example embodiments, the network node 130 may be a core network node, managing the establishment of communication sessions and other various other functionalities for UEs 110. Examples of network node 130 may include mobile switching center (MSC), MME, serving gateway (SGW), packet data network gateway (PGW), operation and maintenance (O&M), operations support system (OSS), SON, positioning node (e.g., Enhanced Serving Mobile Location Center, E-SMLC), location server node, MDT node, and so forth. UEs 110 may exchange certain signals with the network node 130 using the non-access stratum (NAS) layer. In non-access stratum signaling, signals between UEs 110 and the network node 130 may be transparently passed through the radio access network. In some example embodiments, radio access nodes 120 may interface with one or more network nodes 130 over an internode interface. As used herein, the term "network node or entity" has the full breadth of its ordinary meaning and may correspond to any type of radio access node (or radio network node) or any network node, which can communicate with a UE and / or with another network node in a cellular or mobile or wireless communication system. Examples of network nodes are NodeB, MeNB, SeNB, a network node may belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio access node, such as MSR BS, eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission point, transmission node, RRU, RRH, node in distributed antenna system (DAS), core network node (e g., MSC, MME, and so forth), O&M, OSS, Self-organizing Network (SON), positioning node (e g., E-SMLC), MDT, test equipment, and so forth. Example embodiments of a network node are described in more detail below with respect to FIG. 3. In some example embodiments, radio access node 120 may be a distributed radio access node. The components of the radio access node 120, and their associated functions, may be separated into two main units (or sub-radio network nodes) which may be referred to as the central unit (CU) and the distributed unit (DU). Different distributed radio network node architectures are possible. For instance, in some architectures, a DU may be connected to a CU via dedicated wired or wireless link (e.g., an optical fiber cable) while in other architectures, a DU may be connected a CU via a transport network. Also, how the various functions of the radio access node 120 are separated between the CU(s) and DU(s) may vary depending on the implemented architecture. Example wireless communication systems are architectures standardized by the 3rd Generation Partnership Project (3GPP). A latest 3GPP based development is often referred to as the longterm evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radioaccess technology (RAT). The various development stages of the 3GPP specifications are referred to as releases. More recent developments of the LTE are often referred to as LTE Advanced (LTE-A). The LTE (LTE-A) employs a radio mobile architecture known as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a core network known as the Evolved Packet Core (EPC). Base stations of such systems are known as evolved or enhanced Node Bs (eNBs) and provide E-UTRAN features, such as user plane Packet Data Convergence / Radio Link Control / Medium Access Control / Physical layer protocol (PDCP / RLC / MAC / PHY) and control plane Radio Resource Control (RRC) protocol terminations towards the communication devices. Other RAT examples comprise those provided by base stations of systems that are based on technologies, such as WLAN and / or Worldwide Interoperability for Microwave Access (WiMax). A base station can provide coverage for an entire cell or similar radio service area. Core network elements include Mobility Management Entity (MME), Serving Gateway (S-GW) and Packet Gateway (P-GW). An example of a suitable communications system is the 5G or NR concept. Network architecture in NR may be similar to that of LTE-A. Base stations of NR systems may be known as next generation Node Bs (gNBs). Changes to the network architecture may depend on the support for various radio technologies and finer Quality of Service (QoS)t, and some on-demand requirements for QoS levels to support Quality of Experience (QoE) of user point of view. Also network aware services and applications, and service and application aware networks may bring changes to the architecture. Those are related to Information Centric Network (ICN) and User-Centric Content Delivery Network (UC-CDN) approaches. NR may use multiple input-multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for enhanced (e.g., better, increased, and so forth) coverage and data rates. Future networks may utilize network functions virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program code using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications, this may mean node operations are to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes, or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be non-existent. An example 5G core network (CN) comprises functional entities. The CN is connected to a UE via the radio access network (RAN). An UPF (User Plane Function) whose role is called PSA (PDU Session Anchor) may be responsible for forwarding frames back and forth between the DN (data network) and the tunnels established over the 5G towards the UEs exchanging traffic with the data network (DN). The UPF is controlled by an SMF (Session Management Function) that receives policies from a PCF (Policy Control Function). The CN may also include an AMF (Access &Mobility Function). Generally, all concepts disclosed herein may be applicable to different communication networks, comprising but not limited to LTE, LTE-A, 5G, 5G advanced, 6G, and other future or already implemented networks. FIG. 2 is a schematic diagram of an example wireless device, UE 110, according certain example embodiments. UE 110 may include one or more of at least one transceiver 210, at least one processor 220, at least one memory 230, and at least one network interface 240. In certain example embodiments, the transceiver 210 facilitates transmitting wireless signals to and receiving wireless signals from radio access node 120 (e.g., via transmitter(s) (Tx), receiver(s) (Rx) and antenna(s)). The processor(s) 220 execute instructions to provide some or all of the functionalities described herein as being provided by a wireless device / entity or UE, and the memory 230 stores the instructions executed by the processor(s) 220. In some embodiments, the processor(s) 220 and the memory 230 form processing circuitry. The processor(s) 220 may include any suitable combination of hardware to execute instructions and manipulate data to perform some or all of the described functions of a wireless device or entity, such as the functions of UE 110 described herein. In some embodiments, the processor(s) 220 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs) and / or other logic. The memory 230 is generally operable to store instructions, such as a computer program, software, an application including one or more of logic, rules, algorithms, code, tables, and so forth and / or other instructions capable of being executed by a processor 220. Examples of memory 230 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or or any other volatile or non-volatile, non- transitory computer-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processor 220 of UE 110. For example, the memory 230 includes computer program code causing the processor 220 to perform processing according to any corresponding methods (or portions thereof) described herein. The network interface 240 is communicatively coupled to the processor 220 and may refer to any suitable device operable to receive input for UE 110, send output from UE 110, perform suitable processing of the input or output or both, communicate to other devices, or any combination thereof. The network interface 240 may include appropriate hardware (e.g., port, modem, network interface card, and so forth) and software, including protocol conversion and data processing capabilities, to communicate through a network. Other example embodiments of UE 110 may include additional components beyond those shown in FIG. 2 that may be responsible for providing certain aspects of the wireless device’s functionalities, including any of the functionalities described herein and / or any additional functionalities (including any functionality to support the mechanisms according to the disclosure). As an example, UE 110 may include input devices and circuits, output devices, and one or more synchronization units or circuits, which may be part of the processor(s) 220. Input devices include mechanisms for entry of data into UE 110. For example, input devices may include input mechanisms, such as a microphone, input elements, a display, and so forth. Output devices may include mechanisms for outputting data in audio, video and / or hard copy format. For example, output devices may include a speaker, a display, and so forth. In certain example embodiments, the wireless device UE 110 may comprise a series of modules configured to implement the functionalities of the wireless device described herein. It will be appreciated that the various modules may be implemented as combination of hardware and software, for instance, the processor, memory, and transceiver(s) of UE 110 shown in FIG. 2. Certain example embodiments may also include additional modules to support additional and / or optional functionalities. FIG. 3 is a schematic diagram of an example radio access node 120 or network node or entity 130 according to certain example embodiments. Radio access node 120 or network node or entity 130 may include one or more of at least one transceiver 310, at least one processor 320, at least one memory 330, and at least one network interface 340. In certain example embodiments, the transceiver(s) 310 facilitate transmitting wireless signals to and receiving wireless signals from wireless devices, such as UE 110 (e.g., via transmitter(s) (Tx), receiver(s) (Rx), and antenna(s)). The processor(s) 320 execute instructions to provide some or all of the functionalities described herein as being provided by the radio access node 120 or the network node or entity 130, the memory 330 stores the instructions executed by the processor 320. In some example embodiments, the processor(s) 320 and the memory 330 form processing circuitry. The network interface(s) 340 can communicate signals to backend network components, such as a gateway, switch, router, Internet, Public Switched Telephone Network (PSTN), core network nodes or radio network controllers, and so forth. The processor 320 can include any suitable combination of hardware to execute instructions and manipulate data to perform some or all of the described functions of the radio access node 120 or the network node or entity 130, such as those described herein. In some example embodiments, the processor(s) 320 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs) and / or other logic. The memory 330 is generally operable to store instructions, such as a computer program, software, an application including one or more of logic, rules, algorithms, code, tables, and so forth and / or other instructions capable of being executed by the processor(s) 320. Examples of memory 330 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or or any other volatile or non-volatile, non- transitory computer-readable and / or computer-executable memory devices that store information. For example, the memory 330 includes computer program code causing the processor 320 to perform processing according to any corresponding methods (or portions thereof) described herein. In certain example embodiments, the network interface(s) 340 are communicatively coupled to the processor(s) 320 and may refer to any suitable device operable to receive input for the radio access node 120 or the network node or entity 130, send output from the radio access node 120 or the network node or entity 130, perform suitable processing of the input or output or both, communicate to other devices, or any combination of the preceding. The network interface 340 may include appropriate hardware (e.g., port, modem, network interface card, and so forth) and software, including protocol conversion and data processing capabilities, to communicate through a network. Other example embodiments of the radio access node 120 or the network node or entity 130 can include additional components beyond those shown in FIG. 3 that may be responsible for providing certain aspects of the node’s functionalities, including any of the functionalities described herein and / or any additional functionalities (including any functionality to support the solutions described herein). The various different types of radio access nodes or network nodes may include components having the same physical hardware but configured (e.g., via programming) to support different radio access technologies, or may represent partly or entirely different physical components. Processors, interfaces, and memory similar to those described with respect to FIG. 3 may be included in other nodes or entities (such as UE 110, radio access node 120, and so forth). Other nodes or entities may optionally include or not include a wireless interface (such as the transceiver(s) described in FIG. 3). In certain example embodiments, the radio access node 120 or the network node or entity 130 may comprise a series of modules configured to implement the functionalities of the radio access node 120 or the network node or entity 130 described herein. It will be appreciated that the various modules may be implemented as combination of hardware and software, for instance, the processor(s), memory, and transceiver(s) of the radio access node 120 or the network node or entity 130 shown in FIG. 3. Certain example embodiments may also include additional modules to support additional and / or optional functionalities. Before referring to FIGS. 6 to 11 and describing specifics of technique(s) for (e.g. enabling / facilitating / realizing enhancements and / or improvements for) edge computing, such as enhanced (e.g., efficient) decision-making and configuration for edge computing, some additional information and aspects related to certain example embodiments will be provided. It should be noted that all concepts described herein, although described in a specific manner or context, may be more generally applicable, e.g. in another specific manner or context, as will be apparent to the skilled person. FIGs. 4 and 5 show example architectures which may build the network / system basis for some example embodiments of the technique(s) disclosed herein. FIG. 4 shows a schematic diagram of an example architecture of a 5G system, or a 5GS architecture. In FIG. 4, the User Plane, i.e. the network functions, entities and / or elements involved in the transport of user data, is shown at the bottom part, whereas the upper part shows the Control Plane, i.e. the network functions, entities and / or elements involved in control and / or signaling. FIG. 4 depicts network functions, entities or elements of a communication network (which may also be referred to or regarded as an access network), such as (R)AN, UPF, SMF, AMF, AUSF, NSSF, NEF, NRF, PCF, UDM and AF, a user equipment (UE) which may be considered to be part of or residing in the communication network, and a data network (DN) connected to the communication network. Further, interfaces (which may also be referred to as service interfaces or reference points), such as Nl, N2, N3, N4, N6, N9 (N9 being an interface between different UPFs), and so forth are depicted. The architecture, nodes and interfaces may be defined in accordance with a standard, such as 3GPP TS 23.501, although other standards or configurations may be used. FIG. 5 shows a schematic diagram of an example architecture of a 5G system, or a 5GS architecture, supporting edge computing. In view of their similarity, reference is made to the description of FIG. 4 above for details of FIG. 5. It is to be noted that the UPF represents or is configured as a PDU session anchor (PSA) of a PDU session in the communication network and an endpoint of the N6 interface between the communication network and (a local part of) the data network of one or more edge application servers (EAS), wherein any EAS is configured to deliver (or execute, process, and so forth) an application which is controlled by the AF and to be used by the UE. The architecture, nodes and interfaces may be defined in accordance with a standard, such as 3GPP TS 23.548, although other standards or configurations may be used. Irrespective of the exemplifying illustrations of FIGs. 4 and 5, it is to be noted that not all nodes and / or interfaces are required, and / or the architectures of FIGs. 4 and 5 or elements thereof may be combined, and / or other architectures, nodes and interfaces are also applicable for various example embodiments of the technique(s) disclosed herein. The technique(s) disclosed herein generally refers to enhancements and / or improvements for edge computing in a communication system. For example, in the context of a 5G / NR system, the technique(s) disclosed herein refers to enhancements and / or improvements for support of edge computing in a 5G system or core network. This may include, for example, the aspect how to support an enhanced (e.g., more efficient) Edge Hosting Environment (EHE) information management and related EAS Discovery, which may include a consideration whether and how to take into account N6 delay between local PSA and EAS for local UPF and EAS (re)selection, and possibly also whether EAS load is to be taken into account. In this context, the technique(s) disclosed herein may be regarded to at least in part address issues in terms of local UPF and EAS (re)selection, including considerations as to which information could / should be used for this purpose, e.g. N6 delay and / or EAS load. This is described in more detail hereinafter. Application services (relating to delivery, execution or processing of an application) often create multiple service instances. The service instances are usually geographically distributed to multiple sites, and a single site may support multiple instances of a service. High data rate low latency services, e.g. cloud gaming requiring high data rate and low latency communication, depend not only on network metrics, such as bandwidth and latency, but also compute metrics, such as processing, storage capabilities, and capacity as indicators for EAS load. When multiple candidate paths to an application service (or EAS delivering, executing or processing an application) are available for selection of an optimal service instance, e.g., the topologically closest path may not always meet the service specific requirements and metrics. For instance, some of the available links may be congested. In Rel-18, 5GS provides support for means to determine, to report and to expose UE on-path congestions status, data rate information and round-trip delay between UE and PSA UPF. However, no means are defined to also consider above metrics on data network (e.g., N6, such as N6 delay between local PSA and EAS, EAS load) when multiple EAS instance(s) are available for selection to provide an enhanced (e.g., best possible) E2E user experience. In view thereof, it is worthwhile to study whether and how to take into account, e.g. EAS load and / or N6 delay between local PSA and EAS for local UPF and EAS (re)selection. Such study may include one or more of the following items. - How to enable (or otherwise facilitate or realize) 5GC and / or a third party trusted and / or non-trusted Application Function to make most suitable decision in selecting local UPF and EAS considering E2E delay that includes delay between a candidate N6 interface of the 5GS and a candidate EAS. - Which information between the local PSA and EAS (e.g. EAS load, N6 delay information) and at which level is to be considered for local UPF (re-) sei ection and EAS (re)discovery. - How to obtain above information in 5GS. How to manage and handle above information (e.g. as part of edge data network and EAS related information) in 5GS. - Whether and how 5GS to expose above information? - Whether and how to take into account above information for local UPF (re-) sei ection and EAS (re-)discovery. Accordingly, there is room for enhancement and / or improvement in this regard, and the technique(s) disclosed therein refers to at least part of such aspects, issues or considerations which are exemplified above in the context of a 5G / NR system. Hereinafter, various example embodiments of the disclosure are further explained. FIG. 6 shows a flowchart of an example method or process according to at least one example embodiment. This example method or process may be performed or carried out at / by an apparatus. The apparatus may implement (at least in part) or, stated in other words, the method or process may be a method or process of (or, stated in other words, operable or for use in / by) an application function (AF) or AF entity as an example of a network function, entity or element of a communication system. As shown in FIG. 6, the method or process comprises a step / operation (S610) of receiving a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, a step / operation (S620) of acquiring (or deriving or the like), based on the delay-related information, access network delays and data network delays, and a step / operation (S630) of selecting, based on the access network delays and the data network delays, a target data network access identifier from the list of candidate data network access identifiers and / or a target edge application server from the at least one candidate edge application server. It is to be noted that the selecting in step / operation S630 may refer to or encompass initial or subsequent selection, e.g. (re)selection of DNAI and / or EAS, initial or subsequent discovery, e.g. (re)discovery of EAS, and / or the like. It is to be noted that the (selected) target data network access identifier may identify a data network where the (selected) target edge application server is located or with which the (selected) target edge application server is associated. A user plane function entity of the communication network may be identified by an IP address on (or for, with respect to, and so forth) a data network identified by the target data network access identifier (e.g., a network where the (selected) target edge application server is located or with which the (selected) target edge application server is associated). As shown in FIG. 6, the method or process may, e.g. as or as part of the acquiring step / operation S620, comprise a step / operation (S622) of obtaining the access network delays, and / or a step / operation (S624) of determining the data network delays. In step / operation S622, the access network delays may be obtained from the delay-related information. In step / operation S624, the data network delays may be determined (e.g. measured) based on assistance information in the delay-related information. The delay-related information may comprise corresponding information with respect to a candidate edge application server such that the access network delay with respect to the candidate edge application server may be obtained from (information in) the delay-related information and / or the data network delay with respect to the candidate edge application server may be determined (e.g. measured) based on (assistance information in (or, as part of)) the delay-related information. As shown in FIG. 6, the method or process may further comprise a step / operation (S640) of receiving a sending the (selected) target data network access identifier and an edge application server identifier of the (selected) target edge application server. Although not shown in FIG. 6, the method or process may further comprise a step / operation of accessing load information with respect to the at least one candidate edge application server, wherein load information indicates a load of the respective candidate edge application server. For example, at / for an AF, which constitutes, participates or is contained in an edge hosting environment (EHE) of / for or with a particular EAS, the load of this particular EAS of the same EHE is accessible, e.g., locally available, evident or derivable for the AF. Then, the target data network access identifier and the target edge application server may be selected further based on the load information (in addition to other available information). Although not shown in FIG. 6, the method or process may further comprise a step / operation of receiving at least one IP address, each IP address being associated with a user plane function entity. For example, IP addresses may be associated with one or more of (candidate) UPFs or PSA-UPFs. Then, the target data network access identifier and the target edge application server may be selected further based on the at least one IP address (in addition to other available information). Although not shown in FIG. 6, the method or process may further comprise a step / operation requesting notification or provisioning of delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay. For example, such a request may be carried out in a traffic routing influence procedure, a service, operation or procedure for setting up a session with required quality-of-service, a service parameter service, operation or procedure, and / or an edge application server deployment service, operation or procedure. Upon such a request, the requested delay-related information and / or assistance information may be received in the receiving step / operation S610. FIG. 7 shows a flowchart of an example method or process according to at least one example embodiment. This example method or process may be performed or carried out at / by an apparatus. The apparatus may implement (at least in part) or, stated in other words, the method or process may be a method or process of (or, stated in other words, operable or for use in / by) a session management function (SMF) or SMF entity as an example of a network function, entity or element of a communication system. For at least part of the illustrated method or process, the apparatus may implement (at least in part) or, stated in other words, the at least of the method or process may be a method or process of (or, stated in other words, operable or for use in / by) a network exposure function (NEF) or NEF entity as an example of a network function, entity or element of a communication system. As shown in FIG. 7, the method or process comprises a step / operation (S710) of sending a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server. As shown in FIG. 7, the method or process may further comprise a step / operation (S720) of receiving a target data network access identifier from the list of candidate data network access identifiers and / or an edge application server identifier of a target edge application server from the at least one candidate edge application server. After such a receiving step / operation, the method or process may further comprise a step / operation (S730) of configuring, based on the target data network access identifier and the edge application server identifier of the target edge application server, a user plane function entity from one or more user plane function entities of the communication network. Although not shown, after such a receiving step / operation, the method or process may alternatively comprise a step / operation of sending (forwarding) the (received) target data network access identifier and the (received) edge application server identifier. It is to be noted that the configuring in step / operation S730 may refer to or encompass initial or subsequent configuration, e.g. (re)configuration of UPF or PSA-UPF, initial or subsequent selection, location, addition, removal or change, e.g. (re)selection, (re)location, (re)addition, (re)removal or (re)change of UPF or PSA-UPF, and / or the like. Although not shown in FIG. 7, the method or process may further comprise a step / operation of sending at least one IP address, each IP address being associated with a user plane function entity. For example, IP addresses may be associated with one or more of (candidate) UPFs or PSA-UPFs. Although not shown in FIG. 7, the method or process may further comprise a step / operation of acquiring (or obtaining or the like) assistance information for determining the data network delay with respect to a candidate edge application server. Thereupon, the requested assistance information may be sent in the sending step / operation S710. In one example, the assistance information for determining the data network delay may be acquired (or obtained or the like) from a UPF, e.g. in any one of the example architectures of FIGs. 4 and 5. For example, the assistance information for determining the data network delay may be acquired (or obtained or the like) as part of an association setup or update procedure with a UPF, such as a PFCP association setup or update procedure. In another example, the assistance information for determining the data network delay may be acquired (or obtained or the like) from a NRF, e.g. in any one of the example architectures of FIGs. 4 and 5. For example, the assistance information for determining the data network delay may be acquired (or obtained or the like) as part of a network function discovery service, operation or procedure with a NRF of the communication network. Although not shown in FIG. 7, the method or process may further comprise a step / operation of receiving a request for notification or provisioning of delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay. Upon such a request, the requested delay-related information and / or assistance information may be sent in the sending step / operation S710. Although not shown in FIG. 7, the method or process may further comprise a step / operation of receiving a request for notification or provisioning of delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay. For example, upon receiving such a request, a condition for sending the delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay may be set, wherein the delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay may be sent when the condition is met. For example, the condition for sending the delay-related information and / or assistance information may refer to or comprise an AF notification trigger or condition, as described in connection with FIG. 9 below. For example, upon receiving such request, the respective user plane function entity for measurement of the delay between the respective user plane function entity and the respective candidate edge application server may be set. Such request may be received, for example, in a traffic routing influence procedure, a service for setting up a session with required quality-of-service, a service parameter service, and / or an edge application server deployment service. In any one of the methods or processes of FIGs. 6 and 7, the delay-related information enables (or otherwise facilitates or realizes) acquiring (or deriving) access network delays and data network delays. For example, access network delays may (e.g. directly) be obtained (from the delay-related information) and / or data network delays may be determined (e.g. measured) (based on (assistance information in) the delay-related information). An access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network (which is connected to the communication network). An end-to-end (E2E) delay between the user equipment one of the at least one candidate edge application server comprises or is composed of an access network delay and a data network delay, both the access network delay and the data network delay being associated with the same user plane function entity. FIG. 8 shows a schematic diagram illustrating various delays in an example architecture. The example architecture of FIG. 8 can be or be based on any one of the example architectures of FIGs. 4 and 5. As shown in FIG. 8, it is assumed, for example, that a communication network (which may also be referred to or regarded as an access network) comprises a (R)AN and two UPFs, namely UPF1 and UPF2, wherein a UE resides or is served by the communication network, and the communication network is connected to two data networks (which may also be referred to or regarded as (e.g. local) data network parts), namely DN1 and DN2, wherein DN1 comprises edge application server EASI and DN2 comprises edge application server EAS2. The UE may be assumed to (try to) use an application which can be delivered (or executed, processed, and so forth) by any one of EASI and EAS2 (such that any one of EASI and EAS2 can be considered or referred to as candidate EAS), while being controlled by an AF (which is not shown). Further, it is assumed, for example, that it is possible that (e.g. the 3GPP Core can ensure / enable / facilitate / realize that) the UE has connection / link to any of the two UPFs, namely UPF1 and UPF2, via the (R)AN, UPF1 has a connection / link to EASI in DN1 via DNAI1-1 and a connection / link to EAS2 in DN2 via DNAI1-2, and UPF2 has a connection / link to EAS2 in DN2 via DNAI2-2. As evident from FIG. 8, a DNAI may identify user plane access to one or more data networks or (e.g. local) data network parts at / in which specific applications or EAS(s) for delivering (or executing, processing, and so forth) specific applications can be found. It is to be noted that direct connections / links between the UPFs and the EASs are shown for the ease of illustration, but one or more data networks or (e.g. local) data network parts and / or one or more network functions, elements or entities in the illustrated data networks may be located between the respective UPF-EAS pairs. Also, the numbers of network functions, elements or entities, edge application servers, connections / links and networks are also non-limiting and merely depicted for illustrative purposes, and each of the illustrated data networks or (e.g. local) data network parts may comprise more than one edge application server. As shown in FIG. 8, delays in this example architecture, to which the delay-related information may relate, comprise various access network delays and data network delays with respect to EASI and EAS2. For example, as illustrated, these delays comprise the access network delay UE-UPF1 and the data network delay UPF1-EAS1 with respect to EASI and DNAI1-1, the access network delay UE-UPF1 and the data network delay UPF1-EAS2 with respect to EAS2 and DNAI 1-2, the access network delay UE-UPF2 and the data network delay UPF2-EAS2 with respect to EAS2 and DNAI2-2, and the E2E delay UE-EAS2 with respect to EAS2 and DNAI2-2. Accordingly, for this example architecture, the delay-related information may comprise DNAI1-1, DNAI 1-2 and DNAI2-2 as / in the list of DNAIs, and on or more of: the access network delay UE-UPF1 and the data network delay UPF1-EAS1 for DNAI1-1 (with respect to EASI), the access network delay UE-UPF1 and the data network delay UPF1-EAS2 for DNAI 1-2 (with respect to EAS2), the access network delay UE-UPF2 and the data network delay UPF2-EAS2 for DNAI2-2 (with respect to EAS2), and / or the E2E delay UE-EAS2 for DNAI2-2 (with respect to EAS2). As schematically indicated in FIG. 8, the following relationships may be assumed: access network delay UE-UPF1 >access network delay UE-UPF2 data network delay UPF2-EAS2 >data network delay UPF1-EAS2 data network delay UPF1-EAS2 >data network delay UPF1-EAS1 When assuming that these delays are provided by / in the delay-related information for DNAI1 -1, DNAI1-2 and DNAI2-2, it may be concluded that the path with the shortest delay is UE-UPF1-EAS1. In view thereof, based on the acquired access network delays and data network delays, DNAI1-1 may be selected (from DNAI1-1, DNAI1-2 and DNAI2-2) as the target data network access identifier, and EASI may be selected (from EASI and EAS2) as the target edge application server. Then, DNAI1-1 and an identifier of EASI may be sent e.g. from AF to SMF (potentially via NEF) in any one of the example architectures of FIGs. 4 and 5. However, as outlined above, further information can also be taken into account in / for selecting the target data network access identifier and the target edge application server, such as e.g. EAS load. Also, the various (pieces of) information available in / for the selection may be weighted according to any conceivable, dynamic, static or predefined rule or approach. Assuming that the load of EASI is higher (e.g., substantially higher) than that of EAS2 (and, potentially that, a lower data network delay is prioritized over a lower access network delay), EAS2 may be selected (from EASI and EAS2) as the target edge application server, and DNAI1-2 may be selected (from DNAI1-1, DNAI1-2 and DNAI2-2) as the target data network access identifier. Then, DNAI1-2 and an identifier of EAS2 may be sent e.g. from AF to SMF (potentially via NEF) in any one of the example architectures of FIGs. 4 and 5. It is to be noted that the AF is enabled (or otherwise configured) to select a suitable EAS to serve the UE, e.g. to deliver the desired application, and it is up to AF logic to decide the suitable EAS considering other parameters, as explained below. Also, it is to be noted that the SMF is enabled (or otherwise configured) to configure (e.g. select) a suitable UPF to serve the UE, e.g. for delivering the desired application, and it is up to SMF logic to decide the suitable UPF considering other parameters. With regard to the example architectures of FIGs. 4 and 5, a access network delay may represent, comprise or be indicative of a delay on radio interfaces (e.g. between UE and (R)AN) and / or N3 and / or N9 reference points of / between respective functions, elements or entities, and / or a data network delay may represent, comprise or be indicative of a delay on a N6 reference point of / between respective functions, elements or entities or between a respective N6 reference point (or UPF endpoint thereof) and a respective (candidate) edge application server. According to at least one example embodiment, the delay-related information comprises, with respect to a candidate edge application server, information indicating the access network delay and assistance information for determining (e.g., enabling / facilitating / realizing determination of) the data network delay. Then, in the acquiring step / operation S620 in the method or process of FIG. 6, the data network delay with respect to the candidate edge application server can be acquired by determining (e.g. measuring) the data network delay based on the assistance information. The access network delay is directly evident or derivable from the respective information comprised in the delay-related information. For example, referring to FIG. 8, the delay-related information may comprise, for DNAI2-2, the access network delay UE-UPF2 and assistance information for determining the data network delay UPF2-EAS2 with respect to EAS2. Based thereon, the data network delay UPF2-EAS2 with respect to EAS2 can be monitored, measured or found / detected by measurement on the basis of the assistance information. To this end, the apparatus performing the method or process of FIG. 6 can perform or initiate (or trigger) measurement of the data network delay UPF2-EAS2 with respect to EAS2 using the assistance information as part of the received delay-related information. According to at least one example embodiment, the delay-related information comprises, with respect to a candidate edge application server, information indicating an end-to-end delay between the user equipment and the candidate edge application server and assistance information for determining (i.e. facilitating or enabling determination of) the data network delay. Then, in the acquiring step / operation S620 in the method or process of FIG. 6, the data network delay with respect to the candidate edge application server can be acquired by determining the data network delay based on the assistance information, and the access network delay with respect to the candidate edge application server can be acquired by obtaining the access network delay based on the end-to-end delay (which is directly evident or derivable from the respective information comprised in the delay-related information) and the data network delay. For example, referring to FIG. 8, the delay-related information may comprise, for DNAI2-2, the E2E delay UE-EAS2 and assistance information for determining the data network delay UPF2-EAS2 with respect to EAS2. Based thereon, the data network delay UPF2-EAS2 with respect to EAS2 can be monitored, measured or found / detected by measurement on the basis of the assistance information. To this end, the apparatus performing the method or process of FIG. 6 can perform or initiate (or trigger) measurement of the data network delay UPF2-EAS2 with respect to EAS2 using the assistance information. Upon determining the data network delay UPF2-EAS2, the communication data network UE-UPF2 with respect to EAS2 can be calculated, e.g. by subtracting the data network delay UPF2-EAS2 from the E2E delay UE-EAS2. The assistance information is, represents or comprises information for determining (e.g., enabling / facilitating / realizing determination of) the data network delay, such as information for enabling / facilitating / realizing measurement of the data network delay, i.e. the delay between the respective user plane function entity and the respective candidate edge application server. For example, the measurement of the data network delay may be performed or initiated (or triggered) by an AF or by a (candidate) EAS itself, and may be carried out between a UPF and a (candidate) EAS so as to determine the data network delay with respect to that a (candidate) EAS. The measurement enabling / facilitating / realizing information may comprise measurement protocol information about an applicable protocol for the measurement and measurement configuration information about an applicable configuration for the measurement. The information about an applicable protocol for the measurement may indicate a supported e.g. 5GC measurement protocol information, such as e.g. STAMP and / or TWAMP. The measurement configuration information may indicate or comprise protocol configuration information, addressing information, security information and / or validity information for the measurement and / or a connection for the measurement. For example, addressing information may refer to an IP address and / or a port number of a network function, element or entity involved in the measurement, e.g. an endpoint of / for STAMP / TW AMP-based measurement, such as a UPF. Even though STAMP / TWAMP are referred to herein as example measurement protocols, other suitable protocols may be used for the purpose of determining the data network delay (e.g. HTTP-based protocols, and so forth). For example, security information may refer to a FQDN corresponding to a certificate that will be sent to secure a delay measurement protocol, which allows establishment of a secured transport connection for the measurement, e.g. on a connection between a UPF and a (candidate) EAS. For example, validity information may refer to an operational time window for measurement, such as an operational time window for (authorized) measurement endpoints, e.g. UPF and / or EAS, which allows to control when the AF / UPF / EAS is allowed to run such measurement. The operational time window may allow to inform how long (or when) a measurement endpoint, such as a UPF for candidate DNAI(s) shall operate as reflector (e.g. answer to measurement protocol requests, such as a UPF sending an echo response to an echo request from authorized EAS(s) and otherwise e.g. silently discarding echo requests from EAS(s)). It is to be noted that the AF / EAS may not have to know what an UPF is as knowledge of the IP address of the corresponding data network termination point at the communication (or access) network is sufficient. According to at least one example embodiment, the delay-related information comprises, with respect to the candidate edge application server, information indicating an end-to-end delay between the user equipment and the candidate edge application server and information indicating the access network delay. Then, in the acquiring step / operation S620 in the method or process of FIG. 6, the data network delay with respect to the candidate edge application server can be acquired by obtaining the data network delay based on the end-to-end delay and the access network delay (both of which are directly evident or derivable from the respective information comprised in the delay-related information). For example, referring to FIG. 8, the delay-related information may comprise, for DNAI2-2, the E2E delay UE-EAS2 and the access network delay UE-UPF2 with respect to EAS2. Based thereon, the data network delay UPF2-EAS2 with respect to EAS2 can be calculated, e.g. by subtracting the access network delay UE-UPF2 from the E2E delay UE-EAS2. In the following, some example procedures (or use cases) of / for an AF-centric approach according to at least one example embodiment are explained. FIG. 9 shows a sequence diagram of an example procedure according to at least one example embodiment. This procedure represents or comprises (at least part of) the above-described methods or processes, and is - for illustrative purposes - assumed to be based on any one of the example architectures of FIGs. 4 and 5. The procedure of FIG. 9 may be considered to be part of or integrated in a user plane management event notification procedure. Accordingly, for further details (going beyond the subsequent description), reference can be made to section 4.3.6.3 of 3GPP TS 23.502 (e.g. VI 8.4.0) relating to notification of user plane management events. In some examples, the provision of the relevant information by the SMF to the AF is, for instance, part of early notification steps. As shown in FIG. 9, the SMF may send a notification to the AF, either via NEF (steps 2a and 2b) or directly (step 2c), assuming that the AF has subscribed to user plane management / change event notifications (in a preceding step) and a corresponding AF notification trigger or condition is met (step 1). Examples of trigger conditions may comprise one or more of the following: - A PDU Session Anchor identified in the AF subscription request has been established or released. - A DNAI has changed. - The SMF has received a request for AF notification and the on-going PDU Session meets the conditions to notify the AF. - Ethernet PDU Session Anchor Relocation. - Candidate DNAI(s) has changed. All of these trigger conditions may be e.g. due to UE mobility or due to the UE having issued a DNS request towards an FQDN identified as of interest by the AF, or the like. That is, the AF has requested for notification, e.g. as part of AF traffic influence procedure (as described below with respect to FIG. 10), requesting (at least) a list of DNAIs and, per candidate DNAI, delay-related information regarding delay between a UE and one or more candidate EAS(s). The requested information may also comprise other / further information, such as measurement protocol information and / or measurement configuration information, e.g. a protocol, an IP address of a termination point between the communication (or access) network and the data network (corresponding to an UPF N6 interface) to act as endpoint / reflector for measurement by the protocol, e.g. when AF / EAS acts as measurement initiator, or the like. The requested information may be then provided either by steps 2a and 2b or by step 2c. In some examples, the notification messages Nsmf EventExposure Notify and Nnef TrafficInfluence Notify, being enhanced by the mentioned / illustrated information, can be used. While (the message of / in) step 2a is only denoted by “Early Notification” but may have the same contents as (the message of / in) step 2b, the requested information may alternatively be provided by the NEF by step 2b. In some examples, the delay-related information provided by the SMF to the AF comprises, for each DNAI, access network delay (including radio interface and / or N3 / N9 delays) (which may be delay within the 5GS access) as well as assistance information from 5GC to help the AF to determine the aforementioned data network delay (which may be N6 delay) . As mentioned above, the AF may not require this delay-related information. For example, the AF may obtain end-to-end delay and only need either the access network delay (including radio interface and / or N3 / N9 delays) or the assistance information to determine N6 delay, respectively. As mentioned above, the assistance information may comprise information facilitating (or enabling) measurement of the N6 delay, such as measurement protocol information about an applicable protocol for the measurement and, possibly, measurement configuration information about an applicable configuration for the measurement. In some example, this information may comprise e.g. an indication of STAMP and / or TWAMP as the applicable measurement protocol. When the 5GS / NEF has authorized AF request for N6 measurements and determined for each candidate DNAI the UPF N6 measurement endpoints and related protocol configuration, the 5GS / NEF may additionally indicate operational time window for authorized data network measurement endpoints (corresponding to UPF N6 interfaces). Then, the AF can perform, initiate or control N6 delay measurement accordingly, as outlined above. Based on the received information, the AF obtains access network delays and determines data network delays with respect to the list of DNAIs and the one or more candidate EASs, and selects, for the particular PDU session (e.g., the session for delivering an application from an EAS via a PSA-UPF to the UE), a target DNAI and / or a target EAS accordingly, as outlined in more detail above. As mentioned above, further information can also be used in / for the selection, such a e.g. current EAS load information of / for the one or more candidate EASs, which is accessible or derivable by the AF at least for EASs of the same EHE. Thereby, traffic handling / routing on N3 / N9 and on N6 may be controlled by the AF. Then, the AF sends the selected target DNAI and an EAS ID of the selected target EAS to the SMF (via step 2for via the NEF : steps 2d and 2e) and / or via the PCF (step 2f-a or step 2d-a / 2e-a). In some examples, the AF may send the target DNAI and the EAS ID of the selected target EAS, as selected above, to the SMF either directly or via NEF (Steps 2d, 2e, 2d-a, 2f, 2f-a). Based on the thus received information, the SMF configures the UPF or PSA-UPF for the particular PDU session (step 3), thereby configuring the user plane or traffic handling / routing. For example, the SMF may decide to reconfigure the user plane, e.g. by relocating the PSA-UPF. Thereby, traffic handling / routing on N3 / N9 and on N6 may be controlled by / at the SMF. In the subsequent steps, e.g. late notification steps, the SMF may acknowledge and confirm reconfigured user plane or UPF information and / or target DNAI and / or EAS (re)selection or (re)discovery indication. The AF, after consideration, may acknowledge such information in its responses in steps 4e, 4f, 4e-a, 4g, 4ga. It may be assumed that the SMF may access / obtain / leam the delay-related information, such as the assistance information to determine N6 delay about candidate PSA-UPF(s), e.g. UPF(s) that terminates the N6 interface to the data network of any candidate EAS. For example, the SMF may access / obtain / learn the assistance information to determine N6 delay in different ways. An example measure and / or mechanism is to access / obtain / leam the assistance information over N4 as part of N4 association establishment (e.g. when assuming that N4 is defined using PFCP and / or in accordance with 3GPP TS 29.244, then as part of modifications to 3GPP TS 29.244 §6.2.6 PFCP Association Setup Procedure or to 3GPP TS 29.244 §6.2.7 PFCP Association Update Procedure). Another example measure and / or mechanism is to access / obtain / learn the assistance information as part of information registered by the UPF in the NRF (e.g. via a modification of the UPFinfo defined in 3GPP TS 29.510). Namely, for example, the UPF may register the assistance information to determine N6 delay as part of a Nnrf_NFManagement_NFRegister Request or Nnrf_NFManagement_NFUpdate Request defined in 3GPP TS 23.502 §4.17.1 or §4.17.2), and the SMF may discover this information as part of Nnrf NFDiscovery Request. FIG. 10 shows a sequence diagram of an example procedure according to at least one example embodiment. This procedure represents or comprises (at least part of) the above-described methods or processes, and is - for illustrative purposes - assumed to be based on any one of the example architectures of FIGs. 4 and 5. The procedure of FIG. 10 may be considered to be part of or integrated in a traffic routing influence procedure. Accordingly, for further details (going beyond the subsequent description), reference can be made to section 4.3.6.2 of 3GPP TS 23.502 (e.g. V18.4.0) relating to processing AF requests to influence traffic routing and / or service function chaining for sessions not identified by a UE address. As mentioned above with respect to FIG. 9, the AMF may request for notification, e.g. as part of AF traffic influence procedure (as e.g. illustrated in FIG. 10), requesting (at least) a list of DNAIs and, per candidate DNAI, delay-related information regarding delay between a UE and one or more candidate EAS(s). The requested information may also comprise other / further information, such as measurement protocol information and / or measurement configuration information, e.g. a protocol, a UPF to act as endpoint / reflector for measurement by the protocol, e.g. when AF / EAS acts as measurement initiator, or the like. As shown in FIG. 10, the AF, in its request to influence traffic routing, may include a notification request (from SMF, via PCF) for per DNAI information on delay between a UE and at least one candidate EAS (step 1). In some examples, the requested delay-related information comprises (for each DNAI) N3 / N9 delays as example of an access network delay (or delay within the 5GS access) as well as assistance information from 5GC to help the AF to determine N6 delay as example of a data network delay. The AF request may be used by the SMF, for example, to configure, over N4, the candidate UPF as N6 endpoints for delay measurement, e.g. to act as STAMP / TWAMP (session / echo) reflector, and / or to get, over N4, measurement-related parameters (e.g. IP address and / or port, security information, validity information, and so forth) associated with the N6 endpoint for delay measurement, e.g. the STAMP / TWAMP (session / echo) reflector (at the UPF). In some examples, the AF may send the target DNAI and the EAS ID of the target EAS (which are selected based on different criteria, e.g. EAS load, overall delay, and so forth, as outlined above) to the NEF e.g. in Nnef Trafficinfluence Update request (step 2). Such update step / operation may take place after a notification from the SMF, as explained with respect to FIG. 9. The rest of the steps are same or similar as in 3GPP TS 23.502 §4.3.6.2. Alternatively, the AF may request provisioning for delay-related information, such as assistance information, E2E delay, or the like, as / in measurement configuration and management information. This may be accomplished by a corresponding request to 5GS, e.g. via NEF e.g. using Nnef^AFSessionWithQoS service, XnefServiceParameter service, or Nnef EASDeployment service. In view of FIGs. 9 and 10, it is to be noted that the thus illustrated procedures exemplify procedures according to one or more example embodiments, which are based on previously specified procedures, for the sake of illustration. However, the previously specified procedures, used as a basis, may be different, and not all steps and / or information of these previously specified procedures are required in various example embodiments. According to some example embodiments, means and / or configurations are provided in the communication system, such as the communication network, e.g. the 5GS or 5GC, to enable / facilitate / realize or ensure that (only) legitimate endpoints can perform delay measurements, such as N6 delay measurement. Also, it may be enabled or ensured that (only) legitimate endpoints in a (N6- connected) data network can perform delay measurements, such as N6 delay measurement, against the candidate UPF(s) acting as N6 measurement endpoints. In case of STAMP protocol, the AF may request candidate UPF N6 endpoints to act in authenticated mode, require integrity protection and / or confidentiality protection. In case integrity protection is enabled / required, the AF request can include the key to calculate Hashed Message Authentication Code (HMAC) in STAMP message and / or how 5GS can obtain such key, such as e.g. an identifier to keying information provisioned 5GS via 0AM or out of band key distribution mechanism. In case confidentiality protection is enabled / required / implemented, the AF request can include information that enables / facilitates / realizes establishment of dedicated IPsec tunnel(s) between measurement endpoint(s) in EHE and UPF N6 endpoints and / or to share the IPsec tunnel with a monitored flow. 5GS can determine to reject the AF request for candidate UPF N6 measurement endpoints when the AF-provided configuration information does not meet the requirements of 5GS. In case of STAMP, any (session / echo) reflector shall be able to receive STAMP-Test packets on L DP port 862 and to receive STAMP-Test packets from User Ports and Dynamic Ports ranges, which are defined. But UPF may also determine to use other port number values. Further details on STAMP can be derived from RFC 8762, and further details on TWAMP can be derived from RFC 5357. With regard to the above examples, use cases and example embodiments, it is to be noted that these are merely provided for illustrative purposes, without being intended to restrict the disclosure thereto. As described above, various example embodiments provide technique(s) for (e.g. enabling / facilitating / realizing enhancements and / or improvements for) edge computing, such as enhanced (e.g., efficient) decision-making and configuration for edge computing. As described above, in various example embodiments, an Edge Hosting Environment (EHE) can acquire / obtain / determine information (e.g., all required information) for evaluating a delay scenario for a particular PDU session for a UE (trying to) using an application provided or controlled by an AF of the EHE and delivered (executed, processed, and so forth) by an EAS of the EHE. For example, the EHE can initiate and perform QoS / delay measurements on available N6 endpoints and paths towards 5GS as well as other interfaces, e.g., towards adjacent datacenters, and collect the measurement results. To have an end-to-end view in the EHE for determining the target EAS, the AF can request from 5GS for each candidate DNAI QoS / delay measurement results for the delay within the 5GS access and assistance information to determine N6 delay, e.g. delay to the data network and / or outside the 5GS. When the AF receives the candidate assistance information to determine N6 delay, the EHE (the AF or the EAS) can perform the N6 delay measurements for the candidate DNAIs provided by 5GS. Based therein, the AF can select that target DNAI and the target EAS. Using the selected target DNAI and target EAS, a suitable PDF (PSA-UPF) can then be configured, e.g. selected, e.g. by an SMF of the 5GS / 5GC. The above-described functionality as well as its related operations, procedures, methods and processes may be implemented by respective functional elements, entities, modules, units, processors, or the like, as described below. These functional elements, entities, modules, units, processors, or the like, e.g., the implementation of one or more example embodiments, may be realized in a cloud environment, by SDN, by NFV / NFVI, or the like. While various example embodiments are described with reference to operations, procedures, methods and processes, these example embodiments also cover respective apparatuses, entities, modules, units, network nodes and / or systems, including software and / or hardware thereof. Respective example embodiments are described below, while for the sake of brevity reference is made to the detailed description of respective corresponding configurations / setups, schemes, structures, processes, sequences, methods as well as functionalities, principles and operations according to FIGS. 4 to 10. FIG. 11 shows a schematic block diagram illustrating a structure of apparatuses according to at least one example embodiment. In FIG. 11, the blocks are basically configured to perform respective methods, procedures and / or functions as described above. It is to be noted that the individual blocks are meant to illustrate respective functional blocks implementing a respective function, process or procedure, respectively. Such functional blocks are implementation-independent, e.g. may be implemented by means of any kind of hardware or software or combination thereof, respectively. According to at least one example embodiment, an apparatus according to at least one example embodiment may represent or realize / implement / embody a (e.g., part of a) network function, element or entity, such as e.g. an AF or the like. Such apparatus may be illustrated or realized as is shown in FIG. 3. The apparatus or its at least one processor 320 (e.g., together with instructions stored in its at least one memory 330) may be configured to receive a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, acquire, based on the delay-related information, access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network, and select, based on the access network delays and the data network delays, a target data network access identifier from the list of candidate data network access identifiers and a target edge application server from the at least one candidate edge application server. Further, the apparatus or its at least one processor 320 (e.g., together with instructions stored in its at least one memory 330) may be configured to obtain, from the delay-related information, the access network delays, and / or determine, based on assistance information in the delay-related information, the data network delays. Further, the apparatus or its at least one processor 320 (e.g., together with instructions stored in its at least one memory 330) may be configured to perform or realize any methods, steps, operations, functionalities, or the like, as described above, at least with respect to an AF or the like. Such apparatus may be illustrated or realized as is shown in FIG. 11 as apparatus 1110. The apparatus 1110 may comprise (at least) one or more unit / means / circuitry, denoted by receiving section 1111, which represent any implementation for (or configured to) receiving (receive) a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, one or more unit / means / circuitry, denoted by acquiring section 1112, which represent any implementation for (or configured to) acquiring (acquire), based on the delay-related information, access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network, and one or more unit / means / circuitry, denoted by selecting section 1113, which represent any implementation for (or configured to) selecting (select), based on the access network delays and the data network delays, a target data network access identifier from the list of candidate data network access identifiers and a target edge application server from the at least one candidate edge application server. As indicated by dashed lines, the apparatus 1110 may comprise (at least) one or more unit / means / circuitry, denoted by sending section 1114, which represent any implementation for (or configured to) sending (send) sending (send) the target data network access identifier and an edge application server identifier of the target edge application server. Further, the apparatus 1110 may comprise (at least) one or more unit / means / circuitry, denoted by accessing section 1115, which represent any implementation for (or configured to) accessing (access) load information with respect to the at least one candidate edge application server, wherein load information indicates a load of the respective candidate edge application server. Further, the apparatus 1110 may comprise (at least) one or more unit / means / circuitry, denoted by requesting section 1116, which represent any implementation for (or configured to) requesting (request) notification or provisioning of delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay. Further, the receiving section 1111 or another section with corresponding operability may be for (or configured to) receiving (receive) at least one IP address, each IP address being associated with a user plane function entity. According to at least one example embodiment, an apparatus according to at least one example embodiment may represent or realize / implement / embody a (e.g., part of a) network function, element or entity, such as e.g. a SMF or the like. Such apparatus may be illustrated or realized as is shown in FIG. 3. The apparatus or its at least one processor 320 (e.g., together with instructions stored in its at least one memory 330) may be configured to send a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates acquiring access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network. Further, the apparatus or its at least one processor 320 (e.g., together with instructions stored in its at least one memory 330) may be configured to receive a target data network access identifier from the list of candidate data network access identifiers and an edge application server identifier of a target edge application server from the at least one candidate edge application server, and / or configure, based on the target data network access identifier and the edge application server identifier of the target edge application server, a user plane function entity from one or more user plane function entities of the communication network. Further, the apparatus or its at least one processor 320 (e.g., together with instructions stored in its at least one memory 330) may be configured to perform or realize any methods, steps, operations, functionalities, or the like, as described above, at least with respect to a SMF or the like. Such apparatus may be illustrated or realized as is shown in FIG. 11 as apparatus 1120. The apparatus 1120 may comprise (at least) one or more unit / means / circuitry, denoted by sending section 1121, which represent any implementation for (or configured to) sending (send) a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates acquiring access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network. As indicated by dashed lines, the apparatus 1120 may comprise (at least) one or more unit / means / circuitry, denoted by receiving section 1122, which represent any implementation for (or configured to) receiving (receive) a target data network access identifier from the list of candidate data network access identifiers and an edge application server identifier of a target edge application server from the at least one candidate edge application server. Further, the apparatus 1120 may comprise (at least) one or more unit / means / circuitry, denoted by configuring section 1123, which represent any implementation for (or configured to) configuring (configure), based on the target data network access identifier and the edge application server identifier of the target edge application server, a user plane function entity from one or more user plane function entities of the communication network. Further, the apparatus 1120 may comprise (at least) one or more unit / means / circuitry, denoted by acquiring section 1124, which represent any implementation for (or configured to) acquiring (acquire) assistance information for determining the data network delay with respect to a candidate edge application server. Further, the apparatus 1120 may comprise (at least) one or more unit / means / circuitry, denoted by setting section 1125, which represent any implementation for (or configured to) setting (set) setting a condition for sending the delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay and / or setting the respective user plane function entity for measurement of the delay between the respective user plane function entity and the respective candidate edge application server. Further, the sending section 1121 or another section with corresponding operability may be for (or configured to) sending (send) at least one IP address, each IP address being associated with a user plane function entity, and / or the receiving section 1122 or another section with corresponding operability may be for (or configured to) receiving (receive) a request for notification or provisioning of delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay. For further details regarding the operability / functionality of the apparatuses (or units / means thereof) according to some example embodiments, reference is made to the above description in connection with any one of FIGS. 1 to 10, respectively. According to some example embodiments, any one of the (at least one) processor, the (at least one) memory and the (at least one) interface, as well as any one of the illustrated units / means, may be implemented as individual modules, chips, chipsets, circuitries or the like, or one or more of them can be implemented as a common module, chip, chipset, circuitry or the like, respectively. As used herein, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processors)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions), and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device. According to some example embodiments, a system may comprise any conceivable combination of any depicted or described apparatuses and other network elements or functional entities, which are configured to cooperate as described above. In general, it is to be noted that respective functional blocks or elements according to various embodiments described herein can be implemented by any known means, either in hardware and / or software, respectively, if it is only adapted to perform the described functions of the respective parts. The mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device. Generally, a basic system architecture of a (tele)communication network including a mobile communication system where some examples of example embodiments are applicable may include an architecture of one or more communication networks including wireless access network sub- / system(s) and possibly core network(s). Such an architecture may include one or more communication network control elements or functions, such as e.g. access network elements, radio access network elements, access service network gateways or base transceiver stations, like a base station, an access point, a NodeB (NB), an eNB or a gNB, a distributed or a centralized unit, which controls a respective coverage area or cell(s) and with which one or more communication stations such as communication elements or functions, like user devices or terminal devices, like a UE, or another device having a similar function, such as a modem chipset, a chip, a module, and so forth, which can also be part of a station, an element, a function or an application capable of conducting a communication, such as a UE, an element or function usable in a machine-to-machine communication architecture, or attached as a separate element to such an element, function or application capable of conducting a communication, or the like, are capable to communicate via one or more channels via one or more communication beams for transmitting several types of data in a plurality of access domains. Furthermore, core network elements or network functions, such as gateway network elements / functions, mobility management entities, a mobile switching center, servers, databases and the like may be included. The general functions and interconnections of the described elements and functions, which also depend on the actual network type, are known to those skilled in the art and described in corresponding specifications, so that a detailed description thereof is omitted herein. It should be appreciated that several additional network elements and signaling links may be employed for a communication to or from an element, function or application, like a communication endpoint, a communication network control element, such as a server, a gateway, a radio network controller, and other elements of the same or other communication networks besides those described in detail herein below. A communication network architecture as being considered in examples of example embodiments may also be able to communicate with other networks, such as a public switched telephone network or the Internet, including the Internet-of-Things. The communication network may also be able to support the usage of cloud services for virtual network elements or functions thereof, wherein it is to be noted that the virtual network part of the (tele)communication network can also be provided by non-cloud resources, e.g. an internal network or the like. It should be appreciated that network elements of an access system, of a core network, and so forth, and / or respective functionalities may be implemented by using any node, host, server, access node or entity, and so forth being suitable for such a usage. Generally, a network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. a cloud infrastructure. Any method step is suitable to be implemented as software or by hardware without changing the idea or scope of the various example embodiments. Such software may be software code independent and can be specified using any known or future developed programming language, such as e.g. Java, C++, C, and Assembler, as long as the functionality defined by the method steps is preserved. Such hardware may be hardware type independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), and so forth, using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components. A device / apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device / apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module, such as a computer program or a computer program product comprising executable software code portions for execution / being run on a processor. A device may be regarded as a device / apparatus or as an assembly of more than one device / apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example. Apparatuses and / or units / means or parts thereof can be implemented as individual devices, but this does not exclude that they may be implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person. Software in the sense of the description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium, such as a computer-readable (storage) medium having stored thereon a respective data structure or code means / portions or embodied in a signal or in a chip, potentially during processing thereof. Various example embodiments also cover any conceivable combination of method steps and operations described above, and any conceivable combination of nodes, apparatuses, modules or elements described above, as long as the above-described concepts of methodology and structural arrangement are applicable. In view of the above, there are provided measures for (e.g. enabling / facilitating / realizing enhancements and / or improvements for) edge computing, such as enhanced (e.g., efficient) decision-making and configuration for edge computing. Such measures may, for example, comprise that a network function, element or entity receives a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, acquires access network delays (e.g., delays between the user equipment and one or more user plane function entities of a communication network) and data network delays (e.g., delays between one or more user plane function entities and a respective one of the at least one candidate edge application server), and selects a target data network access identifier from the list of candidate data network access identifiers and a target edge application server from the at least one candidate edge application server. Even though various example embodiments are described herein with reference to the accompanying drawings, it is to be understood that the various example embodiments are not restricted thereto. Rather, it is apparent to those skilled in the art that the various example embodiments can be modified in many ways without departing from the intended scope. Some of the various example embodiments of the disclosure are listed below by way of nonlimiting and illustrative example. Example Embodiment 1. A method, comprising: receiving a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, acquiring, based on the delay-related information, access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network, and selecting, based on the access network delays and the data network delays, a target data network access identifier from the list of candidate data network access identifiers and a target edge application server from the at least one candidate edge application server. Example Embodiment 2. The method according to Example Embodiment 1, wherein the acquiring comprises: obtaining, from the delay-related information, the access network delays, and / or determining, based on assistance information in the delay-related information, the data network delays. Example Embodiment 3. The method according to Example Embodiment 1 or 2, wherein the delay-related information comprises, with respect to a candidate edge application server, information indicating the access network delay and assistance information for determining the data network delay, and the acquiring comprises: obtaining, from the delay-related information, the access network delay with respect to the candidate edge application server, and / or determining, based on the assistance information, the data network delay with respect to the candidate edge application server. Example Embodiment 4. The method according to any one of Example Embodiments 1 to 3, wherein a user plane function entity of the communication network is identified by an IP address on a data network identified by the target data network access identifier. Example Embodiment 5. The method according to Example Embodiment 2 or 3, wherein determining a data network delay comprises performing or initiating measurement of the delay between the respective user plane function entity and the respective candidate edge application server using the assistance information. Example Embodiment 6. The method according to any one of Example Embodiments 2, 3 or 5, wherein the assistance information comprises information for facilitating measurement of the delay between the respective user plane function entity and the respective candidate edge application server. Example Embodiment 7. The method according to Example Embodiment 6, wherein the measurement facilitating information comprises measurement protocol information about an applicable protocol for the measurement and measurement configuration information about an applicable configuration for the measurement. Example Embodiment 8. The method according to Example Embodiment 7, wherein the measurement protocol information indicates a simple two-way active measurement protocol and / or a two-way active measurement protocol as applicable measurement protocol, and / or the measurement configuration information comprises one or more of protocol configuration information, addressing information, security information and validity information for the measurement and / or a connection for the measurement. Example Embodiment 9. The method according to any one of Example Embodiments 1 to 8, further comprising: sending the target data network access identifier and an edge application server identifier of the target edge application server. Example Embodiment 10. The method according to any one of Example Embodiments 1 to 9, further comprising: accessing load information with respect to the at least one candidate edge application server, wherein load information indicates a load of the respective candidate edge application server, wherein the target data network access identifier and the target edge application server are selected further based on the load information. Example Embodiment 11. The method according to any one of Example Embodiments 1 to 10, further comprising: receiving at least one IP address, each IP address being associated with a user plane function entity, wherein the target data network access identifier and the target edge application server are selected further based on the at least one IP address. Example Embodiment 12. The method according to any one of Example Embodiments 1 to 11, further comprising: requesting notification or provisioning of delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay. Example Embodiment 13. The method according to Example Embodiment 12, wherein the requesting is carried out in at least one of a traffic routing influence procedure, a service, operation or procedure for setting up a session with required quality-of-service, a service parameter service, operation or procedure, or an edge application server deployment service, operation or procedure. Example Embodiment 14. The method according to any one of Example Embodiments 1 to 13, wherein the method is part of or integrated in a traffic routing influence procedure and / or a user plane management event notification procedure. Example Embodiment 15. The method according to any one of Example Embodiments 1 to 14, wherein the method is operable at or by an application function entity of the communication network, and / or the list of candidate data network access identifiers and the delay-related information are received from a session management function entity or a network exposure function entity of the communication entity, and / or the target data network access identifier and an edge application server identifier of the target edge application server are sent to a session management function entity or a network exposure function entity of the communication entity, and / or the user equipment is to use an application controlled by an application function entity of the communication network, which is to be delivered by an edge application server of the at least one candidate edge application server, and / or the access network delay is indicative of a delay on N3 and / or N9 reference points, and / or the data network delay is indicative of a delay on a N6 reference point. Example Embodiment 16. A method, comprising: sending a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates acquiring access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network. Example Embodiment 17. The method according to Example Embodiment 16, further comprising: receiving a target data network access identifier from the list of candidate data network access identifiers and an edge application server identifier of a target edge application server from the at least one candidate edge application server, and configuring, based on the target data network access identifier and the edge application server identifier of the target edge application server, a user plane function entity from one or more user plane function entities of the communication network. Example Embodiment 18. The method according to Example Embodiment 16 or 17, wherein the delay-related information facilitates: obtaining, from the delay-related information, the access network delays, and / or determining, based on assistance information in the delay-related information, the data network delays. Example Embodiment 19. The method according to any one of Example Embodiments 16 to 18, wherein the delay-related information comprises, with respect to a candidate edge application server, information indicating the access network delay and assistance information for determining the data network delay. Example Embodiment 20. The method according to any one of Example Embodiments 16 to 19, wherein a user plane function entity of the communication network is identified by an IP address on a data network identified by the target data network access identifier. Example Embodiment 21. The method according to Example Embodiment 18 or 19, wherein the delay-related information facilitates determining a data network delay by performing or initiating measurement of the delay between the respective user plane function entity and the respective candidate edge application server using the assistance information. Example Embodiment 22. The method according to any one of Example Embodiments 18, 19 or 21, wherein the assistance information comprises information for facilitating measurement of the delay between the respective user plane function entity and the respective candidate edge application server. Example Embodiment 23. The method according to Example Embodiment 22, wherein the measurement facilitating information comprises measurement protocol information about an applicable protocol for the measurement and measurement configuration information about an applicable configuration for the measurement. Example Embodiment 24. The method according to Example Embodiment 23, wherein the measurement protocol information indicates a simple two-way active measurement protocol and / or a two-way active measurement protocol as applicable measurement protocol, and / or the measurement configuration information comprises one or more of protocol configuration information, addressing information, security information and validity information for the measurement and / or a connection for the measurement. Example Embodiment 25. The method according to any one of Example Embodiments 16 to 24, further comprising: sending at least one IP address, each IP address being associated with a user plane function entity. Example Embodiment 26. The method according to any one of Example Embodiments 16 to 25, further comprising: acquiring assistance information for determining the data network delay with respect to a candidate edge application server. Example Embodiment 27. The method according to Example Embodiment 26, wherein the assistance information for determining the data network delay is acquired from a user plane function entity and / or a network repository function entity of the communication network, and / or the assistance information for determining the data network delay is acquired as part of an association setup or update procedure with a user plane function entity, such as a packet forwarding control protocol association setup or update procedure, and / or a network function discovery service, operation or procedure with a network repository function entity of the communication network. Example Embodiment 28. The method according to any one of Example Embodiments 16 to 27, further comprising: receiving a request for notification or provisioning of delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay. Example Embodiment 29. The method according to Example Embodiment 28, further comprising: upon receiving the request, setting a condition for sending the delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay, wherein the delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay are sent when the condition is met. Example Embodiment 30. The method according to Example Embodiment 28 or 29, further comprising: upon receiving the request, setting the respective user plane function entity for measurement of the delay between the respective user plane function entity and the respective candidate edge application server. Example Embodiment 31. The method according to any one of claims 28 to 30, wherein the request is received in at least one of a traffic routing influence procedure, a service for setting up a session with required quality-of-service, a service parameter service, or an edge application server deployment service. Example Embodiment 32. The method according to any one of Example Embodiments 16 to 31, wherein the method is part of or integrated in a traffic routing influence procedure and / or a user plane management event notification procedure. Example Embodiment 33. The method according to any one of Example Embodiments 16 to 32, wherein the method is operable at or by a session management function entity of the communication network, and / or the list of candidate data network access identifiers and the delay-related information are sent to an application function entity or a network exposure function entity of the communication entity, and / or a target data network access identifier and an edge application server identifier of a target edge application server are received from an application function entity or a network exposure function entity of the communication entity, and / or the user equipment is to use an application controlled by an application function entity of the communication network, which is to be delivered by an edge application server of the at least one candidate edge application server, and / or the user plane function entity is configured as a packet data unit session anchor of a packet data unit session in the communication network and an endpoint of an interface between the communication network and the data network of the target edge application server, and / or the access network delay is indicative of a delay on N3 and / or N9 reference points, and / or the data network delay is indicative of a delay on a N6 reference point. Example Embodiment 34. An apparatus comprising: means for receiving a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, means for acquiring, based on the delay-related information, access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network, and means for selecting, based on the access network delays and the data network delays, a target data network access identifier from the list of candidate data network access identifiers and a target edge application server from the at least one candidate edge application server. Example Embodiment 35. The apparatus according to Example Embodiment 34, comprises: means for obtaining, from the delay-related information, the access network delays, and / or means for determining, based on assistance information in the delay-related information, the data network delays. Example Embodiment 36. The apparatus according to Example Embodiment 34 or 35, wherein the delay-related information comprises, with respect to a candidate edge application server, information indicating the access network delay and assistance information for determining the data network delay, and the acquiring means is configured to: obtain, from the delay-related information, the access network delay with respect to the candidate edge application server, and / or determine, based on the assistance information, the data network delay with respect to the candidate edge application server. Example Embodiment 37. The apparatus according to any one of Example Embodiments 34 to 36, wherein a user plane function entity of the communication network is identified by an IP address on a data network identified by the target data network access identifier. Example Embodiment 38. The apparatus according to Example Embodiment 35 or 36, wherein determining a data network delay comprises performing or initiating measurement of the delay between the respective user plane function entity and the respective candidate edge application server using the assistance information. Example Embodiment 39. The apparatus according to any one of Example Embodiments 35, 36 or 38, wherein the assistance information comprises information for facilitating measurement of the delay between the respective user plane function entity and the respective candidate edge application server. Example Embodiment 40. The apparatus according to Example Embodiment 39, wherein the measurement facilitating information comprises measurement protocol information about an applicable protocol for the measurement and measurement configuration information about an applicable configuration for the measurement. Example Embodiment 41. The apparatus according to Example Embodiment 40, wherein the measurement protocol information indicates a simple two-way active measurement protocol and / or a two-way active measurement protocol as applicable measurement protocol, and / or the measurement configuration information comprises one or more of protocol configuration information, addressing information, security information and validity information for the measurement and / or a connection for the measurement. Example Embodiment 42. The apparatus according to any one of Example Embodiments 34 to 41, further comprising: means for sending the target data network access identifier and an edge application server identifier of the target edge application server. Example Embodiment 43. The apparatus according to any one of Example Embodiments 34 to 42, further comprising: means for accessing load information with respect to the at least one candidate edge application server, wherein load information indicates a load of the respective candidate edge application server, wherein the target data network access identifier and the target edge application server are selected further based on the load information. Example Embodiment 44. The apparatus according to any one of Example Embodiments 34 to 43, further comprising: means for receiving at least one IP address, each IP address being associated with a user plane function entity, wherein the target data network access identifier and the target edge application server are selected further based on the at least one IP address. Example Embodiment 45. The apparatus according to any one of Example Embodiments 34 to 44, further comprising: means for requesting notification or provisioning of delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay. Example Embodiment 46. The apparatus according to Example Embodiment 45, wherein the requesting is carried out in at least one of a traffic routing influence procedure, a service, operation or procedure for setting up a session with required quality-of-service, a service parameter service, operation or procedure, or an edge application server deployment service, operation or procedure. Example Embodiment 47. The apparatus according to any one of Example Embodiments 34 to 46, wherein the apparatus is configured to operate as part of or integrated in a traffic routing influence procedure and / or a user plane management event notification procedure. Example Embodiment 48. The apparatus according to any one of Example Embodiments 34 to 47, wherein the apparatus is operable at or by an application function entity of the communication network, and / or the list of candidate data network access identifiers and the delay-related information are received from a session management function entity or a network exposure function entity of the communication entity, and / or the target data network access identifier and an edge application server identifier of the target edge application server are sent to a session management function entity or a network exposure function entity of the communication entity, and / or the user equipment is to use an application controlled by an application function entity of the communication network, which is to be delivered by an edge application server of the at least one candidate edge application server, and / or the access network delay is indicative of a delay on N3 and / or N9 reference points, and / or the data network delay is indicative of a delay on a N6 reference point. Example Embodiment 49. An apparatus, comprising: means for sending a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates acquiring access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network. Example Embodiment 50. The apparatus according to Example Embodiment 49, further comprising: means for receiving a target data network access identifier from the list of candidate data network access identifiers and an edge application server identifier of a target edge application server from the at least one candidate edge application server, and means for configuring, based on the target data network access identifier and the edge application server identifier of the target edge application server, a user plane function entity from one or more user plane function entities of the communication network. Example Embodiment 51. The apparatus according to Example Embodiment 49 or 50, wherein the delay-related information facilitates: obtaining, from the delay-related information, the access network delays, and / or determining, based on assistance information in the delay-related information, the data network delays. Example Embodiment 52. The apparatus according to any one of Example Embodiments 49 to 51, wherein the delay-related information comprises, with respect to a candidate edge application server, information indicating the access network delay and assistance information for determining the data network delay. Example Embodiment 53. The apparatus according to any one of Example Embodiments 49 to 52, wherein a user plane function entity of the communication network is identified by an IP address on a data network identified by the target data network access identifier. Example Embodiment 54. The apparatus according to claim 51 or 52, wherein the delay-related information facilitates determining a data network delay by performing or initiating measurement of the delay between the respective user plane function entity and the respective candidate edge application server using the assistance information. Example Embodiment 55. The apparatus according to any one of Example Embodiments 51, 52 or 54, wherein the assistance information comprises information for facilitating measurement of the delay between the respective user plane function entity and the respective candidate edge application server. Example Embodiment 56. The apparatus according to Example Embodiment 55, wherein the measurement facilitating information comprises measurement protocol information about an applicable protocol for the measurement and measurement configuration information about an applicable configuration for the measurement. Example Embodiment 57. The apparatus according to Example Embodiment 56, wherein the measurement protocol information indicates a simple two-way active measurement protocol and / or a two-way active measurement protocol as applicable measurement protocol, and / or the measurement configuration information comprises one or more of protocol configuration information, addressing information, security information and validity information for the measurement and / or a connection for the measurement. Example Embodiment 58. The apparatus according to any one of Example Embodiments 49 to 57, further comprising: means for sending at least one IP address, each IP address being associated with a user plane function entity. Example Embodiment 59. The apparatus according to any one of Example Embodiments 49 to 58, further comprising: acquiring assistance information for determining the data network delay with respect to a candidate edge application server. Example Embodiment 60. The apparatus according to Example Embodiment 59, wherein the assistance information for determining the data network delay is acquired from a user plane function entity and / or a network repository function entity of the communication network, and / or the assistance information for determining the data network delay is acquired as part of an association setup or update procedure with a user plane function entity, such as a packet forwarding control protocol association setup or update procedure, and / or a network function discovery service, operation or procedure with a network repository function entity of the communication network. Example Embodiment 61. The apparatus according to any one of Example Embodiments 49 to 60, further comprising: means for receiving a request for notification or provisioning of delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay. Example Embodiment 62. The apparatus according to Example Embodiment 61, further comprising: means for, upon receiving the request, setting a condition for sending the delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay, wherein the delay-related information per candidate data network access identifier and / or assistance information for determining a data network delay are sent when the condition is met. Example Embodiment 63. The apparatus according to Example Embodiment 61 or 62, further comprising: means for, upon receiving the request, setting the respective user plane function entity for measurement of the delay between the respective user plane function entity and the respective candidate edge application server. Example Embodiment 64. The apparatus according to any one of Example Embodiments 61 to 63, wherein the request is received in at least one of a traffic routing influence procedure, a service for setting up a session with required quality-of-service, a service parameter service, or an edge application server deployment service. Example Embodiment 65. The apparatus according to any one of Example Embodiments 49 to 64, wherein the apparatus is configured to operate as part of or integrated in a traffic routing influence procedure and / or a user plane management event notification procedure. Example Embodiment 66. The apparatus according to any one of Example Embodiments 49 to 65, wherein the apparatus is operable at or by a session management function entity of the communication network, and / or the list of candidate data network access identifiers and the delay-related information are sent to an application function entity or a network exposure function entity of the communication entity, and / or a target data network access identifier and an edge application server identifier of a target edge application server are received from an application function entity or a network exposure function entity of the communication entity, and / or the user equipment is to use an application controlled by an application function entity of the communication network, which is to be delivered by an edge application server of the at least one candidate edge application server, and / or the user plane function entity is configured as a packet data unit session anchor of a packet data unit session in the communication network and an endpoint of an interface between the communication network and the data network of the target edge application server, and / or the access network delay is indicative of a delay on N3 and / or N9 reference points, and / or the data network delay is indicative of a delay on a N6 reference point. Example Embodiment 67. A system comprising at least: an apparatus according to any one of Example Embodiments 34 to 48, and. an apparatus according to any one of Example Embodiments 49 to 66. Example Embodiment 68. A computer program product comprising computer program code which, when the computer program code is executed on a computer, is configured to cause the computer to carry out the method according to any one of Example Embodiments 1 to 15 or 16 to 33.

Claims

1. A method, comprising:receiving a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server,acquiring, based on the delay-related information, access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network, andselecting, based on the access network delays and the data network delays, a target data network access identifier from the list of candidate data network access identifiers and a target edge application server from the at least one candidate edge application server.

2. The method according to claim 1, wherein the acquiring comprises:obtaining, from the delay-related information, the access network delays, and / ordetermining, based on assistance information in the delay-related information, the data network delays.

3. The method according to claim 1 or 2, whereinthe delay-related information comprises, with respect to a candidate edge application server, information indicating the access network delay and assistance information for determining the data network delay, andthe acquiring comprises:obtaining, from the delay-related information, the access network delay with respect to the candidate edge application server, and / ordetermining, based on the assistance information, the data network delay with respect to the candidate edge application server.

4. The method according to any one of claims 1 to 3, whereina user plane function entity of the communication network is identified by an IP address on a data network identified by the target data network access identifier.

5. The method according to claim 2 or 3, whereindetermining a data network delay comprises performing or initiating measurement of the delay between the respective user plane function entity and the respective candidate edge application server using the assistance information.

6. The method according to any one of claims 2, 3 or 5, wherein the assistance information comprises information for facilitating measurement of the delay between the respective user plane function entity and the respective candidate edge application server.

7. The method according to claim 6, wherein the measurement facilitating information comprises measurement protocol information about an applicable protocol for the measurement and measurement configuration information about an applicable configuration for the measurement.

8. The method according to claim 7, whereinthe measurement protocol information indicates a simple two-way active measurement protocol and / or a two-way active measurement protocol as applicable measurement protocol, and / orthe measurement configuration information comprises one or more of protocol configuration information, addressing information, security information and validity information for the measurement and / or a connection for the measurement.

9. The method according to any one of claims 1 to 8, further comprising:sending the target data network access identifier and an edge application server identifier of the target edge application server.

10. The method according to any one of claims 1 to 9, further comprising:accessing load information with respect to the at least one candidate edge application server, wherein load information indicates a load of the respective candidate edge application server,wherein the target data network access identifier and the target edge application server are selected further based on the load information.

11. The method according to any one of claims 1 to 10, whereinthe method is operable at or by an application function entity of the communication network, and / orthe list of candidate data network access identifiers and the delay-related information are received from a session management function entity or a network exposure function entity of the communication entity, and / orthe target data network access identifier and an edge application server identifier of the target edge application server are sent to a session management function entity or a network exposure function entity of the communication entity, and / orthe user equipment is to use an application controlled by an application function entity of the communication network, which is to be delivered by an edge application server of the at least one candidate edge application server, and / orthe access network delay is indicative of a delay on N3 and / or N9 reference points, and / or the data network delay is indicative of a delay on a N6 reference point.

12. A method, comprising:sending a list of candidate data network access identifiers and, for each candidate data network access identifier, delay-related information regarding delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates acquiring access network delays and data network delays, wherein an access network delay comprises a delay between the user equipment and a user plane function entity of a communication network, and a data network delay comprises a delay between a user plane function entity of the communication network and one of the at least one candidate edge application server of at least one data network.

13. The method according to claim 12, further comprising:receiving a target data network access identifier from the list of candidate data network access identifiers and an edge application server identifier of a target edge application server from the at least one candidate edge application server, andconfiguring, based on the target data network access identifier and the edge application server identifier of the target edge application server, a user plane function entity from one or more user plane function entities of the communication network.

14. The method according to claim 12 or 13, wherein the delay-related information facilitates: obtaining, from the delay-related information, the access network delays, and / or determining, based on assistance information in the delay-related information, the data network delays.

15. The method according to any one of claims 12 to 14, wherein the delay-related information comprises, with respect to a candidate edge application server, information indicating the access network delay and assistance information for determining the data network delay.

16. The method according to any one of claims 12 to 15, wherein a user plane function entity of the communication network is identified by an IP address on a data network identified by the target data network access identifier.

17. The method according to claim 14 or 15, wherein the delay-related information facilitates determining a data network delay by performing or initiating measurement of the delay between the respective user plane function entity and the respective candidate edge application server using the assistance information.

18. The method according to any one of claims 14, 15 or 17, wherein the assistance information comprises information for facilitating measurement of the delay between the respective user plane function entity and the respective candidate edge application server.

19. The method according to claim 18, wherein the measurement facilitating information comprises measurement protocol information about an applicable protocol for the measurement and measurement configuration information about an applicable configuration for the measurement.

20. The method according to claim 19, whereinthe measurement protocol information indicates a simple two-way active measurement protocol and / or a two-way active measurement protocol as applicable measurement protocol, and / orthe measurement configuration information comprises one or more of protocol configuration information, addressing information, security information and validity information for the measurement and / or a connection for the measurement.

21. The method according to any one of claims 12 to 20, further comprising:sending at least one IP address, each IP address being associated with a user plane function entity.

22. The method according to any one of claims 12 to 21, further comprising:acquiring assistance information for determining the data network delay with respect to a candidate edge application server.

23. The method according to any one of claims 12 to 22, whereinthe method is operable at or by a session management function entity of the communication network, and / orthe list of candidate data network access identifiers and the delay-related information are sent to an application function entity or a network exposure function entity of the communication entity, and / ora target data network access identifier and an edge application server identifier of a target edge application server are received from an application function entity or a network exposure function entity of the communication entity, and / orthe user equipment is to use an application controlled by an application function entity of the communication network, which is to be delivered by an edge application server of the at least one candidate edge application server, and / orthe user plane function entity is configured as a packet data unit session anchor of a packet data unit session in the communication network and an endpoint of an interface between the communication network and the data network of the target edge application server, and / orthe access network delay is indicative of a delay on N3 and / or N9 reference points, and / or the data network delay is indicative of a delay on a N6 reference point.

24. An apparatus comprising means for performing the method according to any one of claims 1 to 11 or 12 to 23.

25. A computer program product comprising computer program code which, when the computer program code is executed on a computer, is configured to cause the computer to carry out the method according to any one of claims 1 to 11 or 12 to 23.