Routing application traffic to servers of a core network in a wireless communication system

Abstract

Various aspects of the present disclosure relate to an first network function for wireless communication. The first network function may be configured to, capable of, or operable to receive a first message from a second network function, wherein the first message comprises an indication that an application traffic of a user equipment, UE, can be routed to a server within a core network, CN, for an application task; determine to route the application traffic to the server within the CN based at least in part on the indication; select as the server, a first server for supporting the application task, wherein the first server comprises one or more computing resources available to process the application task; and route the application traffic to the first server.

Description

ROUTING APPLICATION TRAFFIC TO SERVERS OF A CORE NETWORK IN A WIRELESS COMMUNICATION SYSTEMTECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, including the routing of application traffic to servers of a core network (CN) in a wireless communication system.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise knowns as network equipment (NE) supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like)). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a Docket No. SMM920250170-GR-NPclosed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] The devices (e.g., NE, UE) and methods of the present disclosure each have several innovative aspects and it may be that no single one of which is solely responsible for the desirable features disclosed herein. For example, any number (e.g., any one or combination) of these innovative aspects may be responsible for the desirable features disclosed herein.

[0005] A first network function for wireless communication is described. The first network function may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network function may comprise at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network function to: receive a first message from a second network function, wherein the first message comprises an indication that an application traffic of a UE can be routed to a server within a CN for an application task; determine to route the application traffic to the server within the CN based at least in part on the indication; select as the server, a first server for supporting the application task, wherein the first server comprises one or more computing resources available to process the application task; and route the application traffic to the first server.

[0006] A method performed or performable by a first network function is described herein. The method may comprise: receiving a first message from a second network function, wherein the first message comprises an indication that an application traffic of a UE can be routed to a server within a CN for an application task; determining to route the application traffic to the server within the CN based at least in part on the indication; selecting as the server, a first server for supporting the application task, wherein the first server comprises one or more computing resources available to process the application task; and routing the application traffic to the first server.Docket No. SMM920250170-GR-NPBRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0008] Figure 2 illustrates an example of an architecture supporting edge discovery in accordance with aspects of the present disclosure.

[0009] Figure 3 illustrates an example of a process flow that provides edge deployment information to a CN in accordance with aspects of the present disclosure.

[0010] Figure 4 illustrates an example of a process flow that routes application traffic of a UE via a CN to an application server at the edge in accordance with aspects of the present disclosure.

[0011] Figure 5 illustrates an example of an architecture for routing application traffic of a UE to a computing server within an operator CN in accordance with aspects of the present disclosure.

[0012] Figure 6 illustrates an example of a process flow that includes an application function (AF) providing information to assist a CN to determine computing resources needed for an application / computing task in accordance with aspects of the present disclosure.

[0013] Figures 7A-7B illustrate an example of a process flow for routing application traffic of a UE to a computing server within a CN in accordance with aspects of the present disclosure.

[0014] Figure 8 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0015] Figure 9 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0016] Figure 10 illustrates an example of a NE in accordance with aspects of the present disclosure.Docket No. SMM920250170-GR-NP

[0017] Figure 11 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0018] In a wireless communication system, one or more UE may communicate with one or more NE. For example, the UE may transmit data to and / or receive data from the NE. The UE may transmit data from an application of the UE, to the one or more NE. The transmitted data may be associated with an application executed by the UE. The transmitted data associated with the application may be referred to as application traffic. In some cases, the application may be distributed between the UE and the NE such that all or part of the application may execute tasks on the UE while other tasks may execute on the NE, or a combination thereof. In some cases, communications between the UE and the NE may be associated with a latency or delay.

[0019] The latency or delay may depend on various factors, including but not limited to physical factors and / or an architecture of the wireless communication system. The physical factors contributing to the latency or delay may include, for example, a distance between the UE and the NE (e.g., a server hosting part or all of the application), a communication medium through which the application traffic is communicated (e.g., transmitted, received), and / or a limitation on computing resources (e.g., processor resources, memory resources, and the like of the UE and / or the NE) available to process (e.g., encode, decode, encrypt, decrypt, compress, decompress, parse, render, display, handle, execute, or the like) a task associated with the application, thereby resulting in a computing delay. The task may comprise, for example, processing of the application traffic generated by the application executed at the UE.

[0020] Excessive latency or delay may adversely impact (e.g., degrade) quality of service (QoS) and quality of experience (QoQ) for applications executed at the UE.Additionally, increased latency or delay may further impact user experience and result in reduced traffic throughput in the wireless communication system, and can disrupt overall service provision. Accordingly, the latency or delay may serve as a key parameter for determining a NE (e.g., a local server, an edge server, a cloud server, or the like) for processing the application traffic of the UE.Docket No. SMM920250170-GR-NP

[0021] A network operator of a CN may maintain a variety of computing resources available for computing tasks. It may be desirable for the network operator to provide (e.g., offer) these computing resources to third-party applications for processing application traffic. Rather than deploying application server instances within edge networks (e.g., at application servers located at a periphery (e.g., edge) of a network infrastructure), it may be advantageous to host or relocate such application server instances within a network operator’s CN. By hosting the application server instances in the network operator’s CN, delays, for example, such as N6 delays, may become more predictable, while computing delays and overall end-to-end communication latencies may be reduced.

[0022] Presently, there are no mechanisms (e.g., methods, techniques, configurations) that enable a CN to determine when application traffic associated with a computing task and / or an application task should be routed to a computing resource and / or a server within the CN itself, as opposed to an edge network or edge server. Additionally, there are no mechanisms (e.g., methods, techniques, configurations) that enable the CN to identify or select specific computing resources and / or servers that are suitable for executing or supporting a computing task and / or an application task.

[0023] As described herein, a first network function is configured to receive a first message including an indication that an application traffic of a UE can be routed to a server within a CN. This tends to provide awareness to the first network function that it can determine (e.g., is permitted) to route the application traffic to the server within the CN. For instance, the first network function may initiate monitoring of delay conditions associated with the application traffic and, based on the monitored delay conditions, route the traffic to the server within the CN when the delay conditions are satisfied. The indication can also be used by the first network function to trigger the determination and selection of the appropriate first server of the CN with the appropriate computing resource / s for the application task. This tends to allow the first network function to selectively mitigate communication latencies through use of the local servers and local computing resource / s for particular computing / application tasks. This may ensure or guarantee certain communication delays, improving user experience, data throughput and overall service provision.Docket No. SMM920250170-GR-NP

[0024] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further set forth in the accompanying drawings and the description below. The description set forth herein, in connection with the accompanying drawings, describes example implementations and does not represent all the implementations that may be implemented or that are within the scope of the claims. The detailed description includes specific details for the purpose of providing an understanding of the described implementations. These implementations, however, may be practiced without these specific details. Additionally, the description set forth herein, in connection with the accompanying drawings is provided to enable a person having ordinary skill in the art to make or use the present disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and implementations described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0025] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a CN 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.Docket No. SMM920250170-GR-NP

[0026] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

[0027] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0028] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0029] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, theDocket No. SMM920250170-GR-NPcommunication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0030] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0031] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0032] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). TheDocket No. SMM920250170-GR-NPPDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0033] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0034] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / t=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / t=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / / =1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., g=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / t=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / t=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0035] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations,Docket No. SMM920250170-GR-NPeach frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0036] Additionally, or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / t=0, / t=l, =2, jtz=3, =4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / t=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0037] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data).Docket No. SMM920250170-GR-NPIn some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0038] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / t=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / z=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / z=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., =2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / t=3), which includes 120 kHz subcarrier spacing.

[0039] As part of the edge computing work in the third-generation partnership project (3GPP) SA2, a procedure has been specified where the 3GPP network assists an application in a UE to route application traffic with an application server in an edge network close to the location of the UE, thus minimizing the communication latency. The architecture to support the edge discovery is shown in the figure below.

[0040] Figure 2 illustrates an example of an architecture 200 supporting edge discovery in accordance with aspects of the present disclosure.

