User equipment cache modification for edge computing

Abstract

Various aspects of the disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can store, in a domain name system (DNS) cache, DNS information associated with an edge application server at which an application context associated with an application client present on the UE is located. The UE can receive a first message associated with a handover of the UE or a second message associated with a transfer of the application context. The UE can modify the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message. Numerous other aspects are provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Greek Patent Application No. 20200100673, filed November 9, 2020, entitled “USER EQUIPMENT CACHE MODIFICATION FOR EDGE COMPUTING,” and assigned to the assignee hereof. The disclosure of the prior application is considered part of the disclosure of this patent application and is hereby incorporated by reference in its entirety into this patent application. TECHNICAL FIELD

[0003] Aspects of the disclosure relate generally to wireless communication, and to techniques and apparatus for user equipment (UE) cache modification for edge computing. BACKGROUND

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0005] A wireless network can include a number of base stations (BSs) that can support communication for a number of user equipment (UEs). A UE can communicate with a BS via the downlink and uplink. “Downlink” (or “forward link”) refers to the communication from the BS to the UE, and “uplink” (or “reverse link”) refers to the communication from the UE to the BS. As will be described in more detail herein, a BS can be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a new radio (NR) BS, a 5G Node B, and / or the like.

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. NR, which can also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP- OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. Further improvements to LTE and other radio access technologies can also be considered. SUMMARY

[0007] In some aspects, a method of wireless communication performed by a user equipment (UE) includes storing, in a domain name system (DNS) cache, DNS information associated with an edge application server at which an application context associated with an application client present on the UE is located; receiving a first message associated with a handover of the UE or a second message associated with a transfer of the application context; and modifying the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message.

[0008] In some aspects, a UE for wireless communication includes a memory and one or more processors operatively coupled to the memory, the memory and the one or more processors configured to: store, in a domain name system (DNS) cache, DNS information associated with an edge application server at which an application context associated with an application client present on the UE is located; receive a first message associated with a handover of the UE or a second message associated with a transfer of the application context; and modify the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message.

[0009] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: store, in a DNS cache, DNS information associated with an edge application server at which an application context associated with an application client present on the UE is located; receive a first message associated with a handover of the UE or a second message associated with a transfer of the application context; and modify the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message.

[0010] In some aspects, an apparatus for wireless communication includes means for storing, in a DNS cache, DNS information associated with an edge application server at which an application context associated with an application client present on the apparatus is located; means for receiving a first message associated with a handover of the apparatus or a second message associated with a transfer of the application context; and means for modifying the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message.

[0011] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.

[0012] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples can be readily utilized as bases or premises for the design of other structures for performing the same purposes thereof without departing from the scope of the appended claims. Such equivalent constructions are not to be regarded as a departure from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and their method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying drawings. Each of the figures is provided for the purpose of illustration and description, and is not intended as a limitation on the claims.

[0013] While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases can come about in many different arrangements and scenarios. Innovations described herein can be implemented across many differing platform types, devices, systems, form factors, and packaging arrangements. For example, embodiments and / or uses can come about via integrated chip embodiments, and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (Al)-enabled devices, etc.). While some examples can or can not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations can occur. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and can also span conventional, augmented, and artificial intelligence (Al) enabled implementations herewith. In some physical settings, devices incorporating described aspects and features can also necessarily include additional components and features not explicitly described herein but well known in the art of physical fabrication. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antennas, radio-frequency (RF)-chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is intended that innovations described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution. BRIEF DESCRIPTION OF DRAWINGS

[0014] So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, can be had by reference to various aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description can admit to other equally effective aspects. The same reference numerals in different drawings can identify the same or similar elements.

[0015] Figure 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0016] Figure 2 is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0017] Figure 3 is a diagram illustrating an example of edge computing, in accordance with the present disclosure.

[0018] Figure 4 is a schematic diagram illustrating an example associated with UE cache modification for edge computing according to the present disclosure.

[0019] Figure 5 is a schematic diagram illustrating an example process associated with UE cache modification for edge computing according to the present disclosure.

[0020] Figure 6 is a schematic diagram illustrating an example apparatus for wireless communication according to the present disclosure. DETAILED DESCRIPTION

[0021] Aspects of the disclosure are set forth below in the detailed description and in the appended claims. It should be understood that the aspects described below and illustrated in the drawings are not meant to be limiting. Other aspects can be apparent to those of ordinary skill in the art upon reading the present disclosure, which provides an enabling disclosure of the claimed subject matter. Numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it should be understood that the present disclosure can be practiced without these specific details. In other instances, well-known methods, procedures, components, and networks have not been described in detail so as not to unnecessarily obscure aspects of the present disclosure. Various aspects of the disclosure are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It can be evident, however, that the present disclosure can be practiced without these specific details. In other instances, well-known structures and functions have not been described in detail in order to avoid obscuring the present disclosure.

[0022] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0023] It should be noted that while aspects can be described herein using terminology commonly associated with a 5G or NR radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).

[0024] Figure 1is a schematic diagram illustrating an example of a wireless network 100 in accordance with the present disclosure. The wireless network 100 can be or include a 5G (NR) network and / or an LTE network, among other examples. The wireless network 100 can include a number of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 1 lOd) and other network entities. A base station (BS) is an entity that communicates with user equipment (UEs) and can also be referred to as an NR BS, a Node B, a gNB, a 5G node B (NB), an access point, a transmit receive point (TRP), and / or the like. Each BS can provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0025] BSs can be macro BSs, pico BSs, femto BSs, and / or other types of BSs. A macro BS can cover a relatively large geographic area (e.g., several kilometers in radius) and can allow restricted access by UEs having a subscription with the network provider. A pico BS can cover a relatively small geographic area and can allow restricted access by UEs having a subscription with the network provider. A femto BS can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UEs having a subscription with the network provider. A BS for a macro cell can be referred to as a macro BS. A BS for a pico cell can be referred to as a pico BS. A BS for a femto cell can be referred to as a femto BS or a home BS. In the example shown, a BS 110a can be a macro BS for a macro cell 102a, a BS 110b can be a pico BS for a pico cell 102b, and BSs 110c can be femto BSs for femto cells 102c. A BS can support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” can be used interchangeably herein. Figure 1 The BSs 110a, 110b, 110c, and / or 110d can communicate with one or more UEs 120 (shown as UE 120a, 120b, and 120c) using wireless communication resources in the frequency domain and the time domain. The BSs 110a, 110b, 110c, and / or 110d can communicate with each other using wired and / or wireless backhaul communication resources. The BSs 110a, 110b, 110c, and / or 110d can coordinate with each other using the backhaul communication resources to support communication with the UEs 120.

