Triggering an action in response to a corresponding event notification on a user device

Abstract

Apparatus, methods and systems are disclosed for triggering an action in response to an event notification corresponding to a UE. The method includes receiving an event notification from a detection entity related to an adaptation of a behavior of the at least one UE. The method includes determining a trigger action for at least one application of the at least one UE in response to receiving the event notification. The trigger action includes edge supported service modification, edge supported service cancellation, edge supported service suspension, selection of an alternative application server, creation of a new candidate target application server, or any combination thereof. The method includes sending the trigger action to an application entity, a further application enablement entity, or a combination thereof, for performing the trigger action based on the event notification.

Description

[Technical Field]

[0001] The subject matter disclosed herein relates generally to wireless communications, and more particularly to triggering actions in response to event notifications corresponding to user equipment. [Background technology]

[0002] In certain wireless communication networks, the planned UE behavior may change after the edge support services are initiated, and in such networks, the edge support services may not accurately perform the required functions. Summary of the Invention [Means for solving the problem]

[0003] A method is disclosed for triggering an action in response to an event notification corresponding to user equipment. The apparatus and system also perform the functions of the method. One embodiment of the method includes receiving, at a network entity, an event notification from a detection entity, the event notification relating to behavioral adaptation of at least one user equipment. In some embodiments, the method includes determining a trigger action for at least one application of the at least one user equipment in response to receiving the event notification. The trigger action includes edge-supported service modification, edge-supported service cancellation, edge-supported service suspension, selection of an alternative application server, creation of a new candidate target application server, or some combination thereof. In particular embodiments, the method includes sending the trigger action to an application entity, a further application enablement entity, or a combination thereof, for executing the trigger action based on the event notification.

[0004] An apparatus for triggering an action in response to an event notification corresponding to user equipment includes a network entity. In some embodiments, the apparatus includes a receiver that receives an event notification related to adapting behavior of at least one user equipment from a detection entity. In various embodiments, the apparatus includes a processor that determines a trigger action for at least one application of the at least one user equipment in response to receiving the event notification. The trigger action includes edge-supported service modification, edge-supported service cancellation, edge-supported service suspension, selection of an alternative application server, creation of a new candidate target application server, or some combination thereof. In particular embodiments, the apparatus includes a transmitter that transmits the trigger action to an application entity, a further application enablement entity, or a combination thereof, for executing the trigger action based on the event notification.

[0005] Another embodiment of a method for triggering an action in response to an event notification corresponding to user equipment includes receiving, at a first network entity, a monitoring event from an application, a second network entity, or a combination thereof. In some embodiments, the method includes determining, in response to receiving the monitoring event, an event notification related to adaptation of at least one user equipment behavior. In particular embodiments, the method includes transmitting the event notification to a further application enablement entity.

[0006] Another apparatus for triggering an action in response to an event notification corresponding to user equipment includes a first network entity. In some embodiments, the apparatus includes a receiver that receives monitoring events from an application, a second network entity, or a combination thereof. In various embodiments, the apparatus includes a processor that, in response to receiving the monitoring events, determines an event notification related to adaptation of at least one user equipment behavior. In particular embodiments, the apparatus includes a transmitter that transmits the event notification to a further application enablement entity.

[0007] A more particular description of the embodiments briefly described above will be given by reference to specific embodiments that are illustrated in the accompanying drawings. The embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, with the understanding that these drawings illustrate only some embodiments and therefore should not be considered limiting in scope. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for triggering an action in response to an event notification corresponding to a user equipment. [Figure 2] 1 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to trigger an action in response to an event notification corresponding to a user equipment. [Figure 3] 1 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to trigger an action in response to an event notification corresponding to a user equipment. [Figure 4] 1 is a schematic block diagram illustrating one embodiment of a system for triggering an action in response to an event notification corresponding to a user equipment. [Figure 5] 1 is a timing diagram illustrating a first embodiment of a system for triggering an action in response to an event notification corresponding to a user equipment. [Figure 6] FIG. 1 is a timing diagram illustrating a second embodiment of a system for triggering an action in response to an event notification corresponding to a user equipment. [Figure 7] 1 is a flow chart diagram illustrating one embodiment of a method for triggering an action in response to an event notification corresponding to a user equipment. [Figure 8] FIG. 10 is a flow chart diagram illustrating another embodiment of a method for triggering an action in response to an event notification corresponding to a user equipment. DETAILED DESCRIPTION OF THE INVENTION

[0009] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, all of which may be referred to generally herein as a "circuit," "module," or "system." Furthermore, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and / or non-transmittable. The storage devices may not embody signals. In certain embodiments, the storage devices merely use signals to access the code.

[0010] Some of the functional units described herein may be labeled as modules to more fully emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integrated ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0011] Modules may also be implemented in code and / or software for execution by various types of processors. For example, an identified module of code may include one or more physical or logical blocks of executable code that may be organized, for example, as an object, procedure, or function. Nevertheless, the executable files of identified modules need not be physically located together, but may include different instructions stored in different locations that, when logically combined, comprise that module and achieve the purpose stated for that module.

[0012] In practice, a module of code may be a single instruction or many instructions, and may even be distributed across several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and depicted herein in modules and may be embodied in any suitable form and organized within any suitable type of data structure. Operational data may be collected as a single data set or may be distributed across different locations, including across different computer-readable storage devices. When a module or portions of a module are implemented in software, the software portions are stored on one or more computer-readable storage devices.

[0013] Any combination of one or more computer-readable mediums may be utilized. The computer-readable medium may be a computer-readable storage medium. The computer-readable storage medium may be a storage device that stores code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the above.

[0014] More specific examples (non-exhaustive list) of storage devices include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or Flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0015] The code for performing operations for the embodiments may be any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code may run entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or the connection to the external computer may be made (e.g., through the Internet using an Internet Service Provider).

[0016] References throughout this specification to "one embodiment," "an embodiment," or similar phrases mean that a particular feature, structure, or characteristic described with respect to an embodiment is included in at least one embodiment. Thus, all appearances of the phrases "in one embodiment," "in an embodiment," and similar phrases throughout this specification may, but do not necessarily, refer to the same embodiment, but mean "one or more, but not all, embodiments" unless otherwise specified. The words "including," "comprising," and "having," and variations thereof, mean "including, but not limited to," unless otherwise specified. An enumerated list of items does not imply that any or all of the items are mutually exclusive unless otherwise specified. The terms "a," "an," and "the" also refer to "one or more," unless otherwise specified.

[0017] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, and hardware chips, to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of the specific details or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

[0018] Aspects of the embodiments are described below with reference to schematic flowchart illustrations and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowchart illustrations and / or schematic block diagrams, and combinations of blocks in the schematic flowchart illustrations and / or schematic block diagrams, may be implemented by code. The code may be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in one or more blocks of the schematic flowchart illustrations and / or schematic block diagrams.

[0019] The code may also be stored in a storage device that can instruct a computer, other programmable data processing apparatus, or other device to function in a particular manner, such that the instructions stored on the storage device produce an article of manufacture that includes instructions that implement the functions / acts specified in one or more blocks of the schematic flowchart diagrams and / or schematic block diagrams.

[0020] The code may also be loaded into a computer, other programmable data processing apparatus, or other device to cause the computer, other programmable apparatus, or other device to perform a series of operational steps to generate a computer-implemented process, such that the code running on the computer or other programmable apparatus provides a process for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0021] The schematic flowchart diagrams and / or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and / or schematic block diagrams may represent a module, segment, or portion of code that includes one or more executable instructions of code for implementing the specified logical function(s).

