Enhanced decision and configuration for edge computing

Abstract

The invention relates to enhanced decision and configuration for edge computing. There are provided measures for (implementing / facilitating / implementing enhanced and / or improved) edge computing, such as enhanced decisions and configurations for edge computing. The measures include a network function, unit or entity: receiving a list of candidate data network access identifiers, and for each candidate data network access identifier, receiving delay-related information regarding a delay between the user equipment and at least one candidate edge application server; obtaining an access network delay (a delay between the user equipment and one or more user plane functional entities of the communication network) and a data network delay (a delay between the one or more user plane functional entities and a corresponding one of the at least one candidate edge application server); and selecting a target data network access identifier from the candidate data network access identifier list, and selecting a target edge application server from the at least one candidate edge application server.

Description

Technical Field

[0001] Various example embodiments of the present disclosure generally relate to wireless communication technologies. More specifically (but not exclusively), measures / mechanisms (including, for example, methods, apparatuses, and computer program products) for implementing (or otherwise facilitating or enabling) enhancements and / or improvements for edge computing (such as enhanced (e.g., efficient) decision-making and configuration for edge computing) are described. Background Art

[0002] Examples of mobile or wireless telecommunication technologies and systems can include 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 next-generation (NG) radio systems and network architectures. 5G and 6G network technologies are based on New Radio (NR) technology, but 5G / 6G (or NG) networks can also be built on E-UTRAN radio. It is estimated that NR can provide a bit rate of about 10 - 20 gigabits per second or higher, and can 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 provide extremely wideband and ultra-robust, low-latency connectivity and large-scale networking to support the Internet of Things (IoT).

[0003] List of Abbreviations and Acronyms

[0004] 3GPP Third Generation Partnership Project

[0005] 5G Fifth Generation

[0006] 5GC 5G Core

[0007] 5GS 5G System

[0008] 6G Sixth Generation

[0009] AF Application Function

[0010] AMF Access and Mobility Management Function

[0011] AUSF Authentication Server Function

[0012] DN Data Network

[0013] DNAI Data Network Access Identifier

[0014] E2E End-to-End

[0015] EAS Edge Application Server

[0016] EASDF EAS Discovery Function

[0017] EAS ID EAS Identifier

[0018] EHE Edge Hosting Environment

[0019] FQDN Fully Qualified Domain Name

[0020] HMAC Hash Message Authentication Code

[0021] HTTP Hypertext Transfer Protocol

[0022] IP Internet Protocol

[0023] N3IWF Non-3GPP Interworking Function

[0024] NEF Network Exposure Function

[0025] NFV(I) Network Function Virtualization (Infrastructure)

[0026] NR New Radio

[0027] NRF Network Repository Function

[0028] NSSF Network Slice Selection Function

[0029] PCF Policy Control Function

[0030] PDA PDU Session Anchor

[0031] PDU Packet Data Unit

[0032] PFCP Packet Forwarding Control Protocol

[0033] QoS Quality of Service

[0034] (R)AN (Radio) Access Network

[0035] SDN Software Defined Network

[0036] SMF Session Management Function

[0037] STAMP Simple Two-way Active Measurement Protocol

[0038] TNGF Trusted Non-3GPP Gateway Function

[0039] TWAMP Two-way Active Measurement Protocol

[0040] UDM Unified Data Management

[0041] UDP User Datagram Protocol

[0042] UDR Unified Data Repository

[0043] UE User Equipment

[0044] UPF User Plane Function

[0045] W-AGF Wireless Access Gateway Function SUMMARY OF THE INVENTION

[0046] Various example embodiments solve at least some of the problems, difficulties, and / or disadvantages described herein or otherwise recognized by those skilled in the art in view of the present disclosure.

[0047] The various example embodiments are set forth in the claims.

[0048] Some example embodiments among the various example embodiments are described with respect to particular aspects. These aspects are not intended to indicate key or essential features of the various example embodiments, nor are they intended to limit their scope. Other features, aspects, and elements will be recognized by those skilled in the art in view of the present disclosure.

[0049] According to an example aspect, a method is provided, comprising: receiving a list of candidate data network access identifiers, and for each candidate data network access identifier, receiving delay-related information regarding a delay between a user equipment and at least one candidate edge application server; based on the delay-related information, obtaining an access network delay and a data network delay, wherein the access network delay includes a delay between the user equipment and a user plane function entity of a communication network, and the data network delay includes a delay between the user plane function entity of the communication network and a candidate edge application server among the at least one candidate edge application servers of at least one data network; and based on the access network delay and the data network delay, selecting a target data network access identifier from the list of candidate data network access identifiers, and selecting a target edge application server from the at least one candidate edge application servers.

[0050] According to an example aspect, a device is provided, including: components for receiving a list of candidate data network access identifiers, and for each candidate data network access identifier, receiving delay-related information regarding a delay between a user equipment and at least one candidate edge application server; components for obtaining an access network delay and a data network delay based on the delay-related information, wherein the access network delay includes a delay between the user equipment and a user plane function entity of a communication network, and the data network delay includes a delay between the user plane function entity of the communication network and a candidate edge application server among the at least one candidate edge application servers of at least one data network; and components for selecting a target data network access identifier from the list of candidate data network access identifiers and selecting a target edge application server from the at least one candidate edge application server based on the access network delay and the data network delay.

[0051] According to an example aspect, a device is provided, including at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: receive a list of candidate data network access identifiers, and for each candidate data network access identifier, receive delay-related information regarding a delay between a user equipment and at least one candidate edge application server; obtain an access network delay and a data network delay based on the delay-related information, wherein the access network delay includes a delay between the user equipment and a user plane function entity of a communication network, and the data network delay includes a delay between the user plane function entity of the communication network and a candidate edge application server among the at least one candidate edge application servers of at least one data network; and select a target data network access identifier from the list of candidate data network access identifiers and select a target edge application server from the at least one candidate edge application server based on the access network delay and the data network delay.

[0052] According to an example aspect, a device is provided, including: a circuit configured to: receive a list of candidate data network access identifiers, and for each candidate data network access identifier, receive delay-related information regarding a delay between a user equipment and at least one candidate edge application server; based on the delay-related information, obtain an access network delay and a data network delay, where the access network delay includes a delay between the user equipment and a user plane function entity of a communication network, and the data network delay includes a delay between the user plane function entity of the communication network and a candidate edge application server among the at least one candidate edge application servers of at least one data network; and based on the access network delay and the data network delay, select a target data network access identifier from the list of candidate data network access identifiers, and select a target edge application server from the at least one candidate edge application servers.

[0053] According to various developments / modifications, any one of the foregoing method-related and / or device-related example aspects may include one or more of the following features:

[0054] The obtaining includes: obtaining the access network delay from the delay-related information, and / or determining the data network delay based on auxiliary information in the delay-related information.

[0055] The delay-related information includes information indicating the access network delay regarding a candidate edge application server and auxiliary information for determining the data network delay.

[0056] The obtaining includes: obtaining the access network delay regarding the candidate edge application server from the delay-related information, and / or determining the data network delay regarding the candidate edge application server based on the auxiliary information.

[0057] The 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.

[0058] Determining the data network delay includes: using the auxiliary information to perform or initiate a measurement of a delay between a corresponding user plane function entity and a corresponding candidate edge application server.

[0059] The auxiliary information includes information for facilitating a measurement of a delay between a corresponding user plane function entity and a corresponding candidate edge application server.

[0060] The measurement facilitation information includes measurement protocol information regarding an applicable protocol for the measurement and measurement configuration information regarding an applicable configuration for the measurement.

[0061] The measurement protocol information indicates the Simple Bidirectional Active Measurement Protocol and / or the Bidirectional Active Measurement Protocol as applicable measurement protocols,

[0062] The measurement configuration information includes one or more of protocol configuration information, addressing information, security information, and validity information for measurement and / or for the connection used for measurement,

[0063] The method, function, operability, or configuration includes or implements: sending the target data network access identifier and the edge application server identifier of the target edge application server,

[0064] The method, function, operability, or configuration includes or implements: accessing load information about the at least one candidate edge application server, where the load information indicates the load of the corresponding candidate edge application server, and where the target data network access identifier and the target edge application server are further selected based on the load information,

[0065] The method, function, operability, or configuration includes or implements: receiving at least one IP address, each IP address being associated with a user plane function entity, and where the target data network access identifier and the target edge application server are further selected based on the at least one IP address,

[0066] The method, function, operability, or configuration includes or implements: requesting notification or provision of delay-related information for each candidate data network access identifier and / or auxiliary information for determining data network latency,

[0067] The request is performed in at least one of the following: a service routing impact process; a service, operation, or process for establishing a session with a required quality of service; a service parameter service, operation, or process; or an edge application server deployment service, operation, or process,

[0068] The method, function, operability, or configuration is (operable as) part of or within a service routing impact process and / or a user plane management event notification process, or integrated in a service routing impact process and / or a user plane management event notification process,

[0069] The method, function, operability, or configuration can be operated at or by an application function entity of the communication network,

[0070] 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 a communication entity,

[0071] The target data network access identifier and the edge application server identifier of the target edge application server are sent to the session management function entity or the network exposure function entity of the communication entity.

[0072] The user equipment will use an application controlled by an application function entity of the communication network, and the application will be delivered by an edge application server among the at least one candidate edge application servers.

[0073] The access network delay indicates the delay at the N3 and / or N9 reference points, and / or the data network delay indicates the delay at the N6 reference point.

[0074] According to an example aspect, a method is provided, including: sending a list of candidate data network access identifiers, and for each candidate data network access identifier, sending delay-related information about the delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates obtaining an access network delay and a data network delay, wherein the access network delay includes the delay between the user equipment and a user plane function entity of a communication network, and the data network delay includes the delay between the user plane function entity of the communication network and a candidate edge application server among the at least one candidate edge application servers of at least one data network.

[0075] According to an example aspect, a device is provided, including: components for sending a list of candidate data network access identifiers, and for each candidate data network access identifier, sending delay-related information about the delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates obtaining an access network delay and a data network delay, wherein the access network delay includes the delay between the user equipment and a user plane function entity of a communication network, and the data network delay includes the delay between the user plane function entity of the communication network and a candidate edge application server among the at least one candidate edge application servers of at least one data network.

[0076] According to an example aspect, a device is provided that includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: send a list of candidate data network access identifiers, and for each candidate data network access identifier, send delay-related information regarding a delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates obtaining an access network delay and a data network delay, wherein the access network delay includes a delay between the user equipment and a user plane function entity of a communication network, and the data network delay includes a delay between the user plane function entity of the communication network and one of the at least one candidate edge application servers of at least one data network.

[0077] According to an example aspect, a device is provided that includes: circuitry configured to: send a list of candidate data network access identifiers, and for each candidate data network access identifier, send delay-related information regarding a delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates obtaining an access network delay and a data network delay, wherein the access network delay includes a delay between the user equipment and a user plane function entity of a communication network, and the data network delay includes a delay between the user plane function entity of the communication network and one of the at least one candidate edge application servers of at least one data network.

[0078] According to various developments / modifications, any one of the foregoing method-related and / or device-related example aspects may include one or more of the following features:

[0079] The method, function, operability, or configuration includes or implements: receiving a target data network access identifier from the list of candidate data network access identifiers, and receiving an edge application server identifier of a target edge application server from the at least one candidate edge application server,

[0080] The method, function, operability, or configuration includes or implements: configuring a user plane function entity among one or more user plane function entities from the communication network based on the target data network access identifier and the edge application server identifier of the target edge application server,

[0081] The delay-related information facilitates: obtaining the access network delay from the delay-related information, and / or determining the data network delay based on auxiliary information in the delay-related information,

[0082] The delay-related information includes information indicating the access network delay regarding the candidate edge application server and auxiliary information for determining the data network delay,

[0083] The 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.

[0084] The latency-related information facilitates determining the data network latency by measuring the latency between the corresponding user plane function entity and the corresponding candidate edge application server using the auxiliary information.

[0085] The auxiliary information includes information for facilitating the measurement of the latency between the corresponding user plane function entity and the corresponding candidate edge application server.

[0086] The measurement facilitation information includes measurement protocol information about the applicable protocol for the measurement and measurement configuration information about the applicable configuration for the measurement.

[0087] The measurement protocol information indicates the Simple Bidirectional Active Measurement Protocol and / or the Bidirectional Active Measurement Protocol as the applicable measurement protocol.

[0088] The measurement configuration information includes one or more of protocol configuration information, addressing information, security information, and validity information for the measurement and / or for the connection used for the measurement.

[0089] The method, function, operability, or configuration includes or implements: sending at least one IP address, each IP address associated with a user plane function entity.

[0090] The method, function, operability, or configuration includes or implements: obtaining auxiliary information for determining the data network latency regarding a candidate edge application server.

[0091] The auxiliary information for determining the data network latency is obtained from the user plane function entity and / or the network repository function entity of the communication network.

[0092] The auxiliary information for determining the data network latency is obtained as part of an association establishment or update process (such as a Packet Forwarding Control Protocol association establishment or update process) with the user plane function entity and / or a network function discovery service, operation, or process with the network repository function entity of the communication network.

[0093] The method, function, operability, or configuration includes or implements: receiving a request to notify or provide latency-related information for each candidate data network access identifier and / or auxiliary information for determining the data network latency.

[0094] The method, function, operability, or configuration includes or implements: after receiving the request, setting conditions for sending delay-related information for each candidate data network access identifier and / or auxiliary information for determining data network delay, where when the conditions are met, the delay-related information for each candidate data network access identifier and / or the auxiliary information for determining data network delay are sent,

[0095] The method, function, operability, or configuration includes or implements: after receiving the request, setting a corresponding user plane function entity for measuring the delay between the corresponding user plane function entity and the corresponding candidate edge application server,

[0096] The request is received in at least one of a service routing impact process, a service for establishing a session with a required quality of service, a service parameter service, or an edge application server deployment service,