[0026] In some aspects, a cell can not necessarily be stationary, and the geographic area of the cell can move according to the location of a mobile BS. In some aspects, BSs can be interconnected to one another and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 using any suitable transport network, such as a direct physical connection, or a virtual network. In some aspects, the BSs 110a, 110b, 110c, and / or 110d can be implemented as a distributed BS comprising a centrally located macro BS to which a number of remote BSs are connected. In some aspects, the BSs 110a, 110b, 110c, and / or 110d can be implemented as a centralized BS comprising a plurality of remote units.

[0027] Wireless network 100 can also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station can also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown, relay BS 1 lOd can communicate with macro BS 110a and UE 120d in order to facilitate communication between BS 110a and UE 120d. A relay BS can also be referred to as a relay station, a relay base station, a relay, or the like.

[0028] Wireless network 100 can be a heterogeneous network that includes BSs of different types, such as macro BSs, pico BSs, femto BSs, relay BSs, or the like. These different types of BSs can have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100. For example, macro BSs can have a high transmit power level (e.g., 5 to 40 watts) whereas pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 to 2 watts).

[0029] A network controller can couple to a set of BSs and can provide coordination and control for these BSs. The network controller can communicate with the BSs via a backhaul. The BSs can also communicate with one another, e.g., directly or indirectly via a wireless or wireline backhaul.

[0030] UEs 120 (e.g., 120a, 120b, 120c) can be dispersed throughout wireless network 100, and each UE can be stationary or mobile. A UE can also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, etc. A UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet), an entertainment device (e.g., a music or video device or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

[0031] Some UEs can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC or eMTC UEs include, e.g., robots, drones, remote devices, sensors, meters, monitors, and / or location tags, that can communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node can provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet-of-Things (IoT) devices, and / or can implement NB-IoT (narrowband

[0032] In general, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a particular RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, an air interface, etc. A frequency can also be referred to as a carrier, a frequency channel, etc. Each frequency can support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0033] In some aspects, the UE 120 can communicate with an edge network device 130 of an edge network. The edge network device 130 can offload processing for the UE 120 and help the UE 120 save power and perform other functions. The UE 120 can communicate with the edge network device 130 via the BS 110 and a user plane function (UPF). The edge network device 130 can communicate with a core network or a cloud computing network.

[0034] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another). For example, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein. In this case, the communication links 125 can be configured to support

[0035] Devices of wireless network 100 can communicate using electromagnetic waves with frequencies as high as several hundred GHz. Such high frequencies can be in the form of electromagnetic radiation that can be difficult to contain due to the radiation’s ability to propagate freely through the air. To manage this propagation, wireless devices can use various containment techniques. For example, wireless devices can use enclosures, cases, or other housings to contain the radiation. In some cases, the enclosures, cases, or other housings can be designed to be as small as possible to reduce the size of the wireless devices. However, as the size of the enclosures, cases, or other housings decreases, the ability of the enclosures, cases, or other housings to contain the radiation can decrease.

[0036] As described above, Figure 1 are provided as examples. Other examples can differ from what is described with respect to at least one of the described examples. Figure 1 in reference to the description of the examples as provided herein.

[0037] Figure 2is a diagram illustrating an example 200 of a base station 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. Base stations 110 can be equipped with T antennas 234a through 234t, and UEs 120 can be equipped with R antennas 252a through 252r, where in general T > 1 and R > 1.

[0038] At base station 110, a transmit processor 220 can receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and can provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 can process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a through 232t can be transmitted via T antennas 234a through 234t, respectively.

[0039] At the UE 120, the antennas 252a-252r can receive the downlink signals from the base station 110 and / or other base stations and can provide received signals to the demodulators (DEMODs) 254a-254r, respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from all R demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The term “controller / processor” can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal receiving quality (RSRQ) parameter, and / or a CQI parameter, among other examples. In some aspects, one or more components of UE 120 can be included in a housing 284.

[0040] Antennas (e.g., antennas 234a-234t and / or antennas 252a-252r) can include or be included in one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays, among other examples. An antenna panel, antenna group, antenna element set, and / or antenna array can include one or more antenna elements. An antenna panel, antenna group, antenna element set, and / or antenna array can include a set of co-planar antenna elements and / or a set of non-co-planar antenna elements. An antenna panel, antenna group, antenna element set, and / or antenna array can include antenna elements within a single housing and / or antenna elements within multiple housings. An antenna panel, antenna group, antenna element set, and / or antenna array can include one or more antenna elements coupled to one or more transmit and / or receive components, such as Figure 2 one or more components of the UE 120.

[0041] On the uplink, at UE 120, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmit processor 264 can also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, a modulator and a demodulator (e.g., MOD / DEMOD 254) of the UE 120 can be included in a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver can include any combination of antennas 252, modulators and / or demodulators 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform any of the methods described herein (for example, as described with reference to Figures 4-5 FIGS. 15 and 16).

[0042] At base station 110, the uplink signals from UE 120 and other UEs can be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 can provide the decoded data to a data sink 239 and the decoded control information to controller / processor 240. Base station 110 can include communication unit 244 and can communicate with network controller via communication unit 244. Base station 110 can include scheduler 246 to schedule UEs 120 for downlink and / or uplink communications. In some aspects, a modulator and a demodulator (e.g., MOD / DEMOD 232) of the base station 110 can be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver can include any combination of antennas 234, modulators and / or demodulators 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver can be used by a processor (e.g., controller / processor 240) and memory 242 to perform any of the methods described herein (for example, as described with reference to Figures 4-5 FIGS. 15 and 16).