[0022] It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. Other steps and methods may be contemplated that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated figures.

[0023] Various arrow and line types may be used in the flowchart and / or block diagrams, but these are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used only to indicate the logical flow of the illustrated embodiments. For example, arrows may indicate wait or monitoring periods of unspecified duration between enumerated steps of the illustrated embodiments. It should also be noted that each block of the block and / or flowchart diagrams, and combinations of blocks in the block and / or flowchart diagrams, may be implemented by dedicated hardware-based systems that perform the specified functions or acts, or a combination of dedicated hardware and code.

[0024] The description of an element in each figure may refer to the element in the preceding figure. Like numbers refer to like elements in all figures, including alternative embodiments of like elements.

[0025] 1 illustrates one embodiment of a wireless communication system 100 for triggering an action in response to an event notification corresponding to user equipment. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Those skilled in the art will recognize that although a particular number of remote units 102 and network units 104 are illustrated in FIG. 1, any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0026] In one embodiment, the remote units 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart televisions (e.g., Internet-connected televisions), set-top boxes, game consoles, security systems (including security cameras), vehicle-mounted computers, network devices (e.g., routers, switches, modems), aircraft, drones, etc. In some embodiments, the remote units 102 include wearable devices such as smart watches, fitness bands, optical head-mounted displays, etc. Furthermore, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UEs, user terminals, devices, or other terms used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In particular embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

[0027] The network units 104 may be distributed across a geographic region. In a particular embodiment, the network units 104 may be an access point, access terminal, base, base station, location server, core network ("CN"), radio network entity, Node B, evolved Node B ("eNB"), 5G Node B ("gNB"), home Node B, relay node, device, core network, aeronautical server, radio access node, access point ("AP"), new radio ("NR"), network entity, access and mobility management function ("AMF"), unified data management ("UDM"), unified data repository ("UDR"), UDM / UDR, policy control function ("PCF"), radio access network ("RAN"), network slice selection function ("NSSF"), operations, administration, The network units 104 may also be referred to as and / or include one or more of: Operation and Administration ("OAM"), Session Management Function ("SMF"), User Plane Function ("UPF"), Application Function, Authentication Server Function ("AUSF"), Security Anchor Function ("SEAF"), Trusted Non-3GPP Gateway Function ("TNGF"), Application Function, Service Enabler Architecture Layer ("SEAL") Function, Vertical Application Enabler Server, Edge Enabler Server, Edge Configuration Server, Mobile Edge Computing Platform Function, Mobile Edge Computing Application, middleware entity, or any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is generally communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the Public Switched Telephone Network, among other networks. These and other elements of the radio access network and core network are not shown but are generally well known by those skilled in the art.

[0028] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in the 3rd Generation Partnership Project (“3GPP”), in which the network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”) and the remote unit 102 transmits using a Single Carrier Frequency Division Multiple Access (“SC-FDMA”) scheme or an Orthogonal Frequency Division Multiplexing (“OFDM”) scheme on the uplink (“UL”). More generally, however, the wireless communication system 100 may implement any other open or proprietary communication protocol, such as WiMAX, Institute of Electrical and Electronics Engineers ("IEEE") 802.11 variants, Global System for Mobile Communications ("GSM"), General Packet Radio Service ("GPRS"), Universal Mobile Telecommunications System ("UMTS"), Long Term Evolution ("LTE") variants, Code Division Multiple Access 2000 ("CDMA2000"), Bluetooth, ZigBee, Sigfox, among others. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0029] The network unit 104 may serve several remote units 102 within a serving area, e.g., a cell or a cell sector, via a wireless communication link. The network unit 104 transmits DL communication signals to serve the remote units 102 in the time domain, the frequency domain, and / or the spatial domain.

[0030] In various embodiments, the network unit 104 may receive an event notification from the detection entity, the event notification relating to an adaptation of the behavior of at least one user equipment. In some embodiments, the network unit 104 may determine a trigger action for at least one application of the at least one user equipment in response to receiving the event notification. The trigger action includes an edge supported service modification, an edge supported service cancellation, an edge supported service suspension, a selection of an alternative application server, a creation of a new candidate target application server, or some combination thereof. In particular embodiments, the network unit 104 may send the trigger action to an application entity, a further application enablement entity, or a combination thereof, to perform the trigger action based on the event notification. Thus, the network unit 104 may be used to trigger an action in response to an event notification corresponding to a user equipment.

[0031] In particular embodiments, the network unit 104 may receive a monitoring event from an application, a second network entity, or a combination thereof. In some embodiments, the network unit 104 may determine an event notification related to an adaptation of at least one user equipment behavior in response to receiving the monitoring event. In particular embodiments, the network unit 104 may send the event notification to a further application enablement entity. Thus, the network unit 104 may be used to trigger an action in response to the event notification corresponding to the user equipment.

[0032] 2 illustrates one embodiment of an apparatus 200 that may be used to trigger an action in response to an event notification corresponding to user equipment. The apparatus 200 includes one embodiment of the remote unit 102. Additionally, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined in a single device, such as a touchscreen. In particular embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and / or the display 208.

[0033] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 202 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to implement the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0034] Memory 204, in one embodiment, is a computer-readable storage medium. In some embodiments, memory 204 includes a volatile computer storage medium. For example, memory 204 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 204 includes a non-volatile computer storage medium. For example, memory 204 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and associated data, such as an operating system or other controller algorithms running on remote unit 102.

[0035] The input device 206, in one embodiment, may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touch screen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0036] Display 208, in one embodiment, may include any known electronically controllable display or display device. Display 208 may be designed to output visual, audible, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, a liquid crystal display ("LCD"), a light-emitting diode ("LED") display, an organic light-emitting diode ("OLED") display, a projector, or similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, display 208 may include a wearable display such as a smartwatch, smart glasses, a head-up display, and the like. Furthermore, display 208 may be a component of a smartphone, a personal digital assistant, a television, a tablet computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

[0037] In certain embodiments, the display 208 includes one or more speakers for generating sound. For example, the display 208 may generate audible alerts or notifications (e.g., beeps or chimes). In some embodiments, the display 208 includes one or more haptic devices for generating vibrations, movements, or other haptic feedback. In some embodiments, all or a portion of the display 208 may be integrated with the input device 206. For example, the input device 206 and the display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206.

[0038] Although only one transmitter 210 and one receiver 212 are shown, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and receiver 212 may be part of a transceiver.

[0039] 3 illustrates one embodiment of an apparatus 300 that may be used to trigger an action in response to an event notification corresponding to user equipment. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As can be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively. The apparatus 300 also includes a network interface 314 for communication with network devices and an application interface 316 for communication with applications.

[0040] In a particular embodiment, the receiver 312 receives an event notification from the detection entity, the event notification relating to behavioral adaptation of at least one user equipment. In various embodiments, the processor 302 determines a trigger action for at least one application of the at least one user equipment in response to receiving the event notification. The trigger action includes edge support service modification, edge support service cancellation, edge support service suspension, selection of an alternative application server, creation of a new candidate target application server, or some combination thereof. In a particular embodiment, the transmitter 310 transmits the trigger action to an application entity, a further application enablement entity, or a combination thereof, to perform the trigger action based on the event notification. As used herein, an edge support service may be an ACR.