[0097] The method, function, operability, or configuration is (configured to operate in or as) part of a service routing impact process and / or a user plane management event notification process or integrated in a service routing impact process and / or a user plane management event notification process,

[0098] The method, function, operability, or configuration can operate at the session management function entity of the communication network or be operated by the session management function entity of the communication network,

[0099] The list of candidate data network access identifiers and the delay-related information are sent to the application function entity or the network exposure function entity of the communication entity,

[0100] The target data network access identifier and the edge application server identifier of the target edge application server are received from the application function entity or the network exposure function entity of the communication entity,

[0101] The user equipment will use an application controlled by the application function entity of the communication network, and the application will be delivered by the edge application server in the at least one candidate edge application server,

[0102] The user plane function entity is configured as the packet data unit session anchor for the packet data unit session in the communication network and as the endpoint of the interface between the communication network and the data network of the target edge application server,

[0103] The access network delay indicates the delay at the N3 and / or N9 reference points, and / or the data network delay indicates the delay at the N6 reference point.

[0104] According to an example aspect, a system is provided that includes at least two devices among the devices according to any one of the foregoing example aspects related to the device (and / or any development / modification thereof).

[0105] According to an example aspect, a computer-readable medium including program instructions is provided, the program instructions being for causing a device (e.g., a device according to any one of the foregoing example aspects related to the device (and / or any development / modification thereof)) to at least perform a method according to any one of the foregoing example aspects related to the method (and / or any development / modification thereof).

[0106] According to an example aspect, a computer program product including (computer-executable) computer program code is provided, and when the program code is executed (or run) on a computer or the program runs on a computer (e.g., a computer of a device according to any one of the foregoing example aspects related to the device (and / or any development / modification thereof)), the computer program code is configured to cause the computer to at least perform a method according to any one of the foregoing example aspects related to the method (and / or any development / modification thereof).

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

[0108] As used herein, the term "non-transitory" is a limitation on the medium itself (referring to, for example, a tangible medium rather than a signal), rather than a limitation on data storage persistence (e.g., RAM versus ROM).

[0109] Further developments and / or modifications of the above example aspects are set forth below.

[0110] As an example embodiment, techniques for (e.g., enabling or otherwise facilitating or implementing enhancement and / or improvement) edge computing may be provided, such as enhanced (e.g., efficient) decision-making and configuration for edge computing.

[0111] This overview is intended to provide a brief overview of some aspects (and their features) of various example embodiments according to the present disclosure. Accordingly, it will be understood that the above aspects (and their features) are merely examples and should not be construed as narrowing the scope of the various example embodiments or the disclosure in any way. Other features, aspects, and advantages of the present disclosure will become apparent from the following detailed description, the drawings, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0112] Various example embodiments will be described below with reference to the drawings, wherein:

[0113] Figure 1 Shows a schematic diagram of an example (mobile / wireless) communication system or network;

[0114] Figure 2 Shows a schematic diagram of an example wireless device or entity;

[0115] Figure 3 Shows a schematic diagram of an example network node or entity;

[0116] Figure 4 Shows a schematic diagram of an example architecture of a 5G system;

[0117] Figure 5 Shows a schematic diagram of an example architecture of a 5G system supporting edge computing;

[0118] Figure 6 Shows a flowchart of an example method or process;

[0119] Figure 7 Shows a flowchart of an example method or process;

[0120] Figure 8 Shows a schematic diagram illustrating various delays in an example architecture;

[0121] Figure 9 Shows a sequence diagram of an example process;

[0122] Figure 10 Shows a sequence diagram of an example process;

[0123] Figure 11 Shows a schematic block diagram illustrating the structure of a device. Detailed implementation

[0124] Various example embodiments are described herein with reference to specific non - restrictive and illustrative examples. Those skilled in the art will understand that these various exemplary embodiments are in no way limited to these non - restrictive and illustrative examples and can be more widely applied.

[0125] References in the specification to "one embodiment", "an embodiment", "example embodiment", "some example embodiments", "specific example embodiments", "various example embodiments", etc. indicate that the recited (one or more) embodiment(s) may include the recited (one or more) specific feature(s), (one or more) structure(s) or (one or more) characteristic(s), but not every recited embodiment or example embodiment necessarily includes the (one or more) specific feature(s), (one or more) structure(s) or (one or more) characteristic(s). Moreover, such phrases do not necessarily refer to the same embodiment or example embodiment. Further, when a (one or more) specific feature(s), (one or more) structure(s) or (one or more) characteristic(s) are described in connection with an embodiment or example embodiment, it is considered within the knowledge of those skilled in the art to implement such feature(s), structure(s) or characteristic(s) in connection with any other embodiment or example embodiment, whether or not such combination is explicitly described.

[0126] It should be noted that the detailed description sometimes refers to one or more specifications, which are used as non - limiting and illustrative examples for a particular architecture, network configuration, and system deployment. More specifically, the detailed description refers to 3GPP standards, which are used as non - limiting and illustrative examples. Thus, the exemplary embodiments provided herein may specifically adopt terms directly related thereto. Such terms are used only in the context of non - limiting and illustrative examples and are not intended to limit the example embodiments in any way. Instead, any other system configuration or deployment may be utilized while conforming to what is described herein and / or the example embodiments are applicable to any other such system configuration or deployment.

[0127] For example, various example embodiments may be applied to any (e.g., mobile / wireless) communication system, such as 5G / NR systems and next - generation / future systems beyond 5G. For example, various exemplary embodiments may be applied to 3GPP standardized mobile / wireless communication systems after Release 19. Moreover, although reference is made to 5G / NR, other types of access / systems / networks are also supported / covered, such as future 3GPP radio / 6G, but non - 3GPP access to the 3GPP core is also supported / covered (e.g., untrusted non - 3GPP access to the 3GPP core using, e.g., N3IWF, trusted non - 3GPP access to the 3GPP core using, e.g., TNGF, wired access to the 3GPP core using, e.g., W - AGF), etc.

[0128] When referring to specific terms unique to any such example system, these references should be understood / interpreted to apply more generally with corresponding, similar, or equivalent meanings. More specifically, when referring to some network functions, entities, or units of a 5G / NR or 3GPP system, it should be understood / interpreted to mean or include any network function, entity, or unit of any system that has or exhibits corresponding, similar, or equivalent characteristics, functions, purposes, etc. 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 should mean or include any network function, entity, or unit of any communication network that has or exhibits characteristics, functions, purposes, etc. that are corresponding, similar, or equivalent to those of the referenced application or session management function, respectively.

[0129] In the following, various exemplary embodiments are described using several variations and / or alternatives. Generally, it should be noted that all described variations and / or alternatives can be provided individually or in any conceivable combination (e.g., also including combinations of the individual features of these various variations and / or alternatives), depending on a particular implementation or constraint.

[0130] As used herein, the words "comprising" and "including" should be understood not to limit the example embodiments to only the features already mentioned, and the example embodiments may also include features, structures, units, modules, etc. that are not specifically mentioned, for example.

[0131] As used herein, "at least one of the following: <list of two or more elements>" and "at least one of <list of two or more elements>" and similar expressions (such as "one or more", where the list of two or more elements is connected by "and" or "or") refer to at least any one element, or at least any two or more elements, or at least all elements. As used herein, the expression "and / or" refers to at least any one element, or at least any two or more elements, or at least all elements.

[0132] As used herein, unless explicitly stated to the contrary, performing a step / operation / function "in response to A" does not mean that the step / operation / function is performed immediately after "A" occurs, as one or more intermediate steps / operations / functions may be included between them. Similarly, performing a step / operation / function "based on A" does not mean that the step / operation / function is performed only based on "A", as the referenced step / operation / function may be further based on one or more other conditions (such as "B") in addition to "A".

[0133] As used herein, according to various example embodiments, any operation of sending or receiving may include an actual transmission or communication operation, e.g., sending or transmitting associated information, data, signals, or messages, but may additionally or alternatively include associated processing operations, e.g., preparing / generating / publishing associated information, data, signals, or messages before sending, and / or obtaining / processing associated information, data, signals, or messages after receiving. For example, sending information or data at / by an entity may include generating / publishing and / or sending / transmitting the information or data or sending the corresponding signals or messages in / at / by the entity, and receiving signals or messages at / by an entity may include obtaining / processing and / or processing the signals or messages or receiving the corresponding information or data in / at / by the entity. As used herein, a signal or message may refer to and / or include any kind of corresponding information, data, signals, etc.

[0134] In the drawings, it should be noted that the lines / arrows interconnecting the various blocks or entities generally are intended to show an operational coupling therebetween, which may be a physical and / or logical coupling that is implementation-agnostic on the one hand (e.g., wired or wireless) and may also include any number of intermediate functional blocks or entities not shown on the other hand. In a flowchart or sequence diagram, the shown order of operations or actions generally is non-limiting and illustrative, and any other order of the corresponding operations or actions may be contemplated if feasible.

[0135] Various example embodiments relate to considerations in (e.g., mobile / wireless) communication systems or networks (e.g., 5G / NR systems and next-generation / future systems beyond 5G). For example, various example embodiments may be applied to 3GPP standardized mobile / wireless communication systems or networks after Release 19.

[0136] Such considerations relate to edge computing. Edge computing is a concept that enables (or otherwise facilitates or enables) services to be hosted near service consumers and can provide benefits (e.g., enhanced (e.g., efficient) service delivery with reduced end-to-end latency and reduced load on the transport network). With edge computing, user equipment residing in a communication network may use an application controlled by an application function entity of the communication network, where the application is delivered by an edge application server of a data network connected to the communication system.

[0137] Furthermore, such considerations may relate to enhancements and / or improvements to edge computing, such as enhanced (e.g., efficient) decision-making and configuration for edge computing.

[0138] Before further elaborating on the example embodiments, reference Figures 1 to 3Briefly explain some general aspects of a (mobile / wireless) communication system or network to facilitate understanding of the technology underlying the described example embodiments.

[0139] Figure 1 An example of a (mobile / wireless) communication system or network 100 that can be used for wireless communication is shown. The 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., eNB, gNB, etc.), which are connected to one or more network nodes or entities 130 via an interconnect network 125. The communication system or network 100 can use any suitable deployment scenario. Each UE 110 within the coverage area 115 is capable of communicating directly with the radio access node 120 via a wireless interface. In some example embodiments, the UEs 110 are also capable of communicating with each other via device - to - device (D2D) communication.

[0140] As an example, UE 110A can communicate with radio access node 120A via a wireless interface. That is, UE 110A can send wireless signals to radio access node 120A and / or receive wireless signals from radio access node 120A. The wireless signals can include voice traffic, data traffic, control signals, and / or any other suitable information.

[0141] As used herein, the term "user equipment" (UE) has the full scope of its ordinary meaning and can refer to any type of wireless device or entity capable of communicating with a network node or entity and / or with another UE in a cellular or mobile or wireless / mobile communication system. Examples of UEs are target devices, D2D UEs, machine - type UEs or UEs capable of machine - to - machine (M2M) communication, personal digital assistants, tablets, mobile terminals, smart phones, laptop - embedded devices (LEE), laptop - mounted devices (LME), USB dongles, ProSe UEs, vehicle - to - vehicle (V2V) UEs, V2X UEs, machine - type communication (MTC) UEs, eMTC UEs, FeMTC UEs, UE Cat 0, UE Cat M1, narrowband IoT (NB - IoT) UEs, UE CatNB1, etc. Example embodiments of the UE are described in more detail below with reference to Figure 2 More detailed example embodiments of the UE are described.

[0142] In some example embodiments, the wireless signal coverage area 115 associated with the radio access node 120 can be referred to as a cell. However, particularly for the fifth - generation (5G) / New Radio (NR) mobile communication concept, beams can be used instead of cells, and thus, it is important to note that the concepts described herein apply equally to cells and beams.

[0143] For a beam-based mobile communication system, a radio access node 120 (base station) may transmit a beamformed signal to a UE 110 in one or more transmission directions (transmission beams, Tx beams). The UE 110 may receive the beamformed signal from the base station 120 in one or more reception directions (reception beams, Rx beams). 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 optimal reception and transmission directions for each base station / UE pair, e.g., optimal in the sense that these directions result in the highest link quality or satisfy other quality conditions in the most appropriate manner.

[0144] The interconnect network 125 may refer to any interconnected system capable of sending audio, video, signals, data, messages, etc., or any combination of the foregoing. The interconnect network 125 may include all or a part of the following: 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 wired or wireless network, an enterprise intranet, or any other suitable communication link, including combinations of the foregoing.

[0145] In some example embodiments, the network node 130 may be a core network node that manages the establishment of communication sessions and various other functions of the UE 110. Examples of the network node 130 may include a mobile switching center (MSC), an MME, a serving gateway (SGW), a packet data network gateway (PGW), operations and maintenance (O&M), an operations support system (OSS), a SON, a positioning node (e.g., an enhanced serving mobile location center E-SMLC), a location server node, an MDT node, etc. The UE 110 may use the non-access stratum (NAS) layer to exchange specific signals with the network node 130. In non-access stratum signaling, the signals between the UE 110 and the network node 130 may be transparently passed through the radio access network. In some example embodiments, the radio access node 120 may interface with one or more network nodes 130 through an inter-node interface.

[0146] As used herein, the term "network node or entity" has the full scope of its ordinary meaning and can correspond to any type of radio access node (or radio network node) or any network node capable of communicating with a UE and / or another network node in a cellular or mobile or wireless communication system. Examples of network nodes are NodeB, MeNB, SeNB, network nodes that can belong to MCG or SCG, base station (BS), multi-standard radio (MSR) radio access node (e.g., MSR BS), eNodeB, network controller, radio network controller (RNC), base station controller (BSC), repeater, donor node controlling the repeater, base transceiver station (BTS), access point (AP), transmission point, transmission node, RRU, RRH, nodes in a distributed antenna system (DAS), core network nodes (e.g., MSC, MME, etc.), O&M, OSS, self-organizing network (SON), positioning node (e.g., E-SMLC), MDT, test equipment, etc. Example embodiments of network nodes are described in more detail below with reference to Figure 3 Example embodiments of network nodes are described in more detail below.