[0041] The architecture 200 shown in Figure 2 comprises a CN 210, a first edge network 220, a second edge network 230 and a UE 240. The CN 210 comprises a session management function (SMF) 212 and an edge application server discovery function (EASDF) 214. The first edge network 220 comprises a first application server 222 and a local-domain name server (L-DNS) 224. The second edge network 230 comprises a second application server 232 and a L-DNS 226.

[0042] The EASDF 214 is a new NF that acts as a DNS proxy / relay to UE DNS requests that are initiated by an application in the UE 240 when the application needs to establish a session with an application server.

[0043] The purpose of the EASDF 214 is to ensure that a DNS request from the UE 240 is sent to a DNS server (an L-DNS) that can resolve the DNS query based on awareness ofDocket No. SMM920250170-GR-NPlocal Application Servers close to the vicinity of the UE 240, hence improving the communication latency between the application in the UE 240 and the application server.

[0044] The application in the UE 240 sends a DNS request to the EASDF 214 to discover an application server. The EASDF 214 forwards the UE DNS request to L-DNS 234 or a DNS server in the cloud according to a configuration received from the SMF 212. The SMF 212 provides rules to the EASDF 214 based on knowledge of the edge network 230 in the location of the UE 240. The SMF 212 configures the EASDF 214 by providing DNS message handling rules.

[0045] Each rule provided by the SMF 212 to the EASDF 214 may include at least one of the following items of information: precedence of the DNS message handling rule; DNS message detection template; and Action(s).

[0046] The DNS message detection template may include at least one of the following information. The DNS message type = DNS Query or DNS Response. If the DNS message type = DNS Query then include: Source IP address (i.e. UE IP address); Array of (FQDN ranges). If the DNS message type = DNS Response then include: Array of FQDN ranges and / or array of EAS IP address ranges.

[0047] The possible actions may include report DNS message content to SMF 212. The possible actions may include send the DNS message to a preconfigured DNS server / resolver or an indicated DNS server as following (the indicated DNS server is included in the DNS handling rule): including the information to build optional EDNS Client Subnet option in the DNS message (the information for the EASDF 214 to build the EDNS Client Subnet option is included in the DNS handling rule). The possible actions may include replacement of the DNS message target address with the indicated DNS Server Address; if no DNS Server Address is provided by the SMF 212, then the EASDF 214 is to forward the DNS message to a locally preconfigured DNS server / resolver. The possible actions may include buffer the DNS message and report DNS message content to the SMF 212. The possible actions may include send the buffered DNS response message to UE 240.

[0048] It will now be described how the SMF 212 is made aware of EAS deployments in order to construct DNS message handling rules to the EASDF 214.Docket No. SMM920250170-GR-NP

[0049] Figure 3 illustrates an example of a process flow 300 that provides edge deployment information to CN in accordance with aspects of the present disclosure. The CN may be a 5G CN.

[0050] The process flow 300 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 300 may include an EASDF 310, an SMF 320, a policy control function (PCF) 330, a unified data management (UDM) function / unified data repository (UDR) 340, a network exposure function (NEF) 350, an AF 360, which may be one or more examples of devices described herein with reference to Figure 1. The process flow 300 may be referred to as a procedure, including one or more operations performed by one or more of the EASDF 310, SMF 320, PCF 330, UDM / UDR 340, NEF 350, AF 360.

[0051] In the following description of the process flow 300, the operations or signalling performed between one or more of the EASDF 310, SMF 320, PCF 330, UDM / UDR 340, NEF 350, AF 360 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the EASDF 310, SMF 320, PCF 330, UDM / UDR 340, NEF 350, AF 360 may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 300.Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0052] At step 301, the AF 360 transmits a Nnef_EAS_Deployment_Create message to the NEF 350.

[0053] At step 302a, the NEF 350 performs NEF handling.

[0054] At step 302b, the PCF 330 finds an AMF serving UE.

[0055] At step 303, the NEF 350 transmits an Nudr_DM_Create / Update message to the UDM / UDR 340.Docket No. SMM920250170-GR-NP

[0056] At step 304, the UDM / UDR 340 transmits a Nudr_DM_Create / Update response to the NEF 350.

[0057] At step 305, the NEF 350 transmits a Nnef_EAS_Deployment_Create response message to the AF 360.

[0058] At step 306, the SMF 320 transmits a Nnef_Subscribe_EASDeployment_Subscribe message to the NEF 350.

[0059] At step 307, the NEF 350 transmits a Nnef_Subscribe_EASDeployment_Notify message to the SMF 320.

[0060] At step 308, the SMF 320 creates DNS message handling rules based on EAS Deployment Information and configures the EASDF 310.

[0061] The AF 360 may, at step 301, provide the EAS deployment information by invoking a service request towards the NEF 350 which includes parameters as shown in Table 1.Docket No. SMM920250170-GR-NPTable 1

[0062] The EAS deployment information may be stored in the NEF 350 and UDR 340 and the SMF 320 obtains the information by querying the NEF 350. Based on the EAS deployment information the SMF 320 may configure DNS handling rules to the EASDF 310 at step 308.Docket No. SMM920250170-GR-NP

[0063] When an AF, which may be a 3rd party AF, wishes to route traffic to an application server close to a UE location via the CN for an edge service (e.g. a computing service), a further procedure may be followed as will now be described.

[0064] Figure 4 illustrates an example of a process flow 400 that routes application traffic of a UE via a CN to an application server at the edge in accordance with aspects of the present disclosure. The process flow 400 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 400 may include an EASDF 410, SMF 420, PCF 430, UDM / UDR 440, NEF 450, AF 460, UE 470, RAN 480 which may be one or more examples of devices described herein with reference to Figure 1.

[0065] The process flow 400 may be referred to as a procedure, including one or more operations performed by one or more of the EASDF 410, SMF 420, PCF 430, UDM / UDR 440, NEF 450, AF 460, UE 470, RAN 480.

[0066] In the following description of the process flow 400, the operations or signalling performed between one or more of the EASDF 410, SMF 420, PCF 430, UDM / UDR 440, NEF 450, AF 460, UE 470, RAN 480 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the EASDF 410, SMF 420, PCF 430, UDM / UDR 440, NEF 450, AF 460, UE 470, RAN 480 may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 400. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0067] At step 401, the AF 460 transmits an Nnef TrafficInfluence request towards the NEF 450. The AF 460 includes in the Nnef TrafficInfluence request parameters that assist the NEF 450 and CN to route the application traffic of the UE 470 to an (edge) application server close to the location of the UE 470 and thus reducing end-to-end latency. The parameters may include one or more of: an application ID, traffic filters, a DNAI, an N6 delay measurement indication.Docket No. SMM920250170-GR-NP

[0068] At step 402, the NEF 450 transmits a Nudr_DM_Create / Update message to the UDM / UDR 440.

[0069] At step 403, UDM / UDR 440 transmits a Nudr_DM_Create / Update response message to the NEF 450.

[0070] At step 404, the UDM / UDR 440 transmits a Nudr_DM_Notify message to the PCF 430.

[0071] At step 405, the PCF 430 transmits a PCC rule to the SMF 420. The PCC rule may include the parameters from the Nnef TrafficInfluence request for a UE PDU session.

[0072] At step 406, the UE 470 decides to discover an application server and transmits a DNS request (from an application of the UE 470) to the EASDF 410.

[0073] At step 407, the EASDF 410, based on SMF 420 instructions, routes the DNS request to a local DNS server where the application servers close to the UE 470 are deployed. The DNS response may include a list of application server IP address(es) that is provided to the SMF 420 also in step 407.

[0074] At step 408, the SMF 420 routes the application traffic of the UE 470 via a local UPF close to the location of the UE 470 and the application servers. This decision may be based on DNAI and EAS deployment information. Various procedures on how the SMF 420 routes the traffic is provided in clause 6.2 of the 3GPP Specification TS 23.548 titled “5G System Enhancements for Edge Computing”.

[0075] Procedures have also been described where the CN can trigger relocation of an application server as described in clause 6.3 of the 3GPP Specification TS 23.548. Different procedures have been described where either the SMF 420 informs the AF 460 of the application server change or triggers the UPF to route the traffic to a new application server or to trigger the UE 470 to re-discover an application server. It has been described that the SMF 420 can decide to relocate the application server by considering user plane latency requirement (between UE 470 and UPF) and / or by measuring delay between the UPF and potential application servers (N6 delay).Docket No. SMM920250170-GR-NP