[0043] Edge network device 130 may include a communication unit 294, a controller / processor 290, and a memory 292. Edge network device 130 may use the communication unit 294, the controller / processor 290, and / or the memory 292 to perform aspects of any of the methods described herein, for example, as referenced... Figures 4-5 As described.

[0044] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, the controller / processor 290 of edge network device 130 and / or Figure 2 Any other components may perform one or more techniques associated with UE cache modification for edge computing, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, the controller / processor 290 of edge network device 130, and / or Figure 2 Any other component can perform or direct, for example Figure 5 The operation of process 500, and / or other processes as described herein. Memory 242, 282, and 292 may store data and program code for base station 110, UE 120, and edge network device 130, respectively. In some aspects, memory 242, memory 282, and / or memory 292 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110, UE 120, and / or edge network device 130 (e.g., directly or after compilation, translation, and / or interpretation), may cause one or more processors, base station 110, UE 120, and / or edge network device 130 to perform or direct, for example... Figure 5 The process 500, and / or other processes as described herein. In some aspects, execution instructions may include run instructions, translation instructions, compilation instructions, and / or interpretation instructions, as well as other examples.

[0045] In some aspects, the UE includes means for storing, in a domain name system (DNS) cache, DNS information associated with an edge application server at which an application context associated with an application client present on the UE is located; means for receiving a first message associated with a handover of the UE or a second message associated with a transfer of the application context; or means for modifying the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message. The means for the UE to perform operations described herein can include, for example, one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, or memory 282.

[0046] In some aspects, the UE includes means for performing a DNS-based edge application server discovery procedure to obtain DNS information associated with an edge application server.

[0047] In some aspects, the UE includes means for performing a DNS-based edge application server discovery procedure for a new edge application server at which an application context is located based at least in part on flushing the DNS cache.

[0048] In some aspects, the UE includes means for receiving an indication of whether the UE is to flush a DNS cache in response to receiving a message associated with a handover of the UE.

[0049] In some aspects, the UE includes means for performing an edge application server discovery procedure to obtain an address of a new edge application server at which an application context is located in response to receiving the second message.

[0050] In some aspects, the UE includes means for updating DNS information in the DNS cache using the address of the new edge application server.

[0051] Although Figure 2 The blocks in may be distinct components, but the functionality described above with reference to the blocks can be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with reference to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under the control of controller / processor 280.

[0052] As described above, Figure 2 are provided as examples. Other examples can differ from what is described with respect to the examples Figure 2 described with respect to the examples

[0053] Figure 3is a schematic diagram illustrating an example 300 of edge computing according to the present disclosure. Figure 3 A UE is illustrated with an (edge) application client that shares application data traffic with an edge application server of an edge network device (e.g., edge network device 130) in an edge data network. Figure 3 An edge enabler client of the UE is also illustrated that communicates with an edge enabler server and an edge configuration server of the edge network device. The components of the UE and the edge network device can be implemented by one or more devices.

[0054] The components of the UE and the edge network device can communicate via edge messages. For example, the edge enabler client and the edge enabler server can communicate via an EDGE-1 interface; the edge enabler server and the core network can communicate via an EDGE-2 interface; the edge enabler server and the edge application server can communicate via an EDGE-3 interface, the edge enabler client and the edge configuration server can communicate via an EDGE-4 interface; the application client and the edge enabler client can communicate via an EDGE-5 interface; the edge enabler server and the edge configuration server can communicate via an EDGE-6 interface; the edge application server and the core network can communicate via an EDGE-7 interface; and the edge configuration server and the core network can communicate via an EDGE-8 interface. In some aspects, the edge enabler client and the application client of the UE can communicate via a standardized application programming interface (API) to facilitate optimized edge computing services for the UE.

[0055] Edge computing uses small, distributed local data centers to provide resource-intensive computing platforms close to the originating devices. In edge computing, devices and / or application clients can offload computing requests to edge network devices. Moreover, edge computing provides low-latency access to high processing power and data federation (e.g., aggregation of data from multiple different systems). This can be useful, for example, for IoT applications, data processing applications, and / or multimedia applications, among other examples. Thus, edge computing can serve a wide range of devices with on-demand applications.

[0056] Edge computing brings network devices closer to UEs in order to supplement the capabilities of the UEs and enhance user services. Edge network devices, such as edge network device 130, can offload processing of the UEs and help the UEs save power and multitask. When a UE is using an application, an application context (e.g., a collection of information related to the application, such as information related to application data, application customizations, a current state of the application, etc.) is created, processing for the application (a point of computation) occurs in which, and the point of computation can be in an edge network device or on the UE. More specifically, an application context connected to an application can exist on an edge application server of an edge network device or an edge application client on a UE. The edge application client on the UE can execute the application supported by the application context. The application context can include application data and can include a current state of the application. For example, a user playing an online game can not want to lose a current state of the game, which can include a state of the user’s avatar, a location of the avatar, an inventory of the avatar, capabilities of the avatar, etc. If such characteristics of the avatar are not maintained during a mobility event of the UE or during a change in traffic conditions, the user can experience a game rendering error, or the application can completely fail. If the application is serving a business, the application can impact production or customer relations for the company.

[0057] An edge enabler server of an edge network device can handle operations of edge application servers, including deciding to establish and close edge application servers, and performing other policing functions. The edge enabler server can communicate with an edge configuration server, which can configure the edge enabler server and edge enabler clients. When an application changes a point of computation, an application context can need to be transferred to another edge enabler server. The edge enabler server can therefore determine whether an application context needs to be relocated to another edge enabler server.