[0147] In some example embodiments, radio access node 120 can be a distributed radio access node. The components of radio access node 120 and their associated functions can be divided into two main units (or sub-radio network nodes), which can be referred to as a central unit (CU) and a distributed unit (DU). Different distributed radio network node architectures are possible. For example, in some architectures, the DU can be connected to the CU via a dedicated wired or wireless link (e.g., an optical cable), while in other architectures, the DU can be connected to the CU via a transport network. Moreover, how the various functions of radio access node 120 are divided between the CU and the DU can vary depending on the implemented architecture.

[0148] An example wireless communication system is an architecture standardized by the 3rd Generation Partnership Project (3GPP). The most recent 3GPP-based developments are generally referred to as Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) Radio Access Technology (RAT). The various development stages of 3GPP specifications are referred to as releases. More recent developments of LTE are generally referred to as LTE-Advanced (LTE-A). LTE (LTE-A) employs a radio access architecture called the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a core network called the Evolved Packet Core (EPC). The base stations of such a system are called evolved or enhanced Node Bs (eNBs) and provide E-UTRAN features such as user plane packet data convergence / radio link control / media access control / physical layer protocol (PDCP / RLC / MAC / PHY) towards communication devices and control plane radio resource control (RRC) protocol termination. Other examples of RATs include those provided by base stations of systems based on technologies such as WLAN and / or Worldwide Interoperability for Microwave Access (WiMax). The base stations can provide coverage of an entire cell or a similar radio service area. Core network elements include a Mobility Management Entity (MME), a Serving Gateway (S-GW), and a Packet Gateway (P-GW).

[0149] An example of a suitable communication system is the 5G or NR concept. The network architecture in NR can be similar to that of LTE-A. The base stations of an NR system can be called Next Generation Node Bs (gNBs). Changes to the network architecture can depend on the support for various radio technologies and finer Quality of Service (QoS), as well as some requirements as per the QoS levels that support Quality of Experience (QoE) from the user's perspective. Network-aware services and applications, and service- and application-aware networks can also bring about changes to the architecture. These involve Information-Centric Networking (ICN) and User-Centric Content Delivery Network (UC-CDN) approaches. NR can use multiple-input multiple-output (MIMO) antennas, many more base stations or nodes than LTE (the so-called small cell concept), including macro sites operating in cooperation with smaller stations, and may also employ various radio technologies to achieve enhanced (e.g., better, increased, etc.) coverage and data rates.

[0150] Future networks can utilize Network Function Virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that can be operably connected or chained together to provide services. Virtualized Network Functions (VNFs) can include one or more virtual machines that run computer program code using standard or general-purpose type servers instead of custom hardware. Cloud computing or data storage can also be utilized. In radio communications, this can mean that node operations are to be performed at least in part in a server, host, or node that is operably coupled to a remote radio head. Node operations can also be distributed among multiple servers, nodes, or hosts. It should also be understood that the distribution of work between core network operations and base station operations can be different from or even non-existent compared to that of LTE.

[0151] An example 5G Core Network (CN) includes functional entities. The CN is connected to a UE via a Radio Access Network (RAN). A User Plane Function (UPF), whose role is called the PDU Session Anchor (PSA), can be responsible for forwarding frames back and forth between a Data Network (DN) and a UE that exchanges traffic with the data network (DN) via a tunnel established by 5G. The UPF is controlled by a Session Management Function (SMF) that receives policies from a Policy Control Function (PCF). The CN can also include an Access & Mobility Function (AMF).

[0152] In general, all concepts disclosed herein are applicable to different communication networks, including but not limited to LTE, LTE-A, 5G, 5G Advanced, 6G, and other future or already implemented networks.

[0153] Figure 2 is a schematic diagram of an example wireless device UE 110 according to a specific example embodiment. The UE 110 can include one or more of the following: at least one transceiver 210, at least one processor 220, at least one memory 230, and at least one network interface 240. In a specific example embodiment, the transceiver 210 facilitates sending wireless signals to and receiving wireless signals from a radio access node 120 (e.g., via a transmitter (Tx), a receiver (Rx), and an antenna). The processor 220 executes instructions to provide some or all of the functions described herein as being provided by a wireless device / entity or UE, and the memory 230 stores the instructions executed by the processor 220. In some embodiments, the processor 220 and the memory 230 form a processing circuit.

[0154] The processor 220 may include any suitable combination of hardware for executing instructions and manipulating data to perform some or all of the described functions of the wireless device or entity, such as the functions of the UE 110 described herein. In some embodiments, the processor 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.