[0076] As part of the 6G study in 3GPP, one of the objectives is to allow an operator network to support computing services for a 3rd party application provider. The use case under consideration is the case where a 3rd party application provider has agreements with an operator to use the computing resources available in the operator network (i.e., in the CN). It is envisioned that instead of (or in addition to) placing application servers at the edge of the operator network premises (and usually out of operator scope), to allow the operator to offer its vast computing resources to support a computing / application task for an application. As such there is a requirement to support a procedure where the application traffic of a UE that needs a computing service, can be routed to a computing server within the operator CN premises. The computing server may comprise a server that is able to support one or more computing tasks for an application. The one or more computing tasks may comprise processing image of an application or performing AIML inference for enhancing the video image for example. The computing server may support processing computing tasks for multiple applications. The computing server may support one or more computing tasks of a 3rd party application based on SLA agreements with an operator.

[0077] Figure 5 illustrates an example of an architecture 500 for routing application traffic of a UE to a computing server within an operator CN in accordance with aspects of the present disclosure.

[0078] The architecture 500 comprises a first edge server 502, a second edge server 504, a first computing server 506 within a CN, a second computing server 508 within the CN, an SMF 520, a UE 570, a RAN 580, an AMF 585 and a UPF 590. The first computing server 506 services a first area, with the second computing server 508 serving a second area. The first area and / or second area may be respective location areas, DNAI or network topology areas, for example. An example of a network topology area is an IP submit within an operator CN.

[0079] The first edge server 502 and the second edge server 504 are shown as interfacing with the UPF 590 over N6. The first computing server 506 within the CN and the second computing server 508 within the CN are shown as interfacing with the UPF 590 over N6. The SMF 520 is shown as interfacing with the UPF 590 over N6. The AMF 585 is shown as interfacing with the SMF 520. The AMF 585 is shown as also interfacing with theDocket No. SMM920250170-GR-NPRAN 580 over N2. The RAN 580 is shown as further interfacing with the UPF 590 over GTP-U. The RAN 580 is further shown as interfacing with the UE 570 over Uu.

[0080] As shown in the architecture 500, the N6 delay between the UPF 590 and the first computing server 506 can be referred to as a first delay or a ‘delay 1’, with the N6 delay between the UPF 590 and the second computing server 508 being referred to as a second delay or a ‘delay 2’. The first delay and the second delay tend to be predictable and reliable and hence it is desirable to route application traffic from the UE 570 via the RAN 580 and UPF 590 to the first computing server 506 or to the second computing server 508. This may guarantee the N6 delay and offer potentially reduced computing latency than if the application traffic were routed to the first edge server 502 or the second edge server 504.

[0081] The disclosure herein addresses the problem of how, within the architecture 500, a decision is made to route application traffic of the UE 570 from the edge server 502, 504 to a computing server 506, 508 within the operator network. It is expected that operators will charge more for performing the computing service on behalf of an application and hence the solution may allow the 3rd party application to provide conditions on when the application traffic of the UE 570 should be routed to the computing server 506, 508 within the operator network

[0082] The disclosure herein also addresses the problem of how a function in the CN (i.e., the SMF 520) identifies which computing servers 506, 508 will be able to support the computing / application task required by an application. As such is the disclosure herein also provides for how the CN is aware of the computing services required by an application.

[0083] The manner in which awareness of computing resources needed for an application's task (i.e., a computing task / application task) can be provided will now be described. In particular, the awareness of the computing resources needed for an application’s computing / application task can in some examples be supported through the use of computing task identifiers. A computing task identifier may indicate a specific computing task for the (3rd party) application. Based on such a computer task identifier the CN may determine one or more of: the computing resources needed to be allocated to run the specific computing task; the software that needs to be instantiated to run the Docket No. SMM920250170-GR-NPapplication's computing task; the computing latency, i.e. the expected time taken to run the specific computing task for an application. The software that needs to be instantiated may comprise, by way of example, an AI / ML inference operation.

[0084] The computing task identifiers may be configured based on service level agreement (SLA) between a 3rd party application provider and the operator of the CN. Each identifier may allow the operator of the CN to determine in the computing server / s of the CN what hardware and / or software configuration is needed. The operator will then select and / or deploy computing servers that can support the application's computing task. Such computing servers may be placed within the UPF or they may be placed to a server close to the RAN nodes. The location of each computing server may be stored in the NRF. Each UPF may register the computing task IDs that are supported. A new NF, referred to herein as a computing function, may register to the NRF the computing task identifiers that are supported.

[0085] The 3rd party application provider may provide EAS deployment information to the CN which may include additional information to assist the CN to determine the computing resources required for a computing / application task. The additional information may comprise the computing task identifiers. Existing parameters may be used such as the AF service identifier or group identifier or DNAI to describe computing task(s). In an example the CN identifies the computing task identifiers based on configuration (i.e., the CN has a mapping of AF service identifier or group identifier to computing task identifiers).

[0086] Figure 6 illustrates an example of a process flow 600 that includes an AF providing information to assist a CN to determine computing resources needed for an application / computing task in accordance with aspects of the present disclosure. The process flow 600 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 600 may include SMF 620, PCF 630, UDM / UDR 640, NEF 650, AF 660, computing function, NRF or UPF 690 which may be one or more examples of devices described herein with reference to Figure 1.Docket No. SMM920250170-GR-NP

[0087] The process flow 600 may be referred to as a procedure, including one or more operations performed by one or more of the SMF 620, PCF 630, UDM / UDR 640, NEF 650, AF 660, computing function, NRF or UPF 690.

[0088] In the following description of the process flow 600, the operations or signalling performed between one or more of the SMF 620, PCF 630, UDM / UDR 640, NEF 650, AF 660, computing function, NRF or UPF 690 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the SMF 620, PCF 630, UDM / UDR 640, NEF 650, AF 660, computing function, NRF or UPF 690 may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 600. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0089] At step 601, the AF 660 provides an Nnef_EASDeployment_Create message to the NEF 650. The Nnef EASDeployment Create message includes deployment information which may indicate the computing resources needed for an application / computing task associated with application traffic of a UE. The UE is not shown in the process flow 600. the deployment information may include one or more computing task identifiers.

[0090] At step 602a, the NEF 650 authorises the request (the Nnef_EASDeployment_Create message). Whilst not shown in the process flow 600, the NEF 650 may interact with the computing function, NRF or UPF 690 to determine if there are available computing servers to support the application / computing task. The NEF 650 may translate the computing task identifiers to specific NF IDs supporting the application / computing task. At step 602b, the PCF 630 finds an AMF serving the UE. Neither the AMF nor the UE are shown in the process flow 600.

[0091] At step 603, the NEF 650 stores to the UDM / UDR 640 the deployment information including the computing task identifiers or the NF IDs supporting the application / computing task. This may be performed by the NEF 650 transmitting a Nudr_DM_Create / Update message to the UDM / UDR 640.Docket No. SMM920250170-GR-NP

[0092] At step 604, the UDM / UDR 640 acknowledges the message from the NEF 650. This may be performed by the UDM / UDR 640 transmitting to the NEF 650 a Nudr_DM_Create / Update response message.

[0093] At step 605, the NEF 650 transmits to the AF 660 aNnef EAS Deployment Create Response message to acknowledge the request from the AF 660 in step 601.

[0094] At step 606, when a PDU session is created by the UE (not shown in the process flow), the SMF 620, based on configuration, subscribes from the NEF 650 to retrieve EAS deployment information More specifically, the SMF 620 transmits to the NEF 650 a Nnef_Subscribe_EASDeployment_Subscribe message.

[0095] At step 607, the NEF 650 provides the SMF 620 with the EAS deployment information. More specifically, the NEF 650 transmits a Nnef_Subscribe_EASDeployment_Notify message to the SMF 620.

[0096] At step 608, the SMF 620 may identify the available computing servers that support the computing task in the serving area (i.e. DNAI serving area and / or UE location area and / or network topology) by interfacing with a computing function, NRF or UPF 690 in the CN that contains computer server information.

