Method and system for edge application server management based on application client or user equipment status

Abstract

A user equipment may be configured to implement a procedure for managing an edge application server based on an application client (AC) state and / or a user equipment (UE) state. In some aspects, a network entity may establish a subscription to event information of a user equipment (UE) or an application client executing on the UE associated with an edge application server instance executing within an edge data network. Further, the network entity may receive a notification of a context event for the application client and / or the UE based on the subscription, and cause release, pause, or recovery of the edge application server instance in response to the notification.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 202241046446, filed on August 16, 2022, entitled “Methods and Systems for edge application server management based on application client or User equipment state,” which is expressly incorporated herein by reference in its entirety. Background Art Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to implementing procedures for managing edge application servers based on application client (AC) status and / or user equipment (UE) status.

[0004] introduction

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5GNR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability, such as with the Internet of Things (IoT), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Summary of the invention

[0007] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0008] In some aspects, the technology described herein relates to an edge computing device comprising: a memory storing computer-executable instructions; and at least one processor coupled to the memory and configured to execute the computer-executable instructions to: establish a subscription to event information of a user equipment (UE) or an application client executed on the UE, the application client being associated with an edge application server instance executed within an edge data network; receive notifications of contextual events of the application client and / or the UE based on the subscription; and cause release, suspension, or resumption of the edge application server instance in response to the notification.

[0009] In some aspects, the technology described herein relates to a method for wireless communication, the method comprising: establishing a subscription to event information of a user equipment (UE) or an application client executed on the UE, the application client being associated with an edge application server instance executed within an edge data network; receiving notification of contextual events of the application client and / or the UE based on the subscription; and causing the release, suspension, or resumption of the edge application server instance in response to the notification. In addition, the present disclosure also provides an apparatus comprising a component for performing the above method.

[0010] In some aspects, the technology described herein relates to a non-transitory computer-readable medium having instructions thereon, which, when executed by at least one computing device, cause the at least one computing device to perform operations including: establishing a subscription to event information of a user equipment (UE) or an application client executed on the UE, the application client being associated with an edge application server instance executing within an edge data network; receiving notifications of contextual events of the application client and / or the UE based on the subscription; and causing release, suspension, or resumption of the edge application server instance in response to the notification.

[0011] To achieve the foregoing and related purposes, one or more aspects include features fully described below and specifically pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of the one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a diagram illustrating an example of a wireless communication system and access network according to some aspects of the present disclosure.

[0013] Figure 2A is a diagram illustrating an example of a first 5G / NR frame according to some aspects of the present disclosure.

[0014] Figure 2B is a diagram illustrating an example of DL channels within a 5G / NR subframe according to some aspects of the present disclosure.

[0015] Figure 2C is a diagram illustrating an example of a second 5G / NR frame according to some aspects of the present disclosure.

[0016] Figure 2D is a diagram illustrating an example of UL channels within a 5G / NR subframe according to some aspects of the present disclosure.

[0017] Figure 3 is a diagram illustrating an example of a base station and a UE in an access network according to some aspects of the present disclosure.

[0018] Figure 4 is a diagram illustrating an example decomposed base station architecture according to some aspects of the present disclosure.

[0019] Figure 5 is a diagram illustrating an example of communications of network entities and devices according to some aspects of the present disclosure.

[0020] Figure 6 is a diagram illustrating an example of a hardware implementation for user equipment employing a processing system according to some aspects of the present disclosure.

[0021] Figure 7 is a schematic block diagram of example components of a computing device according to some aspects of the present disclosure, according to some aspects of the present disclosure, and according to various aspects of the present disclosure.

[0022] Figure 8 is a flow chart of a first example method of managing an edge application server based on application client state and / or UE state according to some aspects of the present disclosure.

[0023] Fig. 9 is a flow chart of a second example method of managing an edge application server based on application client state and / or UE state according to some aspects of the present disclosure.

[0024] Fig.10 is a flow chart of a third example method of managing an edge application server based on application client state and / or UE state according to some aspects of the present disclosure.

[0025] Fig.11 is a flow chart of a fourth example method of managing an edge application server based on application client state and / or UE state according to some aspects of the present disclosure. DETAILED DESCRIPTION

[0026] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations with which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it will be apparent to one of ordinary skill in the art that these concepts may be practiced without these specific details. In some instances, structures and components are shown in block diagram form in order to avoid diluting such concepts.

[0027] 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, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0028] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description languages, or other terms.

[0029] Accordingly, in one or more examples, the described functions may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media, which may be referred to as non-transitory computer-readable media. Non-transitory computer-readable media may not include transient signals. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0030] Various specific implementations as a whole relate to a procedure for managing edge application servers based on AC state and / or UE state. Edge computing is a network architecture concept that implements cloud computing capabilities and service environments that are deployed near UEs. Compared with cloud environments, edge computing provides several benefits, such as lower latency, higher bandwidth, reduced backhaul traffic, and prospects for new services. In some aspects, an AC executed on a UE (e.g., a game application client) can employ an edge application server (EAS) instance created in a cloud computing environment using deployed resources. For example, an application client can connect to an edge application server instance to utilize the services of an application with the benefits of edge computing, such as pre-fetching, caching, processing, or services of data. However, in some aspects, if the AC goes into sleep or the UE goes into an idle state, the EAS instance will remain active / instantiated until the application layer decides to deactivate / release the EAS instance. Therefore, resources allocated to the EAS instance may not be reallocated and / or reused, even if they are not currently used by the AC instance and the EAS instance. For example, the present invention may improve power utilization and computational utilization, and increase the number of devices and / or ACs supported by an edge data network.

[0031] Thus, in some aspects, the UE and / or the core network may be configured to notify the edge enabler server, EAS instance, or EAS management system when the served AC becomes active or inactive or when the UE enters an idle or connected state. In addition, the edge enabler server, EAS instance, or EAS management system may be configured to release, suspend, or re-instantiate the EAS instance based on notifications received from the UE and / or the core network. Therefore, in some aspects, the EAS instance can be effectively managed to provide improved resource management in the edge computing network. For example, the present invention can improve power utilization, memory utilization, and computing utilization, and increase the number of devices and / or ACs supported by the edge network.