[0041] In some embodiments, the receiver 312 receives the monitoring event from an application, a second network entity, or a combination thereof. In various embodiments, the processor 302 determines an event notification related to adapting at least one user equipment behavior in response to receiving the monitoring event. In particular embodiments, the transmitter 310 transmits the event notification to a further application enablement entity.

[0042] In certain embodiments, planned user equipment ("UE") behavior may change after initiation of edge support services and / or mobile edge computing ("MEC") platform services, and services may need to be modified due to these changes (e.g., due to changes in UE mobility). As used herein, edge support services may refer to edge platform capabilities (e.g., Platform as a Service ("PaaS") and / or Software as a Service ("SaaS")) that provide support for application integration and / or enablement with the underlying network. Such support capabilities may be application service continuity support and / or application context relocation services when a UE migrates to a different edge platform, or dynamic application server instantiation.

[0043] In some embodiments, such as in mobile edge cloud deployments, one aspect may be portability and / or migration of edge applications to different edge application servers (“EAS”) while maintaining edge service continuity.

[0044] In various embodiments, reasons for application client-EAS remapping may be due to: 1) UE mobility, including predictive or expected UE mobility transmitted from an area covered by one EAS to a target area covered by another EAS; 2) overload conditions in the source EAS (“S-EAS”) or edge data network (“EDN”); 3) maintenance aspects (e.g., graceful shutdown of an EAS); 4) expected performance degradation in the source EAS; 5) improving the quality of experience of a UE application (e.g., a gaming application); and 6) application preference for different slices and / or data network names (“DNNs”).

[0045] In some embodiments, when fifth generation (“5G”) is used for communication between edge application servers and clients, such a transition to a different EAS may have implications on the network side to enable application context transfer (e.g., transfer of required application client context (e.g., application client (“AC”) profile, service key performance indicators (“KPIs”)) for the target EAS) without interruption of communication services and without affecting user quality of experience (“QoE”). In such embodiments, the target EAS may be the best candidate based on application requirements.

[0046] In various embodiments, there may be two edge support services to address application portability: an application context resolution ("ACR") service and a dynamic EAS instantiation service.

[0047] In certain embodiments, for ACR services, if the UE moves to a new location, a different EAS may be more suitable to serve the UE. Such transitions may occur as a result of non-mobility events that require support from the edge enabler layer to maintain service continuity. Service continuity support provides several capabilities to minimize application layer service interruptions by replacing the S-EAS connected to the AC in the UE with a target EAS ("T-EAS"). ACR services may be specified in the edge enabler layer ("EEL"), which is a middleware layer between the network and edge applications. The S-EAS may be associated with application context. To support service continuity, application context from the S-EAS may be transferred to the T-EAS.

[0048] In some embodiments, for dynamic EAS instantiation services, the edge enabler layer may interact with an EAS management system to trigger instantiation of a suitable EAS per application needs (e.g., UE mobility). Upon receiving an EAS discovery request with an EAS discovery filter from an edge enabler client (“EEC”) or source edge enabler server (“EES”) (“S-EES”) during a procedure for EAS discovery or ACR, the EES may fail to discover and select an EAS that matches the UE location and requesting application characteristics due to the EAS not being available or instantiated. Based on dynamic EAS instantiation information, where an EAS may be dynamically instantiated in the associated EDN, the EES may trigger the EAS management system to instantiate an EAS that serves the AC in the EDN before returning the EAS information to the EEC or S-EES.

[0049] In certain embodiments, application mobility service support may be defined, and may be part of edge support services, particularly service continuity support, such that service to a user can resume and continue when an application instance becomes available at the target MEC host and, if necessary, user context is transferred to the application instance there. In such services, application mobility enablement and / or registration may be the first step, where this procedure is to enable the application mobility service and allow the application instance to register with the required application mobility service. This may be followed by initiation, preparation, execution, traffic path updates, and cleanup of application and / or user context transfer.

[0050] In some embodiments, expected and / or predicted UE mobility may not be accurate, and the UE may not be at the predicted location at a given time instance. This may be due to various reasons, such as 1) traffic congestion that may delay the UE, 2) inaccurate and / or failed predictions (e.g., there may be a confidence level that may be wrong), 3) changes in UE behavior, direction, and / or speed, and / or 4) incidents (e.g., accidents, platform failures) that require modification of edge services.

[0051] In various embodiments, different scenarios may result in the following: 1) the target UE may not go to the predicted location, so the respective EEL service (e.g., ACR and / or T-EAS instantiation) may need to be canceled to avoid reserving resources in the T-EAS and / or target EDN, 2) the target UE may go to the location later than predicted, so the ACR and / or T-EAS instantiation may need to be maintained even if the UE does not show up on time, or the context may be removed from the T-EAS if not used (e.g., after some time), and / or 3) the target UE may go to the location early, so the ACR and / or T-EAS instantiation may need to be completed early, or there may be a service disruption.

[0052] Particular embodiments may relate to UE behavior changes that may impact edge-enabled services that rely on predicted UE location, and may relate to application portability and / or migration.