[0097] The SMF 620 may transmit a message to the computing function, NRF or UPF 690 requesting computing servers / functions that can support the application / computing task.

[0098] In step 608, in the example where the computing function, NRF or UPF 690 is a new computing function, then the SMF 620 may send the request via a new SBI interface including the computing task id(s), the application id, DNAI and / or AF service identifiers. The computing function may register the supported computing task identifier and / or serving area (e.g. DNAI(s), location area) in the NRF. The SMF 620 may interface with the NRF to find the computing function(s) supporting the task identifiers at the serving area.

[0099] In step 608, in the example where the computing function, NRF or UPF 690 is a UPF, the SMF 620 may send a request via a new SBI interface including the computingDocket No. SMM920250170-GR-NPtask id, the application id, DNAI and / or AF service identifiers. The UPF may register the supported computing task identifier and / or serving area in the NRF. The SMF 620 may interface with NRF to find the UPF(s) supporting the task identifiers in the serving area.

[0100] In step 608, in the example where the computing function, NRF or UPF 690 is an NRF, the SMF 620 may send a request to the NRF to discover the functions supporting the computing task identifiers at the serving area (UE location / DNAI / AF service ID).

[0101] In step 609, the computing function, NRF or UPF 690 may transmit a response to the SMF 620. The response may include a list of computing server IP addresses and serving area information. If the computing server is collocated at the UPF the UPF may include its IP address plus port information to allow the SMF 620 to route the UE application traffic at the port address of the UPF supporting the computing server.

[0102] At step 610, the SMF 620 builds a computing server deployment information based on the information received in step 609. Furthermore, based on EAS deployment information, the SMF 620 may configure DNS message handling rules at an EASDF (not shown in the process flow 600) as described in the 3 GPP Specification TS 23.548 titled “5G System Enhancements for Edge Computing”. The SMF 620 takes into account the computing server / s supporting the computing task identifiers.

[0103] The DNS message handling rules configured by the SMF 620 may include the address of a computing function 690 that is able to resolve a server supporting an application task for an application.

[0104] The manner in which a decision to route application traffic from a UE to a computing server within the operator CN will now be described.

[0105] When a 3rdparty (i.e., a 3rdparty AF) wishes to route application traffic of a UE to an application server close to the UE location, via the CN for an edge service (e.g., a computing service), the 3rd party AF may also include conditions to allow the application traffic of the UE to be routed to a computing service within the operator's CN. In such a case, an Nnef TrafficInfluence request from the AF to the NEF may include additional information.Docket No. SMM920250170-GR-NP

[0106] The additional information may include one or more computing task identifier(s) that will need to be supported. The computing task identifiers have been hereinbefore described. The computing tasks themselves may be associated to an AF service identifier or a group identifier or a DNAI included within the existing Traffic Influence request.

[0107] The additional information may include a local compute indication (an indication that routing application traffic of the UE to a computing server within the operator CN is allowed).

[0108] The additional information may include requirements to route the traffic to an edge application server / computing server which may be one or more of: an N6 delay threshold (delay between the UPF and the Application Server); an end-to-end delay threshold between the UE and the Application server where the end-to-end delay includes a compute delay; a UE to UPF delay requirement.

[0109] When the SMF receives an indication to route application traffic of a UE to a computing server within the CN, the SMF may start to monitor the delay (either N6 delay or end-2-end delay or UE-UPF delay) and if the delay crosses a specific threshold decide to route the application traffic of the UE to a computing server in the CN. The SMF may take into account the computing task identifier(s) provided by the AF. The SMF may find the computing servers supporting the UE application's computing task by interfacing with a computing function or the NRF (or based on a pre-configuration).

[0110] The SMF may decide to route the application traffic of the UE to a computing server within the CN based on certain other conditions.[OHl] These conditions include RAN congestion information that affects the e2e delay; UPF load conditions (by diverting traffic to a computing server will bypass the UPF); an explicit indication by the AF to immediately route the traffic to a computing server (due to Application Servers at the edge experiencing congestion); when the SMF receives a list of Edge Application Server addresses from a DNS response as part of the initial DNS query as summarised in clause 6.2 of the 3GPP Specification TS 23.548, the SMF determining that the these EAS have low performance (either by interfacing with AFDocket No. SMM920250170-GR-NPor by requesting analytics by the NWDAF for the indicated EAS addresses); the SMF receiving no EAS IP address in a DNS response and deciding to route the application traffic of the UE directly at a computing server in the CN.

[0112] Figures 7A-7B illustrates an example of a process flow 700 for routing application traffic of a UE to a computing server within a CN in accordance with aspects of the present disclosure. The process flow 700 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 700 may include EASDF 719, SMF 720, PCF 730, UDM / UDR 740, NEF 750, AF 760, UE 770, DNS server 785, L-UPF 790, EAS 792, computing repository 794 which may be one or more examples of devices described herein with reference to Figure 1.

[0113] The process flow 700 may be referred to as a procedure, including one or more operations performed by one or more of the EASDF 719, SMF 720, PCF 730, UDM / UDR 740, NEF 750, AF 760, UE 770, DNS server 785, L-UPF 790, EAS 792, computing repository 794.

[0114] In the following description of the process flow 700, the operations or signalling performed between one or more of the EASDF 719, SMF 720, PCF 730, UDM / UDR 740, NEF 750, AF 760, UE 770, DNS server 785, L-UPF 790, EAS 792, computing repository 794 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the EASDF 719, SMF 720, PCF 730, UDM / UDR 740, NEF 750, AF 760, UE 770, DNS server 785, L-UPF 790, EAS 792, computing repository 794 may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 700. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0115] The process flow 700 includes steps 701-718 which have been split across Figures 7A-7B for illustrative purposes. In particular, Figure 7A includes the steps 701-709 and Figure 7B includes the steps 710-718. It will be appreciated that in the example process flow 700, the steps 710-718 may follow from the steps 701-709.Docket No. SMM920250170-GR-NP

[0116] Figure 7A and the steps 701-709 will now be described.

[0117] At step 701, the AF 760 transmits a Nnef_TrafficInfluenceRequest to the NEF 750. The AF 760 triggers the traffic influence request by including within theNnef TrafficInfluenceRequest an application traffic information which may include at least one of application ID (5 tuple), AF service identifier, traffic filters, DNAI, N6 delay measurement indication. The AF 760 may include a requirement to route traffic to a computing server within the CN by including one or more of: computing task identifiers, local compute indication, delay requirements between the UE 770 and the UPF 790, UE 770 and AS 792 or between UPF 790 and AS 792, computational delay requirements.

[0118] At step 702, the NEF 750 authorises and validates the information received in step 701 from the AF 760. The NEF 750 may translate the AF service identifier and / or DNAI and / or application information to a set of computing task identifiers (i.e. in that case the AF does not include computing task identifiers, but these are pre-configured as part of SLA agreements between 3rd party and operator).

[0119] At step 703, the NEF 750 stores the traffic influence request to the UDM / UDR 740 as described in the 3GPP Specification TS 23.502 titled “Procedures for the 5G System (5GS)”. More specifically, the NEF 750 transmits a Nudr_DM_Create / Update message to the UDM / UDR 740.

[0120] At step 704, the UDM / UDR 740 acknowledge the request from the NEF 750 as described in the 3GPP Specification TS 23.502. More specifically the UDM / UDR 740 transmits a Nudr_DM_Create / Update response message to the NEF 750.

[0121] At step 705, the UDM / UDR 740 forwards the information from the NEF 750 in a Nudr_DM_Notify message to any PCF 730 that has subscribed to traffic influence request notifications as described in the 3GPP TS 23.502

[0122] At step 706, the PCF 730 transmits PCC rules to the SMF 720 that may include one or more of DNAI and / or computing task identifiers. The computing task identifiers may be supported with an existing identifier (e.g. AF service identifier or DNAI).Docket No. SMM920250170-GR-NP

[0123] At step 707, when an application / application traffic starts at the UE 770, the application attempts to discover an application server address.

[0124] At step 708, the application transmits a DNS request to EASDF 719 (via the UE 770) via a PDU session established according to URSP rules.