[0032] Figure 1 1 is a diagram illustrating an example of a wireless communication system and an access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0033] In one aspect, the UE 104 may include an edge enabler client 140. Furthermore, the edge enabler client 140 and the core network 190 may be configured to provide state information to the edge data network 198. Additionally, as described in detail herein, the edge data network 198 may manage one or more computing resources (e.g., server instances) of the edge data network 198 based on the state information received from the edge enabler client 140 and the core network 190. Specifically, the edge data network 198 may release, suspend, or reinstantiate one or more resources based on the state information provided by the edge enabler client 140 and the core network 190 regarding the UE utilizing the one or more computing resources.

[0034] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (eg, via the EPC 160 or the core network 190) over a third backhaul link 134 (eg, an X2 interface). The third backhaul link 134 may be wired or wireless.

[0035] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 100. There may be overlapping geographic coverage areas 100. For example, a small cell 102a can have a coverage area 100a that overlaps with the coverage area 100 of one or more macro base stations 102. A network including both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 can include an uplink (UL) (also known as a reverse link) transmission from UE 104 to base station 102 or a downlink (DL) (also known as a forward link) transmission from base station 102 to UE 104. The communication link 120 can use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming, or transmit diversity. The communication link can be through one or more carriers. For each carrier allocated in the carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0036] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.10 standards, LTE, or NR.

[0037] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available prior to communication.

[0038] The small cell 102a may operate in a licensed or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102a may employ NR and use the same 5 GHz unlicensed spectrum as that used by the Wi-Fi AP 150. The small cell 102a employing NR in the unlicensed spectrum may boost the coverage of the access network or increase the capacity of the access network.

[0039] Whether a small cell 102a or a large cell (e.g., a macro base station), the base station 102 may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in one or more frequency bands within the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, frequency bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency ranges designated FR1 (416MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is typically (interchangeably) referred to as the “below 6GHz” band in various documents and articles. A similar naming issue sometimes arises with FR2, which is often referred to (interchangeably) as the “millimeter wave” band in various documents and articles, although it is different from the extremely high frequency (EHF) band (30GHz to 300GHz) that the International Telecommunication Union (ITU) has identified as the “millimeter wave” (mmW) band.

[0040] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, it can be broadly represented as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly represented as a frequency that can include mid-band frequencies, can be within FR2, or can be within the EHF band. Communications using mmW radio frequency bands have extremely high path loss and short range. The mmW base station 180 can utilize beamforming 182 with the UE 104 to compensate for this path loss and short range. The base station 180 and the UE 104 can each include multiple antennas, such as antenna elements, antenna panels, or antenna arrays to facilitate beamforming.

[0041] The base station 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182a. The UE 104 may receive beamformed signals from the base station 180 in one or more receive directions 182b. The UE 104 may also transmit beamformed signals to the base station 180 in one or more transmit directions. The base station 180 may receive beamformed signals from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180 / UE 104. The transmit direction and receive direction of the base station 180 may be the same or may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same.

[0042] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, or other IP services. The BM-SC 170 may provide functions for MBMS user service configuration and delivery. BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. MBMS Gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area of ​​a broadcast specific service, and may be responsible for session management (start / stop) and for collecting eMBMS related billing information.

[0043] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Generally speaking, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are passed through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, or other IP services.

[0044] A base station may include or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver, a wireless base station, a wireless transceiver, a transceiver functional unit, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other appropriate term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include satellite phones, cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, health care devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0045] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0046] FIG. 2A to FIG. 2D Example diagrams 200, 230, 250, and 280 are included that illustrate example structures that may be used for wireless communications by a base station 102 and a UE 104 (e.g., for 5G NR communications). Figure 2A200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G / NR subframe. Figure 2C 250 is a diagram illustrating an example of a second subframe within a 5G / NR frame structure. Figure 2D 280 is a diagram illustrating an example of UL channels within a 5G / NR subframe. The 5G / NR frame structure can be FDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to DL or UL, or can be TDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 34 (most of which are UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE by a received slot format indicator (SFI) (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling). Note that the description presented herein also applies to a 5G / NR frame structure for TDD.

[0047] Other wireless communication technologies may have different frame structures or different channels. A frame (10ms) can be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also called single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots in a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to 5 allow 1, 2, 4, 8, 16 and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4 and 8 slots per subframe, respectively. For slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2μ slots per subframe. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2μ*15kHz, where μ is parameter set 0 to 5. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=5 is 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=0 with 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is about 66.7 μs.

[0048] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0049] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (denoted as Rx for a particular configuration, where 100x is the port number, but other DM-RS configurations are also possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0050] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more CCEs, each CCE includes 9 RE groups (REGs), and each REG includes 4 consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine the subframe / symbol timing and the physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (SSB). The MIB provides the system bandwidth and the number of RBs in the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information such as System Information Blocks (SIBs) not sent through the PBCH, and paging messages.

[0051] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send DM-RS for a physical uplink control channel (PUCCH) and DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. Although not shown, the UE may send a sounding reference signal (SRS). The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0052] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), or UCI.

[0053] Figure 31 is a block diagram of a base station 102 / 180 in communication with a UE 104 in an access network. In the DL, IP packets from the EPC 160 may be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (such as MIB, SIB), RRC connection control (such as RRC connection paging, RRC connection establishment, RRC connection modification and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification) and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling and logical channel prioritization.

[0054] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (such as binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimate may be derived from a reference signal or channel condition feedback sent by the UE 104. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0055] At the UE 104, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 104. If multiple spatial streams are destined for the UE 104, they can be merged into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be transmitted by the base station 102 / 180. These soft decisions can be based on channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 102 / 180 on the physical channel.The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0056] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.

[0057] Similar to the functionality described in conjunction with DL transmissions performed by base station 102 / 180, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0058] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 102 / 180 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0059] UL transmissions are processed at the base station 102 / 180 in a manner similar to that described in conjunction with the receiver functionality at the UE 104. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0060] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 104. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.

[0061] In the UE 104, at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform a combined Figure 1 Aspects of EEC 140.

[0062] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment such as a base station (BS), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0063] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0064] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0065] Figure 4 A diagram illustrating an example decomposed base station 400 architecture is shown. The decomposed base station 400 architecture may include one or more central units (CUs) 410 that may communicate directly with a core network 420 via a backhaul link, or indirectly with the core network 420 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 425 via an E2 link, or a non-real-time (non-RT) RIC 415 associated with a service management and orchestration (SMO) framework 405, or both. The CU 410 may communicate with one or more distributed units (DUs) 430 via respective midhaul links, such as an F1 interface. The DU 430 may communicate with one or more radio units (RUs) 440 via respective fronthaul links. The RU 440 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 440.