[0053] In some embodiments, edge application migration may be supported when the UE location and / or mobility deviates from the predicted UE location and / or mobility (e.g., due to a prediction failure and / or a change in UE behavior). Such embodiments may include: 1) detecting UE location deviation and / or mismatch from the predicted UE location (e.g., this may be detected by monitoring the UE location from the 5GC and / or SEAL or via the UE's AC), detecting events captured by the network or application server, management-triggered events (e.g., performance monitoring (“PM”) and / or fault monitoring (“FM”)), or network-triggered events (e.g., the UE changing the network slice); 2) assessing the need to adapt edge-enabling services related to ACR and / or dynamic EAS instantiation—which may include a cost analysis (e.g., impact on network and / or platform load) to maintain the edge-enabling services—where there may be no impact (e.g., in a low-load scenario), there may be no need to adapt; and 3) determining trigger actions—The actions may include one or more of the following: a) cancellation of edge services related to ACR and / or EAS instantiation, b) suspension of edge services related to ACR and / or EAS instantiation in a given time window and / or area of ​​interest, c) modification and / or early completion of edge services related to ACR and / or EAS instantiation, d) modification and / or late completion of edge services related to ACR and / or EAS instantiation, and / or e) modification and / or change of the target EDN and / or EAS to which the AC is expected to migrate, 4) based on the trigger action type, sending a trigger event report (e.g., including the proposed and / or suggested action) to the decision entity and involved entities (e.g., UE, network entity, application entity) to notify, propose, and / or recommend the trigger action - where the decision entity may be the EES and / or EAS of the source or target edge platform, or the EEC of the target UE, and / or 5) support the decision entity to apply and / or execute the proposed action.

[0054] 4 is a schematic block diagram illustrating one embodiment of a system 400 for triggering an action in response to an event notification corresponding to user equipment. An entity of the system 400 detects 402 the need for AC-EAS remapping (e.g., this can be AC ​​and / or EEC or EES and / or EAS based on the scenario).

[0055] Based on the detection, an entity determines AC-EAS remapping (404) (e.g., this entity can be the EES, EAS, or EEC). Next, EAS discovery 406 occurs (e.g., the EEC identifies available EASs in the target area—dynamic EAS instantiation (e.g., via OAM) 408). In particular, in EEC-based (e.g., UE-centric) scenarios, the EEC determines the target (“T”) EES (“T-EES”) or performs service provisioning procedures by using the provided information. Meanwhile, in EES- and / or EAS-centric scenarios, the S-EES and / or EAS discover the best T-EES and / or T-EAS.

[0056] Step 408 may be performed in conjunction with EAS discovery 406. The AC and EEC select 410 a T-EAS to be used for application traffic (or, in an EES- and / or EAS-centric scenario, the T-EAS determination is made via the source and target EAS and / or EES).

[0057] ACR initiation 412 then occurs, which may be via an ACR request from the EEC (and depending on the scenario, involving S-EES and / or EAS, ECS, T-EES and / or EAS, or a subset thereof).

[0058] In response to the ACR initiation 412, there may be detection 414 of an event related to a change in UE behavior (e.g., as in step 402) and evaluation of a situation and decision update 416 based on the event. The decision may include one of canceling, modifying, modifying with a different EAS, and / or pausing the procedure.

[0059] If the decision is to cancel, based on the decision update 416, an ACR Cancel 418 message is sent to the decision making entity and notifications are sent to all involved entities. If an acknowledgement ("ACK") is received, the ACR stops.

[0060] If the decision is to suspend, an ACR Suspend 420 message is sent to the Decision 404 and Execution entity and / or multiple entities (e.g., EES, EAS, EEC, ECS) to inform them of the suspension decision and the time required for the suspension, or under what criteria the ACR will resume (or if the Decision Update 416 entity specifies that the ACR may continue, ACR resumption may follow after some period of time).

[0061] If the decision is to modify, an ACR modification 420 request is sent to the decision 404 and execution entity (or entities) to specify a time offset (e.g., positive or negative based on whether the ACR completes late or early). If a response is successfully received, EEC context relocation 422 occurs.

[0062] If the decision is a modification involving EAS remapping, the entity deciding on the T-EAS selection will need to update its mapping, so the ACR modification 420 request includes a flag indicating the requirement for a change in T-EAS or a proposal for an alternative T-EAS.

[0063] If an alternative T-EAS is not available in the target EDN area, dynamic EAS instantiation is triggered by the decision update 416 entity to the OAM (e.g., a service to instantiate an alternative T-EAS).

[0064] Following the ACR initiation 412 and update, an EEC context relocation 422 occurs from the S-EES to the T-EES. Note that a decision update 416 may also occur after the EEC context relocation 422 but before the ACT 424, which occurs between the S-EAS and the T-EAS. Post-ACR cleanup 426 then occurs (e.g., removal of the context from the S-EES and / or EAS, and notification).

[0065] A first embodiment described herein includes an EEC-based ACR update procedure. This embodiment provides a mechanism for a UE and / or EEC-triggered ACR update. Figure 5 is a timing diagram illustrating a first embodiment of a system 500 for triggering an action in response to an event notification corresponding to user equipment. The system 500 includes an AC 502, an EEC 504, a UE 506 (the AC 502, EEC 504, and UE 506 may be part of the same device), a fifth-generation core network ("5GC") 508 (and / or a service enabler architecture layer ("SEAL") location management server ("LMS")), an S-EES 510 (and / or S-EAS), a T-EES 512 (and / or T-EAS), an ECS 514, a global AS 516, and an alternate ("Alt") T-EES 518 (and / or T-EAS). Note that each of the communications shown may include one or more messages.

[0066] In the first communication 520, ACR is initiated.

[0067] In a second communication 522, the EEC 504 receives from the AC 502 (e.g., via EDGE-5) an indication that the expected and / or predicted UE location and / or mobility will change. Such a message may include the current, new, expected, and / or predicted location (e.g., in coordinates and / or topological locations that may include cells, addresses, etc.), the current and / or new expected mobility, speed, direction, and / or velocity, and / or expected changes in the UE route and / or trajectory (e.g., a Global Positioning System (“GPS”) route update).

[0068] In the third communication 524 and / or optional fourth communication 526, the S-EES 510, acting as the AF, may receive a UE location report (e.g., based on a location service subscription) from the 5GC 508. The UE location report may serve to indicate that the UE 506 will not be in a predicted location at a given time and is expected to deviate from its original location. The S-EES 510 may also receive an application for slicing remapping notification from the 5GC 508, which may affect which EAS to attach to. Such notification may include a target single (“S”) network slicing selection assistance information (“NSSAI”) (“S-NSSAI”) and / or a combination of DNNs.

[0069] In a fifth communication 528 and / or an optional sixth communication 530, the global AS 516 may provide requirements updates to the S-EES 510 and optionally to the T-EES 512 indicating expected changes in application behavior such as service operation, profile changes, and / or adaptations of application attributes (e.g., platoon speed in vehicle-to-everything (“V2X”)) that may affect the ACR.

[0070] In an optional seventh communication 532, the S-EES 510 sends a UE and / or application (“app”) related event report to the EEC 504 based on steps 524, 526, 528, and / or 530, which may provide information about expected UE and / or app behavior changes and indicate how this may affect the ACR. One example is that the UE 506 may be delayed by X seconds in arriving at the target location at a given confidence level.

[0071] The EEC 504 evaluates the need to adapt the edge-enabling services associated with the ACR (534). The EEC 504 then determines (536) actions to cancel, suspend, modify, and / or change the T-EAS based on the evaluation of step 534.

[0072] The first option 538 may include steps 540, 542, 544, and 546. In an eighth communication 540 and / or an optional ninth communication 542, the EEC 504 sends an ACR modification request message. The message may include one or more of the parameters from Table 1. As used herein in the tables, "M" indicates mandatory and "O" indicates optional.

[0073] [Table 1]

[0074] In a tenth communication 544 and / or an optional eleventh communication 546, the EEC 504 receives a response to the ACR modification request from the decision-making and / or execution entity (e.g., one of the EES, EAS, Edge Configuration Server (“ECS”)). This ACR modification response message may include one or more elements from Table 2.

[0075] [Table 2]

[0076] The second option 548 may include steps 550, 552, 554, 556, 558, and 560. In the twelfth communication 550 and / or the optional thirteenth communication 552, the EEC 504 sends an ACR pause request message. This message may include one or more of the parameters from Table 3.

[0077] [Table 3]

[0078] In a fourteenth communication 554 and / or an optional fifteenth communication 556, the EEC 504 receives a response to the ACR pause request from the decision-making and / or execution entity (e.g., the EES, the EAS, the ECS). The ACR pause response message may include one or more elements from Table 4.

[0079] [Table 4]

[0080] In a sixteenth communication 558, the EEC 504, together with the AC 502, indicates that ACR may be resumed after an ACR suspension. The ACR resume request message may include one or more elements from Table 5.

[0081] [Table 5]

[0082] In a seventeenth communication 560, the EEC 504 receives a response to the ACR resume request from a decision and / or enforcement entity (e.g., EES, EAS, ECS). The ACR resume response message may include one or more elements from Table 6.

[0083] [Table 6]

[0084] The third option 562 may include steps 564, 566, 568, and 570. In an eighteenth communication 564 and / or an optional nineteenth communication 566, the EEC 504 sends an ACR cancellation request message. This message may include one or more of the parameters from Table 7.

[0085] [Table 7]

[0086] At a twentieth communication 568 and / or an optional twenty-first communication 570, the EEC 504 receives a response to the ACR cancellation request from the decision-making and / or execution entity (e.g., the EES, the EAS, the ECS). The ACR cancellation response message may include one or more of the elements in Table 8.

[0087] [Table 8]

[0088] A fourth option 572 may include steps 574, 576, 578, 580, 582, 584, and 586. The AC 502 and EEC 504 select a new T-EAS to be used for the application traffic (e.g., based on an ACR adaptation trigger for changing the target EAS), and optionally a new T-EES (e.g., Alt T-EES 518) corresponding to the new T-EAS (574). Such a T-EES 518 may be in the same or a different EDN.

[0089] In a twenty-second communication 576, an optional twenty-third communication 578, and / or an optional twenty-fourth communication 580, the EEC 504 sends an EAS and / or EES modification request message to one or more of the executing entities (e.g., EES, EAS, ECS). This message may include one or more of the parameters in Table 9.

[0090] [Table 9A]

[0091] [Table 9B]

[0092] In a twenty-fifth communication 582, an optional twenty-sixth communication 584, and / or an optional twenty-seventh communication 586, the EEC 504 receives a response to the EES and / or EAS modification request from the decision-making and / or execution entity (e.g., EES, EAS, ECS). The EES and / or EAS modification response message may include one or more elements from Table 10.

[0093] [Table 10]

[0094] In some embodiments, in the twenty-eighth communication 588, the EEC 504 notifies the AC 502 of the results of the ACR modification, cancellation, and / or EES-EAS change.

[0095] In a twenty-ninth communication 590, the S-EES 510 and / or T-EES 512 notifies the S-EAS and / or T-EAS of the results of the ACR modification, cancellation, and / or EES-EAS change.

[0096] A second embodiment described herein includes an EES- and / or EAS-based ACR update procedure. This procedure may include implementing EAS- and / or EES-triggered changes. Figure 6 is a timing diagram illustrating a second embodiment of a system 600 for triggering an action in response to an event notification corresponding to user equipment. The system 600 includes an AC 602, an EEC 604, a UE 606 (the AC 602, EEC 604, and UE 606 may be part of the same device), a 5GC 608 (and / or a SEAL LMS), a decision update entity 610, an enforcement entity 612, a global AS 614, and an alternate ("Alt") T-EES 616 (and / or a T-EAS). Note that each of the illustrated communications may include one or more messages.

[0097] In the first communication 618, ACR is initiated.

[0098] In a second communication 620, the EEC 604 receives from the AC 602 (e.g., via EDGE-5) an indication that the expected and / or predicted UE location and / or mobility will change. Such a message may include the current, new, expected, and / or predicted location (e.g., in coordinates and / or topological locations that may include cells, addresses, etc.), the current and / or new expected mobility, speed, direction, and / or velocity, and / or expected changes to the UE route and / or trajectory (e.g., a GPS route update).

[0099] In the third communication 622 and / or optional fourth communication 624, the decision update entity 610 acting as an AF (e.g., S-EES, S-EAS, T-EES based on the scenario) may receive a UE location report (e.g., based on a location service subscription) from the 5GC 608. The UE location report may serve to indicate that the UE 606 will not be in a predicted location at a given time and is expected to deviate from its original location. The decision update entity 610 may also receive an application for slicing remapping notification from the 5GC 608, which may affect which EAS to attach to. Such a notification may include a combination of a target S-NSSAI and / or a DNN.

[0100] In an optional fifth communication 626 and / or sixth communication 628, the global AS 614 may provide a requirements update to the decision update entity 610 indicating expected changes in application behavior such as service operation, profile changes, and / or adaptations of application attributes (e.g., platoon speed in V2X) that may affect the ACR.

[0101] In a seventh communication 630 , the decision update entity 610 receives the predicted UE location report derived by the AC 602 in step 620 .

[0102] The decision updating entity 610 evaluates (632) the need to adapt the edge-enabling services associated with the ACR.

[0103] The decision update entity 610 determines (634) an action to cancel, suspend, modify, and / or change the T-EAS based on the evaluation of step 632.

[0104] In a first option including an eighth communication 636, the decision updating entity 610 sends an ACR modification request and / or instruction message (e.g., between the decision updating entity 610 and the executing entity 612 (or multiple entities)). The message may be similar to the first option 538 of the first embodiment, with one difference being that the requester ID may be an EES identifier (“ID”) (“EESID”) or EAS ID (“EASID”), and the message may include EAS profile information for one or both of the source EAS and target EAS. Also, the message may be an instruction (e.g., rather than a request) for some recipients. The decision updating entity 610 receives a response to the ACR modification request from the executing entity 612. This ACR modification response message may be the same as for the first option 538 of the first embodiment.

[0105] In a second option including a ninth communication 638, the decision updating entity 610 sends an ACR pause request and / or instruction message. The message may be similar to the second option 548 of the first embodiment, with one difference being that the requester ID may be an EESID or EASID and the message may also include EAS profile information for one or both of the source EAS and the target EAS. The message may also be an instruction (e.g., rather than a request) for some recipients. The decision updating entity 610 receives a response to the ACR pause request from the executing entity 612 (e.g., EES, EAS, ECS). The ACR pause response message may be the same as the message of the second option 548 of the first embodiment. The decision updating entity 610 indicates that the ACR may be resumed after the ACR pause. The message may be similar to the second option 548 of the first embodiment, with one difference being that the requester ID may be an EESID or EASID and the message may also include EAS profile information for one or both of the source EAS and the target EAS. The message may also include instructions (e.g., rather than a request) for some recipients. The decision updating entity 610 receives a response to the ACR resume request from the executing entity 612 (e.g., EES, EAS, ECS). This ACR resume response message may be the same as the message of the second option 548 in the first embodiment.

[0106] In a third option, including a tenth communication 640, the decision updating entity 610 sends an ACR cancellation request message to the executing entity 612 (e.g., or multiple executing entities) and receives an ACR cancellation response. The message may be similar to the message of the third option 562 of the first embodiment. Also, the message may include instructions (e.g., rather than a request) for some recipients.

[0107] A fourth option 641 may include steps 642, 644, 646, 648, 650, and 652. The decision updating entity 610 may select a new T-EAS to be used for the application traffic (e.g., based on an ACR adaptation trigger for changing the target EAS) and optionally an alternative T-EES 616 corresponding to the new T-EAS (642). The T-EES 616 may be in the same or a different EDN.

[0108] In an eleventh communication 644 and / or a twelfth communication 646, the decision updating entity 610 sends an EAS and / or EES modification request message to the executing entity 612 (e.g., one or more of the EES, EAS, and ECS), and optionally to the EEC and / or AC. Following this, in a thirteenth communication 648 and / or a fourteenth communication 650, the decision updating entity 610 receives a response to the EES and / or EAS modification request from the deciding and / or executing entity 612. These messages may be similar to the message of the fourth option 572 of the first embodiment, except that a requester ID, which may be an EESID or EASID, may be added, and the message may also include EAS profile information for one or both of the source EAS and target EAS. The message may also include instructions (e.g., rather than a request) for some recipients. In an optional fifteenth communication 652, one or more T-EAS reselection complete messages may be sent.

[0109] In an optional sixteenth communication 654, the decision update entity 610 sends a notification message about the decision regarding the ACR modification, cancellation, and / or EES-EAS change to the AC 602 via the EEC 604 (or directly). This notification message may include the ACR ID, the session ID, the type of ACR update, the expected suspension time if it is a suspension, the ID, endpoint, and / or address of the T-EAS if it is a T-EAS change, and / or the authorization information capabilities, ID, and / or address of the new EAS in the case of a newly instantiated T-EAS.

[0110] In an optional seventeenth communication 656, the EEC 604 may also notify the AC 602 of the update. In an eighteenth communication 658, the decision update entity 610 notifies the S-EAS and / or T-EAS of the results of the ACR modification, cancellation, and / or EES-EAS change.

[0111] 7 is a flowchart diagram illustrating one embodiment of a method 700 for triggering an action in response to an event notification corresponding to user equipment. In some embodiments, method 700 is performed by an apparatus such as network unit 104. In particular embodiments, method 700 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0112] In various embodiments, method 700 includes receiving 702 an event notification from a detection entity, the event notification relating to adaptation of behavior of at least one user equipment. In some embodiments, method 700 includes determining 704 a trigger action for at least one application of the at least one user equipment in response to receiving the event notification. The trigger action includes edge supported service modification, edge supported service cancellation, edge supported service suspension, selection of an alternative application server, creation of a new candidate target application server, or some combination thereof. In particular embodiments, method 700 includes sending 706 the trigger action to an application entity, a further application enablement entity, or a combination thereof, to perform the trigger action based on the event notification.