[0125] At step 709, the DNS request is received at the EASDF 719 (as the SMF 720 has already configured to route DNS traffic from a UE 770 to an EASDF server).

[0126] Figure 7B and the steps 710-718 will now be described.

[0127] At step 710a the EASDF 719 transmits a DNS request to the SMF 720. At step 710b the EASDF 719 transmits a DNS request to the DNS server 785. At step 710c the DNS server 785 transmits a DNS response (containing EAS IP addresses) to the EASDF 719. At step 710d the EASDF 719 transmits a DNS response to the SMF 720. Various options are summarized in the 3GPP Specification TS 23.548 titled “5G System Enhancements for Edge Computing” for routing a DNS request from the EASDF 719 to either the local DNS server 785 or to the SMF 720.

[0128] At step 711, the SMF 720 starts by routing traffic to an Edge Application Server 792 according to DNAI received in the PCC rule. The SMF 720 allocates a local UPF 790 as described in the 3 GPP Specification TS 23.548

[0129] At step 712, the application traffic of the UE 770 is routed from the UE 770 to the Edge Application Server 792 via the L-UPF 790.

[0130] At step 713, the SMF 720, based on the local computing indication or delay requirements, determines to measure the N6 delay or end to end delay or UE 770 to UPF 790 delay. The SMF 720 determines whether the delay is below a threshold delay which may consider the computing requirements (according to PCC rules). The SMF 720 may also subscribe from the AMF (not shown) to location changes.

[0131] At step 714, the SMF 720 subscribes to the L-UPF 790 to measure the delay between the L-UPF 790 and the Edge Application Server 792, or to the delay between the UE 770 and the L-UPF 790 or to the delay between the UE 770 and the Edge ApplicationDocket No. SMM920250170-GR-NPServer 792. The latter is supported by the L-UPF 790 measuring N6 delay plus delay between UE 770 and L-UPF 790.

[0132] At step 715, the L-UPF 790 transmits the delay measurements to the SMF 720 in a delay report.

[0133] At step 716, if the SMF 720 determines that the delay crosses the threshold the SMF 720 may decide to route application traffic of the UE 770 to a computing server in the CN.

[0134] At step 717, the SMF 720 finds / discovers available computing servers in the CN that support the computing tasks by interfacing with an NF that contains computing server information. As shown, the NF is referred to as a computing repository 794.

[0135] If the computing repository 794 is a new computing function the SMF 720 sends a request via a new SBI interface including the computing task id(s), the application id, DNAI and / or AF service identifiers. The computing function may register the supported computing task identifier and / or serving area (e.g. DNAI(s), location area) in the NRF. SMF 720 may then interface with NRF to find the computing function(s) supporting the task identifiers at the serving area.

[0136] If the computing repository 794 is a UPF the SMF 720 sends a request via a new SBI interfaces including the computing task id, the application id, DNAI and / or AF service identifiers. The UPF may register the supported computing task identifier and / or serving area in the NRF. SMF 720 may interface with NRF to find the UPF(s) supporting the task identifiers in the serving area.

[0137] If the computing repository 794 is a NRF the SMF 720 sends a request to the NRF to discover the functions supporting the computing task identifiers at the serving area (UE location / DNAI / AF service ID).

[0138] The SMF 720 may already have built computing deployment information based on receiving from NEF 750 computing task identifiers as described herein. In such a case, the SMF 720 may interface with each computing server to identify if there are available resources for the application task. Alternatively, the SMF 720 may check with theDocket No. SMM920250170-GR-NPcomputing function that provided the list of computing servers to check if these servers have available resources for the application computing task. The SMF 720 selects a computing server to route the application traffic of the UE 770.

[0139] At step 718, the SMF 720 triggers edge relocation.

[0140] The SMF 720 may re-route the application traffic of the UE from an edge application server 792 to a computing server within the CN in a number of ways. The SMF 720 may trigger the UE 770 to start EAS re-discovery and change application server as described in clause 6.2.3.3 of the 3GPP Specification TS 23.548. In such a case the SMF 720 may send to the UE 770 a PDU Session Modification Command including EAS rediscovery indication and information to assist computing server discovery in the CN. The SMF 720 may include FQDN)(s) or IP address range(s) of the old EAS(s) and FQDN IP address range of the computing server in the CN. The SMF 720 may select a local UPF 790 and provide routing rules to the L-UPF 790 to route traffic to a local computing server. The application in the UE 770 may then, by receiving information from a new computing server, adjust for EAS change via application implementation means.

[0141] The SMF 720 may configure the EASDF 719 to forward the DNS message to a computing function supporting the computing tasks of the UE application (e.g. based on building computing deployment information as described herein). When the SMF 720 decides that application traffic of the UE 770 needs to be routed to a computing server the SMF 720 may trigger the UE 770 to start EAS re-discovery as described in clause 6.2.3.3 of the 3GPP Specification TS 23.548. The UE 770 may send a DNS request message that is received at the EASDF 719. The EASDF 719 may then forward the DNS message to a computing function. The computing function may then determine the available computing servers supporting the application computing requirements and include in a DNS response a list of IP addresses of the selected computing servers that can support the computing requirements.

[0142] Figure 8 illustrates an example of a UE 800 in accordance with aspects of the present disclosure. The UE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations thereof or various components thereof may be Docket No. SMM920250170-GR-NPexamples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0143] The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0144] The processor 802 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 802 may be configured to operate the memory 804. In some other implementations, the memory 804 may be integrated into the processor 802. The processor 802 may be configured to execute computer-readable instructions stored in the memory 804 to cause the UE 800 to perform various functions of the present disclosure.

[0145] The memory 804 may include volatile or non-volatile memory. The memory 804 may store computer-readable, computer-executable code including instructions when executed by the processor 802 cause the UE 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 804 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0146] In some implementations, the processor 802 and the memory 804 coupled with the processor 802 may be configured to cause the UE 800 to perform one or more of the functions described herein (e.g., executing, by the processor 802, instructions stored in the memory 804). For example, the processor 802 may support wireless communication at the UE 800 in accordance with examples as disclosed herein. The UE 800 may be configured to support the arrangements described herein.Docket No. SMM920250170-GR-NP

[0147] The controller 806 may manage input and output signals for the UE 800. The controller 806 may also manage peripherals not integrated into the UE 800. In some implementations, the controller 806 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 806 may be implemented as part of the processor 802.

[0148] In some implementations, the UE 800 may include at least one transceiver 808. In some other implementations, the UE 800 may have more than one transceiver 808. The transceiver 808 may represent a wireless transceiver. The transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

[0149] A receiver chain 810 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 810 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 810 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 810 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 810 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0150] A transmitter chain 812 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 812 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 812 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 812 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0151] Figure 9 illustrates an example of a processor 900 in accordance with aspects of the present disclosure. The processor 900 may be an example of a processor configured to Docket No. SMM920250170-GR-NPperform various operations in accordance with examples as described herein. The processor 900 may include a controller 902 configured to perform various operations in accordance with examples as described herein. The processor 900 may optionally include at least one memory 904, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 900 may optionally include one or more arithmetic-logic units (ALUs) 906. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0152] The processor 900 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 900) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0153] The controller 902 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 900 to cause the processor 900 to support various operations in accordance with examples as described herein. For example, the controller 902 may operate as a control unit of the processor 900, generating control signals that manage the operation of various components of the processor 900. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0154] The controller 902 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 904 and determine subsequent instruction(s) to be executed to cause the processor 900 to support various operations in accordance with examples as described herein. The controller 902 may be configured to track memory address ofDocket No. SMM920250170-GR-NPinstructions associated with the memory 904. The controller 902 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 902 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 900 to cause the processor 900 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 902 may be configured to manage flow of data within the processor 900. The controller 902 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 900.