[0066] Each of the units (i.e., CU 410, DU 430, RU 440, and near-RT RIC 425, non-RT RIC 415, and SMO framework 405) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0067] In some aspects, CU 410 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 410. CU 410 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 410 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 410 may be implemented to communicate with DU 430 for network control and signaling.

[0068] DU 430 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 440. In some aspects, DU 430 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 430 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 430 or with control functions hosted by CU 410.

[0069] The lower layer functionality may be implemented by one or more RUs 440. In some deployments, a RU 440 controlled by a DU 430 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 440 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 440 may be controlled by the corresponding DU 430. In some scenarios, this configuration may enable the implementation of the DU 430 and the CU 410 in a cloud-based RAN architecture (such as a vRAN architecture).

[0070] The SMO framework 405 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 405 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 405 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 490) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 410, DU 430, RU 440, and near-RT RIC 425. In some specific implementations, the SMO framework 405 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 410) via the O1 interface. Additionally, in some specific implementations, the SMO framework 405 may communicate directly with one or more RUs 440 via the O1 interface. The SMO framework 405 may also include a non-RT RIC 415 configured to support the functionality of the SMO framework 405 .

[0071] The non-RT RIC 415 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 425. The non-RT RIC 415 may be coupled to or communicate with the near-RT RIC 425 (such as via an A1 interface). The near-RT RIC 425 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 410, one or more DUs 430, or both, and the O-eNB with the near-RT RIC 425.

[0072] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 425, the non-RT RIC 415 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 425 and may be received from a non-network data source or from a network function at the SMO framework 405 or the non-RT RIC 415. In some examples, the non-RT RIC 415 or the near-RT RIC 425 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 415 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 405 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0073] refer to Figures 5 to 11 In one non-limiting aspect, according to some aspects of the present disclosure, the system 500 is configured to implement procedures for managing edge application servers based on application client status and / or UE status.

[0074] Figure 5 is a diagram illustrating example communications and components of network entities and devices. Figure 5 As illustrated, system 500 may include one or more UEs 502(1)-502(n) (e.g., UE 104), a core network 504 (e.g., core network 190), and an edge data network (EDN) 506 (e.g., edge data network 198). Some examples of UEs 502(1)-502(n) include smart phone devices, tablet devices, wearable devices, computing devices, Internet of Things (IoT) devices, unmanned aerial vehicles, robots, process automation equipment, sensors, control devices, vehicles, transportation equipment, tactile interaction equipment, virtual and augmented reality (VR and AR) devices, industrial machines, virtual machines, etc. In addition, as Figure 5 As illustrated, UE 502 may include an edge enabler client (EEC) 510 and one or more application clients (ACs) 512(1)-512(n).

[0075] Edge computing is used in distributed computing to bring computing and storage closer to specific data sources. As a result, the EDN 506 can reduce latency at the UE 502 (1)-502 (n) or reduce the load placed on cloud computing resources by the core network 504. In some aspects, the EDN 506 may include a local data network that supports a computer architecture for enabling edge applications. For example, the EDN 506 can provide various edge services to the UE 502 (1)-502 (n) via the core network 504, for example, the core network 504 can provide edge services via one or more base stations 102 / 180. In some aspects, the EDN 506 can provide pre-fetching, caching, processing, or services for data sent to the UE 502 (1)-502 (n). As Figure 5 As illustrated, the EDN 506 may include at least one edge enabler server (EES) 514, an edge application server management component (EAS management component) 516, and one or more edge application server instances (EAS instances) 518(1)-518(n).

[0076] In addition, system 500 may include at least EDGE 1, 2, 3, 5, and 7 in accordance with 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 23.558 to facilitate communications between UEs 502(1)-502(n) (e.g., UE 104), core network 504, and EDN 506. Additionally or alternatively, system 500 may include one or more communication networks 112(1)-112(n) including any one or a combination of a plurality of different types of networks, such as a cellular network, a wireless network, a local area network (LAN), a wide area network (WAN), a personal area network (PAN), the Internet, or any other type of network configured to communicate information between electronic devices (e.g., UEs 502(1)-502(n), 3GPP core network 504, and EDN 506).

[0077] In some aspects, the EEC 510 may be configured to provide support functions to the AC 512. For example, the EEC 510 may retrieve configuration information to enable the exchange of application data traffic 520 with the EAS instances 518(1)-518(n), discover the EAS instances 518(1)-518(n) available in the EDN 506, and detect mobility events for the UEs 502(1)-502(n).

[0078] In some aspects, EES 514 may provide support functions to EAS instances 518 ( 1 )- 518 ( n ) and EEC 510 . For example, the EES 514 may provision configuration information to the EEC 510 to enable the exchange of application data services 520 with the EAS instances 518(1)-518(n), provide an application programming interface (API) invoker and API exposure functionality, interact with the core network 504 for the ability to access network functions, expose events related to application context transfer, provide EEC context transfer between the EES instances 518(1)-518(n), support external exposure of the core network 504 and service capabilities for the EAS instances 518(1)-518(n), provide registration functionality (i.e., registration, update, and deregistration) for the EEC (e.g., EEC 510) of the UE 502(1)-502(n) and the EAS instances 518(1)-518(n), trigger EAS instance 518 instantiation on demand, and support application context relocation (ACR) related operations.

[0079] As described in detail herein, in some aspects, system 500 can provide intelligent resource management functionality for edge computing via subscription and notification procedures. Figure 5 As illustrated, the EES 514 may include a context management component 522 configured to manage the release, suspension, and resumption of EAS instances 518(1)-518(n) based on the activities of the UEs 502(1)-502(n) and the ACs 512(1)-512(n). For example, the AC 512(1) of the UE 502(1) may utilize edge services provided by the EAS instance 518(1) via the application data service 520. For example, the AC 512(1) may be a gaming application that relies on the EAS instance 518(1) for graphics processing and rendering. In addition, to manage the EAS instance 518(1), the EES 514 may subscribe to receive event information about the AC 512(1) and / or the UE 502(1) from the EEC 510 and the core network 504, respectively. For example, context management component 522 can send subscription request 524 to EEC 510 and core network 504, and receive subscription response 526 confirming creation of a subscription for AC 512(1) and / or UE 502(1) at EEC 510 and core network 504. In some aspects, EAS management component 516 or EAS instance 518 can request EES 514 to initiate a subscription in response to instantiation of EAS instance 518 and / or establishment of use of the EAS instance by AC 512(1).