[0058] A UE can maintain one or more DNS caches that map fully qualified domain names (FQDNs) to addresses (e.g., Internet Protocol (IP) addresses, such as IPv4 addresses or IPv6 addresses, among other examples). To populate the DNS cache, the UE can send a request to a DNS resolver to resolve a FQDN. The DNS resolver can respond to the UE with an address associated with the FQDN, and the UE can store the association between the FQDN and the address in the DNS cache.

[0059] In some examples, the UE can use the FQDN to reach edge computing resources of an edge application server at which an application context associated with an application client present on the UE is located. For example, the edge computing resources can be associated with a first edge application server, and a DNS cache of the UE can map the FQDN to an address associated with the first edge application server.

[0060] As described above, the application context can be relocated to a second edge application server, for example, due to mobility of the UE, load balancing, network errors, etc. Thus, after the relocation, the edge computing resources for the UE are reachable only at a new address associated with the second edge application server, and are not reachable at an old address associated with the first edge application server. However, since the DNS cache of the UE can take several seconds or several minutes to clear (e.g., according to a cache expiration time), edge computing requests sent by the UE to the old address can fail. In some cases, if the UE attempts to access resources at the old address, the first edge application server can return a redirect message indicating a new address for the resources, and the UE can update the DNS cache with the new address. However, this process is slow and consumes resources of the first edge application server that could otherwise be used for other edge computing requests.

[0061] Some techniques and apparatuses described herein enable efficient cache updates after relocation of an application context. In some aspects, a UE can store, in a DNS cache, an association between a FQDN of an edge application server at which an application context associated with an application client present on the UE is located and an address (e.g., an IP address). Thus, the UE can make a request for the FQDN of resources of the edge application server. In some aspects, the UE can determine an occurrence of an event (e.g., a handover of the UE) associated with a potential relocation of the application context, and can perform a DNS cache flush (e.g., with respect to the address of the edge application server) based at least in part on determining the occurrence of the event. Additionally or alternatively, the UE can receive an indication of a relocation of the application context, and the UE can perform a DNS cache flush or update (e.g., with respect to the address of the edge application server) based at least in part on receiving the indication. The UE can perform the operations described above and herein at an application level of the UE (e.g., using an edge enabler client of the UE) or at a system level of the UE.

[0062] Flushing the DNS cache can trigger the UE (e.g., at a subsequent request for the FQDN) to query the DNS server to obtain a new address for the new edge application server to which the application context was relocated. In this way, the UE can obtain updated DNS information with improved speed (e.g., relative to obtaining updated DNS information at expiration of the DNS cache) to facilitate edge computing with improved performance and minimal service interruption.

[0063] As described above, Figure 3 are provided by way of example. Other examples can differ from those described Figure 3 without departing from the scope of the disclosure.

[0064] Figure 4 is a schematic diagram illustrating an example 400 associated with UE cache modification for edge computing in accordance with the present disclosure. As shown in Figure 4 example 400 includes communications between a UE 120, first and second edge application servers 405-1, 405-2, and an information server 410 (such as a DNS server that provides DNS resolution). In some aspects, the edge application servers 405 can be implemented by one or more edge network devices (e.g., edge network devices 130). For example, the edge application servers 405 can be implemented by the same or different edge network devices. In some aspects, the UE 120 can communicate with the edge network devices and / or the information server 410 via one or more base stations 110. For example, the UE 120 and the one or more base stations 110 can be included in at least one wireless network, such as the wireless network 100. Here, the edge network devices can be located at the edge of the wireless network. For example, a first edge network device (e.g., implementing the edge application server 405-1) can be located at the site of a first base station 110, and a second edge network device (e.g., implementing the edge application server 405-2) can be located at the site of a second base station 110. As another example, one or more edge network devices (e.g., implementing the edge application servers 405) can be located at the site of the same base station 110.

[0065] As shown by reference number 415, the UE 120 can perform a discovery procedure (e.g., a DNS-based edge application server discovery procedure) to obtain information (e.g., an address) associated with a domain name (e.g., a FQDN). According to the discovery procedure, the UE 120 can transmit a request to the information server 410. The request can identify the domain name, and request information associated with the domain name. The information server 410 can transmit a response to the UE 120 that identifies the information associated with the domain name. For example, the response can indicate an address, such as an IP address, associated with the domain name.

[0066] The IP address can be associated with edge computing resources of the edge application server 405-1. The edge computing resources can be allocated to the UE 120 for use in conjunction with an application client that is present (e.g., executing) on the UE 120. Thus, an application context associated with the application client can be located at the edge application server 405-1.

[0067] As shown by reference number 420, the UE 120 can store the information provided by the information server 410 in a cache (e.g., a data structure). For example, the UE 120 can store DNS information (e.g., DNS records) in a DNS cache. The DNS information can include domain names (e.g., of DNS requests sent by the UE 120) and IP addresses (e.g., of DNS responses received by the UE 120), and the DNS information can indicate associations between the domain names and the IP addresses. Thus, as shown by reference number 425, a request made by the UE 120 for a domain name can be directed to an IP address associated with the edge application server 405-1 based at least in part on information stored in the DNS cache.

[0068] In some aspects, the UE 120 can store information (e.g., DNS information) in a cache (e.g., a DNS cache) associated with an application client. Additionally, or alternatively, the UE 120 can store information (e.g., DNS information) in a cache (e.g., a DNS cache) associated with a high-level operating system (HLOS) that is present (e.g., executing) on the UE 120. For example, the UE 120 can execute the HLOS on hardware of the UE 120, such as a microcontroller and / or a modem, among other examples. The information stored by the UE 120 in the cache can be associated with an expiration time, after which the UE 120 flushes (e.g., purges) the information from the cache. In some aspects, the expiration time associated with records in the application client cache can be from 60 seconds to 120 seconds, and the expiration time associated with records in the HLOS cache can be from 2 seconds to 2 hours.

[0069] As shown by reference number 430, the UE 120 can determine that the UE 120 is to modify (e.g., flush or update) the information in the cache. In some aspects, the UE 120 (e.g., an edge enabler client of the UE 120) can determine to modify the information in the cache based at least in part on receiving a particular message sent by a base station 110.