[0113] In particular embodiments, the event notification includes at least one parameter that is expected to change, the at least one parameter including: an expected mobility of the at least one user equipment, a predicted mobility of the at least one user equipment, an expected location of the at least one user equipment, a predicted location of the at least one user equipment, an expected speed change of the at least one user equipment, a predicted speed change of the at least one user equipment, an expected direction of the at least one user equipment, a predicted direction of the at least one user equipment, a change in service profile of at least one application of the at least one user equipment, a change in service operation of at least one application of the at least one user equipment, a confidence level of the predicted user equipment behavior, an expected quality of service of the at least one user equipment, an expected quality of service of the network device, a predicted quality of service of the at least one user equipment, a predicted quality of service of the network device, or some combination thereof.

[0114] In some embodiments, the event notification further includes a network failure, a network interface failure, an application interface failure, an edge data network unavailability indication, an edge data network failure indication, or some combination thereof. In various embodiments, the edge supported service modification includes a request to an application entity, the request including an application identifier, a user equipment identifier, an edge supported service modification type flag, an edge supported service session identifier, an application context transfer start time, an application context transfer completion time, an edge enabler client context relocation start time, an edge enabler client context relocation completion time, a target edge application server identifier, a target edge application server address, an edge enabler server identifier, an edge enabler server address, a target single network slice selection assistance information, a target data network name, a prediction timer update for each event notification, a time range update for each event notification, or some combination thereof.