[0080] Additionally, EES 514 may receive notifications 528(1)-528(n) based on a subscription. For example, context management component 522 may receive notification 528 in response to activity of AC 512(1) or UE 502(1). In some aspects, notification 528 received from EEC 510 may indicate at least one of: UE 502(1) is in sleep mode or other inactive mode, UE 502(1) is awakened from sleep mode or other inactive mode, a lock screen of UE 502(1) is active, application context focus of AC 512(1), network connectivity of UE 502(1), current throughput capability and performance of UE 502(1), battery power of UE 502(1), or whether a user is currently focusing on and / or holding UE 502(1). In addition, in some aspects, the notification 528 received from the core network 504 may indicate at least one of the reachability of the UE 502(1), the PDU session state of the UE 502(1), or the connection state (e.g., RRC state) of the UE 502(1). In addition, in some aspects, the subscription request 524 may indicate the type of information that should be sent in the notifications 528(1)-528(n). For example, the subscription request to the core network 504 may indicate that the core network 504 should send notifications 528 related to the PDU session state of the UE 502(1) and / or the reachability of the UE 502(1). For another example, the subscription request to the EEC 510 may indicate that the EEC 510 should send notifications 528 related to the activity and / or context state 512(1).

[0081] In addition, EES 514 can send instance instructions 530(1)-530(n) to EAS management component 516 or EAS instance 518 based on notifications 528(1)-528(n). For example, in response to notification 528(1) indicating that AC 512(1) is inactive, context management component 522 can send instance instructions 530(1) indicating that EAS instance 518(1) should be suspended. In addition, EES can receive notification 528(2) in response to AC 512(1) subsequently becoming active, and send instance instructions 530(2) indicating that EAS instance 518(1) should be resumed in response to UE 502(1) returning to an active state. As another example, context management component 522 may transmit instance instruction 530(1) indicating that EAS instance 518(1) should be suspended in response to notification 528(1) indicating that AC 512(1) is inactive and no other AC 512(2)-512(n) is utilizing EAS instance 512(1). In other words, in some aspects, if multiple ACs 512 are utilizing EAS instance 518(2), an event at only one of ACs 512 utilizing EAS instance 518(2) will not result in the release, suspension, or resumption of EAS instance 518(2).

[0082] Moreover, in some aspects, context management component 522 may employ one or more machine learning techniques to determine whether to send instance instruction 530 and the instructions to include within the instance instruction (e.g., resume, release, or pause) based on notifications 528(1)-528(n).

[0083] Additionally or alternatively, in some aspects, notifications 528(1)-528(n) can be sent directly to EAS instances 518(1)-518(n) and / or EAS management component 516. For example, in some aspects, EAS management component 516 can include context management component 522 that is configured to subscribe to receive notifications about AC 512(1) and / or UE 502(1) from EEC 510 and / or core network 504, respectively, and generate instance instructions 530(1)-530(n) based on notifications 528(1)-528(n). Further, in some aspects, AC 512 can send notifications 528(1)-528(n) directly to EAS instances 518(1)-518(n) and / or EAS management component 516.

[0084] Upon receiving notifications 528(1)-528(n), the associated EAS instance 518 and / or the EAS management component 516 can determine whether the associated EAS instance 518 should be released, suspended, or resumed. For example, the associated EAS instance 518 and / or the EAS management component 516 can determine that the associated EAS instance 518 should be suspended or released in response to notification 528(1) indicating that AC 512(1) is inactive and determining that no other ACs 512(2)-512(n) and / or UEs 502(20)-502(n) are utilizing the EAS instance 512(1). For another example, the associated EAS instance 518 and / or the EAS management component 516 can determine that the associated EAS instance 518 should be resumed in response to notification 528(1) indicating that AC 512(1) has entered an active state from an inactive state.

[0085] like Figure 5 As illustrated, in some aspects, the core network 504 may include a monitoring component 532 and a notification component 534. The monitoring component 532 may be configured to monitor the status and / or activity of the ACs 512(1)-512(n) of the UE 502(1) and the status and / or activity of the UE 502(1). For example, the monitoring component 532 may be configured to monitor the reachability of the UE 502(1), the session state (e.g., PDU session state) of the UE 502(1), or the connection state (e.g., RRC state) of the UE 502(1). In addition, the monitoring component 532 may be configured to determine event information based on the monitoring and generate notification information describing the event information. The notification component 534 may manage and operate subscriptions. Specifically, notification component 534 can receive subscription requests 526(1)-526(n), generate subscriptions for AC 512(1)-512(n) and UE 502(1), send subscription responses 526(1)-526(n) confirming or denying the generated subscriptions, and send notifications 528(1)-528(n) to relevant subscribers including notification information generated by monitoring component 532. Additionally or alternatively, AC 512 can include monitoring component 532 and notification component 534.

[0086] like Figure 5As illustrated, in some aspects, the core network 504 may include a monitoring component 536 and a notification component 538. The monitoring component 536 may be configured to monitor the status and / or activity of the ACs 512(1)-512(n) of the UE 502(1) and the status and / or activity of the UE 502(1). For example, the monitoring component 532 may be configured to monitor whether the UE 502(1) is in a sleep mode or other inactive mode, whether the UE 502(1) wakes up from a sleep mode or other inactive mode, whether the lock screen of the UE 502(1) is active, whether the UE 502(1) is currently held by a user, or whether the UE 502(1) is currently the object of the user's gaze. In addition, the monitoring component 532 may be configured to monitor the application context focus of the AC 512(1), the network connectivity of the UE 502(1), the current throughput capability and performance of the UE 502(1), and the battery power of the UE 502(1). In addition, monitoring component 532 can be configured to determine event information based on the monitoring and generate notification information describing the event information. Notification component 534 can manage and operate subscriptions. Specifically, notification component 534 can receive subscription requests 526(1)-526(n), generate subscriptions for AC 512(1)-512(n) and UE 502(1), send subscription responses 526(1)-526(n) confirming or denying the generated subscriptions, and send notifications 528(1)-528(n) to relevant subscribers including notification information generated by monitoring component 532.