[0070] In some aspects, the UE 120 (e.g., an edge enabler client of the UE 120) can detect a handover event of the UE 120. For example, the UE 120 (e.g., an edge enabler client of the UE 120) can receive a message (e.g., from a base station 110) associated with a handover event of the UE 120. The handover event can be associated with a handover of the UE 120 from a first base station 110 to a second base station 110 (e.g., due to movement of the UE 120). The handover event can be associated with a change to an address (e.g., an IP address) associated with the UE 120 and a change to an address (e.g., an IP address) associated with a domain name (e.g., due to transfer of the application context from edge application server 405-1 to edge application server 405-2).

[0071] The UE 120 can determine, based at least in part on the message, a likelihood of a relocation of the application context to the new edge application server 405-2 (e.g., the UE 120 can infer that the application context is being relocated based at least in part on detecting the handover event). In some aspects, the message can be a protocol data unit (PDU) session modification command message, e.g., including a 5G session management cause field indicating a “re-activation requested” cause (e.g., for session and service continuity (SSC) mode 3 when relocation is required). Additionally or alternatively, the message can be a PDU session release command message, e.g., including a 5G session management cause field indicating a “re-activation requested” cause (e.g., for SSC mode 2 when relocation is required). In some aspects, the UE 120 (e.g., an edge enabler client of the UE 120) can detect the handover event by monitoring attention (AT) commands at a modem of the UE 120 (e.g., which can include an indication of the handover event).

[0072] In some aspects, the UE 120 can receive a message associated with a transfer of the application context. For example, an edge enabler client of the UE 120 can receive a message from an edge enabler server (e.g., via an EDGE-1 interface) indicating a transfer of the application context. The application context transfer event can be associated with a change to an address associated with a domain name (e.g., due to transfer of the application context from edge application server 405-1 to edge application server 405-2). Accordingly, the UE 120 can determine, based at least in part on the message, a relocation of the application context to the new edge application server 405-2. In some aspects, the message can be an edge application server application context transfer message.

[0073] The new edge application server 405-2 to which the application context is transferred and the old edge application server 405-1 from which the application context is transferred can be implemented by the same or different edge network devices. For example, in a handover event, the old edge application server 405-1 can be implemented by a first edge network device associated with the first base station 110 and the new edge application server 405-2 can be implemented by a second edge network device associated with the second base station 110. As another example, if the application context transfer is due to a network error (such as a server error), the old edge application server 405-1 and the new edge application server 405-2 can be associated with the same edge network device or different edge network devices associated with the same base station 110. The old edge application server 405-1 and the new edge application server 405-2 can be associated with different information. For example, the old edge application server 405-1 and the new edge application server 405-2 can be associated with different IP addresses.

[0074] As shown by reference number 435, the UE 120 (e.g., the edge enabler client of the UE 120) can modify the cache (e.g., the application client cache and / or the HLOS cache) based at least in part on receiving the message associated with the handover event and / or the message associated with the transfer of the application context. In some aspects, the UE 120 (e.g., the edge enabler client of the UE 120) can modify the cache by flushing (e.g., clearing) the cache. For example, the UE 120 can flush the application client cache and / or the HLOS cache. As an example, the edge enabler client of the UE 120 can flush the application client cache via the EDGE-5 interface with the application client and can flush the HLOS cache.

[0075] In some aspects, the UE 120 can flush the entire cache such that all records are cleared from the cache. In some other aspects, the UE 120 can flush only the information (e.g., DNS information) associated with the old edge application server 405-1 in which the application context was originally located from the cache. The level of granularity with which the UE 120 is to flush the cache can be configured for the UE 120 (e.g., by the base station 110) and / or indicated by the information server 410, as described below.

[0076] In some aspects, the UE 120 can selectively flush a cache (e.g., an application client cache and / or an HLOS cache) based at least in part on an indication of whether the UE 120 is to flush the cache in response to receiving a message associated with a handover event. The UE 120 can receive the indication from the information server 410 and / or a core network (e.g., a device implementing a session management function (SMF) of the core network) via the base station 110. In some aspects, the information server 410 (e.g., a local DNS resolver) can provide the indication of whether the UE 120 is to flush the cache at handover. The information server 410 can provide the indication with a response (e.g., a DNS response) sent by the information server 410, as described above. Thus, the indication can be specific to information (e.g., DNS information) provided with the response. Additionally, or alternatively, the core network (e.g., the SMF) can provide the indication of whether the UE 120 is to flush the cache at handover (e.g., via the base station 110). Here, the indication can be based at least in part on a mobility capability of the UE 120. For example, if the UE 120 is capable of mobility, the indication can indicate that the UE 120 is to flush the cache at handover.

[0077] In some aspects, the UE 120 (e.g., an edge enabler client of the UE 120) can modify the cache by updating the cache. For example, the UE 120 can update an application client cache and / or an HLOS cache. As an example, the edge enabler client of the UE 120 can update the application client cache or the HLOS cache by providing (e.g., via a message) new information (e.g., a domain name and a new IP address) associated with the new edge application server 405-2 to the application client or the HLOS. In some aspects, the UE 120 (e.g., an edge enabler client of the UE 120) can perform an edge application server discovery procedure in response to receiving a message associated with a transfer of an application context. The UE 120 can obtain the new information (e.g., the new IP address) associated with the new edge application server 405-2 by performing the edge application server discovery procedure. The edge application server discovery procedure can include a non-DNS based discovery procedure of an edge application server performed between the edge enabler client of the UE 120, an edge configuration server, and one or more edge enabler servers.

[0078] If the UE 120 flushes the cache, as shown by reference number 440, the UE 120 can perform another discovery procedure (e.g., another DNS-based edge application server discovery procedure) to obtain new information associated with the domain name (e.g., FQDN), as described above with respect to reference number 415. For example, the UE 120 can send a request to the information server 410, and receive a response that identifies new information (such as an IP address) associated with the domain name. Here, the new information can be associated with a new edge application server 405-2 to which the application context was relocated. The UE 120 can store the new information in the cache (e.g., DNS cache), as described above. Thus, as shown by reference number 445, requests made by the UE 120 for the domain name can be directed to the new IP address associated with the new edge application server 405-2 based at least in part on the new information stored in the DNS cache.