[0115] In one embodiment, the edge supported service suspension includes a request to an application entity, the request including an application identifier, a user equipment identifier, an edge supported service session identifier, an event notification suspension start time, an event notification suspension end time, an event notification suspension time duration, an event notification completion time, an application context transfer completion time, an edge enabler client context relocation suspension start time, an edge enabler client context relocation end time, a target edge application server identifier, a target edge application server address, an edge enabler server identifier, an edge enabler server address, a prediction timer update for each event notification, a time range update for each event notification, or some combination thereof. In a particular embodiment, method 700 further includes sending an event notification resume trigger action to notify the application entity that event notifications are required to resume.

[0116] In some embodiments, the network entity comprises an application enablement entity. In various embodiments, the application enablement entity comprises an edge enabler client or an edge enabler server. In one embodiment, the application enablement entity is configured to control edge application service continuity for at least one application.

[0117] In certain embodiments, method 700 further includes transmitting the trigger action to an application entity, a further application enablement entity, or a combination thereof, for performing the trigger action based on the event notification. In some embodiments, method 700 further includes converting the trigger action into at least one edge service parameter for an application service of the at least one application of the at least one user equipment.

[0118] In various embodiments, the method 700 further includes determining, based on the trigger action, an update to the edge enabler client context relocation parameter, an application context corresponding to the edge enabler client context relocation parameter, or a combination thereof. In one embodiment, the method 700 further includes triggering, based on the trigger action, dynamic edge application server instantiation, proactive edge application server instantiation, or a combination thereof.

[0119] 8 is a flowchart diagram illustrating another embodiment of a method 800 for triggering an action in response to an event notification corresponding to user equipment. In some embodiments, the method 800 is performed by an apparatus such as the network unit 104. In particular embodiments, the method 800 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0120] In various embodiments, method 800 includes receiving 802 a monitoring event from an application, a second network entity, or a combination thereof. In some embodiments, method 800 includes determining 804 an event notification related to adaptation of at least one user equipment behavior in response to receiving the monitoring event. In particular embodiments, method 800 includes sending 806 the event notification to a further application enablement entity.

[0121] In particular embodiments, the network entity comprises an application enablement entity, hi some embodiments, the application enablement entity comprises an application client, an edge enabler client, an edge enabler server, or an edge configuration server.

[0122] In various embodiments, the application enablement entity is configured to detect changes in user equipment behavior. In one embodiment, the monitored events include changes in user equipment mobility, changes in user equipment location, changes in application behavior, changes in network conditions in the target edge service area, network failures in the target area, or some combination thereof.

[0123] In one embodiment, an apparatus comprises a network entity, the apparatus further comprising: a receiver that receives, from a detection entity, an event notification related to adaptation of a behavior of at least one user equipment, a processor that determines, in response to receiving the event notification, a trigger action for at least one application of the at least one user equipment, the trigger action including edge-supported service modification, edge-supported service cancellation, edge-supported service suspension, selection of an alternative application server, creation of a new candidate target application server, or some combination thereof, and a transmitter that transmits the trigger action to an application entity, a further application enablement entity, or a combination thereof, for performing the trigger action based on the event notification.

[0124] In particular embodiments, the event notification includes at least one parameter that is expected to change, the at least one parameter including: an expected mobility of the at least one user equipment, a predicted mobility of the at least one user equipment, an expected location of the at least one user equipment, a predicted location of the at least one user equipment, an expected speed change of the at least one user equipment, a predicted speed change of the at least one user equipment, an expected direction of the at least one user equipment, a predicted direction of the at least one user equipment, a change in service profile of at least one application of the at least one user equipment, a change in service operation of at least one application of the at least one user equipment, a confidence level of the predicted user equipment behavior, an expected quality of service of the at least one user equipment, an expected quality of service of the network device, a predicted quality of service of the at least one user equipment, a predicted quality of service of the network device, or some combination thereof.

[0125] In some embodiments, the event notification further includes a network failure, a network interface failure, an application interface failure, an edge data network unavailability indication, an edge data network failure indication, or some combination thereof.

[0126] In various embodiments, the edge supported service modification includes a request to an application entity, the request including an application identifier, a user equipment identifier, an edge supported service modification type flag, an edge supported service session identifier, an application context transfer start time, an application context transfer completion time, an edge enabler client context relocation start time, an edge enabler client context relocation completion time, a target edge application server identifier, a target edge application server address, an edge enabler server identifier, an edge enabler server address, a target single network slice selection assistance information, a target data network name, a prediction timer update per event notification, a time range update per event notification, or some combination thereof.

[0127] In one embodiment, the edge supported service pause includes a request to an application entity, the request including an application identifier, a user equipment identifier, an edge supported service session identifier, an event notification pause start time, an event notification pause end time, an event notification pause time duration, an event notification completion time, an application context transfer completion time, an edge enabler client context relocation pause start time, an edge enabler client context relocation end time, a target edge application server identifier, a target edge application server address, an edge enabler server identifier, an edge enabler server address, a prediction timer update for each event notification, a time range update for each event notification, or some combination thereof.