[0087] Figure 6 600 is a diagram illustrating an example of a hardware implementation for a computing device 602 (e.g., UE 104, UE 502, etc.) that employs a processing system 614. The processing system 614 may be implemented with a bus architecture generally represented by a bus 624. Depending on the specific application and overall design constraints of the processing system 614, the bus 624 may include any number of interconnecting buses and / or bridges. The bus 624 links various circuits together, including one or more processors and / or hardware components (represented by the processor 604, EEC 510, AC 512, monitoring component 532, notification component 534, and computer-readable media (e.g., non-transitory computer-readable media) / memory 606). The bus 624 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0088] The processing system 614 may be coupled to the transceiver 610. The transceiver 610 may be coupled to one or more antennas 620. The transceiver 610 provides components for communicating with various other devices over a transmission medium. The transceiver 610 receives signals from the one or more antennas, extracts information from the received signals, and provides the extracted information to the processing system 614 (specifically, the receiver component 630). The receiver component 630 may receive periodic NTN SI 508(1)-508(n), report requests 514(1)-514(n), and updated NTN SI 516(1)-516(n). In addition, the transceiver 610 receives information from the processing system 614 (specifically, the transmitter component 632) and generates signals to be applied to the one or more antennas based on the received information. In addition, the transmitter component 632 may transmit acquisition indications 510(1)-510(n).

[0089] The processing system 614 includes a processor 604 coupled to a computer-readable medium / memory 606 (e.g., a non-transitory computer-readable medium). The processor 604 is responsible for general processing, including executing software stored on the computer-readable medium / memory 606. When executed by the processor 604, the software causes the processing system 614 to perform various functions described above for any specific device. The computer-readable medium / memory 606 can also be used to store data manipulated by the processor 604 when executing the software. The processing system 614 also includes at least one of the EEC 510, AC 512, monitoring component 532, or notification component 534. The aforementioned components can be software components running in the processor 604, software components residing / stored in the computer-readable medium / memory 606, one or more hardware components coupled to the processor 604, or some combination thereof. The processing system 614 can be a component of the computing device 602 and can include at least one of the memory 360 and / or the TX processor 368, the RX processor 356, and the controller / processor 359. Alternatively, the processing system 614 may be the entire UE (see, for example, Figure 3 350 Figure 5 UE 502).

[0090] The aforementioned means may be one or more of the aforementioned components of the computing device 602 and / or the processing system 614 of the device 602 configured to perform the functions recited by the aforementioned means. As described above, the processing system 614 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Therefore, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0091] Figure 7700 is an example of a hardware implementation for a device 702 (e.g., EDN 506, EES 514, EAS management component 516, EAS instance 518, etc.). In one example, the computing device 702 includes a processor 704 for performing processing functions associated with one or more of the components and functions described herein. The processor 704 may include a single or multiple collections of processors or multi-core processors. In addition, the processor 704 may be implemented as an integrated processing system and / or a distributed processing system. In one example, the processor 704 includes, but is not limited to, any processor that is specially programmed as described herein, including a controller, a microcontroller, a computer processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a system on a chip (SoC), or other programmable logic components or state machines. In addition, the processor 704 may include other processing components, such as one or more arithmetic logic units (ALUs), registers, or control units.

[0092] In one example, the computing device 702 also includes a memory 706 for storing instructions that can be executed by the processor 704 to perform the functions described herein. The memory 706 can be configured to store data and / or computer executable instructions that define an operating system 708, one or more applications 710, and / or are associated with the operating system, the one or more applications, and the processor 704 can execute the operating system 708 and / or the one or more applications 710. Examples of the memory 706 can include, but are not limited to, a type of memory that can be used by a computer, such as a random access memory (RAM), a read-only memory (ROM), a tape, a disk, an optical disk, a volatile memory, a non-volatile memory, and any combination thereof. In one example, the memory 706 can store a local version of an application being executed by the processor 704.

[0093] The example computing device 702 also includes a communication component 712 that provides for establishing and maintaining communications with one or more parties using hardware, software, and services as described herein. The communication component 712 can carry communications between components on the computing device 702 and between the computing device 702 and external devices, such as devices located across a communication network and / or devices connected to the computing device 702 serially or locally. For example, the communication component 712 may include one or more buses, and may also include a transmit chain component and a receive chain component associated with a transmitter and a receiver, respectively, which are operable to interface with external devices.

[0094] The example computing device 702 also includes a data repository 714, which can be any suitable combination of hardware and / or software that provides mass storage of information, databases, and programs used in conjunction with the specific implementations described herein. For example, the data repository 714 can be a data repository for the operating system 708 and / or the application program 710.

[0095] The example computing device 702 also includes a user interface component 716, which is operable to receive input from a user of the computing device 702 and further operable to generate output for presentation to the user. The user interface component 716 may include one or more input devices, including but not limited to a keyboard, a numeric keypad, a mouse, a touch-sensitive display (e.g., display 718), a digitizer, a navigation key, a function key, a microphone, a speech recognition component, any other mechanism capable of receiving input from a user, or any combination thereof. In addition, the user interface component 716 may include one or more output devices, including but not limited to a display (e.g., display 718), a speaker, a tactile feedback mechanism, a printer, any other mechanism capable of presenting output to a user, or any combination thereof.

[0096] Figure 8 is a flowchart of an example method for managing an edge application server based on application client state and / or UE state according to some aspects of the present disclosure. The method can be performed by a computing device (e.g., Figure 5 EES 514, EAS management component 516 or EAS instance 518, Figure 7 The computing device 702 (which may include the memory 706 and which may be the entire computing device 702 or a component of the computing device 702, such as the processor 704)) executes.

[0097] At block 810, method 800 may include establishing a subscription to event information for a user equipment (UE) or an application client executing on the UE, the application client being associated with an edge application server instance executing within an edge data network. For example, EES 514, EAS management component 516, or EAS instance 518 may subscribe to event information corresponding to EEC 510, AC 512(1), and / or AC 512(1) at core network 504, and / or UE 502(1). In some aspects, a subscriber (e.g., EES 514) may subscribe to event information corresponding to EEC 510, AC 512(1), and / or AC 512(1) at core network 504, and / or UE 502(1) by sending a subscription request 524(1) to EEC 510, AC 512(1), and / or core network 504, and receiving a subscription response 526(1) confirming that the subscription has been established.

[0098] Thus, the EES 514, the EAS management component 516, the EAS instance 518, the computing device 702 and / or the processor 704 executing the context management component 522 may provide components for establishing a subscription to event information of a user equipment (UE) or an application client executing on the UE, which application client is associated with an edge application server instance executing within an edge data network.