[0079] In this way, traffic for the application client can be routed to the new IP address associated with the new edge application server 405-2 with reduced latency relative to flushing the cache at the expiration time. Thus, the UE 120 can use edge computing resources with improved responsiveness to changes at the network edge, thereby avoiding degraded performance or service interruption for several seconds or minutes. Moreover, the techniques and apparatuses described herein can enable optimized termination of edge application servers from which an application context is relocated. For example, according to the techniques and apparatuses described herein, traffic can be stopped relatively faster to such old edge application servers, thereby allowing faster termination of edge application servers and efficient release of associated edge computing resources.

[0080] As described above, Figure 4 are provided as examples. Other examples can differ from what is described Figure 4 with respect to the examples described with reference to

[0081] Figure 5 FIG. 5 is a schematic illustration of an example process 500 that can be performed, for example, by a UE, in accordance with the present disclosure. The example process 500 is an example of operations performed by a UE (e.g., UE 120) associated with UE cache modification for edge computing.

[0082] As Figure 5 shown in FIG. 5, in some aspects, the process 500 can include storing, in a DNS cache, DNS information associated with an edge application server at which an application context associated with an application client present on the UE is located (block 510). For example, the UE (e.g., using the DNS cache 215) can store the DNS information in the DNS cache 215, as described above. Figure 6The DNS cache (e.g., the cache component 608 as depicted in FIG. 6) can store DNS information associated with the edge application server at which the application context associated with the application client present on the UE is located in a DNS cache, as described supra.

[0083] As Figure 5 As further shown in FIG. 5, in some aspects, process 500 can include receiving a first message associated with a handover of the UE or a second message associated with a transfer of the application context (block 520). For example, the UE (e.g., using the receiving component 602 as depicted in FIG. 6) can receive a first message associated with a handover of the UE or a second message associated with a transfer of the application context, as described supra. Figure 6 The receiving component 602 as depicted in FIG. 6 can receive a first message associated with a handover of the UE or a second message associated with a transfer of the application context, as described supra.

[0084] As Figure 5 As further shown in FIG. 5, in some aspects, process 500 can include modifying the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message (block 530). For example, the UE (e.g., using the cache component 608 as depicted in FIG. 6) can modify the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message, as described supra. Figure 6 The cache component 608 as depicted in FIG. 6 can modify the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message, as described supra.

[0085] Process 500 can include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0086] In a first aspect, process 500 includes performing a DNS-based edge application server discovery procedure to obtain DNS information associated with an edge application server.

[0087] In a second aspect, alone or in combination with the first aspect, process 500 includes performing a DNS-based edge application server discovery procedure for a new edge application server at which the application context is located based at least in part on flushing the DNS cache.

[0088] In a third aspect, alone or in combination with one or more of the first and second aspects, the DNS information includes at least one of a fully qualified domain name and an address associated with the edge application server.

[0089] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first message is a PDU session modification command message identifying a reactivation request cause or a PDU session release command message identifying a reactivation request cause.

[0090] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the second message is an edge application server application context transfer message.

[0091] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the DNS cache is at least one of a first DNS cache associated with the application client or a second DNS cache associated with an advanced operating system present on the UE.

[0092] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the process 500 includes receiving an indication of whether the DNS cache is to be refreshed in response to receiving a message associated with a handover of the UE.

[0093] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the process 500 includes performing an edge application server discovery procedure to obtain an address of a new edge application server at which the application context is located in response to receiving the second message.

[0094] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, modifying the DNS cache includes updating DNS information in the DNS cache using the address of the new edge application server.

[0095] Although Figure 5 An example block of the process 500 is shown, but in some aspects, the process 500 can include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 5 In conjunction with the described examples, an element, or any portion thereof, can be implemented with a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), processors of

[0096] Figure 6 FIG. 6 is a diagram illustrating an example apparatus 600 for wireless communication in accordance with aspects of the present disclosure. The apparatus 600 can be a UE, or a UE can include the apparatus 600. In some aspects, the apparatus 600 includes a reception component 602 and a transmission component 604, which can be in communication with one another (for example, via one or more buses and / or one or more other components). As shown, the apparatus 600 can communicate with another apparatus 606 (such as a UE, a base station, or another wireless communication device) using the reception component 602 and the transmission component 604. As further shown, the apparatus 600 can include one or more of a cache component 608 or a discovery component 610, among other examples.

[0097] In some aspects, the apparatus 600 can be configured to perform the operations described herein with regard to the method 500. Figure 4The described one or more operations. Alternatively or additionally, the apparatus 600 may be configured to perform one or more processes described herein, such as Figure 5 The process 500 or a combination thereof. In some aspects, the device 600 and / or Figure 6 One or more components shown may include the above-mentioned components. Figure 2 One or more components of the described UE. Alternatively or alternatively, Figure 6 One or more components shown can be combined with the above. Figure 2 Implemented within one or more of the described components. Alternatively or additionally, one or more of the components in a set may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0098] Receiver 602 may receive communications from device 606, such as reference signals, control information, data communications, or combinations thereof. Receiver 602 may provide the received communications to one or more other components of device 600. In some aspects, receiver 602 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signals to one or more other components of device 600. In some aspects, receiver 602 may include the combinations described above. Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0099] Transmitting component 604 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 606. In some aspects, one or more other components of device 600 can generate communications and provide the generated communications to transmitting component 604 for transmission to device 606. In some aspects, transmitting component 604 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples) on the generated communications and can transmit the processed signals to device 606. In some aspects, transmitting component 604 can include the combinations described above. Figure 2 The described UE includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 604 may be co-located with the receive component 602 in a transceiver.