[0128] In a particular embodiment, the transmitter sends an event notification resume trigger action to notify the application entity that event notifications are required to resume.

[0129] In some embodiments, the network entity comprises an application enablement entity.

[0130] In various embodiments, the application enablement entity comprises an edge enabler client or an edge enabler server.

[0131] In one embodiment, the application enablement entity is configured to control edge application service continuity for at least one application.

[0132] In certain embodiments, the transmitter transmits the trigger action to an application entity, a further application enablement entity, or a combination thereof, to perform the trigger action based on the event notification.

[0133] In some embodiments, the processor translates the trigger action into at least one edge service parameter for an application service of the at least one application of the at least one user equipment.

[0134] In various embodiments, the processor determines, based on the trigger action, an update to the edge enabler client context relocation parameter, an application context corresponding to the edge enabler client context relocation parameter, or a combination thereof.

[0135] In one embodiment, the processor triggers dynamic edge application server instantiation, proactive edge application server instantiation, or a combination thereof based on the trigger action.

[0136] In one embodiment, the method of the network entity includes receiving, from the detection entity, an event notification related to adaptation of behavior of at least one user equipment; determining, in response to receiving the event notification, a trigger action for at least one application of the at least one user equipment, wherein the trigger action includes edge supported service modification, edge supported service cancellation, edge supported service suspension, selection of an alternative application server, creation of a new candidate target application server, or some combination thereof; and sending the trigger action to an application entity, a further application enablement entity, or a combination thereof, to perform the trigger action based on the event notification.

[0137] In particular embodiments, the event notification includes at least one parameter that is expected to change, the at least one parameter including: an expected mobility of the at least one user equipment, a predicted mobility of the at least one user equipment, an expected location of the at least one user equipment, a predicted location of the at least one user equipment, an expected speed change of the at least one user equipment, a predicted speed change of the at least one user equipment, an expected direction of the at least one user equipment, a predicted direction of the at least one user equipment, a change in service profile of at least one application of the at least one user equipment, a change in service operation of at least one application of the at least one user equipment, a confidence level of the predicted user equipment behavior, an expected quality of service of the at least one user equipment, an expected quality of service of the network device, a predicted quality of service of the at least one user equipment, a predicted quality of service of the network device, or some combination thereof.

[0138] In some embodiments, the event notification further includes a network failure, a network interface failure, an application interface failure, an edge data network unavailability indication, an edge data network failure indication, or some combination thereof.

[0139] In various embodiments, the edge supported service modification includes a request to an application entity, the request including an application identifier, a user equipment identifier, an edge supported service modification type flag, an edge supported service session identifier, an application context transfer start time, an application context transfer completion time, an edge enabler client context relocation start time, an edge enabler client context relocation completion time, a target edge application server identifier, a target edge application server address, an edge enabler server identifier, an edge enabler server address, a target single network slice selection assistance information, a target data network name, a prediction timer update per event notification, a time range update per event notification, or some combination thereof.

[0140] In one embodiment, the edge supported service pause includes a request to an application entity, the request including an application identifier, a user equipment identifier, an edge supported service session identifier, an event notification pause start time, an event notification pause end time, an event notification pause time duration, an event notification completion time, an application context transfer completion time, an edge enabler client context relocation pause start time, an edge enabler client context relocation end time, a target edge application server identifier, a target edge application server address, an edge enabler server identifier, an edge enabler server address, a prediction timer update for each event notification, a time range update for each event notification, or some combination thereof.

[0141] In a particular embodiment, the method further includes sending an event notification resume trigger action to notify the application entity that event notifications are required to resume.

[0142] In some embodiments, the network entity comprises an application enablement entity.

[0143] In various embodiments, the application enablement entity comprises an edge enabler client or an edge enabler server.

[0144] In one embodiment, the application enablement entity is configured to control edge application service continuity for at least one application.

[0145] In certain embodiments, the method further includes sending the trigger action to an application entity, a further application enablement entity, or a combination thereof, for executing the trigger action based on the event notification.

[0146] In some embodiments, the method further includes converting the trigger action into at least one edge service parameter for an application service of the at least one application of the at least one user equipment.

[0147] In various embodiments, the method further includes determining, based on the trigger action, an update to the edge enabler client context relocation parameter, an application context corresponding to the edge enabler client context relocation parameter, or a combination thereof.

[0148] In one embodiment, the method further includes triggering dynamic edge application server instantiation, proactive edge application server instantiation, or a combination thereof based on the trigger action.

[0149] In one embodiment, an apparatus comprises a first network entity, the apparatus further comprising: a receiver for receiving monitoring events from an application, a second network entity, or a combination thereof, a processor for determining an event notification related to adaptation of at least one user equipment behavior in response to receiving the monitoring events, and a transmitter for transmitting the event notification to a further application enablement entity.

[0150] In a particular embodiment, the network entity comprises an application enablement entity.

[0151] In some embodiments, the application enablement entity comprises an application client, an edge enabler client, an edge enabler server, or an edge configuration server.

[0152] In various embodiments, the application enablement entity is configured to detect changes in user equipment behavior.

[0153] In one embodiment, the monitored events include a change in user equipment mobility, a change in user equipment location, a change in application behavior, a change in network conditions in the target edge service area, a network failure in the target area, or some combination thereof.

[0154] In one embodiment, the method of the first network entity includes receiving a monitoring event from an application, a second network entity, or a combination thereof; determining an event notification related to adaptation of a behavior of the at least one user equipment in response to receiving the monitoring event; and transmitting the event notification to a further application enablement entity.

[0155] In a particular embodiment, the network entity comprises an application enablement entity.

[0156] In some embodiments, the application enablement entity comprises an application client, an edge enabler client, an edge enabler server, or an edge configuration server.

[0157] In various embodiments, the application enablement entity is configured to detect changes in user equipment behavior.

[0158] In one embodiment, the monitored events include a change in user equipment mobility, a change in user equipment location, a change in application behavior, a change in network conditions in the target edge service area, a network failure in the target area, or some combination thereof.

[0159] The embodiments may be embodied in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are intended to be embraced within their scope. [Explanation of symbols]

[0160] 100 Wireless Communication System 102 Remote Unit 104 Network Unit 200 equipment 202 processors 204 memory 206 Input Devices 208 Display 210 Transmitter 212 receiver 300 equipment 302 processor 304 memory 306 Input Devices 308 Display 310 Transmitter 312 Receiver 314 Network Interface 316 Application Interface 400 System 402 Detected 404 decision 406 EAS Discovery 408 Dynamic EAS Instantiation 410 T-EAS Selection 412 ACR started 414 detected 416 Decision update 418 ACR Cancellation 420 ACR pause, ACR correction 422 EEC Context Relocation 424 ACT 426 Post-ACR Cleanup 500 Systems 502 AC 504 EEC 506 UE 508 5th Generation Core Network, 5GC 510 S-EES 512 T-EES 514 ECS 516 Global AS 518 Alternative T-EES, Alt T-EES 520 First Communication 522 Second Communication 524 Third Communication 526 Fourth Communication 528 Fifth Communication 530 Sixth Communication 532 Seventh Communication 538 First Option 540 Eighth Communication 542 Ninth Communication 544 10th Communication 546 11th Communication 548 Second Option 550 12th Communication 552 13th Communication 554 14th Communication 556 15th Communication 558 16th Communication 560 17th Communication 562 Third Option 564 18th Communication 566 19th Communication 568 20th Communication 570 21st Communication 572 Fourth Option 576 22nd Communication 578 23rd Communication 580 24th Communication 582 25th Communication 584 26th Communication 586 27th Communication 588 28th Communication 590 29th Communication 600 System 602 AC 604 EEC 606 UE 608 5GC 610 Decision Update Entity 612 Execution Entity 614 Global AS 616 Alternative T-EES 618 First Communication 620 Second Communication 622 Third Communication 624 Fourth Communication 626 Fifth Communication 628 Sixth Communication 630 Seventh Communication 636 Eighth Communication 638 Ninth Communication 640 Tenth Communication 641 Fourth Option 644 11th Communication 646 12th Communication 648 13th Communication 650 14th Communication 652 15th Communication 654 16th Communication 656 17th Communication 658 18th Communication 700 methods 800 ways