[0155] The memory 904 may include one or more caches (e.g., memory local to or included in the processor 900 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 904 may reside within or on a processor chipset (e.g., local to the processor 900). In some other implementations, the memory 904 may reside external to the processor chipset (e.g., remote to the processor 900).

[0156] The memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 900, cause the processor 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 902 and / or the processor 900 may be configured to execute computer-readable instructions stored in the memory 904 to cause the processor 900 to perform various functions. For example, the processor 900 and / or the controller 902 may be coupled with or to the memory 904, the processor 900, the controller 902, and the memory 904 may be configured to perform various functions described herein. In some examples, the processor 900 may include multiple processors and the memory 904 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0157] The one or more ALUs 906 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or moreDocket No. SMM920250170-GR-NPALUs 906 may reside within or on a processor chipset (e.g., the processor 900). In some other implementations, the one or more ALUs 906 may reside external to the processor chipset (e.g., the processor 900). One or more ALUs 906 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 906 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 906 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 906 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 906 to handle conditional operations, comparisons, and bitwise operations.

[0158] The processor 900 may support wireless communication in accordance with examples as disclosed herein. The processor 900 may be configured to or operable to support a means for a first network function as described herein. The processor 900 may be configured to or operable to support a means for receiving a first message from a second network function, wherein the first message comprises an indication that an application traffic of a UE can be routed to a server within a CN for an application task; determining to route the application traffic to the server within the CN based at least in part on the indication; selecting as the server, a first server for supporting the application task, wherein the first server comprises one or more computing resources available to process the application task; and routing the application traffic to the first server.

[0159] Figure 10 illustrates an example of a NE 1000 in accordance with aspects of the present disclosure. The NE 1000 may include a processor 1002, a memory 1004, a controller 1006, and a transceiver 1008. The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.Docket No. SMM920250170-GR-NP

[0160] The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0161] The processor 1002 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1002 may be configured to operate the memory 1004. In some other implementations, the memory 1004 may be integrated into the processor 1002. The processor 1002 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the NE 1000 to perform various functions of the present disclosure.

[0162] The memory 1004 may include volatile or non-volatile memory. The memory 1004 may store computer-readable, computer-executable code including instructions when executed by the processor 1002 cause the NE 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1004 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0163] In some implementations, the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to cause the NE 1000 to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004). For example, the processor 1002 may support wireless communication at the NE 1000 in accordance with examples as disclosed herein. The NE 1000 may be configured to support a means for a first network function as disclosed herein. The NE 1000 may be configured to support a means for receiving a first message from a second network function, wherein the first message comprises an indication that an applicationDocket No. SMM920250170-GR-NPtraffic of a UE can be routed to a server within a CN for an application task; determining to route the application traffic to the server within the CN based at least in part on the indication; selecting as the server, a first server for supporting the application task, wherein the first server comprises one or more computing resources available to process the application task; and routing the application traffic to the first server.

[0164] The controller 1006 may manage input and output signals for the NE 1000. The controller 1006 may also manage peripherals not integrated into the NE 1000. In some implementations, the controller 1006 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1006 may be implemented as part of the processor 1002.

[0165] In some implementations, the NE 1000 may include at least one transceiver 1008. In some other implementations, the NE 1000 may have more than one transceiver 1008. The transceiver 1008 may represent a wireless transceiver. The transceiver 1008 may include one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.

[0166] A receiver chain 1010 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1010 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1010 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 1010 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1010 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0167] A transmitter chain 1012 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1012 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude Docket No. SMM920250170-GR-NPmodulation (QAM). The transmitter chain 1012 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1012 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0168] Figure 11 illustrates a flowchart of a method 1100 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0169] At 1102, the method 1100 may include receiving a first message from a second network function, wherein the first message comprises an indication that an application traffic of a UE can be routed to a server within a CN for an application task. The operations of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by a NE as described with reference to Figure 10.

[0170] At 1104, the method 1100 may include determining to route the application traffic to the server within the CN based at least in part on the indication. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by a NE as described with reference to Figure 10.

[0171] At 1106, the method 1100 may include selecting as the server, a first server for supporting the application task, wherein the first server comprises one or more computing resources available to process the application task. The operations of 1106 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1106 may be performed a NE as described with reference to Figure 10.

[0172] At 1108, the method may include routing the application traffic to the first server. The operations of 1108 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1108 may be performed by a NE as described with reference to Figure 10.Docket No. SMM920250170-GR-NP

[0173] It should be noted that the method 1100 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0174] A first network function for wireless communication is described. The first network function may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network function may comprise at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network function to: receive a first message from a second network function, wherein the first message comprises an indication that an application traffic of a UE can be routed to a server within a CN for an application task; determine to route the application traffic to the server within the CN based at least in part on the indication; select as the server, a first server for supporting the application task, wherein the first server comprises one or more computing resources available to process the application task; and route the application traffic to the first server.

[0175] The indication may alternatively be referred to herein as a local computing indication.

[0176] The disclosure herein may refer to the server within the CN as being a ‘local’ server or a ‘local’ computing resource. The term ‘local’ is used to indicate that the server instance is supported by a server within the CN premises. This may be contrasted with a server instance that is instead supported by an edge server at an edge network. A server within the CN may comprise one or more computing resources.

[0177] The at least one processor may be further configured to cause the first network function to: prior to routing the application traffic to the first server, route the application traffic of the UE to an application server of an edge network via a UPF; and then route the application traffic to the first server by triggering a relocation, to the first server, of an application server instance of the application server of the edge network.

[0178] The first network function may initially route the application traffic of the UE to the application server at the edge network. This routing may be via a UPF based on a data network access identifier (DNAI) parameter (as may be received in a PCC rule). The firstDocket No. SMM920250170-GR-NPnetwork function may subsequently trigger the relocation of the application server instance to the first server.

[0179] The at least one processor may be further configured to cause the first network function to: determine to route the application traffic to the server within the CN based at least in part on one or more delay conditions.

[0180] The one or more delay conditions may comprise at least one of: an N6 delay between the UPF and the application server at the edge network crossing an N6 delay threshold; an end-to-end delay between the UE and the application server at the edge network crossing an end-to-end delay threshold; a UE-to-UPF delay between the UE and the UPF crossing an UE-to-UPF delay threshold; a RAN congestion information; a UPF load condition; an AF requirement to immediately route application traffic to the server; a low performance of an edge application server, EAS; and a lack of an EAS address in a domain name server, DNS, response.

[0181] The term ‘crossing’ may include ‘exceeding’. TheN6 delay threshold, end-to-end delay threshold, UE-to-UPF delay threshold may be provided to the first network function in the first message.

[0182] The first message may further comprise one or more computing task identifiers, wherein each computing task identifier indicates a respective computing task for the application traffic of the UE; or the at least one processor is further configured to cause the first network function to receive, from a NEF, the one or more computing task identifiers.

[0183] The computing task identifiers may be configured based on a service level agreement (SLA) between a third-party application provider and a network operator.Accordingly, the NEF may be preconfigured with the computing task identifiers and may translate information received from the third-party application to the computing task identifiers or to specific NF identifiers. The third-party application may be the application that generates the application traffic of the UE. Each identifier may allow a network operator to determine what configuration of computing resource is required for the computing task, what software is required to run the computing task and / or the computing latency (the expected time taken to run the computing task). The computing task identifiersDocket No. SMM920250170-GR-NPmay alternatively be provided by the third-party application directly to the CN (i.e., to the NEF).

[0184] The computing task identifiers may be provided to the first network function in the first message from the second network function. For example, the computing task identifiers may be provided from a PCF as part of PCC rules. Alternatively, the computing task identifiers may be provided to the first network function by a NEF, for example, as part of EAS deployment information.

[0185] The computing task identifiers may be associated to an AF service identifier or a group identifier or a DNAI where the SMF is aware of the mapping of AF service identifier / group identifier / DNAI to one or more computing task identifiers or may be a new identifier(i.e. a new computing task identifier).

[0186] The at least one processor may be further configured to: select as the server, the first server, based at least in part on the one or more computing task identifiers.

[0187] The at least one processor may be further configured to select as the server, the first server, by causing the first network function to: transmit a second message to a third network function, wherein the second message comprises the one or more computing task identifiers; receive a third message from the third network function, wherein the third message comprises one or more addresses of one or more candidate servers within the CN, wherein the third message optionally comprises serving area information associated with the one or more candidate servers within the CN; and select as the server, the first server, based at least in part on the third message.