[0099] At block 820, method 800 may include receiving notifications of contextual events for application clients and / or UEs based on a subscription. For example, EES 514, EAS management component 516, or EAS instance 518 may receive one or more notifications 528 from EEC 510 and / or core network 504 identifying activities of AC 512(1) and / or UE 502(1) based on a previously established subscription. The context event may indicate at least one of: UE 502(1) being in sleep mode or other inactive mode, a lock screen of UE 502(1) being active, UE 502(1) waking up from sleep mode or other inactive mode, application context focus of AC 512(1), network connectivity of UE 502(1), current throughput capability and performance of UE 502(1), battery power of UE 502(1), whether a user is currently focusing on and / or holding UE 502(1), reachability of UE 502(1), PDU session state of UE 502(1), or connection state of UE 502(1) (e.g., RRC state).

[0100] Thus, the EES 514, EAS management component 516, EAS instance 518, computing device 702, and / or processor 704 executing context management component 522 may provide means for receiving notifications of contextual events for application clients and / or UEs based on subscriptions.

[0101] At block 830, method 800 may include causing release, suspension, or resumption of the edge application server instance in response to the notification. For example, EES 514 may send instance instructions 530(1) based on one or more notifications 528.

[0102] Thus, EES 514, EAS management component 516, EAS instance 518, computing device 702, and / or processor 704 executing context management component 522 may provide means for causing release, suspension, or resumption of an edge application server instance in response to a notification.

[0103] Fig. 9 is a flowchart of an example method for managing an edge application server based on application client state and / or UE state according to some aspects of the present disclosure. The method can be performed by a computing device (e.g., Figure 5EAS instance 518, Figure 7 The computing device 702 (which may include the memory 706 and which may be the entire computing device 702 or a component of the computing device 702, such as the processor 704)) executes.

[0104] At block 910, method 900 includes subscribing, by an edge application server instance, to event information of a user equipment (UE) or an application client executing on the UE, the application client being associated with an edge application server instance executing within an edge data network. For example, EAS instance 518 may subscribe to event information corresponding to EEC 510, AC 512(1), and / or AC 512(1) at core network 504, and / or UE 502(1). In some aspects, EAS instance 518 may subscribe to event information corresponding to EEC 510, AC 512(1), and / or AC 512(1) at core network 504, and / or UE 502(1) by sending a subscription request 524(1) to EEC 510, AC 512(1), and / or core network 504, and receiving a subscription response 526(1) confirming that the subscription has been established.

[0105] Thus, the EAS instance 518, the computing device 702, and / or the processor 704 executing the context management component 522 may provide a component for subscribing, by an edge application server instance, to event information of a user equipment (UE) or an application client executed on the UE, the application client being associated with the edge application server instance executing within an edge data network.

[0106] At block 920, method 900 may include receiving a first notification of a first context event of an application client and / or UE based on a subscription. For example, EAS instance 518 may receive one or more notifications 528 from AC 512(1) within application data service 520 based on a previously established subscription. Additionally or alternatively, in some aspects, EAS instance 518 may receive one or more notifications 528 from EEC 510 via EES 514. Furthermore, one or more notifications 528 may indicate a state and / or application context of AC 512(1). The first context event may indicate at least one of: UE 502(1) being in sleep mode or other inactive mode, UE 502(1) waking up from sleep mode or other inactive mode, a lock screen of UE 502(1) being active, application context focus of AC 512(1), network connectivity of UE 502(1), current throughput capability and performance of UE 502(1), battery power of UE 502(1), or whether a user is currently focusing on and / or holding UE 502(1).

[0107] Thus, the EAS instance 518, computing device 702, and / or processor 704 executing context management component 522 may provide means for receiving a first notification of a first context event for an application client and / or UE via an application data service based on a subscription.

[0108] At block 930, method 900 may include receiving a second notification of a second context event for the application client and / or UE from the core network based on the subscription. For example, EAS instance 518 may receive one or more notifications 528 identifying activities of AC 512(1) and / or UE 502(1) based on a previously established subscription from core network 504. The second context event may indicate at least one of reachability of UE 502(1), a PDU session state of UE 502(1), or a connection state (e.g., RRC state) of UE 502(1).

[0109] Thus, the EAS instance 518, computing device 702, and / or processor 704 executing context management component 522 may provide means for receiving a second notification of a second context event of an application client and / or UE from the core network based on the subscription.

[0110] At block 940 , method 900 may include releasing, pausing, or resuming the edge application server instance based on the first notification and / or the second notification. For example, EES 514 may release itself, suspend itself, or resume based on one or more notifications 528 .

[0111] Thus, the EAS instance 518, computing device 702, and / or processor 704 executing context management component 522 may provide means for releasing, suspending, or resuming an edge application server instance based on the first notification and / or the second notification.

[0112] Fig.10 1 is a flowchart of an example method for managing an edge application server based on application client state and / or UE state according to some aspects of the present disclosure. The method can be performed by a computing device (e.g., EAS management component 516, Figure 7 The computing device 702 (which may include the memory 706 and which may be the entire computing device 702 or a component of the computing device 702, such as the processor 704)) executes.

[0113] At block 1010, method 1000 includes subscribing, by an edge application server manager, event information of a user equipment (UE) or an application client executing on the UE, the application client being associated with an edge application server instance executing within an edge data network. For example, EAS management component 516 may subscribe to event information corresponding to EEC 510, AC 512(1), and / or AC 512(1) at core network 504, and / or UE 502(1). In some aspects, EAS management component 516 may subscribe to event information corresponding to EEC 510, AC 512(1), and / or AC 512(1) at core network 504, and / or UE 502(1) by sending a subscription request 524(1) to EEC 510, AC 512(1), and / or core network 504, and receiving a subscription response 526(1) confirming that the subscription has been established.

[0114] Thus, the EAS management component 516, the computing device 702, and / or the processor 704 executing the context management component 522 may provide a component for subscribing, by an edge application server manager, to event information of a user equipment (UE) or an application client executed on the UE, the application client being associated with an edge application server instance executing within an edge data network.

[0115] At block 1020, method 1000 may include receiving a first notification of a first contextual event for an application client and / or UE based on a subscription. For example, subscriber EAS management component 516 may receive one or more notifications 528 from EEC 510 identifying an activity of AC 512(1) and / or UE 502(1) based on a previously established subscription. In some aspects, EAS management component 516 may receive one or more notifications 528 from EEC 510 via EES 514. Additionally, one or more notifications 528 may indicate a state and / or application context of AC 512(1). Some examples of contextual events may include:

[0116] Thus, the EAS management component 516, computing device 702, and / or processor 704 executing context management component 522 may provide means for receiving a first notification of a first context event for an application client and / or UE via an application data service based on a subscription.

[0117] At block 1030, method 1000 may include receiving a second notification of a second context event of the application client and / or UE from the core network based on the subscription. For example, management component 516 may receive one or more notifications 528 from core network 504 identifying activities of AC 512(1) and / or UE 502(1) based on a previously established subscription.

[0118] Thus, the EAS management component 516, computing device 702, and / or processor 704 executing context management component 522 may provide means for receiving a second notification of a second context event for an application client and / or UE from the core network based on a subscription.

[0119] At block 1040, method 1000 can include causing release, suspension, or resumption of the edge application server instance in response to the first notification and / or the second notification.For example, EAS management component 516 can send instance instruction 530(1) based on one or more notifications 528.

[0120] Thus, the EAS management component 516, computing device 702, and / or processor 704 executing context management component 522 can provide means for causing release, suspension, or resumption of an edge application server instance in response to the first notification and / or the second notification.

[0121] Fig.11 is a flow chart of an example method for managing an edge application server based on application client state and / or UE state according to some aspects of the present disclosure.

[0122] The method may be performed by a UE (eg, Figure 1 and Figure 3 UE 104, which may include memory 360 and which may be the entire UE 104 or a component of UE 104 (such as EEC 140, EEC 510, monitoring component 532, notification component 534, TX processor 368, RX processor 356 and / or controller / processor 359; Figure 5 UE 502; and / or Figure 6 Executed by computing device 602)).

[0123] At block 1110, method 1100 may include generating a subscription in response to a subscription request received from a subscriber. For example, EEC 510 may receive a subscription request 524(1) from a subscriber (e.g., EES 514, EAS management component 516, or EAS instance 518) and send a subscription response 526(1) confirming that a subscription has been established.

[0124] Thus, UE 104, UE 502, computing device 602, TX processor 368, RX processor 356, and / or controller / processor 359 executing EEC 510 may provide means for generating a subscription in response to a subscription request received from a subscriber.

[0125] At block 1120, method 1100 may include detecting an event associated with a UE and / or an application client executing on the UE, wherein the application client is supported by an edge application server instance. For example, EEC 510 may monitor the activities of AC 512(1) and UE 502 and detect an event related to the status of AC 512(1) and UE 502.

[0126] Thus, the UE 104, UE 502, computing device 602, TX processor 368, RX processor 356 and / or controller / processor 359 executing the EEC 510 may provide components for detecting events associated with the UE and / or an application client executing on the UE, where the application client is supported by an edge application server instance.

[0127] At block 1130, method 1100 may include sending a notification to a subscriber identifying an event associated with a UE and / or an application client executing on the UE, wherein the subscriber causes a release, suspension, or resumption of an edge application server instance based at least in part on the notification. For example, EEC 510 may generate one or more notifications 528 based on the detected event and send one or more notifications 528 to EES 514, EAS management component 516, or EAS instance 518. Further, upon receiving the one or more notifications, EES 514, EAS management component 516, EAS instance 518 causes a release, suspension, or resumption of EAS instance 518(1).

[0128] Thus, the UE 104, UE 502, computing device 602, TX processor 368, RX processor 356, and / or controller / processor 359 executes the EEC 510 executed on the UE, wherein the subscriber causes the release, suspension, or resumption of the edge application server instance based at least in part on the notification.

[0129] The previous description is provided to enable any person of ordinary skill in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those of ordinary skill in the art, and the universal principles defined in this article can be applied to other aspects. The claims are not intended to be limited to the aspects shown in this article, but should be granted the full scope consistent with the claims in language, wherein the singular reference of the element is not intended to represent "there is and only one", but "one or more", unless otherwise stated. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" include any combination of A, B or C, and may include multiples of A, multiples of B or multiples of C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are or later will be known to persons of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosure is explicitly recited in the claims, nothing disclosed herein is intended to be disclosed to the public. Words such as "module," "mechanism," "element," "device," etc. cannot replace the word "component." Therefore, no claim element will be understood to be a part plus function unless the element is expressly stated using the phrase "component for..."

[0130] Sample Clauses

[0131] The following example clauses describe various aspects of the disclosure.

[0132] A. A method for wireless communication, the method comprising: establishing a subscription to event information of a user equipment (UE) or an application client executed on the UE, the application client being associated with an edge application server instance executed within an edge data network; receiving notifications of contextual events of the application client and / or the UE based on the subscription;

[0133] And in response to the notification, the edge application server instance is released, suspended or resumed.

[0134] B. A method according to clause A, wherein establishing the subscription to the event information of the application client includes: requesting the subscription to the event information of the application client and / or the UE from a wireless core network serving the UE; and receiving confirmation of the subscription from the wireless core network serving the UE; and wherein receiving the notification of the context event includes receiving the notification of the context event from the wireless core network based on wireless activity between the UE and the wireless core network.

[0135] C. A method as described in any of clauses A to B, wherein the notification identifies at least one of a protocol data unit (PDU) session state or a UE reachability state.

[0136] D. A method according to any one of clauses A to C, wherein establishing the subscription to the event information of the application client includes: requesting the subscription to the event information of the application client and / or the UE from an edge enabler client executed on the UE; and receiving confirmation of the subscription from the edge enabler client executed on the UE; and wherein receiving the notification of the context event includes receiving the notification of the context event from the UE based on device activity at the UE, the context event being detected by the edge enabler client based on monitoring of the UE and / or application.

[0137] E. A method as described in any of clauses A to D, wherein the notification identifies at least one of an application context of the application client or a device context of the UE.

[0138] F. A method according to any one of clauses A to E, wherein causing the release, suspension or resumption of the edge application server instance in response to the notification includes sending a release request, a suspension request or a resumption request to the edge application server instance or an edge application server manager that manages the edge application server instance.

[0139] G. A method according to any one of clauses A to F, wherein causing the release or suspension of the edge application server instance in response to the notification comprises: determining that no other applications and / or UEs are currently associated with the edge application server instance;

[0140] And the edge application server instance is released, suspended or resumed based on the fact that no other application and / or UE is currently associated with the edge application server instance.