Claims

1. 1. An apparatus for performing network functions, comprising: At least one memory; at least one processor coupled to the at least one memory, the at least one processor comprising: receiving, from a detection entity, an event notification relating to adaptation of a behavior of at least one user equipment (UE); and determining a trigger action for at least one application of the at least one UE in response to receiving the event notification, the trigger action comprising: ACR Service Modification, ACR service cancellation, ACR service suspended, Selection of an alternative application server, Create a new candidate target application server, or combinations of these determining, sending the trigger action to an application entity, a further application enablement entity, or a combination thereof, for executing the trigger action based on the event notification; and causing the device to: The ACR service modification includes a request to an application entity, the request comprising: application identifier, UE identifier, ACR service modification type flag, ACR service session identifier, Application context transfer start time, Application context transfer completion time, Edge Enabler Client Context Relocation Start Time, Edge Enabler Client Context Relocation Completion Time, a target edge application server identifier; target edge application server address, Edge Enabler Server Identifier, Edge Enabler Server Address, Target single network slice selection support information, Target Data Network Name, Update of the prediction timer for each event notification, Update time range for each event notification, or a combination thereof Including, Device.

2. The event notification includes at least one parameter that is expected to change, the at least one parameter comprising: the expected mobility of the at least one UE; a predicted mobility of the at least one UE; an expected location of the at least one UE; a predicted location of the at least one UE; an expected speed change of the at least one UE; a predicted speed change of the at least one UE; an expected direction of the at least one UE; a predicted direction of the at least one UE; changing a service profile of the at least one application of the at least one UE; changing a service operation of the at least one application of the at least one UE; the confidence level of the predicted UE behavior; an expected quality of service for the at least one UE; the expected quality of service of the network device; a predicted quality of service for the at least one UE; a predicted quality of service of the network device; or a combination thereof The apparatus of claim 1 , comprising:

3. The apparatus of claim 1 , wherein the event notification further comprises a network failure, a network interface failure, an application interface failure, an edge data network unavailability indication, an edge data network failure indication, or a combination thereof.

4. The ACR service suspension includes a request to the application entity, the request comprising: application identifier, UE identifier, ACR service session identifier, Event notification suspension start time, Event notification pause end time, Event notification pause time duration, Event notification completion time, Application context transfer completion time, Edge Enabler Client Context Relocation Pause Start Time, Edge Enabler Client Context Relocation End Time, a target edge application server identifier; target edge application server address, Edge Enabler Server Identifier, Edge Enabler Server Address, Update of the prediction timer for each event notification, Update time range for each event notification, or a combination thereof The apparatus of claim 1 , comprising:

5. 5. The apparatus of claim 4, wherein the at least one processor is configured to cause the apparatus to send an event notification resume trigger action to notify the application entity that the event notifications are required to resume.

6. The apparatus of claim 1 , wherein the network function comprises an application enablement entity.

7. The apparatus of claim 6 , wherein the application enablement entity comprises an edge enabler client or an edge enabler server.

8. The apparatus of claim 6 , wherein the application enablement entity is configured to control edge application service continuity for the at least one application.

9. 2. The apparatus of claim 1, wherein the at least one processor is configured to cause the apparatus to send the trigger action to the application entity, the further application enablement entity, or the combination thereof, to execute the trigger action based on the event notification.

10. 2. The apparatus of claim 1, wherein the at least one processor is configured to cause the apparatus to convert the trigger action into at least one edge service parameter for an application service of the at least one application of the at least one UE.

11. 2. The device of claim 1, wherein the at least one processor is configured to cause the device to determine, based on the trigger action, an update to an edge enabler client context relocation parameter, an application context corresponding to the edge enabler client context relocation parameter, or a combination thereof.

12. 10. The apparatus of claim 1, wherein the at least one processor is configured to cause the apparatus to trigger dynamic edge application server instantiation, proactive edge application server instantiation, or a combination thereof based on the trigger action.

13. 1. A method for performing a network function, comprising: receiving, from a detection entity, an event notification relating to adaptation of a behavior of at least one user equipment (UE); determining a trigger action for at least one application of the at least one UE in response to receiving the event notification, the trigger action comprising: ACR Service Modification, ACR service cancellation, ACR service suspended, Selection of an alternative application server, Create a new candidate target application server, or combinations of these and sending the trigger action to an application entity, a further application enablement entity, or a combination thereof, for executing the trigger action based on the event notification; Including, The ACR service modification includes a request to an application entity, the request comprising: application identifier, UE identifier, ACR service modification type flag, ACR service session identifier, Application context transfer start time, Application context transfer completion time, Edge Enabler Client Context Relocation Start Time, Edge Enabler Client Context Relocation Completion Time, a target edge application server identifier; target edge application server address, Edge Enabler Server Identifier, Edge Enabler Server Address, Target single network slice selection support information, Target Data Network Name, Update of the prediction timer for each event notification, Update time range for each event notification, or a combination thereof Including, method.

14. The event notification includes at least one parameter that is expected to change, the at least one parameter comprising: the expected mobility of the at least one UE; a predicted mobility of the at least one UE; an expected location of the at least one UE; a predicted location of the at least one UE; an expected speed change of the at least one UE; a predicted speed change of the at least one UE; an expected direction of the at least one UE; a predicted direction of the at least one UE; changing a service profile of the at least one application of the at least one UE; changing a service operation of the at least one application of the at least one UE; the confidence level of the predicted UE behavior; an expected quality of service for the at least one UE; the expected quality of service of the network device; a predicted quality of service for the at least one UE; a predicted quality of service of the network device; or a combination thereof 14. The method of claim 13, comprising:

15. The event notification further comprises a network failure, a network interface failure, an application interface failure, an edge data network unavailability indication, an edge data network failure indication, or a combination thereof. The method of claim 13.

16. The ACR service suspension includes a request to the application entity, the request comprising: application identifier, UE identifier, ACR service session identifier, Event notification suspension start time, Event notification pause end time, Event notification pause time duration, Event notification completion time, Application context transfer completion time, Edge Enabler Client Context Relocation Pause Start Time, Edge Enabler Client Context Relocation End Time, a target edge application server identifier; target edge application server address, Edge Enabler Server Identifier, Edge Enabler Server Address, Update of the prediction timer for each event notification, Update time range for each event notification, or a combination thereof Including, The method of claim 13.

Images