[0100] The cache component 608 can store, in a DNS cache, DNS information associated with edge application servers at which application contexts associated with application clients present on the UE are located. In some aspects, the cache component 608 can include the memory, controller / processor, or combination thereof described above in connection with the UE. Figure 2 The described controller / processor, memory, or combination thereof of the UE. The reception component 602 can receive a first message associated with a handover of the UE or a second message associated with a transfer of an application context. The cache component 608 can modify the DNS cache by updating DNS information or flushing DNS information based at least in part on receiving the first message or the second message.

[0101] The discovery component 610 can perform a DNS-based edge application server discovery procedure to obtain DNS information associated with an edge application server. The discovery component 610 can perform a DNS-based edge application server discovery procedure for a new edge application server at which an application context is located based at least in part on flushing the DNS cache. In some aspects, the discovery component 610 can include the one or more antennas, modulators, transmit MIMO processor, transmit processor, demodulators, MIMO detector, receive processor, controller / processor, memory, or combination thereof described above in connection with the UE. Figure 2 The described one or more antennas, modulators, transmit MIMO processor, transmit processor, demodulators, MIMO detector, receive processor, controller / processor, memory, or combination thereof of the UE.

[0102] The reception component 602 can receive an indication of whether the DNS cache is to be flushed in response to receiving a message associated with a handover of the UE.

[0103] The discovery component 610 can perform an edge application server discovery procedure to obtain an address of a new edge application server at which an application context is located in response to receiving the second message.

[0104] Figure 6 The number and arrangement of components shown in FIG. 10 are provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 10. Additionally, or alternatively, Figure 6 components shown in FIG. 10 can be implemented within a single component, or Figure 6 two or more components shown in FIG. 10 can be implemented within a single component, Figure 6 a single component shown in FIG. 10 can be implemented as multiple, distributed components. Additionally or alternatively, Figure 6 a set of components (e.g., one or more components) shown in FIG. 10 can perform one or more functions described as being performed by another set of components shown in FIG. 10. Figure 6

[0105] An overview of some aspects of the disclosure is provided below.

[0106] ​Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: storing, in a domain name system (DNS) cache, DNS information associated with an edge application server at which an application context associated with an application client present on the UE is located; receiving a first message associated with a handover of the UE or a second message associated with a transfer of the application context; and modifying the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message.

[0107] Aspect 2: The method of aspect 1, further comprising: performing a DNS-based edge application server discovery procedure to obtain the DNS information associated with the edge application server.

[0108] Aspect 3: The method of any of aspects 1-2, further comprising: performing a DNS-based edge application server discovery procedure for a new edge application server at which the application context is located based at least in part on flushing the DNS cache.

[0109] Aspect 4: The method of any of aspects 1-4, wherein the DNS information comprises at least one of a fully qualified domain name or an address associated with the edge application server.

[0110] Aspect 5: The method of any of aspects 1-4, wherein the first message is a protocol data unit (PDU) session modification command message that identifies a reactivation request cause or a PDU session release command message that identifies a reactivation request cause.

[0111] Aspect 6: The method of any of aspects 1-5, wherein the second message is an edge application server application context transfer message.

[0112] Aspect 7: The method of any of aspects 1-6, wherein the DNS cache is at least one of a first DNS cache associated with the application client or a second DNS cache associated with a high level operating system present on the UE.

[0113] Aspect 8: The method of any of aspects 1-7, further comprising: receiving an indication of whether the DNS cache is to be flushed by the UE in response to receiving the message associated with the handover of the UE.

[0114] Aspect 9: The method of any of aspects 1-8, further comprising: performing an edge application server discovery procedure to obtain an address of a new edge application server at which the application context is located in response to receiving the second message.

[0115] Aspect 10: The method of aspect 9, wherein modifying the DNS cache comprises updating DNS information in the DNS cache using the address of the new edge application server.

[0116] Aspect 11: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-10.

[0117] Aspect 12: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-10.

[0118] Aspect 13: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-10.

[0119] Aspect 14: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-10.

[0120] Aspect 15: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-10.

[0121] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be possible based on the above disclosure or from practice of the aspects.

[0122] As used herein, the term “component” is intended to be broadly interpreted to include hardware, and / or a combination of hardware and software. “Software” shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a processor is implemented in hardware and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein can be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and

[0123] As used herein, depending on the context, satisfying a threshold can refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and / or the like.

[0124] Although specific combinations of features are set forth in the claims and / or disclosed herein, those combinations are not intended to limit the disclosure of various aspects. To the contrary, numerous combinations of features can be assumed by one of ordinary skill in the art. Although each dependent claim listed below directly depends on only one claim, the disclosure of each dependent claim can be combined with each other dependent claim and the independent claims. As used herein, a phrase referring to “at least one of’ a list of items means any combination of those items (including single members). As an example, “at least one of a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any of the possible multiples of the

[0125] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and can be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items, and can be used interchangeably with “the one or more.” Also, as used herein, the terms “set” and “group” are intended to include one or more items (for example, related items, unrelated items, or a combination of related and unrelated items), and can be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or “comprise,” and variations thereof, are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series of items (for example, “a, b, or c” or “a, b, and c”) unless explicitly stated otherwise (for example, when used in either “only one of’ or “...the other of’).

Claims

1. A user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to, individually or in any combination: store, in a domain name system (DNS) cache, DNS information associated with an edge application server at which an application context associated with an application client present on the UE is located to be relocated, the DNS information comprising a fully qualified domain name associated with the edge application server; receive: a first message associated with a handover of the UE from a first network device to a second network device, a transfer of the application context from the edge application server to a new edge application server associated with the handover, and a change of an internet protocol (IP) address associated with the fully qualified domain name due to the transfer of the application context, or a second message associated with the transfer of the application context from the edge application server to a new edge application server and the change of the IP address associated with the fully qualified domain name due to the transfer of the application context; and modify the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message. the one or more processors are further configured to:

2. The UE of claim 1, wherein, perform a DNS-based edge application server discovery procedure to obtain the DNS information associated with the edge application server. the one or more processors are further configured to:

3. The UE of claim 1, wherein, perform a DNS-based edge application server discovery procedure for the new edge application server at which the application context is located based at least in part on flushing the DNS cache. the DNS information further comprises an address associated with the edge application server.