[0188] The first network function may determine servers in the CN that can support the one or more computing task identifiers in the serving area (i.e., the DNAI serving area and / or UE location area). This may be achieved by the first network function interfacing with an appropriate third network function in the CN that contains information related to the servers in the CN. The third network function may comprise a computing function, an NRF or a UPF, for example.

[0189] In an example, the third network function is a new computing function. The second message may be transmitted via a new SBI interface. In some examples, one or Docket No. SMM920250170-GR-NPmore computing functions may have registered their supported computing task identifiers and / or serving areas with a network repository function (NRF). Accordingly, the first network function may initially interface with the NRF to find the computing function(s) supporting the computing task identifiers within a serving area.

[0190] In another example, the third network function is a UPF. The second message may be transmitted via a new SBI interface. In some examples, one or more UPFs may have registered their supported computing task identifiers and / or serving areas with a NRF. Accordingly, the first network function may initially interface with the NRF to find the UPF supporting the computing task identifiers in a serving area.

[0191] In another example, the third network function may be the NRF itself.

[0192] The one or more addresses may comprise one or more IP addresses.

[0193] The at least one processor may be configured to cause the first network function to: receive, from the NEF, a first server deployment information of one or more application servers at the edge network for an application, wherein the first server deployment information comprises an information of a first serving area of the one or more application servers, wherein the one or more application servers are associated with the one or more computing task identifiers and wherein the application is associated with the application traffic; transmit the second message to the third network function, wherein the second message further comprises the information of the first serving area; and receive the third message from the third network function, wherein the one or more candidate servers are candidate servers associated with the first serving area.

[0194] The application may be a third-party application. The application may generate the application traffic.

[0195] The application servers of the edge network may be associated with respective serving area i.e., a DNAI.

[0196] The first server deployment information may comprise addresses of the application servers. The addresses may comprise IP addresses.Docket No. SMM920250170-GR-NP

[0197] The at least one processor may be further configured to cause the first network function to: generate, based at least on the one or more addresses, a second server deployment information of the one or more candidate servers; interface with each candidate server of the one or more candidate servers, based on the second server deployment information, to determine the one or more computing resources available to process the application task; and select, as the first server, the candidate server of the one or more candidate servers having the one or more computing resources available to process the application task.

[0198] The third network function may comprise: a computing function; a UPF; or a network repository function, NRF.

[0199] The computing function, UPF or NRF may contain computing resource information, wherein the computing resource information comprises the one or more s addresses and / or the serving area information.

[0200] The first network function may comprise a session management function, SMF.

[0201] The second network function may comprise a PCF.

[0202] The first message may comprise a policy and charging control, PCC, rule.

[0203] The at least one processor may be further configured to: select as the server, the first server based at least in part on a location of the UE.

[0204] A method performed or performable by a first network function is described herein. The method may comprise: receiving a first message from a second network function, wherein the first message comprises an indication that an application traffic of a UE can be routed to a server within a CN for an application task; determining to route the application traffic to the server within the CN based at least in part on the indication; selecting as the server, a first server for supporting the application task, wherein the first server comprises one or more computing resources available to process the application task; and routing the application traffic to the first server.

[0205] The method may further comprise: prior to routing the application traffic to the first server, routing the application traffic of the UE to an application server of an edgeDocket No. SMM920250170-GR-NPnetwork via a UPF; and then routing the application traffic to the first server by triggering a relocation, to the first server, of an application server instance of the application server of the edge network.

[0206] The method may further comprise: determining to route the application traffic to the server within the CN based at least in part on one or more delay conditions.

[0207] The one or more delay conditions may comprise: an N6 delay between the UPF and the application server at the edge network crossing an N6 delay threshold; an end-to-end delay between the UE and the application server at the edge network crossing an end-to-end delay threshold; a UE-to-UPF delay between the UE and the UPF crossing an UE-to-UPF delay threshold; a RAN congestion information; a UPF load condition; an AF requirement to immediately route the application traffic to the server; a low performance of an EAS; and a lack of an EAS address in a DNS response.

[0208] The first message may further comprise one or more computing task identifiers, wherein each computing task identifier indicates a respective computing task for the application traffic of the UE.

[0209] The method may further comprise receiving, from a NEF, the one or more computing task identifiers.

[0210] The method may further comprise: selecting as the server, the first server, based at least in part on the one or more computing task identifiers.

[0211] The selecting as the server, the first server, may comprise: transmitting a second message to a third network function , wherein the second message comprises the one or more computing task identifiers; receiving a third message from the third network function, wherein the third message comprises one or more addresses of one or more candidate servers within the CN, wherein the third message optionally comprises serving area information associated with the one or more candidate servers within the CN; and selecting as the server, the first server, based at least in part on the one or more addresses.

[0212] The method may comprise: receiving, from the NEF, a first server deployment information of one or more application servers at the edge network for an application,Docket No. SMM920250170-GR-NPwherein the first server deployment information comprises an information of a first serving area of the one or more application servers, wherein the one or more application servers are associated with the one or more computing task identifiers and wherein the application is associated with the application traffic; transmitting the second message to the third network function, wherein the second message further comprises the information of the first serving area; and receiving the third message from the third network function, wherein the one or more candidate servers are candidate servers associated with the first serving area.

[0213] The method may comprise: generating, based at least on the one or more addresses, a second server deployment information; interfacing with each candidate server of the one or more candidate servers, based on the second server deployment information, to determine the one or more computing resources available to process the application task; and selecting, as the first server, the candidate server of the one or more candidate servers having the one or more computing resources.

[0214] The selecting as the server, the first server, may be based at least in part on a location of the UE.

[0215] The third network function may comprise: a computing function; a UPF; or a NRF.

[0216] The first network function may comprise a SMF.

[0217] The second network function may comprise a PCF; and / or the first message may comprise a PCC rule.

[0218] As part of the 6G study in 3GPP one of the objectives is to allow the operator network to support computing services for a 3rd party application provider. The use case under consideration is the case where a 3rd party application provider has agreements with an operator to use the computing resources available in the operator network (i.e., within the CN). It is envisioned that instead of (or in addition of) placing application servers at the edge of the operator network premises (and usually out of operator scope), to allow the operator to offer its vast computing resources to support a computing / application task for an application. As such there is a requirement to support a procedure where the UE'sDocket No. SMM920250170-GR-NPapplication traffic that needs a computing service can be routed to a computing server within the operator CN premises.

[0219] To address the requirement, it is necessary to consider how a decision can be made to route traffic to a computing server within the operator network. It is expected that operators will charge more for performing the computing service on behalf of the application. Hence a proposed solution should allow the 3rd party to provide conditions relating to when the application traffic of a UE should be routed to a computing server within the operator network.

[0220] Furthermore, in addressing the requirement it is necessary to consider how a network function in the CN identifies which computing servers will be able to support the computing / application task required by an application. As such in a proposed solution, how the CN is aware of the computing services required by an application should be described.

[0221] In some examples of the solution described herein, it is proposed that as part of a 3rd party AF sending a traffic influence request to route traffic to an application server at the edge of the network, the 3rd party AF also includes a new indication that routing the application traffic of a UE to a computing server within the CN is also permitted.

[0222] Based on the new indication, an SMF in the CN may (based on corresponding policy rule from a PCF in the CN) find the available computing server(s) in the location of the UE that support the computing task and trigger relocation of the application traffic of the UE to the computing server in the CN. The triggering of the relocation may be based on some pre-conditions being met. For example, the preconditions may include an N6 delay between the UPF and the application server at the edge where the SMF triggers relocation only when the N6 delay exceeds a specific threshold provided by the 3rd party AF.

[0223] As part of the computing services there are already procedures available that can assist the SMF to determine when "edge" relocation is needed when some pre-condition are met, for example when N6 delay exceed a certain threshold the SMF can decide to route the application traffic of the UE from an application server with high N6 delay to an application server with a more optimal N6 delay. Whilst the existing procedure tends to be used to trigger relocation, what has not yet been established is how the SMF firstDocket No. SMM920250170-GR-NPdetermines that it is permitted to route traffic to a local computing server in the CN, and in addition, how the SMF selects a computing server in the CN that can perform the computing task of a UE application. The latter tends to require consideration of the computing resources available at the computing server and whether they are sufficient to perform the task with as little as possible computing delay.