[0141] H. One or more non-transitory computer-readable media encoded with instructions that, when executed by one or more processors, configure a computing device to perform a computer-implemented method as described in any of clauses A to G.

[0142] I. A device comprising one or more processors and one or more computer-readable media encoded with instructions that, when executed by the one or more processors, configure the computer to perform a computer-implemented method as described in any one of clauses A to G.

[0143] J. An apparatus comprising means for performing a method according to any one of clauses A to G.

Claims

1. An edge computing device, the edge computing device comprising: a memory storing computer executable instructions; and at least one processor coupled to the memory and configured to execute the computer-executable instructions to: Establishing a subscription to event information of a user equipment (UE) or an application client executing on the UE, the application client being associated with an edge application server instance executing within an edge data network; receiving notifications of contextual events of the application client and / or the UE based on the subscription; as well as The edge application server instance is released, suspended, or resumed in response to the notification.

2. The edge computing device according to claim 1, wherein in order to establish the subscription to the event information of the application client, the at least one processor is configured to execute the computer executable instructions to request the subscription to the event information of the application client and / or the UE from the wireless core network serving the UE; and receive confirmation of the subscription from the wireless core network serving the UE, and Wherein, to receive the notification of the context event, the at least one processor is configured to execute the computer-executable instructions to receive the notification of the context event from the wireless core network based on wireless activities between the UE and the wireless core network.

3. The edge computing device of claim 2, wherein the notification identifies at least one of a protocol data unit (PDU) session state or a UE reachability state.

4. The edge computing device according to claim 1, wherein in order to establish the subscription to the event information of the application client, the at least one processor is configured to execute the computer executable instructions to request the subscription to the event information of the application client and / or the UE from the edge enabler client executed on the UE; and receive confirmation of the subscription from the edge enabler client executed on the UE, Wherein, in order to receive the notification of the context event, the at least one processor is configured to execute the computer-executable instructions to receive the notification of the context event from the UE based on device activity at the UE, and the context event is detected by the edge enabler client based on monitoring of the UE and / or application.

5. The edge computing device of claim 4, wherein the notification identifies at least one of an application context of the application client or a device context of the UE.

6. The edge computing device according to claim 1, wherein in order to cause the release, suspension or resumption of the edge application server instance in response to the notification, the at least one processor is configured to execute the computer-executable instructions to send a release request, a suspension request or a resumption request to the edge application server instance or an edge application server manager that manages the edge application server instance.

7. The edge computing device of claim 1 , wherein in order to cause the release or suspension of the edge application server instance in response to the notification, the at least one processor is configured to execute the computer executable instructions to: Determining that no other applications and / or UEs are currently associated with the edge application server instance; and The edge application server instance is released, suspended or resumed based on the fact that no other application and / or UE is currently associated with the edge application server instance.

8. A method for wireless communication, the method comprising: Establishing a subscription to event information of a user equipment (UE) or an application client executing on the UE, the application client being associated with an edge application server instance executing within an edge data network; receiving notifications of contextual events of the application client and / or the UE based on the subscription; as well as The edge application server instance is released, suspended, or resumed in response to the notification.

9. The method according to claim 8, wherein establishing the subscription to the event information of the application client comprises: Requesting the subscription to the event information of the application client and / or the UE from a wireless core network serving the UE; and receiving a confirmation of the subscription from the wireless core network serving the UE; and Wherein receiving the notification of the context event comprises receiving the notification of the context event from the wireless core network based on wireless activity between the UE and the wireless core network.

10. The method of claim 9, wherein the notification identifies at least one of a protocol data unit (PDU) session state or a UE reachability state.

11. The method according to claim 8, wherein establishing the subscription to the event information of the application client comprises: Requesting, from an edge enabler client executed on the UE, the subscription to the event information of the application client and / or the UE; and receiving a confirmation of the subscription from the edge enabler client executing on the UE; and Wherein receiving the notification of the context event comprises receiving the notification of the context event from the UE based on device activity at the UE, the context event being detected by the edge enabler client based on monitoring of the UE and / or an application.

12. The method of claim 11, wherein the notification identifies at least one of an application context of the application client or a device context of the UE.

13. The method of claim 8, wherein causing the release, suspension, or resumption of the edge application server instance in response to the notification comprises sending a release request, a suspension request, or a resumption request to the edge application server instance or an edge application server manager that manages the edge application server instance.

14. The method according to claim 8, wherein causing the release or suspension of the edge application server instance in response to the notification comprises: Determining that no other application and / or UE is currently associated with the edge application server instance; as well as The edge application server instance is released, suspended, or resumed based on the fact that no other application and / or UE is currently associated with the edge application server instance.

15. A non-transitory computer-readable medium having instructions thereon, which, when executed by at least one computing device, cause the at least one computing device to perform operations comprising: Establishing a subscription to event information of a user equipment (UE) or an application client executing on the UE, the application client being associated with an edge application server instance executing within an edge data network; receiving notifications of contextual events of the application client and / or the UE based on the subscription; as well as The edge application server instance is released, suspended, or resumed in response to the notification.

16. The non-transitory computer-readable medium of claim 15, wherein establishing the subscription to the event information of the application client comprises: Requesting the subscription to the event information of the application client and / or the UE from a wireless core network serving the UE; and receiving a confirmation of the subscription from the wireless core network serving the UE; and Wherein receiving the notification of the context event comprises receiving the notification of the context event from the wireless core network based on wireless activity between the UE and the wireless core network.

17. The non-transitory computer-readable medium of claim 16, wherein the notification identifies at least one of a protocol data unit (PDU) session state or a UE reachability state.

18. The non-transitory computer-readable medium of claim 15, wherein establishing the subscription to the event information of the application client comprises: Requesting, from an edge enabler client executed on the UE, the subscription to the event information of the application client and / or the UE; and receiving a confirmation of the subscription from the edge enabler client executing on the UE; and Wherein receiving the notification of the context event comprises receiving the notification of the context event from the UE based on device activity at the UE, the context event being detected by the edge enabler client based on monitoring of the UE and / or an application.

19. The non-transitory computer-readable medium of claim 18, wherein the notification identifies at least one of an application context of the application client or a device context of the UE.

20. The non-transitory computer-readable medium of claim 15, wherein causing the release, suspension, or resumption of the edge application server instance in response to the notification comprises sending a release request, a suspension request, or a resumption request to the edge application server instance or an edge application server manager that manages the edge application server instance.

Images