4. The UE of claim 1, wherein, the first message is a protocol data unit (PDU) session modification command message identifying a reactivation request cause or a PDU session release command message identifying a reactivation request cause.

5. The UE of claim 1, wherein, the second message is an edge application server application context transfer message.

6. The UE of claim 1, wherein, the DNS cache is at least one of a first DNS cache associated with the application client or a second DNS cache associated with an advanced operating system present on the UE.

7. The UE of claim 1, wherein, the one or more processors are further configured to:

8. The UE of claim 1, wherein, receive an indication of whether the DNS cache is to be flushed by the UE in response to receiving a message associated with the handover of the UE. the one or more processors are further configured to:

9. The UE of claim 1, wherein, perform an edge application server discovery procedure to obtain an address of the new edge application server at which the application context is located in response to receiving the second message. the one or more processors, when modifying the DNS cache, are configured to:

10. The UE of claim 9, wherein, update the DNS information in the DNS cache using the address of the new edge application server.

11. A method of wireless communication performed by a user equipment (UE), comprising: ​ storing, in a domain name system (DNS) cache, DNS information associated with an edge application server at which an application context associated with an application client present on the UE is located that is to be relocated, the DNS information comprising a fully qualified domain name associated with the edge application server; receiving each of: a first message associated with a handover of the UE from a first network device to a second network device, a transfer of the application context from the edge application server to a new edge application server associated with the handover, and a change of an internet protocol (IP) address associated with the fully qualified domain name due to the transfer of the application context, or a second message associated with the transfer of the application context from the edge application server to a new edge application server and the change of the IP address associated with the fully qualified domain name due to the transfer of the application context; and based at least in part on receiving the first message or the second message, modifying the DNS cache by updating the DNS information or flushing the DNS information.

12. The method of claim 11, further comprising: performing a DNS-based edge application server discovery procedure to obtain the DNS information associated with the edge application server.

13. The method of claim 11, further comprising: performing a DNS-based edge application server discovery procedure for the new edge application server at which the application context is located based at least in part on flushing the DNS cache.

14. The method of claim 11, wherein, the DNS information further comprises an address associated with the edge application server.

15. The method of claim 11, wherein, the first message is a protocol data unit (PDU) session modification command message identifying a reactivation request cause or a PDU session release command message identifying a reactivation request cause.

16. The method of claim 11, wherein, the second message is an edge application server application context transfer message.

17. The method of claim 11, wherein, the DNS cache is at least one of a first DNS cache associated with the application client or a second DNS cache associated with an advanced operating system present on the UE.

18. The method of claim 11, further comprising: receiving an indication of whether the UE is to flush the DNS cache in response to receiving a message associated with the handover of the UE.

19. The method of claim 11, further comprising: performing an edge application server discovery procedure to obtain an address of the new edge application server at which the application context is located in response to receiving the second message.

20. The method of claim 19, wherein, modifying the DNS cache comprises: updating the DNS information in the DNS cache using the address of the new edge application server.

21. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: storing, in a domain name system (DNS) cache, DNS information associated with an edge application server at which an application context associated with an application client present on the UE is located that is to be relocated, the DNS information comprising a fully qualified domain name associated with the edge application server; receiving: a first message associated with a handover of the UE from a first network device to a second network device, a transfer of the application context from the edge application server to a new edge application server associated with the handover, and a change of an internet protocol (IP) address associated with the fully qualified domain name due to the transfer of the application context, or a second message associated with the transfer of the application context from the edge application server to a new edge application server and the change of the IP address associated with the fully qualified domain name due to the transfer of the application context; and based at least in part on receiving the first message or the second message, modifying the DNS cache by updating the DNS information or flushing the DNS information.

22. The non-transitory computer-readable medium of claim 21, wherein, The one or more instructions further cause the UE to: perform a DNS-based edge application server discovery procedure to obtain the DNS information associated with the edge application server.

23. The non-transitory computer-readable medium of claim 21, wherein, The one or more instructions further cause the UE to: perform a DNS-based edge application server discovery procedure for the new edge application server at which the application context is located based at least in part on flushing the DNS cache.

24. The non-transitory computer-readable medium of claim 21, wherein, The first message is a protocol data unit (PDU) session modification command message identifying a reactivation request cause or a PDU session release command message identifying a reactivation request cause.

25. The non-transitory computer-readable medium of claim 21, wherein, The DNS cache is at least one of a first DNS cache associated with the application client or a second DNS cache associated with an advanced operating system present on the UE.

26. An apparatus for wireless communication, comprising: means for storing, in a domain name system (DNS) cache, DNS information associated with an edge application server at which an application context associated with an application client present on the apparatus is located that is to be relocated, the DNS information comprising a fully qualified domain name associated with the edge application server; means for receiving: a first message associated with a handover of the apparatus from a first network device to a second network device, a transfer of the application context from the edge application server to a new edge application server associated with the handover, and a change of an internet protocol (IP) address associated with the fully qualified domain name due to the transfer of the application context, or a second message associated with the transfer of the application context from the edge application server to a new edge application server and the change of the IP address associated with the fully qualified domain name due to the transfer of the application context; and means for modifying the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message. means for modifying the DNS cache by updating the DNS information or flushing the DNS information based at least in part on receiving the first message or the second message.

27. The apparatus of claim 26, further comprising: means for performing a DNS-based edge application server discovery procedure to obtain the DNS information associated with the edge application server.

28. The apparatus of claim 26, further comprising: means for performing a DNS-based edge application server discovery procedure for the new edge application server at which the application context is located based at least in part on flushing the DNS cache.

29. The apparatus of claim 26, wherein, the first message is a protocol data unit (PDU) session modification command message identifying a reactivation request cause or a PDU session release command message identifying a reactivation request cause.

30. The apparatus of claim 26, wherein, the DNS cache is at least one of a first DNS cache associated with the application client or a second DNS cache associated with an advanced operating system present on the apparatus.

Images