[0224] The disclosure herein provides examples where an SMF decides to route application traffic of a UE from an application server at an edge network to a computing server in the CN.

[0225] The disclosure herein provided a method performed or performable by a first network function. The first network function may comprise an SMF. The method may comprise: routing a UE application traffic to an application server at the edge of a network via a local UPF based on a data network access identifier, DNAI, parameter received in a first PCC rule; deciding to route the UE application traffic to a local computing server within a CN based on a local computing indication received in the first PCC rule; identifying a computing server that can support the application computing requirements by sending a request to a third network function, the request consisting of an identifier indicating the computing requirement; selecting a computing server supporting the computing requirement of the application taking into account the location of the UE; and triggering relocation of the application server instance to the computing server instance.

[0226] The decision to route the UE application traffic to a local computing server within the CN may be based on receiving N6 delay measurements between the UPF and existing application server at the edge of the network.

[0227] As described herein, the SMF may decide to route UE application traffic to a "local" computing server instead of an application server at the edge of the network. The SMF may decide based on: a local compute indication received in a PCC rule; delay requirements from the AF.

[0228] As described herein, the SMF may identify the local computing server supporting the requirements of an application for computing, based on one or moreDocket No. SMM920250170-GR-NPcomputing task identifiers and then interfacing with another NF to find the computer servers supporting the computing task taking into account location of the UE.

[0229] The disclosure herein may ensure guaranteed application traffic end-to-end delay between a UE and computing servers within the CN.

[0230] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0231] The following abbreviations are relevant in the field addressed by this document: AF, Application Function; DNAI, Data Network Access Identifier; DNN, Data Network Name; DNS, Domain Name System; EASDF, Edge Application Server Discovery Function; FQDN, Fully Qualified Domain Name; NF, Network Function; NWDAF, Network Data Analytics Function; PDU, Packet Data Unit; PSA, PDU Session Anchor; UE, User Equipment; and UL / CL, Uplink Classifier.Docket No. SMM920250170-GR-NP

Claims

CLAIMSWhat is claimed is:

1. A first network function for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the first network function to:receive a first message from a second network function, wherein the first message comprises an indication that an application traffic of a user equipment, UE, can be routed to a server within a core network, CN, for an application task;determine to route the application traffic to the server within the CN based at least in part on the indication;select as the server, a first server for supporting the application task, wherein the first server comprises one or more computing resources available to process the application task; androute the application traffic to the first server.

2. The first network function of claim 1, wherein the at least one processor is further configured to cause the first network function to:prior to routing the application traffic to the first server, route the application traffic of the UE to an application server of an edge network via a user plane function, UPF; and thenroute the application traffic to the first server by triggering a relocation, to the first server, of an application server instance of the application server of the edge network.

3. The first network function of claim 2, wherein the at least one processor is further configured to cause the first network function to:determine to route the application traffic to the server within the CN based at least in part on one or more delay conditions.Docket No. SMM920250170-GR-NP4. The first network function of claim 3, wherein the one or more delay conditions comprise at least one ofan N6 delay between the UPF and the application server at the edge network crossing an N6 delay threshold;an end-to-end delay between the UE and the application server at the edge network crossing an end-to-end delay threshold;a UE-to-UPF delay between the UE and the UPF crossing an UE-to-UPF delay threshold;a radio access network, RAN, congestion information;a UPF load condition;an application function, AF, requirement to immediately route application traffic to the server;a low performance of an edge application server, EAS; anda lack of an EAS address in a domain name server, DNS, response.

5. The first network function of any one of claims 2-4, wherein:the first message further comprises one or more computing task identifiers, wherein each computing task identifier indicates a respective computing task for the application traffic of the UE; orthe at least one processor is further configured to cause the first network function to receive, from a network exposure function, NEF, the one or more computing task identifiers.

6. The first network function of claim 5, wherein the at least one processor is further configured to:select as the server, the first server, based at least in part on the one or more computing task identifiers.

7. The first network function of claim 6, wherein the at least one processor is further configured to select as the server, the first server, by causing the first network function to:Docket No. SMM920250170-GR-NPtransmit a second message to a third network function, wherein the second message comprises the one or more computing task identifiers;receive a third message from the third network function, wherein the third message comprises one or more addresses of one or more candidate servers within the CN, wherein the third message optionally comprises serving area information associated with the one or more candidate servers within the CN; andselect as the server, the first server, based at least in part on the third message.

8. The first network function of claim 7, wherein the at least one processor is configured to cause the first network function to:receive, from the NEF, a first server deployment information of one or more application servers at the edge network for an application, wherein the first server deployment information comprises an information of a first serving area of the one or more application servers, wherein the one or more application servers are associated with the one or more computing task identifiers and wherein the application is associated with the application traffic;transmit the second message to the third network function, wherein the second message further comprises the information of the first serving area; andreceive the third message from the third network function, wherein the one or more candidate servers are candidate servers associated with the first serving area.

9. The first network function of any one of claims 7-8, wherein the at least one processor is further configured to cause the first network function to:generate, based at least on the one or more addresses, a second server deployment information of the one or more candidate servers;interface with each candidate server of the one or more candidate servers, based on the second server deployment information, to determine the one or more computing resources available to process the application task; andselect, as the first server, the candidate server of the one or more candidate servers having the one or more computing resources available to process the application task.Docket No. SMM920250170-GR-NP10. The first network function of any one of claims 7-9, wherein the third network function comprises:a computing function;a UPF; ora network repository function, NRF.

11. The first network function of any one of the preceding claims, wherein the first network function comprises a session management function, SMF.

12. The first network function of any one of the preceding claims, wherein:the second network function comprises a policy control function, PCF; and / or the first message comprises a policy and charging control, PCC, rule.

13. The first network function of any one of the preceding claims, wherein the at least one processor is further configured to:select as the server, the first server, based at least in part on a location of the UE.

14. A method performed or performable by a first network function, the method comprising:receiving a first message from a second network function, wherein the first message comprises an indication that an application traffic of a UE can be routed to a server within a CN for an application task;determining to route the application traffic to the server within the CN based at least in part on the indication;selecting as the server, a first server for supporting the application task, wherein the first server comprises one or more computing resources available to process the application task; androuting the application traffic to the first server.

15. The method of claim 14, further comprising:Docket No. SMM920250170-GR-NPprior to routing the application traffic to the first server, routing the application traffic of the UE to an application server of an edge network via a UPF; and then routing the application traffic to the first server by triggering a relocation, to the first server, of an application server instance of the application server of the edge network.

16. The method of claim 15, further comprising:determining to route the application traffic to the server within the CN based at least in part on one or more delay conditions.

17. The method of claim 16, wherein the one or more delay conditions comprises: an N6 delay between the UPF and the application server at the edge network crossing an N6 delay threshold;an end-to-end delay between the UE and the application server at the edge network crossing an end-to-end delay threshold;a UE-to-UPF delay between the UE and the UPF crossing an UE-to-UPF delay threshold;a RAN congestion information;a UPF load condition;an AF requirement to immediately route the application traffic to the server;a low performance of an EAS; anda lack of an EAS address in a DNS response.

18. The method of any one of claims 15-17, wherein:the first message further comprises one or more computing task identifiers, wherein each computing task identifier indicates a respective computing task for the application traffic of the UE; orthe method further comprises receiving, from a NEF, the one or more computing task identifiers.

19. The method of claim 18, further comprising:Docket No. SMM920250170-GR-NPselecting as the server, the first server, based at least in part on the one or more computing task identifiers.

20. The method of claim 19, wherein the selecting as the server, the first server, comprises:transmitting a second message to a third network function , wherein the second message comprises the one or more computing task identifiers;receiving a third message from the third network function, wherein the third message comprises one or more addresses of one or more candidate servers within the CN, wherein the third message optionally comprises serving area information associated with the one or more candidate servers within the CN; andselecting as the server, the first server, based at least in part on the one or more addresses.Docket No. SMM920250170-GR-NP

Images