[0155] The memory 230 is generally operable to store instructions, such as computer programs, software, applications including one or more of logic, rules, algorithms, code, tables, etc., and / or other instructions executable by the processor 220. Examples of the memory 230 include computer memory (e.g., random access memory (RAM) or read only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory computer-readable and / or computer-executable storage device storing information, data, and / or instructions that may be used by the processor 220 of the UE 110. For example, the memory 230 includes computer program code that causes the processor 220 to perform processing according to any corresponding method (or portions thereof) described herein.

[0156] The network interface 240 is communicatively coupled to the processor 220 and may refer to any suitable device operable to receive inputs for the UE 110, transmit outputs from the UE 110, perform appropriate processing of the inputs or outputs or both, communicate with other devices, or any combination of the foregoing. The network interface 240 may include suitable hardware (e.g., ports, modems, network interface cards, etc.) and software (including protocol conversion and data processing capabilities) to communicate over a network.

[0157] Other example embodiments of the UE 110 may include Figure 2 additional components beyond those shown, which may be responsible for providing specific aspects of the functionality of the wireless device, including any of the functions described herein and / or any additional functions (including supporting any functions in accordance with the mechanisms of the present disclosure). By way of example, the UE 110 may include input devices and circuitry, output devices, and one or more synchronization units or circuitry, which may be part of the processor 220. Input devices include mechanisms for inputting data into the UE 110. For example, the input devices may include input mechanisms such as microphones, input elements, displays, etc. Output devices may include mechanisms for outputting data in audio, video, and / or hard copy format. For example, the output devices may include speakers, displays, etc.

[0158] In a particular example embodiment, the wireless device UE 110 may include a series of modules configured to implement the functions of the wireless device described herein.

[0159] It should be understood that the various modules may be implemented as a combination of hardware and software (e.g., Figure 2 the processor, memory, and transceiver of the UE 110 as shown). The particular example embodiment may also include additional modules for supporting additional and / or optional functions.

[0160] Figure 3 is a schematic diagram of an example radio access node 120 or network node or entity 130 according to a particular example embodiment. The radio access node 120 or network node or entity 130 may include one or more of the following: at least one transceiver 310, at least one processor 320, at least one memory 330, and at least one network interface 340. In a particular example embodiment, the transceiver 310 facilitates sending wireless signals to wireless devices such as the UE 110 and receiving wireless signals from wireless devices such as the UE 110 (e.g., via a transmitter (Tx), a receiver (Rx), and an antenna). The processor 320 executes instructions to provide some or all of the functions described herein as being provided by the radio access node 120 or network node or entity 130, and the memory 330 stores the instructions executed by the processor 320. In some example embodiments, the processor 320 and the memory 330 form a processing circuit. The network interface 340 may convey signals to backend network components such as gateways, switches, routers, the Internet, the public switched telephone network (PSTN), core network nodes, or radio network controllers, etc.

[0161] The processor 320 may include any suitable combination of hardware for executing instructions and manipulating data to perform some or all of the described functions of the radio access node 120 or network node or entity 130 (e.g., those functions described herein). In some example embodiments, the processor 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.

[0162] Memory 330 is generally operable to store instructions, such as computer programs, software, applications including one or more of logic, rules, algorithms, code, tables, etc. and / or other instructions executable by processor 320. Examples of memory 330 include computer memory (e.g., random access memory (RAM) or read only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory computer-readable and / or computer-executable storage device storing information. For example, memory 330 includes computer program code that causes processor 320 to perform processing according to any corresponding method (or portion thereof) described herein.

[0163] In a particular example embodiment, network interface 340 is communicatively coupled to processor 320 and may refer to any suitable device operable to receive inputs for radio access node 120 or network node or entity 130, transmit outputs from radio access node 120 or network node or entity 130, perform appropriate processing of the inputs or outputs or both, communicate with other devices, or any combination of the foregoing. Network interface 340 may include suitable hardware (e.g., ports, modems, network interface cards, etc.) and software (including protocol conversion and data processing capabilities) to communicate over a network.

[0164] Other example embodiments of radio access node 120 or network node or entity 130 may include Figure 3 additional components beyond those shown, which may be responsible for providing specific aspects of the functionality of the node, including any functionality described herein and / or any additional functionality (including any functionality supporting the solutions described herein). 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 partially or completely different physical components.

[0165] Similar processors, interfaces, and memories as those described with respect to Figure 3 may be included in other nodes or entities (such as UE 110, radio access node 120, etc.). Other nodes or entities may optionally include or not include a wireless interface (e.g., Figure 3 the transceiver described in

[0166] In a particular example embodiment, radio access node 120 or network node or entity 130 may include a series of modules configured to implement the functionality of radio access node 120 or network node or entity 130 described herein.

[0167] It should be understood that various modules can be implemented as a combination of hardware and software (e.g., the processor, memory, and transceiver of the wireless access node 120 or network node or entity 130 as shown in Figure 3 ). Specific example embodiments may also include additional modules for supporting additional and / or optional functionality.

[0168] Before referring to Figures 6 to 11 and describing the details of the techniques for (e.g., enabling / facilitating / implementing enhanced and / or improved) edge computing (such as enhanced (e.g., efficient) decision-making and configuration for edge computing), some additional information and aspects related to specific example embodiments will be provided. It should be noted that although described in a specific manner or context, all concepts described herein can be more generally applied to, for example, another specific manner or context as will be apparent to those skilled in the art.

[0169] Figure 4 and 5 shows an example architecture of the network / system foundation on which some example embodiments for the techniques disclosed herein can be built.

[0170] Figure 4 shows a schematic diagram of an example architecture of a 5G system or 5GS architecture.

[0171] In Figure 4 , the user plane (i.e., the network functions, entities, and / or units involved in the transmission of user data) is shown at the bottom, while the upper part shows the control plane, i.e., the network functions, entities, and / or units involved in control and / or signaling.

[0172] Figure 4 shows the network functions, entities, or units of a communication network (which may also be referred to as or considered an access network), such as (R)AN, UPF, SMF, AMF, AUSF, NSSF, NEF, NRF, PCF, UDM, and AF, user equipment (UE) that can be considered part of the communication network or reside in the communication network, and a data network (DN) connected to the communication network. In addition, interfaces (which may also be referred to as service interfaces or reference points) such as N1, N2, N3, N4, N6, N9 (N9 is the interface between different UPFs), etc. are depicted. The architecture, nodes, and interfaces can be defined according to standards such as 3GPP TS23.501, although other standards or configurations may be used.

[0173] Figure 5 shows a schematic diagram of an example architecture of a 5G system or 5GS architecture that supports edge computing.

[0174] Given their similarity, refer to the above Figure 4 description to obtain Figure 5Details. It should be noted that the UPF represents or is configured as the PDU session anchor (PSA) of a PDU session in a communication network and the endpoint of the N6 interface between the communication network and the (local part of the) data network of one or more edge application servers (EASs), where any EAS is configured to deliver (or execute, process, etc.) an application controlled by the AF and used by the UE. These architectures, nodes, and interfaces can be defined according to standards such as 3GPP TS23.548, although other standards or configurations can be used.

[0175] Regardless Figure 4 and 5 how the exemplary illustration of Figure 4 and 5 is, it should be noted that not all nodes and / or interfaces are required, and / or can be combined

[0176] The techniques disclosed herein generally relate to enhancements and / or improvements to edge computing in a communication system.

[0177] For example, in the context of a 5G / NR system, the techniques disclosed herein refer to enhancements and / or improvements to support edge computing in a 5G system or core network. This can include, for example, aspects of how to support enhanced (e.g., more efficient) edge hosting environment (EHE) information management and related EAS discovery, which can include whether and how to consider the N6 latency between the local PSA and the EAS for local UPF and EAS (re)selection, and may also include whether to consider EAS load.

[0178] In this context, the techniques disclosed herein can be considered to at least partially address issues in the area of local UPF and EAS (re)selection, including considerations of what information can / should be used for this purpose, such as N6 latency and / or EAS load. This will be described in more detail below.

[0179] Application services (involving the delivery, execution, or processing of an application) typically create multiple service instances. Service instances are typically geographically distributed across multiple sites, and a single site can support multiple instances of a service. High data rate low latency services (e.g., cloud gaming that requires high data rate and low latency communication) depend not only on network metrics (e.g., bandwidth and latency) but also on computing metrics (e.g., processing, storage capabilities, and capacity as an indicator of EAS load).

[0180] When multiple candidate paths to an application service (or an EAS that delivers, executes, or processes the application) are available for selecting an optimal service instance, for example, the topologically closest path may not always meet service-specific requirements and metrics. For example, some available links may be congested. In Rel-18, 5GS provides support for means to determine, report, and disclose congestion status, data rate information, and round-trip latency on the UE path between the UE and the PSA UPF. However, when multiple EAS instances are available for selection to provide an enhanced (e.g., best possible) E2E user experience, no means are defined that also consider the above metrics regarding the data network (e.g., N6 (such as the N6 latency between the local PSA and the EAS), EAS load).

[0181] In view of this, it is worth studying whether and how to consider, for example, EAS load and / or the N6 latency between the local PSA and the EAS for local UPF and EAS (re)selection. Such a study may include one or more of the following items.

[0182] - How to enable (or otherwise facilitate or implement) 5GC and / or third-party trusted and / or untrusted application functions to make the most appropriate decision in selecting the local UPF and EAS considering the E2E latency including the latency between the candidate N6 interface including 5GS and the candidate EAS.

[0183] - What information (e.g., EAS load, N6 latency information) between the local PSA and the EAS is considered and at which level for local UPF (re)selection and EAS (re)discovery.

[0184] - How to obtain the above information in 5GS. How to manage and process the above information in 5GS (e.g., as part of edge data network and EAS-related information).

[0185] - Whether and how 5GS discloses the above information.

[0186] - Whether and how to consider the above information for local UPF (re)selection and EAS (re)discovery.

[0187] Therefore, there is room for enhancement and / or improvement in this regard, and the techniques disclosed herein relate to at least a portion of these aspects, issues, or considerations illustrated above in the context of the 5G / NR system.

[0188] Hereinafter, various example embodiments of the present disclosure are further explained.

[0189] Figure 6A flowchart of an example method or process according to at least one example embodiment is shown. The example method or process may be executed at or by a device. The device may (at least partially) implement or in other words the method or process may be a method or process of an Application Function (AF) or an AF entity that is an example of a network function, entity, or unit of a communication system (or in other words, operable or used in / by the application function or AF entity).

[0190] As Figure 6 shown, the method or process includes: a step / operation (S610) of receiving a list of candidate data network access identifiers and, for each candidate data network access identifier, receiving delay-related information regarding the delay between a user equipment and at least one candidate edge application server; a step / operation (S620) of obtaining (or deriving, etc.) an access network delay and a data network delay based on the delay-related information; and a step / operation (S630) of selecting a target data network access identifier from the list of candidate data network access identifiers and / or selecting a target edge application server from at least one candidate edge application server based on the access network delay and the data network delay.

[0191] It should be noted that the selection in step / operation S630 may refer to or include an initial or subsequent selection (such as a (re)selection of DNAI and / or EAS), an initial or subsequent discovery (such as a (re)discovery of EAS), etc.

[0192] It should be noted that the (selected) target data network access identifier may identify the data network in which the (selected) target edge application server is located or to which the (selected) target edge application server is associated. The user plane function entity of a communication network may be identified by an IP address on the data network identified by the target data network access identifier (e.g., the network in which the (selected) target edge application server is located or the network to which the (selected) target edge application server is associated) (or for, regarding the data network, etc.).

[0193] As Figure 6As shown, the method or process may include, for example, the step / operation of obtaining the access network latency (S622) as part of or as the acquisition step / operation S620, and / or the step / operation of determining the data network latency (S624). In step / operation S622, the access network latency may be obtained from latency-related information. In step / operation S624, the data network latency may be determined (e.g., measured) based on the auxiliary information in the latency-related information. The latency-related information may include corresponding information about candidate edge application servers, such that the access network latency of the candidate edge application servers can be obtained from the information in the latency-related information, and / or the data network latency of the candidate edge application servers can be determined (e.g., measured) based on the auxiliary information (or as part of the latency-related information) in the latency-related information.

[0194] As Figure 6 shown, the method or process may further include the step / operation of sending the (selected) target data network access identifier and the edge application server identifier of the (selected) target edge application server (S640).

[0195] Although not shown in Figure 6 it, the method or process may further include the step / operation of accessing the load information about at least one candidate edge application server, where the load information indicates the load of the corresponding candidate edge application server. For example, at or for the AF (the AF constituting, participating in, or included in the edge hosting environment (EHE) of a specific EAS / for a specific EAS / with a specific EAS), the load of the specific EAS of the same EHE is accessible, e.g., locally available, obvious, or exportable for the AF. Then, the target data network access identifier and the target edge application server may be further selected based on the load information (in addition to other available information).

[0196] Although not shown in Figure 6 it, the method or process may further include the step / operation of receiving at least one IP address, each IP address being associated with a user plane function entity. For example, the IP address may be associated with one or more of the (candidate) UPF or PSA-UPF. Then, the target data network access identifier and the target edge application server may be further selected based on the at least one IP address (in addition to other available information).

[0197] Although not shown in Figure 6is not shown, but the method or process may further include steps / operations of requesting notification or providing delay-related information for each candidate data network access identifier and / or auxiliary information for determining data network delay. For example, such a request may be performed in a service routing impact process, a service, operation, or process for establishing a session with a desired quality of service, a service parameter service, operation, or process, and / or an edge application server deployment service, operation, or process. After receiving such a request, the requested delay-related information and / or auxiliary information may be received in the receiving step / operation S610.

[0198] Figure 7 FIG. shows a flowchart of an example method or process according to at least one example embodiment. The example method or process may be performed at or by a device. The device may (at least partially) implement or in other words the method or process may be a method or process of a session management function (SMF) or an SMF entity that is an example of a network function, entity, or unit of a communication system (or in other words the method or process is operable or used in / by an SMF or an SMF entity). For at least a part of the shown method or process, the device may implement (at least partially) or in other words at least a part of the method or process may be a method or process of a network exposure function (NEF) or an NEF entity that is an example of a network function, entity, or unit of a communication system (or in other words the method or process is operable or used in / by an NEF or an NEF entity).

[0199] As Figure 7 shown, the method or process includes steps / operations (S710) of sending a list of candidate data network access identifiers and, for each candidate data network access identifier, sending delay-related information about the delay between the user equipment and at least one candidate edge application server.

[0200] As Figure 7 shown, the method or process may further include steps / operations (S720) of receiving a target data network access identifier from the list of candidate data network access identifiers and / or receiving an edge application server identifier of a target edge application server from at least one candidate edge application server. After such a receiving step / operation, the method or process may further include steps / operations (S730) of configuring a user plane function entity among one or more user plane function entities from a communication network based on the target data network access identifier and the edge application server identifier of the target edge application server. Although not shown, after such a receiving step / operation, the method or process may alternatively include steps / operations of sending (forwarding) the received target data network access identifier and the received edge application server identifier.

[0201] It should be noted that the configuration in step / operation S730 may refer to or include initial or subsequent configurations, such as (re)configuration of the UPF or PSA-UPF, initial or subsequent selection, positioning, addition, removal, or change, such as (re)selection, (re)positioning, (re)addition, (re)removal, or (re)change of the UPF or PSA-UPF, etc.

[0202] Although not shown in Figure 7 the method or process may further include the step / operation of sending at least one IP address, each IP address being associated with a user plane function entity. For example, the IP address may be associated with one or more of the (candidate) UPF or PSA-UPF.

[0203] Although Figure 7 not shown in, the method or process may further include the step / operation of obtaining (or acquiring, etc.) auxiliary information for determining the data network latency regarding the candidate edge application server. Thus, the requested auxiliary information may be sent in the sending step / operation S710. In one example, for example, in any of the example architectures of Figure 4 and Figure 5 the auxiliary information for determining the data network latency may be obtained (or acquired, etc.) from the UPF. For example, the auxiliary information for determining the data network latency may be obtained (or acquired, etc.) as part of the association establishment or update process with the UPF (such as the PFCP association establishment or update process). In another example, for example, in any of the example architectures of Figure 4 and Figure 5 the auxiliary information for determining the data network latency may be obtained (or acquired, etc.) from the NRF. For example, the auxiliary information for determining the data network latency may be obtained (or acquired, etc.) as part of the network function discovery service, operation, or process of the NRF of the communication network.

[0204] Although Figure 7 not shown in, the method or process may further include the step / operation of receiving a request to notify or provide latency-related information for each candidate data network access identifier and / or auxiliary information for determining the data network latency. After such a request, the requested latency-related information and / or auxiliary information may be sent in the sending step / operation S710.

[0205] Although Figure 7is not shown, but the method or process may further include the step / operation of receiving a request for delay-related information for notifying or providing each candidate data network access identifier and / or auxiliary information for determining the data network delay. For example, after receiving such a request, conditions for sending the delay-related information for each candidate data network access identifier and / or the auxiliary information for determining the data network delay may be set, where when the conditions are met, the delay-related information for each candidate data network access identifier and / or the auxiliary information for determining the data network delay may be sent. For example, the conditions for sending the delay-related information and / or the auxiliary information may refer to or include AF notification triggers or conditions, as described below in conjunction with Figure 9 as described. For example, after receiving such a request, the corresponding user plane function entity for measuring the delay between the corresponding user plane function entity and the corresponding candidate edge application server may be set. For example, such a request may be received in a service routing impact process, a service for establishing a session with the required quality of service, a service parameter service, and / or an edge application server deployment service.

[0206] In Figure 6 and Figure 7 in any of the methods or processes, the delay-related information enables (or otherwise facilitates or enables) the acquisition (or derivation) of the access network delay and the data network delay. For example, the access network delay may be obtained (from the delay-related information) (e.g., directly), and / or the data network delay may be determined (e.g., measured) (based on the auxiliary information in the delay-related information). The access network delay includes the delay between the user equipment and the user plane function entity of the communication network, and the data network delay includes the delay between the user plane function entity of the communication network and one of the at least one candidate edge application servers of at least one data network (which is connected to the communication network). The end-to-end (E2E) delay between the user equipment and the at least one candidate edge application server includes or is composed of the access network delay and the data network delay, and both the access network delay and the data network delay are associated with the same user plane function entity.

[0207] Figure 8 shows a schematic diagram illustrating various delays in an exemplary architecture. Figure 8 The exemplary architecture of Figure 4 and 5 may be or be based on any one of the exemplary architectures of

[0208] As Figure 8As shown, for example, assume that a communication network (which may also be referred to or regarded as an access network) includes a (R)AN and two UPFs, namely UPF1 and UPF2, where a UE resides in 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 segments), namely DN1 and DN2, where DN1 includes an edge application server EAS1, and DN2 includes an edge application server EAS2. The UE may be assumed (to attempt) to use an application that can be delivered (or executed, processed, etc.) by either of EAS1 and EAS2 (such that either of EAS1 and EAS2 may be considered or referred to as a candidate EAS), while being controlled by an AF (not shown). Additionally, for example, assume that (e.g., 3GPP core can ensure / enable / facilitate / implement) the UE has a connection / link via the (R)AN to either of the two UPFs (i.e., UPF1 and UPF2), UPF1 has a connection / link via DNAI1-1 to EAS1 in DN1, and a connection / link via DNAI1-2 to EAS2 in DN2, and UPF2 has a connection / link via DNAI2-2 to EAS2 in DN2.

[0209] As is apparent from Figure 8 it, the DNAI can identify the user plane access to one or more data networks or (e.g., local) data network segments where a specific application or an EAS for delivering (or executing, processing, etc.) a specific application can be found.

[0210] It should be noted that the direct connection / link between the UPF and the EAS is shown for illustrative convenience, but one or more data networks or (e.g., local) data network segments and / or one or more network functions, units, or entities in the shown data networks may be located between the corresponding UPF-EAS pairs. Additionally, the number of network functions, units, or entities, edge application servers, connections / links, and networks is also non-limiting and is depicted only for illustrative purposes, and each of the depicted data networks or (e.g., local) data network segments may include more than one edge application server.

[0211] As Figure 8As shown, the delays involved in the delay-related information in this example architecture may include various access network delays and data network delays regarding EAS1 and EAS2. For example, as shown in the figure, these delays include the access network delay UE-UPF1 and data network delay UPF1-EAS1 regarding EAS1 and DNAI1-1, the access network delay UE-UPF1 and data network delay UPF1-EAS2 regarding EAS2 and DNAI1-2, the access network delay UE-UPF2 and data network delay UPF2-EAS2 regarding EAS2 and DNAI2-2, and the E2E delay UE-EAS2 regarding EAS2 and DNAI2-2.

[0212] Therefore, for this example architecture, the delay-related information may include DNAI1-1, DNAI1-2, and DNAI2-2 as a DNAI list / in the DNAI list, and one or more of the following items: the access network delay UE-UPF1 and data network delay UPF1-EAS1 for DNAI1-1 (regarding EAS1), the access network delay UE-UPF1 and data network delay UPF1-EAS2 for DNAI1-2 (regarding EAS2), the access network delay UE-UPF2 and data network delay UPF2-EAS2 for DNAI2-2 (regarding EAS2), and / or the E2E delay UE-EAS2 for DNAI2-2 (regarding EAS2).

[0213] As Figure 8 schematically shown, the following relationships can be assumed:

[0214] Access network delay UE-UPF1 > Access network delay UE-UPF2

[0215] Data network delay UPF2-EAS2 > Data network delay UPF1-EAS2

[0216] Data network delay UPF1-EAS2 > Data network delay UPF1-EAS1

[0217] When assuming that these delays are provided by / in the delay-related information for DNAI1-1, DNAI1-2, and DNAI2-2, it can be concluded that the path with the shortest delay is UE-UPF1-EAS1. In view of this, based on the obtained access network delays and data network delays, DNAI1-1 can be selected as the target data network access identifier (from DNAI1-1, DNAI1-2, and DNAI2-2), and EAS1 can be selected as the target edge application server (from EAS1 and EAS2). Then, in Figure 4 and 5In any of the example architectures, identifiers of DNAI1-1 and EAS1 can be sent, for example, from the AF to the SMF (possibly via the NEF).

[0218] However, as described above, when selecting the target data network access identifier and the target edge application server / in order to select the target data network access identifier and the target edge application server, other information can also be considered, such as the EAS load. In addition, the various (multiple) information in the selection / for selection can be weighted according to any conceivable, dynamic, static, or predefined rules or methods. Assuming that the load of EAS1 is higher than (e.g., significantly higher than) the load of EAS2 (and potentially, lower data network latency is preferred over lower access network latency), EAS2 can be selected as the target edge application server (from EAS1 and EAS2), and DNAI1-2 can be selected as the target data network access identifier (from DNAI1-1, DNAI1-2, and DNAI2-2). Then, in Figure 4 and 5 In any of the example architectures, identifiers of DNAI1-2 and EAS2 can be sent, for example, from the AF to the SMF (possibly via the NEF).

[0219] It should be noted that the AF is capable of (or otherwise configured to) select a suitable EAS to serve the UE, for example, to deliver the desired application, and the AF logic is responsible for considering other parameters to determine the suitable EAS, as described below. Also, it should be noted that the SMF is capable of (or otherwise configured to) configure (e.g., select) a suitable UPF to serve the UE, for example, for delivering the desired application, and the SMF logic is responsible for considering other parameters to determine the suitable UPF.

[0220] Regarding Figure 4 and 5 In the example architectures, the access network latency can represent, include, or indicate the latency on the radio interface (e.g., between the UE and the (R)AN) and / or on the N3 and / or N9 reference points between the corresponding functions, units, or entities, and / or the data network latency can represent, include, or indicate the latency on the N6 reference point between the corresponding functions, units, or entities or between the corresponding N6 reference point (or its UPF endpoint) and the corresponding (candidate) edge application server.

[0221] According to at least one example embodiment, the latency-related information includes information indicating the access network latency regarding the candidate edge application server and auxiliary information for determining (e.g., enabling / facilitating / implementing the determination of) the data network latency. Then, in Figure 6In the obtaining step / operation S620 of the method or process, the data network delay regarding the candidate edge application server can be obtained by determining (e.g., measuring) the data network delay based on the auxiliary information. The access network delay is directly obvious or can be derived from the corresponding information included in the delay-related information.

[0222] For example, referring to Figure 8 , for DNAI2-2, the delay-related information may include the access network delay UE-UPF2 and the auxiliary information for determining the data network delay UPF2-EAS2 regarding EAS2. Based on this, the data network delay UPF2-EAS2 regarding EAS2 can be monitored, measured, or discovered / detected by measurement based on the auxiliary information. For this purpose, the device performing Figure 6 the method or process can use the auxiliary information that is part of the received delay-related information to perform or initiate (or trigger) the measurement of the data network delay UPF2-EAS2 regarding EAS2.

[0223] According to at least one example embodiment, the delay-related information includes information indicating the end-to-end delay between the user equipment and the candidate edge application server regarding the candidate edge application server and the auxiliary information for determining (i.e., facilitating or enabling the determination of) the data network delay. Then, in Figure 6 the obtaining step / operation S620 of the method or process, by determining the data network delay based on the auxiliary information, the data network delay regarding the candidate edge application server can be obtained, and by obtaining the access network delay based on the end-to-end delay (which is directly obvious or can be derived from the corresponding information included in the delay-related information) and the data network delay, the access network delay regarding the candidate edge application server can be obtained.

[0224] For example, referring to Figure 8 , for DNAI2-2, the delay-related information may include the E2E delay UE-EAS2 and the auxiliary information for determining the data network delay UPF2-EAS2 regarding EAS2. Based on this, the data network delay UPF2-EAS2 regarding EAS2 can be monitored, measured, or discovered / detected by measurement based on the auxiliary information. For this purpose, the device performing Figure 6 the method or process can use the auxiliary information to perform or initiate (or trigger) the measurement of the data network delay UPF2-EAS2 regarding EAS2. After determining the data network delay UPF2-EAS2, for example, by subtracting the data network delay UPF2-EAS2 from the E2E delay UE-EAS2, the communication data network delay UE-UPF2 regarding EAS2 can be calculated.

[0225] The auxiliary information is, represents, or includes information for determining (e.g., enabling / facilitating / implementing the determination of) data network latency, such as information for enabling / facilitating / implementing the measurement of data network latency (i.e., the latency between the corresponding user plane function entity and the corresponding candidate edge application server). For example, the measurement of data network latency can be performed or initiated (or triggered) by the AF or by the (candidate) EAS itself, and can be performed between the UPF and the (candidate) EAS to determine the data network latency regarding the (candidate) EAS.

[0226] The measurement enabling / facilitating / implementing information can include measurement protocol information regarding the applicable protocol for measurement and measurement configuration information regarding the applicable configuration for measurement. The information regarding the applicable protocol for measurement can indicate the supported 5GC measurement protocol information, such as, for example, STAMP and / or TWAMP. The measurement configuration information can indicate or include protocol configuration information, addressing information, security information, and / or validity information for measurement and / or for the connection for measurement. For example, the addressing information can refer to the IP address and / or port number of the network function, unit, or entity involved in the measurement, such as the endpoints for STAMP / TWAMP-based measurement / the endpoints for STAMP / TWAMP-based measurement, such as the UPF. Although STAMP / TWAMP are referred to as example measurement protocols herein, other suitable protocols (e.g., HTTP-based protocols, etc.) can be used for the purpose of determining data network latency. For example, the security information can refer to the FQDN corresponding to the certificate that will be sent to secure the latency measurement protocol, which allows, for example, the establishment of a secure transport connection for measurement on the connection between the UPF and the (candidate) EAS. For example, the validity information can refer to the operation time window for measurement, such as the operation time window for the (authorized) measurement endpoints (e.g., UPF and / or EAS), which allows controlling when the AF / UPF / EAS is allowed to run such a measurement. The operation time window can allow notifying the measurement endpoints (e.g., the UPF for the candidate DNAI) how long (or when) they should operate as a reflector (e.g., in response to a measurement protocol request, such as the UPF sending an echo response to an echo request from an authorized EAS, or otherwise quietly discarding the echo request from the EAS). It should be noted that the AF / EAS may not have to know what the UPF is, as knowing the IP address of the corresponding data network endpoint at the communication (or access) network is sufficient.

[0227] According to at least one example embodiment, the latency-related information includes information indicating the end-to-end latency between the user equipment and the candidate edge application server and information indicating the access network latency regarding the candidate edge application server. Then, in Figure 6In the acquisition step / operation S620 of the method or process, the data network latency regarding the candidate edge application server can be obtained by obtaining the data network latency based on the end-to-end latency and the access network latency (both are directly obvious or can be derived from the corresponding information included in the latency-related information).

[0228] For example, referring to Figure 8 , for DNAI2-2, the latency-related information may include the E2E latency UE-EAS2 and the access network latency UE-UPF2 regarding EAS2. Based on this, for example, by subtracting the access network latency UE-UPF2 from the E2E latency UE-EAS2, the data network latency UPF2-EAS2 regarding EAS2 can be calculated.

[0229] In the following, some example processes (or use cases) of the AF-centric method according to at least one example embodiment are explained.

[0230] Figure 9 A sequence diagram of an example process according to at least one example embodiment is shown. This process represents or includes (at least in part) the above method or process, and is assumed for illustrative purposes to be based on Figure 4 and 5 any one of the example architectures of.

[0231] Figure 9 The process of can be considered as part of or integrated in the user plane management event notification process. Therefore, for further details (beyond the subsequent description), reference can be made to Section 4.3.6.3 of 3GPP TS23.502 (e.g., V18.4.0), which relates to the notification of user plane management events.

[0232] In some examples, the SMF providing relevant information to the AF is, for example, part of the early notification step.

[0233] As Figure 9 shown, the SMF can send a notification to the AF via the NEF (steps 2a and 2b) or directly (step 2c), assuming that the AF has subscribed to the user plane management / change event notification (in the previous step) and the corresponding AF notification trigger or condition is met (step 1). Examples of trigger conditions may include one or more of the following:

[0234] - The PDU session anchor identified in the AF subscription request has been established or released.

[0235] - DNAI has changed.

[0236] - The SMF has received a request for AF notification, and the ongoing PDU session meets the conditions for notifying the AF.

[0237] - Ethernet PDU session anchor re - location.

[0238] - The candidate DNAI has changed.

[0239] All of these triggering conditions can be due to, for example, UE mobility or because the UE has issued a DNS request to an FQDN identified by the AF as interesting, etc.

[0240] That is, the AF has requested notification, for example, as part of an AF service impact process (as described in the following reference Figure 10 ), thereby requesting (at least) a DNAI list, and for each candidate DNAI, requesting delay - related information about the delay between the UE and one or more candidate EASs. The requested information may also include other / additional information, such as measurement protocol information and / or measurement configuration information, e.g., the protocol, the IP address of the termination point between the communication (or access) network and the data network (corresponding to the UPF N6 interface) to act as an endpoint / reflector for measurements by the protocol, for example, when the AF / EAS acts as the measurement initiator, etc.

[0241] Then, the requested information can be provided by step 2a and 2b or by step 2c. In some examples, the notification messages Nsmf_EventExposure_Notify and Nnef_TrafficInfluence_Notify enhanced with the mentioned / illustrated information can be used. Although step 2a (the message in step 2a) is only represented by "early notification" but may have the same content as step 2b (the message in step 2b), the requested information can alternatively be provided by the NEF through step 2b.

[0242] In some instances, the delay - related information provided by the SMF to the AF includes, for each DNAI, the access network delay (including radio interface and / or N3 / N9 delay) (which can be the delay within 5GS access) and the auxiliary information from the 5GC to help the AF determine the aforementioned data network delay (which can be the N6 delay). As mentioned above, the AF may not need this delay - related information. For example, the AF can obtain the end - to - end delay and only needs the access network delay (including radio interface and / or N3 / N9 delay) or the auxiliary information to determine the N6 delay accordingly.

[0243] As described above, the auxiliary information may include information that facilitates (or enables) the measurement of the N6 latency, such as measurement protocol information regarding the applicable protocol for the measurement and possibly measurement configuration information regarding the applicable configuration for the measurement. In some examples, the information may include an indication of STAMP and / or TWAMP as the applicable measurement protocol. When the 5GS / NEF has authorized the AF request for N6 measurement and determined the UPF N6 measurement endpoints and the associated protocol configuration for each candidate DNAI, the 5GS / NEF may additionally indicate the operation time window for the authorized data network measurement endpoints (corresponding to the UPF N6 interface). Then, the AF may accordingly perform, initiate, or control the N6 latency measurement, as described above.

[0244] Based on the received information, the AF obtains the access network latency and determines the data network latency regarding the DNAI list and one or more candidate EASs, and accordingly selects the target DNAI and / or the target EAS for a specific PDU session (e.g., the session for delivering the application from the EAS via the PSA-UPF to the UE), as outlined in more detail above. As described above, additional information may also be used for the selection, such as the current EAS load information of / for one or more candidate EASs, which is at least accessible or derivable by the AF for EASs of the same EHE. Thereby, the traffic handling / routing on N3 / N9 and N6 can be controlled by the AF.

[0245] Then, the AF sends the EAS ID of the selected target DNAI and the selected target EAS to the SMF (via step 2 or via the NEF: steps 2d and 2e) and / or via the PCF (step 2f-a or steps 2d-a / 2e-a). In some examples, the AF may send the EAS ID of the target DNAI and the selected target EAS selected as above directly or via the NEF to the SMF (steps 2d, 2e, 2d-a, 2f, 2f-a).

[0246] Based on the information received in this way, the SMF configures the UPF or PSA-UPF for a specific PDU session (step 3), thereby configuring the user plane or traffic handling / routing. For example, the SMF may decide to reconfigure the user plane, such as by repositioning the PSA-UPF. Thereby, the traffic handling / routing on N3 / N9 and N6 can be controlled / at the SMF.

[0247] In subsequent steps, for example, in the late notification step, the SMF may confirm the reconfigured user plane or UPF information and / or the (re)selection or (re)discovery indication of the target DNAI and / or EAS. After consideration, the AF may confirm such information in its response in steps 4e, 4f, 4e-a, 4g, 4g-a.

[0248] It can be assumed that the SMF can access / obtain / learn delay-related information, such as auxiliary information, to determine the N6 delay regarding a candidate PSA-UPF (e.g., the UPF terminating the N6 interface to any candidate EAS data network). For example, the SMF can access / obtain / learn auxiliary information to determine the N6 delay in different ways. Example measures and / or mechanisms are to access / obtain / learn auxiliary information as part of the N4 association establishment (e.g., when assuming the use of PFCP and / or as defined in 3GPP TS 29.244 for N4, then as part of the modification to the 3GPP TS 29.244 §6.2.6 PFCP association establishment procedure or the 3GPP TS 29.244 §6.2.7 PFCP association update procedure). Another example measure and / or mechanism is to access / obtain / learn auxiliary information as part of the information registered by the UPF in the NRF (e.g., via the modification of UPFinfo defined in 3GPP TS 29.510). That is, for example, the UPF can register auxiliary information to determine the N6 delay as part of the 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 can discover this information as part of the Nnrf_NFDiscovery_Request.

[0249] Figure 10 A sequence diagram of an example process according to at least one example embodiment is shown. The process represents or includes (at least in part) the above method or process and is assumed for illustrative purposes to be based on Figure 4 and 5 any of the example architectures of.

[0250] Figure 10 The process of can be considered as part of or integrated in the service routing impact process. Therefore, for further details (beyond the subsequent description), reference can be made to Section 4.3.6.2 of 3GPP TS 23.502 (e.g., V18.4.0), which relates to handling AF requests to affect the service routing and / or service function chain for sessions not identified by the UE address.

[0251] As described above regarding Figure 9 the AMF can request notifications, for example, as part of the AF service impact process (e.g., as Figure 10as described therein), thereby requesting (at least) the DNAI list and delay-related information regarding the delay between the UE and one or more candidate EASs for each candidate DNAI. The requested information may also include other / additional information, such as measurement protocol information and / or measurement configuration information, e.g., the protocol, the UPF acting as an endpoint / reflector for measurements performed by the protocol when the AF / EAS acts as a measurement initiator, etc.

[0252] As Figure 10 shown, the AF may include, in its request that affects traffic routing, a request for notification of each DNAI information regarding the delay between the UE and at least one candidate EAS (from the SMF, via the PCF) (step 1). In some examples, the requested delay-related information includes (for each DNAI) N3 / N9 delay (or delay within 5GS access) as an example of access network delay and auxiliary information from the 5GC to assist the AF in determining the N6 delay as an example of data network delay.

[0253] The AF request may be used by the SMF, for example, to configure a candidate UPF as an N6 endpoint via N4 for delay measurement, e.g., to act as a STAMP / TWAMP (session / echo) reflector, and / or to obtain measurement-related parameters (e.g., IP address and / or port, security information, validity information, etc.) associated with the N6 endpoint via N4 for delay measurement, e.g., STAMP / TWAMP (session / echo) reflector (at the UPF).

[0254] In some examples, the AF may send, for example, in an Nnef_TrafficInfluence_Update request, the target DNAI and the EAS ID of the target EAS (which is selected based on different criteria (such as EAS load, total delay, etc.) as described above) to the NEF (step 2). This update step / operation may occur after notification from the SMF, as explained with reference to Figure 9 as explained.

[0255] The remaining steps are the same or similar to those in 3GPP TS23.502 §4.3.6.2.

[0256] Alternatively, the AF may request the provision of delay-related information, such as auxiliary information, E2E delay, etc., as measurement configuration and management information / within the measurement configuration and management information. This may be achieved, for example, by a corresponding request to the 5GS via the NEF (e.g., using the Nnef_AFSessionWithQoS service, the Nnef_ServiceParameter service, or the Nnef_EASDeployment service).

[0257] In view of Figure 9and 10 It should be noted that, for illustration purposes, the processes shown as such exemplify processes according to one or more example embodiments, which are based on previously specified processes. However, the previously specified processes used as a basis can be different, and in various example embodiments, not all steps and / or information of these previously specified processes are required.

[0258] According to some example embodiments, in a communication system (such as a communication network, e.g., 5GS or 5GC), devices and / or configurations are provided to enable / facilitate / implement or ensure that only legitimate endpoints can perform latency measurements, such as N6 latency measurements. Moreover, it can be enabled or ensured that only legitimate endpoints in a data network (connected to N6) can perform latency measurements relative to a candidate UPF acting as an N6 measurement endpoint, such as N6 latency measurements. In the case of the STAMP protocol, the AF can request the candidate UPF N6 endpoint to act in an authentication mode, requiring integrity protection and / or confidentiality protection. In the case of enabling / requiring integrity protection, the AF request may include the key for calculating the hash message authentication code (HMAC) in the STAMP message and / or how the 5GS can obtain this key, e.g., the identifier of the keying information provided to the 5GS via OAM or an out-of-band key distribution mechanism. In the case of enabling / requiring / implementing confidentiality protection, the AF request may include information enabling / facilitating / implementing the establishment of a dedicated IPsec tunnel between the measurement endpoint in the EHE and the UPF N6 endpoint and / or sharing an IPsec tunnel with the monitored flow. When the configuration information provided by the AF does not meet the requirements of the 5GS, the 5GS can determine to reject the AF request for the candidate UPF N6 measurement endpoint. In the case of STAMP, any (session / echo) reflector will be able to receive STAMP test packets on UDP port 862 and be able to receive STAMP test packets from user ports and a dynamic port range (which are defined). However, the UPF can also determine to use other port number values. Further details about STAMP can be obtained from RFC 8762, and further details about TWAMP can be obtained from RFC 5357.

[0259] Regarding the above examples, use cases, and example embodiments, it should be noted that these are provided for illustrative purposes only and are not intended to limit the present disclosure thereto.

[0260] As described above, various example embodiments provide techniques for (e.g., enabling / facilitating / implementing enhanced and / or improved) edge computing, such as enhanced (e.g., efficient) decision-making and configuration for edge computing.

[0261] As described above, in various example embodiments, an Edge Hosting Environment (EHE) can obtain / acquire / determine information (e.g., all required information) for evaluating the latency scenario of a specific PDU session of a UE that is attempting to use an application provided or controlled by the AF of the EHE and delivered (executed, processed, etc.) by the EAS of the EHE.

[0262] For example, the EHE can initiate and perform QoS / latency measurements on the available N6 endpoints and the path towards 5GS and other interfaces such as towards adjacent data centers, and collect the measurement results. To have an end-to-end view in the EHE for determining the target EAS, the AF can request QoS / latency measurement results for the latency within 5GS and auxiliary information for determining the N6 latency (e.g., latency to the data network and / or outside 5GS) from 5GS for each candidate DNAI. When the AF receives the candidate auxiliary information for determining the N6 latency, the EHE (AF or EAS) can perform N6 latency measurements for the candidate DNAIs provided by 5GS. Based on this, the AF can select the 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) by the SMF of 5GS / 5GC, for example.

[0263] The above functions and their related operations, processes, methods, and treatments can be implemented by corresponding functional elements, entities, modules, units, processors, etc., as described below. These functional elements, entities, modules, units, processors, etc. (e.g., the implementation of one or more example embodiments) can be implemented in a cloud environment through SDN, NFV / NFVI, etc.

[0264] Although various example embodiments are described with reference to operations, processes, methods, and treatments, these example embodiments also cover the corresponding apparatuses, entities, modules, units, network nodes, and / or systems, including their software and / or hardware.

[0265] The following describes each example embodiment, and for the sake of brevity, reference is made to the detailed descriptions of Figures 4 to 10 the respective corresponding configurations / settings, scenarios, structures, processes, sequences, methods, and functions, principles, and operations.

[0266] Figure 11 A schematic block diagram showing the structure of an apparatus according to at least one example embodiment is shown.

[0267] In Figure 11Among them, the blocks are basically configured to execute the corresponding methods, processes, and / or functions as described above. It should be noted that each block is intended to separately illustrate the corresponding functional blocks for implementing the corresponding functions, processes, or programs. Such functional blocks are independent of the implementation and can be implemented, for example, separately by means of any kind of hardware or software or a combination thereof.

[0268] According to at least one example embodiment, the apparatus according to at least one example embodiment may represent or implement / implement / incarnate (e.g., in part) network functions, elements, or entities, such as AF, etc.

[0269] The apparatus may be illustrated or implemented as Figure 3 shown. The apparatus or at least one of its processors 320 (e.g., together with instructions stored in at least one of its memories 330) may be configured to: receive a list of candidate data network access identifiers, and for each candidate data network access identifier, receive delay-related information regarding the delay between the user equipment and at least one candidate edge application server; based on the delay-related information, obtain an access network delay and a data network delay, where the access network delay includes the delay between the user equipment and the user plane function entity of the communication network, and the data network delay includes the delay between the user plane function entity of the communication network and one of the at least one candidate edge application servers of at least one data network; and based on the access network delay and the data network delay, select a target data network access identifier from the list of candidate data network access identifiers, and select a target edge application server from the at least one candidate edge application server.

[0270] In addition, the apparatus or at least one of its processors 320 (e.g., together with instructions stored in at least one of its memories 330) may be configured to: obtain the access network delay from the delay-related information; and / or determine the data network delay based on the auxiliary information in the delay-related information. In addition, the apparatus or at least one of its processors 320 (e.g., together with instructions stored in at least one of its memories 330) may be configured to execute or implement at least any method, step, operation, function, etc. as described above regarding AF, etc.

[0271] The apparatus may be illustrated or implemented as Figure 11The one shown is illustrated or implemented as apparatus 1110. Apparatus 1110 may include (at least): one or more units / components / circuits represented by a receiving part 1111, which represents any implementation for (or configured to) receive a list of candidate data network access identifiers, and for each candidate data network access identifier, receive latency-related information regarding the latency between the user equipment and at least one candidate edge application server; one or more units / components / circuits represented by an obtaining part 1112, which represents any implementation for (or configured to) obtain an access network latency and a data network latency based on the latency-related information, wherein the access network latency includes the latency between the user equipment and the user plane function entity of the communication network, and the data network latency includes the latency between the user plane function entity of the communication network and one candidate edge application server among at least one candidate edge application server of at least one data network; and one or more units / components / circuits represented by a selecting part 1113, which represents any implementation for (or configured to) select a target data network access identifier from the list of candidate data network access identifiers and select a target edge application server from at least one candidate edge application server based on the access network latency and the data network latency.

[0272] As shown by the dashed line, apparatus 1110 may include (at least): one or more units / components / circuits represented by a sending part 1114, which represents any implementation for (or configured to) send the target data network access identifier and the edge application server identifier of the target edge application server. In addition, apparatus 1110 may include (at least): one or more units / components / circuits represented by an accessing part 1115, which represents any implementation for (or configured to) access load information regarding at least one candidate edge application server, wherein the load information indicates the load of the corresponding candidate edge application server. In addition, apparatus 1110 may include (at least): one or more units / components / circuits represented by a requesting part 1116, which represents any implementation for (or configured to) request to notify or provide latency-related information per candidate data network access identifier and / or auxiliary information for determining the data network latency. In addition, the receiving part 1111 or another part with corresponding operability may be used for (or configured to) receive at least one IP address, each IP address being associated with a user plane function entity.

[0273] According to at least one example embodiment, the apparatus according to at least one example embodiment may represent or implement / implement / incarnate (e.g., in part) a network function, element, or entity, such as an SMF, etc.

[0274] The apparatus may be as Figure 3be illustrated or implemented as shown. The apparatus or at least one of its processors 320 (e.g., together with instructions stored in at least one of its memories 330) can be configured to: send a list of candidate data network access identifiers, and for each candidate data network access identifier, send latency-related information regarding the latency between the user equipment and at least one candidate edge application server, wherein the latency-related information facilitates obtaining an access network latency and a data network latency, wherein the access network latency includes the latency between the user equipment and a user plane function entity of the communication network, and the data network latency includes the latency between the user plane function entity of the communication network and a candidate edge application server among at least one candidate edge application servers of at least one data network.

[0275] In addition, the apparatus or at least one of its processors 320 (e.g., together with instructions stored in at least one of its memories 330) can be configured to: receive a target data network access identifier from the list of candidate data network access identifiers, and receive an edge application server identifier of a target edge application server from at least one candidate edge application server, and / or configure a user plane function entity among one or more user plane function entities from the communication network based on the target data network access identifier and the edge application server identifier of the target edge application server. In addition, the apparatus or at least one of its processors 320 (e.g., together with instructions stored in at least one of its memories 330) can be configured to perform or implement any method, step, operation, function, etc. at least regarding the SMF as described above.

[0276] The apparatus can be as Figure 11 shown and be illustrated or implemented as apparatus 1120. Apparatus 1120 can include (at least): one or more units / components / circuits represented by a sending part 1121, which represents any implementation for (or configured to) send a list of candidate data network access identifiers and, for each candidate data network access identifier, send latency-related information regarding the latency between the user equipment and at least one candidate edge application server, wherein the latency-related information facilitates obtaining an access network latency and a data network latency, wherein the access network latency includes the latency between the user equipment and a user plane function entity of the communication network, and the data network latency includes the latency between the user plane function entity of the communication network and a candidate edge application server among at least one candidate edge application servers of at least one data network.

[0277] As shown by the dashed line, the apparatus 1120 may include (at least): one or more units / components / circuits represented by a receiving part 1122, which represents any implementation for (or configured to) receive a target data network access identifier from a list of candidate data network access identifiers and receive an edge application server identifier of a target edge application server from at least one candidate edge application server. In addition, the apparatus 1120 may include (at least): one or more units / components / circuits represented by a configuration part 1123, which represents any implementation for (or configured to) configure a user plane function entity in one or more user plane function entities from a communication network based on the target data network access identifier and the edge application server identifier of the target edge application server. In addition, the apparatus 1120 may include (at least): one or more units / components / circuits represented by an obtaining part 1124, which represents any implementation for (or configured to) obtain auxiliary information for determining a data network latency regarding a candidate edge application server. In addition, the apparatus 1120 may include (at least): one or more units / components / circuits represented by a setting part 1125, which represents any implementation for (or configured to) set conditions for sending latency-related information of each candidate data network access identifier and / or auxiliary information for determining a data network latency and / or set a corresponding user plane function entity for measuring a latency between the corresponding user plane function entity and a corresponding candidate edge application server. In addition, a sending part 1121 or another part with corresponding operability may be used for (or configured to) send at least one IP address, each IP address associated with a user plane function entity, and / or a receiving part 1122 or another part with corresponding operability may be used for (or configured to) receive a request for notifying or providing latency-related information of each candidate data network access identifier and / or auxiliary information for determining a data network latency.

[0278] For further details regarding the operability / function of the apparatus (or its units / components) according to some example embodiments, reference is made to the above description in conjunction with any one of Figures 1 to 10 above.

[0279] According to some example embodiments, any one of (at least one) processor, (at least one) memory, and (at least one) interface, as well as any one of the illustrated units / components, may be implemented as a separate module, chip, chipset, circuit, etc., or one or more of them may be respectively implemented as a common module, chip, chipset, circuit, etc.

[0280] As used herein, the term "circuit" can refer to one or more or all of the following: (a) a pure hardware circuit implementation (such as an implementation in a pure analog and / or digital circuit) and (b) a combination of a hardware circuit and software, such as, where applicable: (i) a combination of an analog and / or digital hardware circuit and software / firmware, and (ii) a hardware processor and software (including a digital signal processor), any part of the software and memory, which work together to enable a device such as a mobile phone or a server to perform various functions, and (c) a hardware circuit and / or a processor, such as a microprocessor or a part of a microprocessor, which requires software (such as firmware) to operate, but where software is not required to operate, the software may be absent.

[0281] This definition of a circuit applies to all uses of the term herein, including in any claims. As a further example, as used herein, the term "circuit" also encompasses an implementation of a pure hardware circuit or a processor (or processors) or a part of a hardware circuit or a processor and its (or their) attendant software and / or firmware. The term "circuit" also encompasses, for example and where applicable to a particular claim element, a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

[0282] According to some example embodiments, a system may include any conceivable combination of any of the devices and other network units or functional entities depicted or described (which are configured to cooperate as described above).

[0283] In general, it should be noted that if only suitable for performing the corresponding part of the function, the corresponding functional blocks or units according to the various embodiments described herein can be implemented separately in hardware and / or software by any known means. The mentioned method steps can be implemented in separate functional blocks or by separate devices, or one or more method steps can be implemented in a single functional block or by a single device.

[0284] Generally, the basic system architecture of a (telecommunication) communication network of a mobile communication system to which some examples including exemplary embodiments may apply may include the architecture of one or more communication networks, and the one or more communication networks include a radio access network subsystem / system and possibly a core network. Such an architecture may include one or more communication network control units or functions (such as access network units, radio access network units, access service network gateways or base station transceivers (such as base stations, access points, Node B (NB), eNB or gNB), distributed or centralized units), and the one or more communication network control units or functions control corresponding coverage areas or cells, and the following can communicate with the one or more communication network control units or functions via one or more communication beams through one or more channels to send various types of data in multiple access domains: one or more communication stations, such as communication units or functions, such as user equipment or terminal equipment (such as UE) or another device with a similar function (such as a modem chipset, chip, module, etc.), which may also be part of a station, unit, function or application capable of communication (such as a UE, unit or function that can be used in a machine-to-machine communication architecture, or attached as a separate unit to such a communication-capable unit, function or application, etc.). In addition, core network units or network functions may be included, such as gateway network units / functions, mobility management entities, mobile switching centers, servers, databases, etc.

[0285] The general functions and interconnections of the described units and functions (which also depend on the actual network type) are known to those skilled in the art and are described in the corresponding specifications, and thus the detailed description thereof is omitted herein. It should be understood that multiple additional network units and signaling links may be employed for communication to or from a unit, function or application, such as a communication endpoint, a communication network control unit, such as a server, gateway, radio network controller, and other units of the same or other communication networks other than those described in detail below.

[0286] The communication network architecture considered in the example of the exemplary embodiment is also capable of communicating with other networks (such as a public switched telephone network or the Internet including the Internet of Things). The communication network is also capable of supporting the use of cloud services for virtual network elements or their functions, where it should be noted that the virtual network part of the (telecommunication) communication network may also be provided by non-cloud resources (such as an internal network, etc.). It should be understood that the network units and / or corresponding functions of the access system, core network, etc. may be implemented by using any node, host, server, access node or entity suitable for such a purpose. Generally, network functions may be implemented as network units on dedicated hardware, software instances running on dedicated hardware, or virtualized functions instantiated on a suitable platform (such as a cloud infrastructure).

[0287] Any method step is suitable for implementation as software or by hardware without changing the idea or scope of the various exemplary embodiments. Such software can be code-independent and can be specified using any known or future-developed programming language, such as Java, C++, C, and assembler, as long as the functionality defined by the method step is retained. Such hardware can be hardware-type independent and can be implemented using any known or future-developed hardware technology or any combination of the following, such as MOS (metal-oxide semiconductor), CMOS (complementary MOS), BiMOS (bipolar MOS), BiCMOS (bipolar CMOS), ECL (emitter-coupled logic), TTL (transistor-transistor logic), etc., for example, using ASIC (application-specific IC (integrated circuit)) components, FPGA (field-programmable gate array) components, CPLD (complex programmable logic device) components, or DSP (digital signal processor) components. A device / apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module including such a chip or chipset; however, this does not exclude the possibility that the functionality of the device / apparatus or module is not implemented in hardware but as software in a (software) module (e.g., a computer program or a computer program product including an executable software code portion for execution / run on a processor). For example, whether functionally cooperating with each other or functionally independent of each other but within the same device housing, a device can be considered as one device / apparatus or an assembly of more than one device / apparatus.

[0288] The device and / or its unit / component or part can be implemented as a separate device, but this does not exclude the possibility that they can be implemented in a distributed manner throughout the system as long as the functionality of the device is retained. Such principles and similar principles are considered to be known to those skilled in the art.

[0289] Software in the illustrative sense includes software code, which includes code components or portions or a computer program product for performing the corresponding functions, and software (or a computer program or a computer program product) embodied on a tangible medium, the tangible medium being, for example, a computer-readable (storage) medium on which the corresponding data structure or code component / portion is stored, or which may be embodied in a signal or a chip during its processing.

[0290] The various exemplary embodiments also cover any conceivable combination of the above method steps and operations, as well as any conceivable combination of the above nodes, devices, module units, as long as the above concepts of the method and the structural arrangement are applicable.

[0291] In view of the above, measures are provided for (e.g., enabling / facilitating / implementing enhanced and / or improved) edge computing, such as enhanced (e.g., efficient) decision-making and configuration for edge computing. Such measures may include, for example: a network function, unit, or entity receiving a list of candidate data network access identifiers, and for each candidate data network access identifier, receiving latency-related information regarding the latency between a user equipment and at least one candidate edge application server; obtaining an access network latency (e.g., the latency between the user equipment and one or more user plane function entities of a communication network) and a data network latency (e.g., the latency between one or more user plane function entities and the corresponding candidate edge application server among at least one candidate edge application servers of at least one data network); and selecting a target data network access identifier from the list of candidate data network access identifiers, and selecting a target edge application server from among at least one candidate edge application server.

[0292] Although various example embodiments are described herein with reference to the accompanying drawings, it should be understood that the various example embodiments are not limited thereto. On the contrary, it will be apparent to those skilled in the art that the various example embodiments can be modified in many ways without departing from the intended scope.

[0293] Some example embodiments among the various example embodiments of the present disclosure are listed below by way of non-limiting and illustrative examples.

[0294] Example Embodiment 1. A method, comprising:

[0295] receiving a list of candidate data network access identifiers, and for each candidate data network access identifier, receiving latency-related information regarding the latency between a user equipment and at least one candidate edge application server,

[0296] obtaining an access network latency and a data network latency based on the latency-related information, wherein the access network latency includes the latency between the user equipment and a user plane function entity of a communication network, and the data network latency includes the latency between a user plane function entity of the communication network and a candidate edge application server among at least one candidate edge application servers of at least one data network, and

[0297] selecting a target data network access identifier from the list of candidate data network access identifiers and selecting a target edge application server from among at least one candidate edge application server based on the access network latency and the data network latency.

[0298] Example Embodiment 2. The method according to Example Embodiment 1, wherein the obtaining comprises:

[0299] obtaining the access network latency from the latency-related information, and / or

[0300] Determine the data network latency based on the auxiliary information in the latency-related information.

[0301] Example Embodiment 3. The method according to Example Embodiment 1 or 2, wherein

[0302] the latency-related information includes information indicating the access network latency of a candidate edge application server and auxiliary information for determining the data network latency, and

[0303] the obtaining includes:

[0304] obtain the access network latency of a candidate edge application server from the latency-related information, and / or

[0305] determine the data network latency of a candidate edge application server based on the auxiliary information.

[0306] Example Embodiment 4. The method according to any one of Example Embodiments 1 to 3, wherein

[0307] The user plane function entity of the communication network is identified by an IP address on a data network identified by a target data network access identifier.

[0308] Example Embodiment 5. The method according to Example Embodiment 2 or 3, wherein

[0309] Determining the data network latency includes: using the auxiliary information to perform or initiate a measurement of the latency between the corresponding user plane function entity and the corresponding candidate edge application server.

[0310] Example Embodiment 6. The method according to any one of Example Embodiments 2, 3 or 5, wherein the auxiliary information includes information for facilitating the measurement of the latency between the corresponding user plane function entity and the corresponding candidate edge application server.

[0311] Example Embodiment 7. The method according to Example Embodiment 6, wherein the measurement facilitation information includes measurement protocol information about an applicable protocol for measurement and measurement configuration information about an applicable configuration for measurement.

[0312] Example Embodiment 8. The method according to Example Embodiment 7, wherein

[0313] the measurement protocol information indicates the Simple Bidirectional Active Measurement Protocol and / or the Bidirectional Active Measurement Protocol as the applicable measurement protocol, and / or

[0314] the measurement configuration information includes one or more of protocol configuration information for measurement and / or for a connection for measurement, addressing information, security information, and validity information.

[0315] Example Embodiment 9. The method according to any one of Example Embodiments 1 to 8 further includes:

[0316] Sending a target data network access identifier and an edge application server identifier of a target edge application server.

[0317] Example Embodiment 10. The method according to any one of Example Embodiments 1 to 9 further includes:

[0318] Accessing load information about at least one candidate edge application server, where the load information indicates the load of the corresponding candidate edge application server,

[0319] where the target data network access identifier and the target edge application server are further selected based on the load information.

[0320] Example Embodiment 11. The method according to any one of Example Embodiments 1 to 10 further includes:

[0321] Receiving at least one IP address, each IP address being associated with a user plane function entity,

[0322] where the target data network access identifier and the target edge application server are further selected based on the at least one IP address.

[0323] Example Embodiment 12. The method according to any one of Example Embodiments 1 to 11 further includes:

[0324] Requesting to notify or provide delay-related information of each candidate data network access identifier and / or auxiliary information for determining data network delay.

[0325] Example Embodiment 13. In the method according to Example Embodiment 12, the request is performed in at least one of the following: a service routing impact process; a service, operation, or process for establishing a session with a required quality of service; a service parameter service, operation, or process; or an edge application server deployment service, operation, or process.

[0326] Example Embodiment 14. In the method according to any one of Example Embodiments 1 to 13,

[0327] the method is part of a service routing impact process and / or a user plane management event notification process, or integrated in a service routing impact process and / or a user plane management event notification process.

[0328] Example Embodiment 15. In the method according to any one of Example Embodiments 1 to 14,

[0329] the method can be operated at or by an application function entity of a communication network, and / or

[0330] The list of candidate data network access identifiers and latency-related information are received from the session management function entity or the network exposure function entity of a communication entity, and / or

[0331] The target data network access identifier and the edge application server identifier of the target edge application server are sent to the session management function entity or the network exposure function entity of a communication entity, and / or

[0332] The user equipment will use an application controlled by the application function entity of the communication network, and the application will be delivered by an edge application server among at least one candidate edge application servers, and / or

[0333] The access network latency indicates the latency at the N3 and / or N9 reference points, and / or the data network latency indicates the latency at the N6 reference point.

[0334] Example embodiment 16. A method, comprising:

[0335] Sending a list of candidate data network access identifiers, and for each candidate data network access identifier, sending latency-related information about the latency between the user equipment and at least one candidate edge application server, wherein the latency-related information facilitates obtaining an access network latency and a data network latency, wherein the access network latency includes the latency between the user equipment and the user plane function entity of the communication network, and the data network latency includes the latency between the user plane function entity of the communication network and a candidate edge application server among at least one candidate edge application servers of at least one data network.

[0336] Example embodiment 17. The method according to example embodiment 16, further comprising:

[0337] Receiving a target data network access identifier from the list of candidate data network access identifiers, and receiving the edge application server identifier of the target edge application server from at least one candidate edge application server, and

[0338] Configuring a user plane function entity among one or more user plane function entities from the communication network based on the target data network access identifier and the edge application server identifier of the target edge application server.

[0339] Example embodiment 18. The method according to example embodiment 16 or 17, wherein the latency-related information facilitates:

[0340] Obtaining the access network latency from the latency-related information, and / or

[0341] Determining the data network latency based on the auxiliary information in the latency-related information.

[0342] Example Embodiment 19. The method according to any one of Example Embodiments 16 to 18, wherein the delay-related information includes information indicating the access network delay of the candidate edge application server and auxiliary information for determining the data network delay.

[0343] Example Embodiment 20. The method according to any one of Example Embodiments 16 to 19, wherein the 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.

[0344] Example Embodiment 21. The method according to Example Embodiment 18 or 19, wherein the delay-related information facilitates determining the data network delay by measuring the delay between the corresponding user plane function entity and the corresponding candidate edge application server using the auxiliary information.

[0345] Example Embodiment 22. The method according to any one of Example Embodiments 18, 19 or 21, wherein the auxiliary information includes information for facilitating the measurement of the delay between the corresponding user plane function entity and the corresponding candidate edge application server.

[0346] Example Embodiment 23. The method according to Example Embodiment 22, wherein the measurement facilitation information includes measurement protocol information about the applicable protocol for measurement and measurement configuration information about the applicable configuration for measurement.

[0347] Example Embodiment 24. The method according to Example Embodiment 23, wherein

[0348] the measurement protocol information indicates the Simple Bidirectional Active Measurement Protocol and / or the Bidirectional Active Measurement Protocol as the applicable measurement protocol, and / or

[0349] the measurement configuration information includes one or more of protocol configuration information for measurement and / or for the connection for measurement, addressing information, security information, and validity information.

[0350] Example Embodiment 25. The method according to any one of Example Embodiments 16 to 24, further comprising:

[0351] sending at least one IP address, each IP address being associated with the user plane function entity.

[0352] Example Embodiment 26. The method according to any one of Example Embodiments 16 to 25, further comprising:

[0353] obtaining auxiliary information for determining the data network delay regarding the candidate edge application server.

[0354] Example Embodiment 27. The method according to Example Embodiment 26, wherein

[0355] The auxiliary information for determining the data network latency is obtained from the user plane function entity and / or the network repository function entity of the communication network, and / or

[0356] The auxiliary information for determining the data network latency is obtained as part of the association establishment or update process with the user plane function entity (such as the packet forwarding control protocol association establishment or update process) and / or the network function discovery service, operation, or process of the network repository function entity of the communication network.

[0357] Example embodiment 28. The method according to any one of example embodiments 16 to 27 further includes:

[0358] Receiving a request to notify or provide latency-related information for each candidate data network access identifier and / or the auxiliary information for determining the data network latency.

[0359] Example embodiment 29. The method according to example embodiment 28 further includes:

[0360] After receiving the request, setting conditions for sending the latency-related information for each candidate data network access identifier and / or the auxiliary information for determining the data network latency,

[0361] wherein when the conditions are met, the latency-related information for each candidate data network access identifier and / or the auxiliary information for determining the data network latency are sent.

[0362] Example embodiment 30. The method according to example embodiment 28 or 29 further includes:

[0363] After receiving the request, setting the corresponding user plane function entity for measuring the latency between the corresponding user plane function entity and the corresponding candidate edge application server.

[0364] 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 service routing impact process, a service for establishing a session with a required quality of service, a service parameter service, or an edge application server deployment service.

[0365] Example embodiment 32. The method according to any one of example embodiments 16 to 31, wherein,

[0366] the method is part of a service routing impact process and / or a user plane management event notification process or integrated in a service routing impact process and / or a user plane management event notification process.

[0367] Example embodiment 33. The method according to any one of example embodiments 16 to 32, wherein,

[0368] The method can be operated at or by a session management function entity of a communication network, and / or

[0369] A list of candidate data network access identifiers and latency-related information are sent to an application function entity or a network exposure function entity of a communication entity, and / or

[0370] 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 a communication entity, and / or

[0371] A user equipment will use an application controlled by an application function entity of a communication network, and the application will be delivered by an edge application server among at least one candidate edge application servers, and / or

[0372] A user plane function entity is configured as a packet data unit session anchor for a packet data unit session in a communication network and as an endpoint of an interface configured between the communication network and a data network of a target edge application server, and / or

[0373] An access network latency indicates a latency at an N3 and / or N9 reference point, and / or a data network latency indicates a latency at an N6 reference point.

[0374] Example embodiment 34. An apparatus, comprising:

[0375] Components for receiving a list of candidate data network access identifiers, and for each candidate data network access identifier, receiving latency-related information regarding a latency between a user equipment and at least one candidate edge application server,

[0376] Components for obtaining an access network latency and a data network latency based on the latency-related information, wherein the access network latency includes a latency between the user equipment and a user plane function entity of a communication network, and the data network latency includes a latency between the user plane function entity of the communication network and a candidate edge application server among at least one candidate edge application servers of at least one data network, and

[0377] Components for selecting a target data network access identifier from the list of candidate data network access identifiers and for selecting a target edge application server from among at least one candidate edge application server for the access network latency and the data network latency.

[0378] Example embodiment 35. The apparatus according to example embodiment 34, comprising:

[0379] Components for obtaining an access network latency from the latency-related information, and / or

[0380] A component for determining the data network latency based on the auxiliary information in the latency-related information.

[0381] Example embodiment 36. The apparatus according to example embodiment 34 or 35, wherein

[0382] The latency-related information includes information indicating the access network latency of a candidate edge application server and auxiliary information for determining the data network latency, and

[0383] The obtaining component is configured to:

[0384] Obtain the access network latency of the candidate edge application server from the latency-related information, and / or

[0385] Determine the data network latency of the candidate edge application server based on the auxiliary information.

[0386] Example embodiment 37. The apparatus according to any one of example embodiments 34 to 36, wherein

[0387] The user plane function entity of the communication network is identified by an IP address on the data network identified by the target data network access identifier.

[0388] Example embodiment 38. The apparatus according to example embodiment 35 or 36, wherein

[0389] Determining the data network latency includes: using the auxiliary information to perform or initiate a measurement of the latency between the corresponding user plane function entity and the corresponding candidate edge application server.

[0390] Example embodiment 39. The apparatus according to any one of example embodiments 35, 36 or 38, wherein the auxiliary information includes information for facilitating the measurement of the latency between the corresponding user plane function entity and the corresponding candidate edge application server.

[0391] Example embodiment 40. The apparatus according to example embodiment 39, wherein the measurement facilitation information includes measurement protocol information about the applicable protocol for measurement and measurement configuration information about the applicable configuration for measurement.

[0392] Example embodiment 41. The apparatus according to example embodiment 40, wherein

[0393] The measurement protocol information indicates the Simple Bidirectional Active Measurement Protocol and / or the Bidirectional Active Measurement Protocol as the applicable measurement protocol, and / or

[0394] The measurement configuration information includes one or more of protocol configuration information for measurement and / or for the connection for measurement, addressing information, security information, and validity information.

[0395] Example Embodiment 42. The apparatus according to any one of Example Embodiments 34 to 41 further comprises:

[0396] A component for sending a target data network access identifier and an edge application server identifier of a target edge application server.

[0397] Example Embodiment 43. The apparatus according to any one of Example Embodiments 34 to 42 further comprises:

[0398] A component for accessing load information about at least one candidate edge application server, where the load information indicates the load of the corresponding candidate edge application server,

[0399] where the target data network access identifier and the target edge application server are further selected based on the load information.

[0400] Example Embodiment 44. The apparatus according to any one of Example Embodiments 34 to 43 further comprises:

[0401] A component for receiving at least one IP address, each IP address being associated with a user plane function entity,

[0402] where the target data network access identifier and the target edge application server are further selected based on the at least one IP address.

[0403] Example Embodiment 45. The apparatus according to any one of Example Embodiments 34 to 44 further comprises:

[0404] A component for requesting to notify or provide delay-related information of each candidate data network access identifier and / or auxiliary information for determining data network delay.

[0405] Example Embodiment 46. For the apparatus according to Example Embodiment 45, wherein the request is executed in at least one of the following: a service routing impact process; a service, operation, or process for establishing a session with a required quality of service; a service parameter service, operation, or process; or an edge application server deployment service, operation, or process.

[0406] Example Embodiment 47. For the apparatus according to any one of Example Embodiments 34 to 46, wherein

[0407] the apparatus is configured to operate as part of a service routing impact process and / or a user plane management event notification process or integrated in a service routing impact process and / or a user plane management event notification process.

[0408] Example Embodiment 48. For the apparatus according to any one of Example Embodiments 34 to 47, wherein

[0409] The apparatus can operate at or by an application function entity of a communication network, and / or

[0410] a list of candidate data network access identifiers and delay-related information are received from a session management function entity or a network exposure function entity of a communication entity, and / or

[0411] a target data network access identifier and an edge application server identifier of a target edge application server are sent to a session management function entity or a network exposure function entity of a communication entity, and / or

[0412] a user equipment will use an application controlled by an application function entity of a communication network, and the application will be delivered by an edge application server among at least one candidate edge application servers, and / or

[0413] An access network delay indicates a delay at the N3 and / or N9 reference points, and / or a data network delay indicates a delay at the N6 reference point.

[0414] Example embodiment 49. An apparatus, comprising:

[0415] means for sending a list of candidate data network access identifiers, and for each candidate data network access identifier, sending delay-related information about a delay between a user equipment and at least one candidate edge application server, wherein the delay-related information facilitates obtaining an access network delay and a data network delay, wherein the access network delay includes a delay between the user equipment and a user plane function entity of a communication network, and the data network delay includes a delay between the user plane function entity of the communication network and a candidate edge application server among at least one candidate edge application servers of at least one data network.

[0416] Example embodiment 50. The apparatus according to example embodiment 49, further comprising:

[0417] means for receiving a target data network access identifier from the list of candidate data network access identifiers, and receiving an edge application server identifier of a target edge application server from at least one candidate edge application server, and

[0418] means for configuring a user plane function entity among one or more user plane function entities from a communication network based on the target data network access identifier and the edge application server identifier of the target edge application server.

[0419] Example embodiment 51. The apparatus according to example embodiment 49 or 50, wherein the delay-related information facilitates:

[0420] obtaining an access network delay from the delay-related information, and / or

[0421] Determine the data network latency based on the auxiliary information in the latency-related information.

[0422] Example Embodiment 52. The apparatus according to any one of Example Embodiments 49 to 51, wherein the latency-related information includes information indicating the access network latency regarding the candidate edge application server and auxiliary information for determining the data network latency.

[0423] Example Embodiment 53. The apparatus according to any one of Example Embodiments 49 to 52, wherein the user plane function entity of the communication network is identified by an IP address on the data network identified by the target data network access identifier.

[0424] Example Embodiment 54. The apparatus according to Claim 51 or 52, wherein the latency-related information facilitates determining the data network latency by performing or initiating a measurement of the latency between the corresponding user plane function entity and the corresponding candidate edge application server using the auxiliary information.

[0425] Example Embodiment 55. The apparatus according to any one of Example Embodiments 51, 52 or 54, wherein the auxiliary information includes information for facilitating the measurement of the latency between the corresponding user plane function entity and the corresponding candidate edge application server.

[0426] Example Embodiment 56. The apparatus according to Example Embodiment 55, wherein the measurement facilitation information includes measurement protocol information regarding the applicable protocol for measurement and measurement configuration information regarding the applicable configuration for measurement.

[0427] Example Embodiment 57. The apparatus according to Example Embodiment 56, wherein

[0428] the measurement protocol information indicates the Simple Bidirectional Active Measurement Protocol and / or the Bidirectional Active Measurement Protocol as the applicable measurement protocol, and / or

[0429] the measurement configuration information includes one or more of protocol configuration information, addressing information, security information, and validity information for measurement and / or for the connection for measurement.

[0430] Example Embodiment 58. The apparatus according to any one of Example Embodiments 49 to 57, further comprising:

[0431] a component for sending at least one IP address, each IP address being associated with a user plane function entity.

[0432] Example Embodiment 59. The apparatus according to any one of Example Embodiments 49 to 58, further comprising:

[0433] Obtain auxiliary information for determining the data network latency regarding a candidate edge application server.

[0434] Example embodiment 60. The apparatus according to example embodiment 59, wherein,

[0435] The auxiliary information for determining the data network latency is obtained from a user plane function entity and / or a network repository function entity of the communication network, and / or

[0436] The auxiliary information for determining the data network latency is obtained as part of an association establishment or update process with the user plane function entity (such as a packet forwarding control protocol association establishment or update process) and / or a network function discovery service, operation, or process with the network repository function entity of the communication network.

[0437] Example embodiment 61. The apparatus according to any one of example embodiments 49 to 60, further comprising:

[0438] A component for receiving a request for notifying or providing latency-related information of each candidate data network access identifier and / or auxiliary information for determining the data network latency.

[0439] Example embodiment 62. The apparatus according to example embodiment 61, further comprising:

[0440] A component for setting, after receiving the request, a condition for sending latency-related information of each candidate data network access identifier and / or auxiliary information for determining the data network latency,

[0441] wherein, when the condition is satisfied, the latency-related information of each candidate data network access identifier and / or the auxiliary information for determining the data network latency is sent.

[0442] Example embodiment 63. The apparatus according to example embodiment 61 or 62, further comprising:

[0443] A component for setting a corresponding user plane function entity for measuring the latency between the corresponding user plane function entity and the corresponding candidate edge application server after receiving the request.

[0444] 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 service routing impact process, a service for establishing a session with a required quality of service, a service parameter service, or an edge application server deployment service.

[0445] Example embodiment 65. The apparatus according to any one of example embodiments 49 to 64, wherein,

[0446] The apparatus is configured to operate as part of a service routing impact procedure and / or a user plane management event notification procedure or to be integrated and operate in a service routing impact procedure and / or a user plane management event notification procedure.

[0447] Example embodiment 66. The apparatus according to any one of example embodiments 49 to 65, wherein,

[0448] The apparatus can operate at or be operated by a session management function entity of a communication network, and / or

[0449] A list of candidate data network access identifiers and latency-related information is sent to an application function entity or a network exposure function entity of a communication entity, and / or

[0450] 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 a communication entity, and / or

[0451] The user equipment will use an application controlled by an application function entity of a communication network, and the application will be delivered by an edge application server in at least one candidate edge application server, and / or

[0452] The user plane function entity is configured as a packet data unit session anchor for a packet data unit session in a communication network and as an endpoint configured as an interface between the communication network and a data network of a target edge application server, and / or

[0453] The access network latency indicates the latency at the N3 and / or N9 reference points, and / or the data network latency indicates the latency at the N6 reference point.

[0454] Example embodiment 67. A system, at least comprising:

[0455] The apparatus according to any one of example embodiments 34 to 48, and

[0456] The apparatus according to any one of example embodiments 49 to 66.

[0457] Example embodiment 68. A computer program product comprising computer program code which, when executed on a computer, is configured to cause the computer to perform 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, receiving delay-related information regarding a delay between a user equipment and at least one candidate edge application server, Based on the delay-related information, obtaining a data network delay, wherein the data network delay includes a delay between a user plane function entity of the communication network and a candidate edge application server among the at least one candidate edge application servers of at least one data network, and Based on the data network delay, selecting a target data network access identifier from the list of candidate data network access identifiers, and selecting a target edge application server from the at least one candidate edge application server.

2. The method according to claim 1, wherein The obtaining comprises: Determining the data network delay based on auxiliary information in the delay-related information.

3. The method according to claim 1 or 2, wherein, The delay-related information includes information indicating auxiliary information for determining the data network delay regarding the candidate edge application server, and The obtaining comprises: Determining the data network delay regarding the candidate edge application server based on the auxiliary information.

4. The method according to claim 2 or 3, wherein, Determining the data network delay includes: performing or initiating measurement of a delay between a corresponding user plane function entity and a corresponding candidate edge application server using the auxiliary information.

5. The method according to any one of claims 2 to 4, wherein The auxiliary information includes information for facilitating measurement of a delay between a corresponding user plane function entity and a corresponding candidate edge application server.

6. The method according to claim 5, wherein The measurement facilitation information includes measurement protocol information regarding an applicable protocol for the measurement and measurement configuration information regarding an applicable configuration for the measurement.

7. The method according to claim 6, wherein, The measurement protocol information indicates the Simple Bidirectional Active Measurement Protocol and / or the Bidirectional Active Measurement Protocol as applicable measurement protocols, and / or The measurement configuration information includes protocol configuration information.

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

9. An apparatus, comprising components for performing the method according to any one of claims 1 to 8.

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

Images