ACR selection and coordination
Through collaborative work between mobile communication devices and network nodes, using ACR selection and coordination functions, the problem of complexity of application context relocation management is solved, seamless service continuity and mobility management are achieved, and mobile communication devices are improved stability and performance.
Patent Information
- Application Number
- CN202380034374.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-18
- Filing Date
- 2023-03-17
- Publication Date
- 2024-11-26
AI Technical Summary
The prior art is difficult to effectively manage and coordinate the application context relocation of mobile communication devices between different network nodes, resulting in complex service continuity and mobility management.
Provides a system and method to determine and manage appropriate ACR procedures through collaborative work between the processor and the wireless sending/receiving unit (WTRU) and network nodes, using application context relocation (ACR) selection and coordination functions, ensuring that Service continuity and mobility management are smoothly carried out.
It realizes seamless application context relocation between different network nodes, improves service continuity and mobility management efficiency, and ensures the stability and performance of mobile communication devices.
Smart Images

Figure CN119032555A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 321,329, filed on March 18, 2022, the contents of which are hereby incorporated by reference into this document. Background Art
[0003] Mobile communications using wireless communications continue to evolve. The fifth generation of mobile communications radio access technology (RAT) may be referred to as 5G New Radio (NR). Previous generation (legacy) mobile communications RAT may be, for example, fourth generation (4G) Long Term Evolution (LTE). Summary of the invention
[0004] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be performed by a processor (e.g., the processor may be configured to perform the method). And the processor may be associated with a device such as a wireless transmit / receive unit (WTRU). Configuration information associated with one or more of a first network node, a second network node, and an application client (AC) may be received. The configuration information may be used to determine the first network node and the second network node. The second network node may provide a service and may be associated with the first network node. One or more application context relocation (ACR) procedures for providing continuity for the service may be determined. These procedures may be based on WTRU capabilities, first network node capabilities, and second network node capabilities. A selection request message may be transmitted to the first network node. The selection request message indicates an identifier of the second network node, a WTRU identifier, and one or more ACR procedures determined. A selection response message may be received from the first network node. The message may indicate a request processing status result.
[0005] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be performed by a processor (e.g., the processor may be configured to perform the method). And the processor may be associated with a device such as a first network node. A selection request message may be received from a WTRU. The selection request message may indicate one or more ACR procedures, a second network node identifier, and a WTRU identifier. The second network node identifier may be used to determine that the second network node has subscribed to receive selection notifications. The WTRU identifier may be used to determine that the WTRU may be authorized to communicate with the second network node. A notification message may be transmitted to the second network node, the notification message may indicate one or more ACR procedures requested. A selection response message indicating a request processing status result may be transmitted to the WTRU.
[0006] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be performed by a processor (e.g., the processor may be configured to perform the method). And the processor may be associated with a device such as a wireless transmit / receive unit (WTRU). Configuration information associated with at least an application client (AC) may be received. The configuration information may be used to determine a first network node and a second network node. The second network node may be associated with the first network node. A selection request message may be transmitted to the first network node. The selection request message may indicate a request for an application context relocation (ACR) procedure from the first network node. The selection request message may indicate service continuity support information associated with the WTRU. A selection response message may be received from the first network node. The selection response message may indicate one or more ACR procedures that may be supported by the WTRU.
[0007] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be performed by a processor (e.g., the processor may be configured to perform the method). And the processor may be associated with a device such as a first network node. A selection request message may be received from a wireless transmit / receive unit (WTRU). The selection request message may request selection of an application context relocation (ACR) procedure and may indicate service continuity capability information associated with the WTRU. One or more ACR procedures for providing continuity for a service may be selected based on service continuity capability information associated with the WTRU, the first network node, and the second network node. A list may be determined based on the selected one or more ACR procedures. The list may include at least one or more selected ACR procedures. The selected one or more ACR procedures may be compatible with one or more of the WTRU, the application client (AC) of the WTRU, the edge enabler client (EEC) of the WTRU, the first network node, or the second network node. A selection response message indicating the list may be transmitted to the WTRU.
[0008] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be executed by a processor (e.g., the processor may be configured to execute the method). And the processor may be associated with a device such as a wireless transmit / receive unit (WTRU). When an application context relocation (ACR) event may be detected, a first ACR coordination message may be transmitted to a first network node. The ACR event may be detected according to an ACR procedure. A second ACR coordination message may be received from the first network node. An ACR execution message may be generated based on the second ACR coordination message. The ACR execution message may be generated according to the ACR procedure. The ACR execution message may be transmitted to at least one of the first network node or the second network node.
[0009] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be performed by a processor (e.g., the processor may be configured to perform the method). And the processor may be associated with a device such as a first network node. A first application context relocation (ACR) coordination message may be received from at least one of a wireless transmit / receive unit (WTRU) or a second network node. An entity for performing an ACR procedure may be determined. The entity may be one of the first network node, the second network node, or the WTRU. A first coordination decision may be determined based on an identifier of the determined entity and the WTRU. A second coordination decision may be determined based on an identifier of the determined entity and the second network node. A second ACR coordination message may be transmitted to the WTRU. The second ACR coordination message may indicate the first coordination decision. A third ACR coordination message may be transmitted to the second network node. The third ACR coordination message may indicate the second coordination decision.
[0010] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. An ACR selection function (ASF) may be used to select, communicate, and / or manage ACR procedures for service continuity between an edge application server and an application client on a WTRU (wireless transmit / receive unit). An entity (e.g., an EEC or EES) may act as an ASF. Acting as an ASF may include one or more of the following: selecting ACR procedures that can be used for AC and EAS pairs and generating an ACR-detection-decision list (e.g., an ACR list, an ACR identifier, and / or an ACR valid area); selecting an ACF entity when more than one ACR procedure is selected; communicating and / or transmitting an ASF decision (e.g., an ACR-detection-decision list and / or an ACF entity identifier) to other entities (e.g., EEC, EES, and / or EAS); or re-evaluating the selected ACR procedure when selection criteria and / or inputs (e.g., WTRU location, WTRU planned route, WTRU mobility analysis, neighboring EDN ACR capabilities) change.
[0011] When ACR procedures (e.g., concurrent ACR procedures) are used for service continuity between an edge application server and an application client on a WTRU, an ACR coordination function (ACF) may be used to gate ACR execution. An entity (e.g., an EEC or EES) may act as an ACF. Acting as an ACR coordination function (ACF) may include one or more of the following: receiving a request from an entity (e.g., an EEC, an EES, and / or an EAS). The request may indicate that ACR is used (e.g., required) and may request permission to execute the ACR procedure; or transmitting a response to the requesting entity to indicate whether the ACR procedure may be executed. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented.
[0013] Figure 1B is an example of a method that can be used according to an embodiment of the present invention. Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within an example communication system.
[0014] Figure 1C is an example of a method that can be used according to an embodiment of the present invention. Figure 1A System diagram of an example Radio Access Network (RAN) and an example Core Network (CN) used within an illustrated communication system.
[0015] Figure 1D is an example of a method that can be used according to an embodiment of the present invention. Figure 1A System diagram of another example RAN and another example CN for use within the illustrated communication system.
[0016] Figure 2 An example of a SA6 architecture for enabling edge applications is shown.
[0017] Figure 3 An example of a brief overview of Application Context Relocation (ACR) is shown.
[0018] Figure 4 An example of a brief overview of application context relocation with ACR selection functionality and ACR coordination functionality is shown.
[0019] Figure 5 An example of application context migration with an application context migration (ACT) authorization token is shown.
[0020] Figure 6 An example of an ACR selection function performed by an edge enabler server (EES) is shown.
[0021] Figure 7 An example of an ACR selection function performed by an edge enabler client (EEC) is shown.
[0022] Figure 8 An example of the ACR coordination function performed by the EES is shown.
[0023] Fig. 9 An example of the ACR coordination function performed by the EEC is shown.
[0024] Fig.10 An example of an ACR Selection Function (ASF) and an ACR Coordination Function (ACF) used in combination is shown. DETAILED DESCRIPTION
[0025] Figure 1A 1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.
[0026] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.
[0027] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device that is configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be base transceiver stations (BTS), Node Bs, eNode Bs, Home Node Bs, Home eNode Bs, gNBs, NR Node Bs, site controllers, access points (APs), wireless routers, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0028] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send and / or receive wireless signals on one or more carrier frequencies (which may be referred to as cells (not shown)). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrums. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.
[0029] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).
[0030] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and / or High Speed UL Packet Access (HSUPA).
[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).
[0032] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using New Radio (NR).
[0033] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may together implement LTE radio access and NR radio access, for example using the dual connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).
[0034] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.
[0035] Figure 1AThe base station 114b in the may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in local areas such as commercial venues, homes, vehicles, campuses, industrial facilities, sky corridors (e.g., for use by drones), roads, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or a femtocell. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.
[0036] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Although not described in detail in the text, the CN 106 / 115 may be configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Figure 1A Although not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
[0037] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.
[0038] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
[0039] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0040] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0041] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from the base station via an air interface 116. For example, in one embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In an embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, an IR, UV or visible light signal. In another embodiment, the send / receive element 122 may be configured to send and / or receive both an RF signal and an optical signal. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.
[0042] Although the transmit / receive element 122 Figure 1B 1 as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
[0043] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.
[0044] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
[0045] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.
[0046] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.
[0047] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. Peripheral device 138 may include one or more sensors, which may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.
[0048] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via signal processing performed via hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.
[0049] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.
[0050] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.
[0051] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.
[0052] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements is depicted as being part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0053] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.
[0054] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.
[0055] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0056] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.
[0057] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communication interface with a communication network.
[0058] In a representative embodiment, the other network 112 may be a WLAN.
[0059] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the target STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Direct link establishment (DLS) may be used to transmit point-to-point traffic between the source STA and the target STA (e.g., directly between them). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.
[0060] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is listened / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.
[0061] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.
[0062] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by sending STA. At the receiver of the receiving STA, the above-mentioned operation for 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).
[0063] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support instrument type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).
[0064] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only a 1MHz operating mode) is sending to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.
[0065] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.
[0066] Figure 1D 1 is a system diagram illustrating the RAN 113 and the CN 115 in accordance with an embodiment. As noted above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.
[0067] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In an embodiment, gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).
[0068] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths over time).
[0069] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the evolved Node-B 160a, 160b, 160c. For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRU 102a, 102b, 102c.
[0070] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.
[0071] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0072] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.
[0073] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure the traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0074] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.
[0075] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
[0076] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU102a-d, base station 114a-b, evolved Node B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b and / or any other device described herein. The simulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.
[0077] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices may perform one or more functions or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communications to perform testing.
[0078] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which can include one or more antennas) can be used by the simulation device to send and / or receive data.
[0079] References herein to a timer may refer to a time, a time period, tracking a time, tracking a time period, etc. References herein to expiration of a timer may refer to determining that a time has occurred or a time period has expired.
[0080] The application layer may be used to support edge services. As disclosed herein, an application layer may be provided.
[0081] An architecture for enabling one or more edge applications may be provided. Figure 2 An example of a SA6 architecture for enabling edge applications is shown.
[0082] The components of the SA6 architecture can be described with respect to Table 1.
[0083] Table 1—SA6 Edge Enablement Layer (EEL) Entities
[0084]
[0085]
[0086] Data Networks (DNs) and / or Local Area Data Networks (LADNs) may be provided. The system may inform the WTRU of available DNs and may provide information about DN capabilities. A LADN Information Element (IE) may be provided. The LADN Information IE may be a mechanism by which the network conveys to the WTRU a Data Network Name (DNN) and the geographic area where such DNN may be accessible.
[0087] LADN information (e.g., LADN service area information and / or LADN DNN) may be provided to the WTRU by the AMF during a registration procedure or a WTRU configuration update procedure. For a LADN DNN configured in the AMF (e.g., each LADN DNN), the corresponding LADN service area information may include a set of tracking areas belonging to the registration area assigned to the WTRU by the AMF (e.g., the intersection of the LADN service area and the assigned registration area).
[0088] When the WTRU indicates to the AMF that it is capable of receiving LADN information via a registration request, the LADN information may be transmitted by the AMF to the WTRU.
[0089] Service continuity may be provided. For example, the embodiments disclosed herein may provide service continuity.
[0090] If the WTRU moves to a certain location (e.g., a new location), a different EAS and / or EDN may be more suitable for serving the AC in the WTRU. Such mobility transition may result in replacing the EAS in the source EDN (S-EAS) with the EAS in the target EDN (T-EAS).
[0091] Replacing S-EAS with T-EAS may involve a procedure called Application Context Relocation (ACR). Figure 3 A brief algorithm of the 5 ACR procedures is shown.
[0092] ARC available. Figure 3 An example of a brief overview of the ACR is shown.
[0093] The ACR detection and / or ACR decision phases may be performed by different entities according to the ACR procedure. Table 2 may present an overview of the detection entity and / or decision entity. As shown in the table, there may be multiple detection entities and / or decision entities at the same time. In other words, two or more different entities may independently detect that the ACR is being used and may independently decide which procedure may be executed.
[0094] Table 2—Overview of ACR testing and decision making
[0095]
[0096] The ACR execution phase may vary according to the ACR procedure. During the ACR execution phase, the EEL entities may exchange a number of messages shown in Table 3.
[0097] For a given AC and EAS pair, ACR procedures (eg, two or more ACR procedures) may not be performed concurrently because the order and sequence of messages may be incompatible. ACR (eg, a single ACR procedure) may be performed to make the ACR successful.
[0098] Table 3 - ACR Execution Overview
[0099]
[0100]
[0101] ACR post-processing may be similar for ACR protocols (eg, all ACR protocols), as shown in Table 4.
[0102] Table 4—ACR post-processing overview
[0103]
[0104]
[0105] One or more ACR protocols may be provided.
[0106] Table 5 may illustrate that the "ACR performed by EEC via T-EES" ACR procedure (e.g., only the "ACR performed by EEC via T-EES" ACR procedure) may succeed when triggered by WTRU movement into or out of the service area of a data network (e.g., DN or LADN). Other ACR procedures (e.g., all other ACR procedures) may fail when the WTRU moves out of the service area of the source LADN based on the EEC no longer being able to communicate with the S-EES that may reside in the source LADN.
[0107] Table 5 - Failure scenarios for ACR without SCP
[0108]
[0109]
[0110] Service Continuity Planning (SCP) questions may be addressed.
[0111] The SCP may be a variation of the ACR procedure (eg, each ACR procedure) that aims to prepare the target EAS before WTRU mobility involves the ACR.
[0112] Service continuity planning may be defined as an edge enabler layer value added feature that provides support for seamless service continuity, for example, when information about planned, planned and / or expected behavior is available at the EES or provided by the EEC. In service continuity planning, the application context may be replicated and / or transferred from the S-EAS to the T-EAS before the WTRU moves to the intended location.
[0113] Table 6 illustrates that ACR procedures (e.g., all ACR procedures) may fail during ACR execution and / or ACR purge. ACR execution may fail in the case of a planned WTRU movement triggered into the service area of the target LADN based on the EEC being unable to communicate with the T-EES residing in the target LADN. ACR purge may fail in the case of a WTRU movement triggered out of the service area of the source LADN based on the EEC no longer being able to communicate with the S-EES that may reside in the source LADN.
[0114] Table 6 - Failure scenarios for ACR with SCP
[0115]
[0116]
[0117] As described herein, service continuity procedures may be provided.
[0118] ACR scenarios may not support concurrent execution. For example, if multiple ACR scenarios are used concurrently, the edge enabling layer (EEL) entity (e.g., EEC, EES, and / or EAS) may detect and decide to trigger the execution of ACR procedures at the same time. ACR procedures may not support concurrent execution, resulting in undefined behavior, which may cause unsuccessful service continuity for the WTRU.
[0119] In an example, with a LADN use case (e.g., all LADN use cases, such as entering or leaving), no ACR scenario can succeed. For example, a LADN may be a data network with an associated service area. The WTRU may communicate with the LADN when (e.g., only) it is located inside the LADN service area. For example, an ACR scenario without SCP may involve (e.g., require) the WTRU to communicate with the EAS / EES located in the LADN after, for example, the WTRU has left the service area, while an ACR scenario with SCP may involve (e.g., require) the WTRU to communicate with the EAS / EES located in the LADN before the WTRU enters the service area of the LADN. Both of these situations may result in the failure of the ACR procedure and unsuccessful service continuity for the WTRU.
[0120] When executing ACR, an application context may be moved from a first entity (e.g., EES or EAS) to a second entity (e.g., EES or EAS). The security capabilities of the first entity and the second entity may be different. When selecting the ACR procedures to be executed, it may be necessary to coordinate which security procedures should be used to communicate with the second entity (e.g., the target entity), and it may be necessary to exchange security credentials (e.g., tokens, certificates, etc.) with the ACR participant entities.
[0121] The ACR procedure may result in service continuity failure if used concurrently and / or with LADN.
[0122] ACR Selection Function (ASF) may be defined to select the ACR scenario to be used for service continuity. ASF may be represented by 0, such as Figure 4 The output of ASF may be a list of 0 or more ACR procedures, which may be used to perform 1 and 2 and the selection of an ACR coordination function (ACF) when multiple ACR procedures are in the list.
[0123] The list of procedures that can be used for 1 and 2 can be called the ACR-Detection-Decision List.
[0124] Multiple ACR procedures may be executed concurrently at 1 and 2. Multiple ACR procedures may be used concurrently to detect that AC and EAS may involve (e.g., require) ACR, and multiple ACR procedures may be used concurrently to determine that AC and EAS may require ACR. As described herein, an ACR procedure (e.g., a single ACR procedure) may be allowed to proceed to the execution stage in 3.
[0125] When the ASF generates an ACR-detection-decision list including more than one ACR procedure, and when multiple ACR procedures detect and / or decide to execute ACR concurrently, a single ACR procedure may be allowed to reach the execution stage. The gating of ACR execution may be performed by an ACR coordination function (ACF), which may be described herein. An example of ACR selection performed by the ASF may be to inform an ACR decision entity (e.g., EEC, EES, and / or EAS) which ACR procedure can perform detection and decision making. An example of ACR coordination performed by the ACF may be to allow one ACR procedure (e.g., only one ACR procedure) to reach the execution stage.
[0126] If concurrent ACR procedures are used for service continuity (e.g., multiple ACR procedures in an ACR-detection-decision list), an ACF may be defined to coordinate ACR scenario execution. The ACF may be represented by 2.1, such as Figure 4 shown.
[0127] Figure 4 An example of a brief overview of application context relocation with ACR selection functionality and ACR coordination functionality is shown.
[0128] ASF and / or ACF may be used for ACR, as described herein. ASF and ACF may be used concurrently for ACR, as described herein.
[0129] The ASF may be a logical function that may be implemented in a standalone server, or may reside in the EEC, EES, EAS, or any other server portion of the EEL or interact with the EEL.
[0130] The ACF may be a logical function that may be implemented in a standalone server, or may reside in the EEC, EES, EAS, or any other server portion of the EEL or interact with the EEL.
[0131] ASF available.
[0132] The ACR selection function may perform one or more operations to ensure that the EEL entity is consistent with respect to the ACR procedures to be used for a session between an AC residing on the WTRU and an EAS residing in an EDN (eg, a DN or LADN).
[0133] The role of the ASF may include one or more of the following: selecting ACR procedures that can be used for an AC and EAS pair (e.g., each AC and EAS pair) and generating an ACR-detection-decision list; selecting an ACF entity when more than one ACR procedure is selected; communicating the ASF decision (e.g., the ACR-detection-decision list and / or the ACF entity) to the appropriate entity; or re-evaluating the selected ACR procedure when the selection criteria and / or inputs change.
[0134] ACR protocol may be selected.
[0135] ACR procedure selection may be performed by the ASF to determine the ACR-detection-decision list and the ACF entity. The procedure may produce one of the following results: no ACR procedure is selected for the list, a single ACR procedure is selected for the list, or multiple ACR procedures are selected for the list.
[0136] When ACR is not involved (e.g., not required) between the AC and its EAS counterpart or when there is no common ACR procedure supported by the involved EEL entities (e.g., AC, EEC, EES and / or EAS), the ASF may not include the ACR procedure in the ACR-detection-decision list.
[0137] When there is a common ACR procedure (single common ACR procedure) supported by the EEL entities involved (e.g., AC, EEC, EES and / or EAS), the ASF may include the ACR procedure (e.g., single ACR procedure) in the ACR-detection-decision list. In the example, if there are multiple common ACR procedures supported and if the ASF determines that the use of the ACR procedure (e.g., single ACR procedure) is beneficial, the ACR procedure (e.g., single ACR procedure) may be included. For example, selecting an ACR procedure (e.g., single ACR procedure) can minimize processing and / or message transmission by minimizing requests for coordination (e.g., eliminating the need for coordination). For example, selecting an ACR procedure (e.g., single ACR procedure) can avoid using an ACR procedure that may be incompatible with the source edge data network type / target edge data network type (e.g., DN and / or LADN).
[0138] When there are multiple common ACR procedures supported by the EEL entities involved (e.g., AC, EEC, EES and / or EAS) and when the ASF determines that there is a benefit in using multiple concurrent ACR procedures, the ASF may select multiple ACR procedures. For example, it may be beneficial to select multiple ACR procedures to improve ACR detection by using multiple ACR detection entities. For example, it may be beneficial to select multiple ACR procedures to support WTRU transitions where the source edge data network type and / or target edge data network type (e.g., DN and / or LADN) involved involve the use of different ACR procedures.
[0139] The ACR procedure selection performed by the ASF may be based on the EEL participants (e.g., AC, EEC, EES, and / or EAS). ACR capabilities may include SCP capabilities and / or current EDN type and surrounding EDN types (e.g., DN and / or LADN). For example, EAS service continuity support may be found in the EAS profile. EES service continuity support may be found in the EES profile. EEC service continuity support may be provided by the EEC in a registration request or an EAS discovery request, and AC service continuity support may be found in the AC profile. For example, the EDN type may be determined by the EES topology and / or geographic service area in the EES profile or the EAS topology and / or geographic service area in the EES profile.
[0140] The ACR procedure selection for the WTRU location (e.g., geographic and / or topological) may be based on the planned route and / or trajectory of the EEC. For example, if the EEC is hosted in a vehicle or drone, the EEC may provide the planned route and / or trajectory to the ASF. The ASF may use this information to determine which ACR procedures may be supported at the future location of the EEC.
[0141] The ACR procedure selection may be based on data analytics information obtained from the Network Data Analytics Function (NWDAF) about the WTRU hosting the EEC. For example, the ASF may use the WTRU mobility analytics information to determine which ACR procedures may be supported at the future location of the EEC. The ASF may invoke the Nnwdaf_AnalyticsSubscription service or the Nnwdaf_AnalyticsInfo service to obtain WTRU mobility statistics and / or predictions.
[0142] The ASF may assign a globally unique identifier to an entry (e.g., each entry) in the ACR-detection-decision list to identify the selected ACR procedure (e.g., each ACR procedure). The ACR identifier may be used for ACR management operations, such as re-evaluating or terminating an ACR. The ACR identifier may be used when an active ACR (e.g., detection and decision) reports an ACR decision to the ACF.
[0143] For example, the ASF may assign a valid area and / or location to an ACR entry (e.g., each ACR entry) in the ACR-detection-decision list to narrow the scope of the ACR procedure. The ACR detection and / or decision entity may use the valid area to decide when to start and / or stop ACR detection and / or decision based on the WTRU location. The WTRU location may be a geographic location (e.g., geographic coordinates and / or a city address) or a topological location in the network (e.g., a cell identifier, a tracking area identifier (TAI), or a public land mobile network (PLMN)). The service area capability allows the ASF to perform ACR planning based on the WTRU location. For example, when the WTRU is in a location with a neighboring LADN, the ASF may select a specific ACR procedure compatible with the LADN, otherwise, the ASF may select a different ACR procedure. For example, when the neighboring EAS / EES supports different ACR procedures in the neighboring EDN, the ASF may perform ACR planning.
[0144] ACF entities can be selected.
[0145] The ACF entity may be a node in the system and / or may be dynamically selected by the ASF. When one or more participants (eg, each participant) know the ACF, the ASF may not request the selection of the ACF (eg, the ASF may not need to select the ACF).
[0146] When the ACF is dynamically selected by the ASF, the ACF entity selection may produce one of the following results: no ACF entity is selected or one ACF entity is selected.
[0147] If ACR is not used or if an ACR procedure (eg, a single ACR procedure) is selected (eg, the ACR-detection-decision list includes 0 entries or 1 entry), the ASF may not select an ACF entity.
[0148] If the ACR-detection-decision list includes multiple ACR procedures to be used concurrently, the ASF may select an ACF entity (eg, one ACF entity).
[0149] The output of the ACF selection procedure may be an identification of the ACF (eg, the FQDN or IP address of the ACF).
[0150] A communication ASF decision may be provided.
[0151] The ACR procedure selection may be communicated to the ACR detection and decision entity. The ACR detection and decision entity may be the EEC, EES and / or EAS. The ASF may provide the ACR-detection-decision list to the EEC, EES and / or EAS.
[0152] For the ACR detection entity, based on receiving the ACR-detection-decision list, the ACR detection entity may initiate the ACR detection process when (e.g., only when) the selected ACR procedure authorizes the ACR detection process. If multiple ACR procedures are selected, the ACR detection entity may initiate the ACR detection process for the selected ACR procedures that authorize the ACR detection process (e.g., all selected ACR procedures). If ACR is not used or if the selected ACR procedure does not require the ACR detection entity to participate, the detection process may not be initiated.
[0153] For the ACR decision entity, based on receiving the ACR-detection-decision list, the ACR decision entity may initiate the ACR decision process (e.g., waiting for detection) when (e.g., only when) the selected ACR procedure authorizes the ACR decision process. If multiple ACR procedures are selected, the ACR decision entity may use the selected ACF entity. If ACR is not used or if the selected ACR procedure does not require the participation of the ACR decision entity, the decision process may not be initiated.
[0154] The ACF entity selection may be communicated to the ACR decision entity. The ACR decision entity may be the EEC, EES and / or EAS.
[0155] For the ACR decision entity, based on receiving the ACF entity selection, the ACR decision entity may configure its ACR decision processing using the selected ACF entity. If the ACF entity is selected, the ACR decision entity may inform the ACF entity of its ACR decision and may not continue to trigger the ACR execution phase until the ACR decision entity receives confirmation from the ACR coordination entity that it can continue. If the ACF entity is not selected, the ACR decision entity may continue to trigger the ACR execution phase.
[0156] The AC may be informed of the ACR-detection-decision list and / or the ACR coordination entity.
[0157] A reassessment of selected ACR protocols may be provided.
[0158] For example, if the WTRU moves in the network, if the ACR capabilities of a neighboring EDN change, if the WTRU's planned route changes, or if the ACR capabilities of an EEL participant change, the ASF may periodically re-evaluate (e.g., needs to periodically re-evaluate) the ACR-detection-decision list.
[0159] When the ASF performs a reassessment, the ASF may generate an ACR-detection-decision list (e.g., a new ACR-detection-decision list) and may select an ACF entity in the same manner as described herein. The reassessed list may be the same as the initial list, may be a partially modified list, or may include a complete set of entries (e.g., a new entry). The unchanged list entry may be an entry with a pre-existing globally unique identifier, and the entry (e.g., a new entry) may be an entry with a globally unique identifier (e.g., a new globally unique identifier).
[0160] When the ASF communicates the re-evaluated ACR-detection-decision list, the recipient may react based on the received ACR-detection-decision list. For example, the ACR procedure whose identifier has been removed from the list may be stopped. The ACR procedure that has been added (e.g., a new ACR procedure) may be started. An existing ACR procedure identifier assigned to an ACR procedure (e.g., a new ACR procedure) may cause the ACR procedure to be stopped and another ACR procedure to be started.
[0161] An ACR coordination function (ACF) may be provided.
[0162] When multiple ACR procedures have been selected for a session between an AC residing on a WTRU and an EAS residing in an EDN (eg, a DN or LADN), the ACR coordination function may perform one or more operations to prioritize the ACR procedure execution.
[0163] The role of the ACF may be to select an ACR procedure to execute when an ACR has been detected and / or determined for an AC and EAS pair.
[0164] Coordination of ACR protocols may be provided.
[0165] The ACR procedure coordination performed by the ACF may produce one of the following results: allowing the ACR to be performed or not allowing the ACR to be performed.
[0166] The ACF may prevent execution of an ACR procedure when another ACR is being executed for a given AC and EAS pair. For example, when ACR procedures (e.g., two or more ACR procedures) concurrently detect and decide that an ACR is needed, the ACF may decide to allow execution of one of the ACR procedures and may deny execution of the other (multiple) ACR procedures. The ACF may prevent execution of an ACR procedure if the ACF determines that the ACR procedure will fail due to, for example, an unsupported WTRU move or planned move as described herein.
[0167] ACF may allow execution of an ACR procedure when it is the first ACR procedure to detect and / or decide that an ACR is needed. For example, if a single ACR procedure detects and / or decides to trigger ACR execution for AC and EAS, ACF may allow execution of the ACR procedure. In the case of concurrent use of multiple ACRs, ACF may decide to allow execution of one ACR procedure and reject other ACR procedures.
[0168] When reporting concurrent ACR decisions, the ACF may coordinate ACR execution based on different conditions. For example, the ACF may allow ACR execution for the first reported ACR. In this case, the ACR decision reporting timestamp may be used to determine the ACR procedure for ACR execution. For example, the ACF may allow ACR execution based on a preferred ACR list. In this case, the ACR procedure priority in the preferred ACR list may be used to determine the ACR procedure for ACR execution. For example, the ACF may allow ACR execution based on the source EDN type or the target EDN type (e.g., DN and / or LADN). In this case, the source EDN type or the target EDN type may be obtained from the WTRU registration information, from the EAS profile, or from the EES profile. For example, the ACF may allow ACR execution based on the WTRU location. In this case, the WTRU location may be obtained from the WTRU or from the network.
[0169] ACR procedure coordination performed by the ACF may involve (e.g., require) the EEL participants' (e.g., AC, EEC, EES and / or EAS) ACR and SCP capabilities, source EDN type (e.g., DN or LADN), target EDN type (e.g., DN or LADN), WTRU location, detection triggers (e.g., WTRU movement or planned WTRU movement), and / or an identifier of the ACR procedure that reports ACR detections and / or decisions to the ACF.
[0170] Can provide security for ACR.
[0171] As described herein, the ACR capabilities of an entity (e.g., AC, EEC, EES, and / or EAS) may be provided to the ASF. The ACR capabilities may include a list of ACR procedures performed by the entity. The ACR capabilities may include a list of security procedures supported by the entity.
[0172] In an example, the EEC may discover T-EAS and transmit an ACR coordination request. The ACR coordination request may indicate an identification of T-EAS. The ACR coordination request may include the ACR capabilities of the EEC. The EES may receive the ACR coordination request and use the ACR capabilities of the EEC and T-EAS to determine the ACR coordination response. The EES may have been configured with the ACR capabilities of T-EAS. The EES may transmit an ACR coordination response to the EEC. The ACR coordination response may notify the EEC that the ACR procedure has been selected to execute. The ACR coordination response may trigger an entity to establish a secure connection with a target entity (e.g., T-EAS or T-EES). The ACR coordination response may provide information about the target entity to the entity. The information about the target entity may include an identification of the target entity, security credentials that can be used when establishing security with the target entity, an indication of which procedures the target entity supports, and / or an indication of which security procedures can be used to establish security with the target entity. Transmitting security credentials in the ACR coordination response may cause the EEC to not execute (e.g., not need to execute) a second procedure for obtaining security credentials from the ECS.
[0173] After deciding on the ACR procedures, security procedures may be performed between entities in the source EDN (e.g., EES and / or EAS) and entities in the target EDN (e.g., EES and / or EAS) to protect the application context transfer from the S-EAS to the T-EAS. Security procedures may be performed between the AC and / or EEC to the T-EES and T-EAS. Depending on the trust domains of the source and target EDNs and the deployment scenario, the security procedures may determine whether the WTRU uses (e.g.,) authentication (e.g., new authentication) and authorization in a service area (e.g., a new service area) or whether AKMA / Generic Bootstrapping Architecture (GBA) is used to reboot the security credentials to be used in the target EDN. The security procedures may generate authorization for the AC and / or a token for the EEC to access the T-EAS.
[0174] If the ECS has not changed during the ACR procedure, the EEC may establish security protection with the ECS via TLS with credentials (e.g., certificate-based, AKMA, and / or GBA-based) and may receive an authorization token to be used with the EES in the target EDN. Depending on security (e.g., security requirements), WTRU authentication (e.g., new WTRU authentication) may be performed with the target EDN and AKMA / GBA procedures (e.g., new AKMA / GBA procedures) may be performed. If WTRU authentication (e.g., new WTRU authentication) is not used (e.g., not required), the WTRU may use existing AKMA / GBA credentials with the ECS and / or EES in the target EDN to establish a secure connection and receive an authorization token (e.g., new authorization token) to be used with the target EES.
[0175] Figure 5 An example of application context migration with an ACT authorization token is shown.
[0176] like Figure 5 As shown, procedures for application context migration may be used for S-EAS to T-EAS (eg, S-EES to T-EES when needed) as well as one or more of the following procedures discussed below.
[0177] At 1, the EEC may establish a secure connection with the source ECS, which may be based on a TLS setup with AKMA or GBA pre-shared keys. Depending on the configuration, when the AC receives the ACR selection message, re-authentication and / or AKMA / GBA may be used (eg, required).
[0178] At 2, the AC may receive an ACR Select message, and the message may trigger the EEC to start an ACT. The AC may decide to initiate an application context migration from S-EAS to T-EAS. The EEC may initiate a service provisioning request to the ECS to request a token (e.g., an ACT authorization token) for T-EES authorization and authorization of application context migration from S-EAS to T-EAS. The token may have been received via an ACR Select message.
[0179] At 3, the ECS may process the request and may generate the requested token after authorization by the EEC. The ACT authorization token may include one or more of the following: AC ID, S-EAS ID, T-EAS ID, ECS ID, token validity time, authorized actions, etc. The ECS may transmit the token and the ACT authorization token to the AC / EEC. If the ECS changes during the ACR, the AC / EEC may establish TLS with the target ECS, and the AC / EEC may receive the authorization token to access the T-EES / T-EAS and establish TLS with the T-EES / T-EAS.
[0180] At 5, AC / EEC may transmit an application context migration request to T-EAS, and the request may include a T-EES access authorization token and an ACT authorization token. At 6, in an example, T-EAS and S-EAS may establish a secure connection (e.g., a TLS connection). At 7, T-EAS may authorize AC using the EAS access token, and may transmit the ACT authorization token to S-EAS. At 8, based on receiving the ACT request from T-EAS, S-EAS may transmit the ACT authorization token to ECS for verification. At 9, after ECS verifies (e.g., successfully verifies) the ACT authorization token, ECS may respond to S-EAS by confirming. At 10, S-EAS may migrate the AC application context to T-EAS. At 11, T-EAS may transmit an ACT completion message to AC / EEC.
[0181] An EES that implements ASF is available.
[0182] ACF and ASF may be logic functions, which may be part of other logic functions. Figure 6 An ACR selection function is shown, for example, as performed by the EES.
[0183] Figure 6An example of an ACR selection function performed by an EES is shown. The selection of an ACR scene may be performed by an EES (e.g., a first network node) for a given AC and a selected EAS (e.g., a second network node) from one or more supported ACR scenes of an AC, an EEC, a selected EES, and a selected EAS. The one or more supported ACR scenes may include ACR scenes commonly supported by AC, EEC, a selected EES, and a selected EAS. The EES may receive configuration information from a first network node, a second network node, and an application client. The EES may use the configuration information to determine a first network node and a second network node, and the second network node may be associated with the first network node.
[0184] One or more of the following may apply to the ACR selection function performed by the EES: the EES may be pre-configured to perform the ASF; the AC profile may be provisioned in the EEC; or the AC profile may include an AC service continuity support information element (IE) having a list of supported and / or preferred ACR scenarios (e.g., the AC profile may specify SCP capabilities for each supported and / or preferred ACR scenario).
[0185] One or more of the following may be applied to the ACR selection function performed by the EES.
[0186] At 1, the EEC may perform an EAS discovery procedure as described herein. The EEC may obtain a list of EASs that meet the EEC criteria specified via an EAS discovery request. The EEC may perform EAS discovery with multiple EESs to discover EASs that may be available in different EDNs.
[0187] At 2, the EEC may select an EAS (eg, one EAS) from the list of discovered EASs. The EEC may transmit an EAS selection request to the EES in which the selected EAS is registered. The terms "EAS selection request" and "EAS information deployment request" may be used interchangeably.
[0188] At 3, the EEC may transmit a selection request message to the first network node, and the selection request message may request an ACR procedure from the first network node and indicate service continuity support information associated with the EEC. The selection request may indicate security credentials, a WTRU identifier, an application client identifier, and / or an application client profile. The selection request message may include an application client (AC) intent, and the AC's intent may be to communicate with the second network.
[0189] The request may indicate the AC's intention to use the selected EAS and may include one or more of the following information elements. The request may include the selected EAS ID, which identifies the EAS that has been selected for use by the AC. The request may include a selected EAS endpoint (e.g., a URI, FQDN, IP address, etc.) that identifies how to communicate with the selected EAS. The request may include a WTRU identifier (e.g., a GPSI or an identification token) that identifies the hosted WTRU. The request may include an EEC identifier that identifies the EEC, for example, because there may be multiple co-located EECs on a single WTRU. The request may include EEC service continuity support that identifies ACR procedures supported and / or preferred by the EEC, the EEC service continuity support including SCP capabilities and including the willingness of the EEC to perform ACF functionality. The request may include security credentials generated by authorization (e.g., successful authorization) of edge computing services. The request may include AC profile information, which includes AC service continuity support.
[0190] The EAS deployment request may include an ACR scene selection request. In the ACR scene selection request, the EES may be informed (e.g., by the EEC) to perform the ACR scene selection. At 4, based on receiving the EAS selection request (e.g., from the EEC), the EES may continue to select an ACR procedure compatible with AC, EEC, EES, and / or EAS (e.g., select an ACR scene list) by using one or more of the following information: an AC service continuity support information element from the AC profile; an EEC service continuity support information element as defined in an EEC registration request or in an EAS discovery request (e.g., the defined EEC context may not include service continuity support information and may be added); EES service continuity support known at the EES; or an EAS service continuity support information element from the EAS profile.
[0191] SCP capabilities and / or ACR preferences may be considered in ACR selection and may be included in service continuity support information. Since ACF may be included in the EEC context and EAS profile, EES may consider the willingness of EEC and EAS to participate. EES may consider one or more of the following information to select the ACR procedure: the current EDN type (e.g., DN or LADN), which may be derived from the EES topology and / or geographic service area in the EES profile or the EAS topology and / or geographic service area in the EES profile; the EDN type of the surrounding EDN (e.g., the surrounding EES may be obtained from the ECS), which may be derived from the EES topology and / or geographic service area in the EES profile; or the WTRU location (e.g., geographic and / or topological), which may be obtained as described herein. After establishing the ACR-detection-decision list, EES may assign a globally unique identifier to the ACRs (e.g., each ACR) present in the list. For example, the identifier may be used for ACR management when the ACR may be re-evaluated, terminated, or when the ACR reports the detection of the ACF. The EES may assign an ACR validity area (eg, geographic and / or topological) to the ACRs present in the list (eg, each ACR). The identifier may be used to enable or disable selected ACR procedures based on the presence of WTRUs in the defined area.
[0192] At 5, the EES may transmit an ACR selection request to the selected EAS. In an example, if a subscription-notification model is used (e.g., if the EAS is already subscribed), the EES may transmit an ACR selection notification to the selected EAS. The EES may determine one or more ACR procedures for providing continuity for the service based on the requested ACR procedures, service continuity support information associated with the WTRU, the first network node, and the second network node. The one or more ACR procedures may include the requested ACR procedures. The EES may determine the deployment information of the WTRU.
[0193] The request or notification may include one or more of the following information elements: an ACR-detection-decision list (e.g., including a globally unique identifier associated with the selected ACR procedures (e.g., each ACR procedure and including an ACR valid area associated with the selected ACR procedures (e.g., each ACR procedure); a selected ACF identifier (e.g., FQDN, IP address, etc.); security credentials generated by authorization of the edge computing service (e.g., successful authorization); an AC identifier that uniquely identifies the AC; or a WTRU identifier of the hosting WTRU (e.g., GPSI or identification token).
[0194] At 6, the EES may transmit an EAS selection response to the EEC. The EEC may receive a selection response message from the first network node, wherein the selection response message indicates one or more ACR procedures, and the ACR procedures may be supported by the WTRU and include the requested ACR procedures. The EES may transmit a selection response message to the WTRU, and the selection response message may indicate the determined one or more ACR procedures.
[0195] The response may include one or more of the following information elements (e.g., information elements in an EAS Information Provisioning Response): ACR-Detection-Decision List (e.g., including a globally unique identifier for an ACR (e.g., each ACR) in the list, and including a valid area (such as geographic and / or topological) for an ACR (e.g., each ACR) in the list. The ACR-Detection-Decision List may be referred to as an ACR Scenario List, as described herein. The selected ACR Procedure List may not include ACR procedures, or may include one or more ACR procedures that the WTRU may support. The detection-decision list may include the requested ACR procedure.
[0196] One or more of the following may be applied to the ACR selection function performed by the EES. At 7a, based on receiving the EAS selection response, if the provided ACR-detection-decision list includes one or more ACR procedures that use (e.g., require) ACR detection at the EEC, the EEC may start ACR detection. The EEC may use the selected ACR scenario list to determine whether the EEC should perform ACT detection and / or ACR decision. Otherwise, the EEC may not perform ACR detection. The EEC may store a globally unique identifier associated with its ACR procedure for future ACR management operations, such as ACR termination requests and / or reporting ACR detection to the ACF. If the EAS selection response includes an ACR valid area, the EEC may verify whether the WTRU is in the valid area before starting ACR detection. Otherwise, the EEC may not start ACR detection until the WTRU enters the valid area, and may stop ACR detection if the WTRU leaves the valid area. At 7b, after performing ACR selection, if the provided ACR-detection-decision list includes one or more ACR procedures that use (e.g., require) ACR detection at the EES, the EES may start ACR detection. The EES may use the selected ACR scene list to determine whether the EEC should perform ACT detection and / or ACR decision. Otherwise, the EES may not perform ACR detection. The EES may store a globally unique identifier associated with its ACR procedure for future ACR management operations, such as ACR termination requests and / or reporting ACR detection to the ACF. If an ACR valid area is used, the EES may verify whether the WTRU is in a valid area before starting ACR detection. Otherwise, the EES may not start ACR detection until the WTRU enters the valid area, and may stop ACR detection when the WTRU leaves the valid area. At 7c, based on receiving an ACR selection request and / or notification, if the provided ACR-detection-decision list includes one or more ACR procedures that use (e.g., require) ACR detection at the EAS, the EAS may start ACR detection. The EAS may use the selected ACR scenario list to determine whether the EEC should perform ACT detection and / or ACR decision. Otherwise, the EAS may not perform ACR detection. The EAS may store a globally unique identifier associated with its ACR procedure for future ACR management operations, such as ACR termination requests and / or reporting ACR detection to the ACF. If the ACR selection request includes an ACR valid area, the EAS may verify whether the WTRU is in the valid area before starting ACR detection. Otherwise, the EAS may not start ACR detection until the WTRU enters the valid area, and may stop ACR detection if the WTRU leaves the valid area.
[0197] EEC can execute ASF.
[0198] ACF and ASF may be logic functions, which may be part of other logic functions. Figure 7 An example of an ACR selection function performed, for example, by the EEC is shown.
[0199] Figure 7 An example of an ACR selection function performed by the EEC is shown.
[0200] One or more of the following may be applied to the ACR selection function performed by the EEC. The EEC may be pre-configured to execute the ASF. The AC profile may be provisioned in the EEC. The AC profile may include an AC service continuity support IE with a list of supported and / or preferred ACR scenarios (e.g., the AC profile may specify SCP capabilities for supported and / or preferred ACR scenarios).
[0201] One or more of the following may be applied to the ACR selection function performed by the EEC. At 1, the EEC may perform an EAS discovery procedure as described herein. The EEC may receive configuration information from an EES (e.g., a first network node), an EAS (e.g., a second network node), and an application client. The EEC may use the configuration information to determine a first network node and a second network node, and the second network node may provide a service. The second network node may register with (e.g., associate with) the first network node.
[0202] Thus, the EEC may obtain a list of EASs that meet the EEC criteria specified via the EAS discovery request. The EEC may perform EAS discovery with multiple EESs to discover EASs that may be available in different EDNs. At 2, the EEC may select an EAS (e.g., one EAS) from the list of discovered EASs. The EEC may select an ACR procedure compatible with AC, EEC, EES, and / or EAS by using one or more of the following information: an AC service continuity support information element from an AC profile; EEC service continuity support known at the EEC; an EES service continuity support information element from an EES profile; or an EAS service continuity support information element from an EAS profile. SCP capabilities and / or ACR preferences may be considered in ACR selection and included in the service continuity support information. The selection of an ACR procedure (e.g., a scenario) may be performed by the EEC for the application client (AC) and the EAS selected from the ACR procedures commonly supported by the AC, EEC, the selected EES, and the selected EAS. The application of ACR procedures to provide continuity for services may be determined based on the capabilities of the WTRU, the capabilities of the EES (e.g., the first network node), and the capabilities of the EAS (e.g., the second network node). The ACR procedures may be determined by an ACR-detection-decision list. The detection-decision list may include the determined ACR procedures, and the determined ACR procedures may be compatible with the EEC (e.g., WTRU), the application client (AC) of the WTRU, the first network node, and the second network node. The determined ACR procedures may be determined based on service continuity support information of the AC, the WTRU, the first network node, and the second network node.
[0203] The EEC may consider the willingness to participate in EES and EAS as an ACF included in the EES profile and / or EAS profile. The EEC may consider one or more of the following information to select the ACR procedure: the current EDN type (e.g., DN or LADN), which can be derived from the EES topology and / or geographic service area in the EES profile or the EAS topology and / or geographic service area in the EES profile; the EDN type of the surrounding EDN (e.g., the surrounding EES can be obtained from the ECS), which can be derived from the EES topology and / or geographic service area in the EES profile; or the WTRU location known at the terminal (e.g., geographic and / or topological). After establishing the ACR-detection-decision list, the EEC may assign a globally unique identifier to the ACRs (e.g., each ACR) present in the list. For example, the identifier can be used for ACR management when the ACR may be re-evaluated, terminated, or when the ACR reports the detection of the ACF. The EEC may assign an ACR effective area (e.g., geographic and / or topological) to the ACRs (e.g., each ACR) present in the list. This identifier may be used to enable or disable selected ACR procedures based on the presence of WTRUs in a defined area.
[0204] At 3, the EEC may transmit an EAS selection request (e.g., an ACR scene selection notification) to the EES registered with the selected EAS. The request may indicate AC intent. The EAS selection request may inform the EES of the EAS that has been selected by the EEC, and may provide the EES with a selected ACR scene list. The EEC may transmit an EAS information selection request (also referred to herein as a deployment request) to the EES. The ACR selection request may include an ACR scene list selected by the EEC, an EEC security credential, a selected EASID, a selected EAS endpoint, an EECID, and an ACID. The selection request message may request information for a second network node, request one or more application context relocation (ACR) procedures, and indicate a second network node identifier, a WTRU identifier, and security credentials. The selection request may include a second network endpoint identifier, and the second network endpoint identifier may identify how the device communicates with the second network.
[0205] The request may indicate the AC's intent to use the selected EAS (e.g., an intent to communicate with an EAS (e.g., a second network node)), and may include one or more of the following information elements: the selected EAS identifying the EAS that has been selected for use by the AC ID; a selected EAS endpoint (e.g., URI, FQDN, IP address, etc.) identifying how to communicate with the selected EAS; an ACR-detection-decision list including a globally unique identifier associated with the selected ACR procedures (e.g., each selected ACR procedure) and including an ACR effective area associated with the selected ACR procedures (e.g., each selected ACR procedure); a selected ACF identifier (e.g., FQDN, IP address, etc.); a WTRU identifier (e.g., GPSI or identification token) identifying the hosting WTRU; an EEC identifier identifying the EEC when multiple EECs may be co-located on a single WTRU; EEC service continuity support for ACR procedures supported and / or preferred by the EEC, including SCP capabilities; EEC service continuity support for ACR procedures supported by the EEC, including SCP capabilities; security credentials generated by authorization (e.g., successful authorization) for edge computing services; or AC profile information including AC service continuity support. The ACR-detection-decision list may include zero or more ACR procedures. The capabilities of the first network node may include service continuity support information of the first network node, and the capabilities of the second network node may include service continuity support information of the second network node. At 4, the EES may transmit an ACR selection request to the selected EAS. In the example, if a subscription-notification model is used (e.g., if the EAS has been subscribed and if the EES allows ACR scenario selection based on the EEC), the EES may (e.g., upon receiving a request from the EEC) transmit an ACR selection notification to the selected EAS. The EES may use an identifier of the second network node to determine that the second network node has subscribed to receive a selection notification. The EES may use a WTRU identifier and security credentials to determine that the EES is authorized to communicate with the second network node. When the WTRU is authorized to communicate with the second network node and the second network node has subscribed to receive a selection notification, the EES may transmit a notification message to the second network node. The notification message may indicate the requested ACR procedure.
[0206] ACR selection may inform EAS of the selected ACR scene list for the AC using EAS. If ACR selection occurs, the selection notification may include the selected ACR scene list, AC ID, and WTRU ID. Upon receiving the notification, EAS may determine whether EAS should perform ACR detection and / or make an ACR decision for a (e.g., specific) AC (ACID, WTRU ID). EES may transmit a selection notification to a second network node if the second network node has subscribed to the notification.
[0207] The request and / or notification may include one or more of the following information elements: an ACR-detection-decision list, including a globally unique identifier associated with the selected ACR procedure (e.g., each selected ACR procedure) and an ACR valid area associated with the selected ACR procedure (e.g., each selected ACR procedure); security credentials generated by authorization of the edge computing service (e.g., successful authorization); an AC identifier identifying the AC; or a WTRU identifier of the hosting WTRU (e.g., a GPSI or an identification token). At 5, the EES may transmit an EAS selection response to the EEC. EAS selection response and EAS information deployment response may be used interchangeably in this document. The selection response may include deployment information for the second network node, and the selection response message may indicate a success status.
[0208] One or more of the following may be applied to the ACR selection function performed by the EEC. At 6a, after performing ACR selection, if the provided ACR-detection-decision list includes one or more ACR procedures that use (e.g., require) ACR detection at the EEC, the EEC may initiate ACR detection. In an example, the EEC may use the selected ACR scenario list to determine whether the EEC should perform ACR detection and / or make an ACR decision. ACR may be detected under the condition that one of the determined ACR procedures includes an ACR procedure with ACR detection performed at the WTRU, EES, and / or EAS.
[0209] Otherwise, the EEC may not perform ACR detection. The EEC may store a globally unique identifier associated with its ACR procedure for future ACR management operations, such as ACR termination requests and / or reporting ACR detection to the ACF. If an ACR valid area is used, the EEC may verify whether the WTRU is in a valid area before starting ACR detection. Otherwise, the EEC may not start ACR detection until the WTRU enters the valid area, and may stop ACR detection when the WTRU leaves the valid area. At 6b, based on receiving an EAS selection request, if the provided ACR-detection-decision list includes one or more ACR procedures that use (e.g., require) ACR detection at the EES, the EES may start ACR detection. Otherwise, the EES may not perform ACR detection. The EES may store a globally unique identifier associated with its ACR procedure for future ACR management operations, such as ACR termination requests and / or reporting ACR detection to the ACF. If the EAS selection request includes an ACR valid area, the EES may verify whether the WTRU is in a valid area before starting ACR detection. Otherwise, the EES may not start ACR detection until the WTRU enters the valid area, and may stop ACR detection if the WTRU leaves the valid area. At 6c, based on receiving the ACR selection request and / or notification, if the provided ACR-detection-decision list includes one or more ACR procedures that use (e.g., require) ACR detection at the EAS, the EAS may start ACR detection. Otherwise, the EAS may not perform ACR detection. The EAS may store a globally unique identifier associated with its ACR procedures for future ACR management operations, such as ACR termination requests and / or reporting ACR detection to the ACF. If the ACR selection request includes an ACR valid area, the EAS may verify whether the WTRU is in the valid area before starting ACR detection. Otherwise, the EAS may not start ACR detection until the WTRU enters the valid area, and may stop ACR detection if the WTRU leaves the valid area.
[0210] An EES that performs ACF is available.
[0211] ACF and ASF may be logic functions, which may be part of other logic functions. Figure 8 An example of an ACR coordination function, such as performed by an EES, is shown.
[0212] Figure 8 An example of the ACR coordination function performed by the EES is shown.
[0213] One or more of the following may be applied to the ACR coordination function performed by the EES. The ASF may include two or more ACR procedures in the ACR-detection-decision. The ASF may select the EES as the ACF entity.
[0214] One or more of the following may be applied to the ACR coordination function performed by the EES. At 1a, the ASF may choose to use (e.g., require) the EEC to perform the ACR procedures for ACR detection and decision-making. The ASF may select EES as the ACF entity. Based on the received ACR selection, the EEC may configure the EES as an ACR coordinator. At 1b, the ASF may choose to use (e.g., require) the EAS to perform the ACR procedures for ACR detection and decision-making. In the example, the ASF may select the EES as the ACF entity. Based on the received ACR selection, the EAS may configure the EES as an ACR coordinator. At 2a, the EEC may decide to use (e.g., require) the ACR and may transmit an ACR coordination request to the EES. The request may include one or more of the following information elements: a requestor identifier (e.g., EECID) that identifies the EEC; a unique identifier assigned by the EEC and that can identify the ACR coordination request; or an ACR procedure identifier that identifies the ACR procedures for performing detection and decision-making (e.g., the identifier is provided in the ACR-detection-decision list). At 2b, the EAS may (e.g., concurrently) decide to use (e.g., require) the ACR and may transmit an ACR coordination request to the EES. The request may include one or more of the following information elements: a requestor identifier (e.g., EASID) that identifies the EAS; a unique identifier assigned by the EAS and that can identify the ACR coordination request; or an ACR procedure identifier that identifies the ACR procedure that performs detection and decision making (e.g., the identifier is provided in the ACR-Detection-Decision List). At 3, based on receiving the ACR coordination request (e.g., from the second network node), the EES may evaluate which ACR procedure is allowed to execute and may select one (e.g., only one) ACR procedure to execute. The first network node may transmit an ACR event notification to the second network node, and the event notification may indicate that the ACR event has begun. The first network node may transmit an ACR event notification to the second network node based on determining the selected ACR procedure from the one or more determined ACR procedures.
[0215] The ACR selection algorithm may select an ACR procedure based on, for example, one or more of the following: an ACR coordination request timestamp; a preferred list of ACR procedures; a source EDN type (e.g., DN or LADN); a target EDN type (e.g., DN or LADN); or a WTRU location. After selecting the ACR coordination request, the EES may transmit an ACR coordination response to the parties (e.g., all parties) that transmitted the ACR coordination request. The response may include a decision to enter the ACR execution phase (e.g., true or false), an ACR globally unique identifier of the ACR that entered the execution phase, and / or an ACR coordination request identifier received in the corresponding request. At 4a, based on receiving the coordination response, the EEC may verify that the ACR identifier selected to proceed to the execution phase matches its own ACR identifier, that the decision is positive, and / or that the ACR coordination request identifier matches the identifier provided in the request. If the response is positive, the ACR identifier may match the EEC ACR and the ACR coordination request identifier matches, and the EEC may proceed to the ACR execution phase. Otherwise, the EEC may not proceed to ACR execution. At 4b, based on receiving the coordination response, the EAS may verify that the ACR identifier selected to proceed to the execution phase matches its own ACR identifier, the decision is affirmative, and / or the ACR coordination request identifier matches the identifier provided in the request. If the response is affirmative, the ACR identifier may match the EECACR and the ACR coordination request identifier matches, and the EEC may proceed to the ACR execution phase. Otherwise, the EEC may not proceed to ACR execution. In an example, the response may be negative, and the selected ACR identifier may not be the identifier that the EAS is executing. In this case, the EAS may not enter the ACR execution phase. At 5, in an example, the response may be positive, and the selected ACR identifier matches the ACR of the EEC, and the ACR coordination identifier received in the response matches the identifier provided in the request. In this case, the EEC may enter the ACR execution phase in accordance with the selected ACR procedure.
[0216] EECs that perform ACF are available.
[0217] ACF and ASF may be logic functions, which may be part of other logic functions. Fig. 9 An example of an ACR coordination function, such as performed by an EEC, is shown.
[0218] Fig. 9 An example of the ACR coordination function performed by the EEC is shown.
[0219] One or more of the following may apply to the ACR coordination function performed by the EEC: The ASF has included two or more ACR procedures in the ACR-detection-decision, or the ASF has selected the EEC as the ACF entity.
[0220] One or more of the following may be applied to the ACR coordination function performed by the EEC. At 1a, the ASF may choose to use (e.g., require) the EEC to perform an ACR procedure for ACR detection and decision-making. The ASF may select the EEC as the ACF. Based on the received ACR selection information, the EEC may configure the EEC as an ACR coordinator. At 1b, the ASF may choose to use (e.g., require) the EES to perform an ACR procedure for ACR detection and decision-making. The ASF may select the EEC as the ACF. Based on the received ACR selection information, the EES may configure the EEC as an ACR coordinator. At 2a, the EEC may decide to use (e.g., require) the ACR and may transmit an ACR coordination request to the EEC. The request may include one or more of the following information elements: a requestor identifier (e.g., EECID) that identifies the EEC; a unique identifier assigned by the EEC and that can identify the ACR coordination request; or an ACR procedure identifier that identifies the ACR procedure for performing detection and decision-making (e.g., the identifier is provided in the ACR-detection-decision list). In an example, the EEC may communicate the ACR decision to the ACF internally. At 2b, the EES may (e.g., concurrently) decide to use (e.g., require) the ACR and may transmit an ACR coordination request to the EEC. The request may include one or more of the following information elements: a requestor identifier (e.g., EESID) that identifies the EES; a unique identifier assigned by the EES and that may identify the ACR coordination request; or an ACR procedure identifier that identifies the ACR procedure that performs detection and decision making (e.g., the identifier is provided in the ACR-Detection-Decision List). At 3, based on receiving the ACR coordination request, the EEC may evaluate which ACR procedure is allowed to execute and may select one (e.g., only one) ACR procedure to execute. The ACR selection algorithm may select an ACR procedure based on, for example, one or more of the following: an ACR coordination request timestamp; a preferred list of ACR procedures; a source EDN type (e.g., DN or LADN); a target EDN type (e.g., DN or LADN); or a WTRU location. After selecting the ACR coordination request, the EEC may transmit an ACR coordination response to the parties (e.g., all parties) that transmitted the ACR coordination request. The response may include a decision to enter the ACR execution phase (e.g., true or false), the ACR globally unique identifier of the ACR that entered the execution phase, and / or the ACR coordination request identifier received in the corresponding request. At 4a, based on receiving the coordination response, the EEC may verify that the ACR identifier selected to proceed to the execution phase matches its own ACR identifier, that the decision is affirmative, and / or that the ACR coordination request identifier matches the identifier provided in the request. If the response is affirmative and the ACR identifier can match the EEC ACR, the ACR coordination can match the requested identifier match, and the EEC can proceed to the ACR execution phase.Otherwise, the EEC may not proceed to ACR execution. In an example, the response may be negative, and the selected ACR identifier may not be the identifier that the EEC is executing. In this case, the EEC may not enter the ACR execution phase. At 4b, based on receiving the coordination response, the EES may verify that the ACR identifier selected to proceed to the ACR execution phase matches its own ACR identifier, the decision is affirmative, and / or the ACR coordination request identifier matches the identifier provided in the request. If the response is positive, the ACR identifier may match the EES ACR and the ACR coordination request identifier matches, and the EES may proceed to the ACR execution phase. Otherwise, the EEC may not proceed to ACR execution. At 5, in an example, the response may be positive, the selected ACR identifier may match the ACR of the EES, and the ACR coordination identifier received in the response matches the identifier provided in the request. In this case, the EES may enter the ACR execution phase in accordance with the selected ACR procedure.
[0221] Combination use of ASF and ACF is available.
[0222] ACF and ASF may be logic functions, which may be part of other logic functions.
[0223] Fig.10 An example is shown in which an ACR selection function, such as performed by an EEC as described herein, is used in combination with an ACR coordination function, such as performed by an EES as described herein. Fig.10 An example of ASF and ACF used in combination is shown.
[0224] One or more of the following may be applied to the ASF and ACF used in combination. At 1, the EEC may perform an EAS discovery procedure. Thus, the EEC may obtain a list of EASs that meet the EEC standards specified in the EAS discovery request. The EEC may perform EAS discovery with multiple EESs to discover EASs that may be available in different EDNs. At 2, the EEC may select an EAS (e.g., one EAS) from a list of discovered EASs. The EEC may select an ACR procedure that follows the procedures described herein. At 3, the EEC may transmit an EAS selection request to the EES in which the selected EAS is registered. The request may indicate the AC's intention to use the selected EAS, and may include an ACR-detection-decision list and an ACF identifier. In an example, the EEC may decide to include an ACR procedure (e.g., two ACR procedures) in the ACR-detection-decision list. The first selected ACR procedure may use (e.g., require) the EEC to perform ACR detection and decision. The second selected ACR procedure may use (e.g., require) the EAS to perform ACR detection and decision. In an example, the EEC may select EES as the ACR coordination function. At 4, the EES may transmit an ACR selection request to the selected EAS. The EES may evaluate the provided ACR-detection-decision list and may infer that the included ACR procedures do not use (e.g., do not require) EES to perform ACR detection. In this case, the ACR detection process may not be started. Since the EES has been selected to provide ACR coordination, if the ACR coordination process is used (e.g., required), the EES may initiate the ACR coordination process. At 5, the EES may transmit an EAS selection response to the EEC. At 6a, for example, after performing ACR selection, the EEC may identify that one of the ACR procedures included in the ACR-detection-decision list uses (e.g., requires) the EEC to perform ACR detection at the EEC and may start ACR detection and decision processing. At 6b, based on receiving the ACR selection request, the EAS may identify one of the ACR procedures included in the ACR-detection-decision list to use (e.g., request) the EAS to perform ACR detection at the EAS and may initiate ACR detection and decision processing. When the WTRU moves, the ACR detection at the EEC and the EAS may detect the WTRU mobility, and both the EEC and the EAS may decide that application context relocation is required. At 7a, the EEC may transmit an ACR coordination request to the EES selected as the ACR coordination function described herein. At 7b, the EAS may transmit an ACR coordination request to the EES selected as the ACR coordination function described herein. At 8, based on receiving the ACR coordination request, the EES may decide which ACR procedure may proceed to the execution stage. In the example, the EES may select the EEC for ACR procedure execution and may deny the EAS from executing the ACR procedure.At 9A, based on receiving the coordination response, the EEC may verify the ACR identifier, execution decision and / or ACR request identifier. The EEC may proceed to the ACR procedure execution phase based on the ACR coordination request response. At 9b, based on receiving the coordination response, the EAS may verify the ACR identifier, execution decision and / or ACR request identifier. The EAS may not proceed to the ACR procedure execution phase based on the ACR coordination request response. At 10, based on the received affirmative response, the EEC may start an ACR execution that migrates the AC context stored at the source EAS to the target EAS.
[0225] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. A wireless transmit / receive unit (WTRU) may receive configuration information about one or more of a first network node (e.g., an edge enabler server (EES)), a second network node (e.g., an edge application server (EAS)), and an application client (AC). The WTRU may use the configuration information to determine the first network node and the second network node. The second network node may provide a service, and the second network node may be associated with the first network node. The WTRU may determine one or more ACR procedures for providing continuity for the service based on WTRU capabilities, first network node capabilities, and second network node capabilities. The WTRU may transmit a selection request message to the first network node, and the selection request message may indicate an identifier of the second network node, a WTRU identifier, and one or more ACR procedures determined. The WTRU may receive a selection response message indicating a request processing status from the first network node.
[0226] The first network node may be an edge enabler server (EES), and the second network node may be an edge application server (EAS). The WTRU may further determine a list based on service continuity capability information associated with the WTRU, the first network node, and the second network node. The list may include the determined one or more ACR procedures, and the determined one or more ACR procedures may be compatible with one or more of the WTRU, the WTRU's application client (AC), the WTRU's edge enabler client (EEC), the first network node, or the second network node.
[0227] The WTRU may determine that the determined one or more ACR procedures are determined based on service continuity support information of an application client (AC) associated with the WTRU, the WTRU, the EEC, the first network node, or the second network node. The WTRU may detect ACR under the condition of using the determined one or more ACR procedures.
[0228] Systems, methods, and tools for ACR selection and / or coordination are disclosed herein. A first network node may receive a selection request message from a wireless transmit / receive unit (WTRU), wherein the selection request message indicates one or more application context relocation (ACR) procedures, a second network node identifier, a WTRU identifier, and security credentials. The first network node may use the identifier of the second network node to determine that the second network node has subscribed to receive selection notifications. The first network node may use the WTRU identifier and the security credentials to determine that the WTRU is authorized to communicate with the second network node. The first network node may transmit a notification message to the second network node, and the notification message may indicate the requested one or more ACR procedures. The first network node may transmit a selection response message to the WTRU indicating a request processing status.
[0229] The first network node may be an edge enabler server (EES), and the second network node may be an edge application server (EAS). The second network node may register with the first network node. The selection request message may include an application client (AC) intent, and the AC intent may be to communicate with the second network.
[0230] The first network node may detect the ACR on the condition that at least one ACR procedure among the requested one or more ACR procedures includes an ACR procedure for detecting a required ACR at the first network node.
[0231] The first network node may detect the ACR under the condition that at least one ACR procedure among the requested one or more ACR procedures includes an ACR procedure for detecting a required ACR at the second network node.
[0232] Disclosed herein are systems, methods, and tools for ACR selection and / or coordination. A WTRU may receive configuration information about one or more of a first network node, a second network node, and an application client. The WTRU may use the configuration information to determine a first network node and a second network node, and the second network node may be associated with the first network node. The WTRU may transmit a selection request message to the first network node. The selection request message may indicate a request for an application context relocation (ACR) procedure from the first network node, and may indicate service continuity support information associated with the WTRU. The WTRU may receive a selection response message from the first network node, and the selection response message may indicate one or more ACR procedures. The one or more ACR procedures may be supported by the WTRU.
[0233] The first network node may be an edge enabler server (EES) and the second network node may be an edge application server (EAS).The selection request may indicate at least one of security credentials, a WTRU identifier, an application client identifier, or an application client profile.
[0234] The selection request message also indicates an application client (AC) intent, and the AC intent may be to communicate with the second network.The selection response may include a list, and the list may include the one or more ACR procedures supported by the WTRU.
[0235] The WTRU may detect an ACR on the condition that at least one of the one or more ACR procedures received in the selection response includes an ACR procedure for detecting a need for an ACR at the WTRU.
[0236] Disclosed herein are systems, methods, and tools for ACR selection and / or coordination. A first network node may receive a selection request message from a wireless transmit / receive unit (WTRU). The selection request message may request the selection of an application context relocation (ACR) procedure and may indicate service continuity capability information associated with the WTRU. The first network node may determine one or more ACR procedures for providing continuity for a service based on the service continuity capability information associated with the WTRU, the first network node, and the second network node. The first network node may further determine a detection-decision list based on the one or more ACR procedures, and the detection-decision list may include the determined one or more ACR procedures. The determined one or more ACR procedures may be compatible with one or more of the WTRU, the WTRU's application client (AC), the WTRU's edge enabler client (EEC), the first network node, or the second network node. The first network node may transmit a selection response message to the WTRU, and the selection response message may indicate the determined one or more ACR procedures.
[0237] The first network node may be an edge enabler server (EES), and the second network node may be an edge application server (EAS). The first network node may detect the ACR using the one or more ACR procedures. The selection response may include a list, and the list may include the one or more ACR procedures supported by the WTRU. The first network node may transmit a selection notification to the second network node on the condition that the second network node has subscribed to notifications. The service continuity support information may indicate at least the capabilities of the first network node, the capabilities of the second network node, and / or the capabilities of the WTRU.
[0238] Systems, methods, and tools for ACR selection and / or coordination are disclosed herein. A WTRU may detect that an application context relocation (ACR) is required. The WTRU may transmit an ACR coordination request to a first network node under the condition that the WTRU detects that an ACR is required. The WTRU may receive an ACR coordination request response, and based on the ACR coordination response, the WTRU may determine whether to perform the ACR. The WTRU may receive an ACR coordination notification instructing the WTRU to stop ACR detection under the condition that the WTRU does not determine that an ACR is required.
[0239] The first network node may be an edge enabler server (EES). Upon determining that the WTRU or the second network node has requested an ACR, the WTRU may transmit an ACR coordination request to the second network node.
[0240] Disclosed herein are systems, methods, and tools for ACR selection and / or coordination. A first network node may detect whether application context relocation (ACR) is required. The first network node may transmit a first notification to one or more of a wireless transmit receive unit (WTRU) or a second network node under the condition that the first network node detects that an ACR is required. The first network node may stop ACR detection under the condition that the first network node does not detect that an ACR is required and under the condition that the first network node receives a first ACR coordination request. The first network node may transmit a notification to the WTRU and / or the second network node, and the notification may indicate that ACR detection has stopped. The first network node may transmit an ACR coordination response indicating that ACR is allowed to one or more of the WTRU or the second network node. The first network node may indicate to one or more of the WTRU or the second network node that ACR is not allowed under the condition that the first network node receives a second ACR coordination request.
[0241] The first network node may be an edge enabler server (EES) and the second network node may be an edge application server (EAS).The first ACR coordination request may be received from one or more of the WTRU or the second network node.
[0242] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. An ACR selection function (ASF) may be used to select, communicate, and / or manage ACR procedures for service continuity between an edge application server and an application client on a WTRU (wireless transmit / receive unit). An entity (e.g., an EEC or EES) may act as an ASF. Acting as an ASF may include one or more of the following: selecting ACR procedures that can be used for AC and EAS pairs and generating an ACR-detection-decision list (e.g., an ACR list, an ACR identifier, and / or an ACR valid area); selecting an ACF entity when more than one ACR procedure is selected; communicating and / or transmitting an ASF decision (e.g., an ACR-detection-decision list and / or an ACF entity identifier) to other entities (e.g., EEC, EES, and / or EAS); or re-evaluating the selected ACR procedure when selection criteria and / or inputs (e.g., WTRU location, WTRU planned route, WTRU mobility analysis, neighboring EDN ACR capabilities) change.
[0243] When ACR procedures (e.g., concurrent ACR procedures) are used for service continuity between an edge application server and an application client on a WTRU, an ACR coordination function (ACF) may be used to gate ACR execution. An entity (e.g., an EEC or EES) may act as an ACF. Acting as an ACR coordination function (ACF) may include one or more of the following: receiving a request from an entity (e.g., an EEC, an EES, and / or an EAS). The request may indicate that ACR is used (e.g., required) and may request permission to execute the ACR procedure; or transmitting a response to the requesting entity to indicate whether the ACR procedure may be executed.
[0244] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be performed by a processor (e.g., the processor may be configured to perform the method). And the processor may be associated with a device such as a wireless transmit / receive unit (WTRU). Configuration information associated with one or more of a first network node, a second network node, and an application client (AC) may be received. The configuration information may be used to determine the first network node and the second network node. The second network node may provide a service and may be associated with the first network node. One or more application context relocation (ACR) procedures for providing continuity for the service may be determined. These procedures may be based on WTRU capabilities, first network node capabilities, and second network node capabilities. A selection request message may be transmitted to the first network node. The selection request message indicates an identifier of the second network node, a WTRU identifier, and one or more ACR procedures determined. A selection response message may be received from the first network node. The message may indicate a request processing status result.
[0245] In an example, the first network node may be an edge enabler server (EES).The second network node is an edge application server (EAS).
[0246] In an example, a list may be determined based on service continuity capability information associated with the WTRU, the first network node, and the second network node. It may include one or more ACR procedures determined, and these procedures may be compatible with one or more of the WTRU, the AC, the WTRU's edge enabler client (EEC), the first network node, or the second network node.
[0247] In an example, the determined one or more ACR procedures may also be based on service continuity support information of the AC, the WTRU, the EEC, the first network node, or the second network node.
[0248] In an example, the ACR may be detected under the condition of using the determined one or more ACR procedures.
[0249] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be performed by a processor (e.g., the processor may be configured to perform the method). And the processor may be associated with a device such as a first network node. A selection request message may be received from a WTRU. The selection request message may indicate one or more ACR procedures, a second network node identifier, and a WTRU identifier. The second network node identifier may be used to determine that the second network node has subscribed to receive selection notifications. The WTRU identifier may be used to determine that the WTRU may be authorized to communicate with the second network node. A notification message may be transmitted to the second network node, the notification message may indicate one or more ACR procedures requested. A selection response message indicating a request processing status result may be transmitted to the WTRU.
[0250] In an example, the first network node may be an edge enabler server (EES) and the second network node may be an edge application server (EAS).
[0251] In an example, the second network node may register with the first network node.
[0252] In an example, the selection request message may further include an application client (AC) intent. The AC intent may be to communicate with the second network node.
[0253] In an example, the ACR may be detected under the condition that at least one of the requested one or more ACR procedures may include an indication that the first network node is to perform ACR detection.
[0254] In an example, the ACR may be detected under the condition that at least one of the requested one or more ACR procedures may include an indication that the second network node is to perform ACR detection.
[0255] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be performed by a processor (e.g., the processor may be configured to perform the method). And the processor may be associated with a device such as a wireless transmit / receive unit (WTRU). Configuration information associated with at least an application client (AC) may be received. The configuration information may be used to determine a first network node and a second network node. The second network node may be associated with the first network node. A selection request message may be transmitted to the first network node. The selection request message may indicate a request for an application context relocation (ACR) procedure from the first network node. The selection request message may indicate service continuity support information associated with the WTRU. A selection response message may be received from the first network node. The selection response message may indicate one or more ACR procedures that may be supported by the WTRU.
[0256] In an example, the first network node may be an edge enabler server (EES).The second network node may be an edge application server (EAS).
[0257] In an example, the selection request message may indicate at least one of security credentials, a WTRU identifier, an AC identifier, or an AC profile.
[0258] In an example, the selection request message may indicate an AC intention. The AC intention may be to communicate with the second network node.
[0259] In an example, the selection response message may include a list. The list may include the one or more ACR procedures that may be supported by the WTRU.
[0260] In an example, an ACR may be detected. The ACR detection may occur under the condition that at least one of the one or more ACR procedures received in the selection response message may include an ACR procedure for detecting an ACR at the WTRU, for example.
[0261] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be performed by a processor (e.g., the processor may be configured to perform the method). And the processor may be associated with a device such as a first network node. A selection request message may be received from a wireless transmit / receive unit (WTRU). The selection request message may request selection of an application context relocation (ACR) procedure and may indicate service continuity capability information associated with the WTRU. One or more ACR procedures for providing continuity for a service may be selected based on service continuity capability information associated with the WTRU, the first network node, and the second network node. A list may be determined based on the selected one or more ACR procedures. The list may include at least one or more selected ACR procedures. The selected one or more ACR procedures may be compatible with one or more of the WTRU, the application client (AC) of the WTRU, the edge enabler client (EEC) of the WTRU, the first network node, or the second network node. A selection response message indicating the list may be transmitted to the WTRU.
[0262] In an example, the first network node may be an edge enabler server (EES) and the second network node may be an edge application server (EAS).
[0263] In an example, the ACR may be detected under the condition that the list may include an indication that the second network node is to perform ACR detection.
[0264] In an example, the selection notification may be transmitted to the second network node on the condition that the second network node has subscribed to notifications.
[0265] In an example, the service continuity capability information may indicate at least the capability of the first network node, the capability of the second network node, or the capability of the WTRU.
[0266] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be executed by a processor (e.g., the processor may be configured to execute the method). And the processor may be associated with a device such as a wireless transmit / receive unit (WTRU). When an application context relocation (ACR) event may be detected, a first ACR coordination message may be transmitted to a first network node. The ACR event may be detected according to an ACR procedure. A second ACR coordination message may be received from the first network node. An ACR execution message may be generated based on the second ACR coordination message. The ACR execution message may be generated according to the ACR procedure. The ACR execution message may be transmitted to at least one of the first network node or the second network node.
[0267] In an example, the first ACR coordination message may be an ACR coordination request. The second ACR coordination message may be an ACR coordination response message.
[0268] In an example, the second ACR coordination message may be at least one of an ACR coordination notification message or an ACR coordination response message.
[0269] In an example, the second ACR coordination message may indicate that ACR execution is to be performed by the WTRU.
[0270] In an example, the ACR event may be detected.
[0271] In an example, the ACR event may be detected under the condition that the ACR procedure indicates a procedure for detecting ACR at the WTRU.
[0272] In an example, a selection response message may be received from the first network node. The selection response message may indicate the ACR procedure.
[0273] In an example, the first network node may be a first edge enabler server (EES).The second network node may be a second EES or an edge configuration server (ECS).
[0274] Disclosed herein are systems, methods, and tools for application context relocation (ACR) selection and / or coordination. For example, a method may be provided that may be performed by a processor (e.g., the processor may be configured to perform the method). And the processor may be associated with a device such as a first network node. A first application context relocation (ACR) coordination message may be received from at least one of a wireless transmit / receive unit (WTRU) or a second network node. An entity for performing an ACR procedure may be determined. The entity may be one of the first network node, the second network node, or the WTRU. A first coordination decision may be determined based on an identifier of the determined entity and the WTRU. A second coordination decision may be determined based on an identifier of the determined entity and the second network node. A second ACR coordination message may be transmitted to the WTRU. The second ACR coordination message may indicate the first coordination decision. A third ACR coordination message may be transmitted to the second network node. The third ACR coordination message may indicate the second coordination decision.
[0275] In an example, the first coordination decision may indicate that the WTRU may be an ACR execution entity.The second coordination decision may indicate that the second network node will wait for ACR execution.
[0276] In an example, the first coordination decision may indicate that the WTRU is to wait for ACR execution.The second coordination decision may indicate that the second network node is an ACR execution entity.
[0277] In an example, the first coordination decision may indicate that the WTRU is to wait for ACR execution.The second coordination decision may indicate that the second network node is to wait for ACR execution.
[0278] In an example, an ACR event may be detected.
[0279] In an example, the ACR event may be detected under the condition that the ACR procedure may indicate a procedure for detecting an ACR at the first network node.
[0280] In an example, the first network node may be a first edge enabler server (EES).The second network node may be at least one of a second EES, an edge application server (EAS), or an edge configuration server (ECS).
[0281] Although the above features and elements are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without the other features and elements.
[0282] Although the implementations described herein may consider 3GPP specific protocols, it should be understood that the implementations described herein are not limited to such scenarios and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it should be understood that the solutions described herein are not limited to such scenarios and may be applicable to other wireless systems.
[0283] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or a processor. Examples of computer-readable media include, but are not limited to, electronic signals (sent via a wired or wireless connection) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as, but not limited to, built-in hard disks and removable disks), magneto-optical media, and optical media (such as compact disk (CD)-ROM disks and / or digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, a terminal, a base station, an RNC, and / or any host computer.
Claims
1. A wireless transmit / receive unit (WTRU), the WTRU comprising: A processor, the processor being configured to: receiving configuration information associated with one or more of a first network node, a second network node, and an application client (AC); determining, using the configuration information, the first network node and the second network node, wherein the second network node provides a service, and wherein the second network node is associated with the first network node; determining one or more application context relocation (ACR) procedures for providing continuity for the service based on the WTRU capabilities, the first network node capabilities, and the second network node capabilities; transmitting a selection request message to the first network node, wherein the selection request message indicates an identifier of the second network node, a WTRU identifier, and the determined one or more ACR procedures; as well as A selection response message indicating a request processing status result is received from the first network node.
2. The WTRU of claim 1 , wherein the first network node is an edge enabler server (EES), and wherein the second network node is an edge application server (EAS).
3. The WTRU of claim 1, wherein the processor is further configured to determine a list based on service continuity capability information associated with the WTRU, the first network node, and the second network node, wherein the list includes one or more determined ACR procedures, and wherein the determined one or more ACR procedures are compatible with one or more of the WTRU, the AC, the WTRU's edge enabler client (EEC), the first network node, or the second network node.
4. The WTRU of claim 1, wherein the determined one or more ACR procedures are also based on service continuity support information of the AC, the WTRU, the EEC, the first network node, or the second network node.
5. The WTRU of claim 1, wherein the processor is further configured to detect an ACR conditionally using the determined one or more ACR procedures.
6. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: receiving configuration information associated with one or more of a first network node, a second network node, and an application client (AC); determining, using the configuration information, the first network node and the second network node, wherein the second network node provides a service, and wherein the second network node is associated with the first network node; determining one or more application context relocation (ACR) procedures for providing continuity for the service based on the WTRU capabilities, the first network node capabilities, and the second network node capabilities; transmitting a selection request message to the first network node, wherein the selection request message indicates an identifier of the second network node, a WTRU identifier, and the determined one or more ACR procedures; as well as A selection response message is received from the first network node indicating a request processing status.
7. The method of claim 6, wherein the first network node is an edge enabler server (EES), and wherein the second network node is an edge application server (EAS).
8. The method of claim 6, wherein the method further comprises determining a list based on service continuity capability information associated with the WTRU, the first network node, and the second network node, wherein the list includes one or more determined ACR procedures, and wherein the determined one or more ACR procedures are compatible with one or more of the WTRU, the AC, the WTRU's edge enabler client (EEC), the first network node, or the second network node.
9. The method of claim 6, wherein the determined one or more ACR procedures are also based on service continuity support information of the AC, the WTRU, the EEC, the first network node, or the second network node. 10 . The method of claim 6 , wherein the method further comprises detecting the ACR under the condition of using the determined one or more ACR protocols.
11. A first network node, the first network node comprising: A processor, the processor being configured to: receiving a select request message from a wireless transmit / receive unit (WTRU), wherein the select request message indicates one or more application context relocation (ACR) procedures, a second network node identifier, and a WTRU identifier; using the second network node identifier to determine that the second network node has subscribed to receive selection notifications; using the WTRU identifier and security credentials to determine that the WTRU is authorized to communicate with the second network node; transmitting a notification message to the second network node, wherein the notification message indicates the requested one or more ACR procedures; as well as A selection response message is transmitted to the WTRU indicating a result of the request processing status.
12. The first network node of claim 11, wherein the first network node is an edge enabler server (EES), and wherein the second network node is an edge application server (EAS).
13. The first network node of claim 11, wherein the second network node is registered with the first network node.
14. The first network node of claim 11, wherein the selection request message further includes an application client (AC) intent, and wherein the AC intent is to communicate with the second network node.
15. The first network node of claim 11, wherein the processor is further configured to detect ACRs on the condition that at least one of the requested one or more ACR procedures includes an indication that the first network node is to perform ACR detection. 16 . The first network node of claim 11 , wherein the processor is further configured to detect an ACR on the condition that at least one of the requested one or more ACR procedures includes an indication that the second network node is to perform ACR detection.
17. A method performed by a first network node, the method comprising: receiving a select request message from a wireless transmit / receive unit (WTRU), wherein the select request message indicates one or more application context relocation (ACR) procedures, a second network node identifier, a WTRU identifier, and security credentials; using the second network node identifier to determine that the second network node has subscribed to receive selection notifications; determining, using the WTRU identifier and the security credentials, that the WTRU is authorized to communicate with the second network node; transmitting a notification message to the second network node, wherein the notification message indicates the requested one or more ACR procedures; as well as A selection response message is transmitted to the WTRU indicating a result of the request processing status.
18. The method of claim 17, wherein the first network node is an edge enabler server (EES), and wherein the second network node is an edge application server (EAS).
19. The method of claim 17, wherein the second network node registers with the first network node.
20. The method of claim 17, wherein the select request message further includes an application client (AC) intent, and wherein the AC intent is to communicate with the second network node.
21. The method of claim 17, wherein the method further comprises detecting the ACR under the condition that at least one of the requested one or more ACR procedures includes an indication that the second network node is to perform ACR detection.
22. The method of claim 17, wherein the method further comprises detecting the ACR on the condition that at least one of the requested one or more ACR procedures includes an indication that the second network node is to perform ACR detection.
23. A wireless transmit / receive unit (WTRU), the WTRU comprising: A processor, the processor being configured to: receiving configuration information associated with at least an application client (AC); determining a first network node and a second network node using the configuration information, wherein the second network node is associated with the first network node; transmitting a selection request message to the first network node, wherein the selection request message indicates a request for an application context relocation (ACR) procedure from the first network node and indicates service continuity support information associated with the WTRU; as well as A selection response message is received from the first network node, wherein the selection response message indicates one or more ACR procedures, wherein the one or more ACR procedures are supported by the WTRU.
24. The WTRU of claim 23, wherein the first network node is an edge enabler server (EES), and wherein the second network node is an edge application server (EAS).
25. The WTRU of claim 23, wherein the selection request message further indicates at least one of security credentials, a WTRU identifier, an AC identifier, or an AC profile.
26. The WTRU of claim 23, wherein the selection request message further indicates an AC intent, and wherein the AC intent is to communicate with the second network node.
27. The WTRU of claim 23, wherein the selection response message further comprises a list, and wherein the list further comprises the one or more ACR procedures supported by the WTRU.
28. The WTRU of claim 23, wherein the processor is further configured to detect an ACR under the condition that at least one of the one or more ACR procedures received in the selection response message includes an ACR procedure for detecting an ACR at the WTRU.
29. A first network node, the first network node comprising: A processor, the processor being configured to: receiving a selection request message from a wireless transmit / receive unit (WTRU), wherein the selection request message requests selection of an application context relocation (ACR) procedure and indicates service continuity capability information associated with the WTRU; selecting one or more ACR procedures for providing continuity for service based on the service continuity capability information associated with the WTRU, the first network node, and the second network node; determining a list based on the selected one or more ACR procedures, wherein the list includes at least the selected one or more ACR procedures, wherein the selected one or more ACR procedures are compatible with one or more of the WTRU, an application client (AC) of the WTRU, an edge enabler client (EEC) of the WTRU, the first network node, or the second network node; and A selection response message is transmitted to the WTRU, wherein the selection response message indicates the list.
30. The first network node of claim 29, wherein the first network node is an edge enabler server (EES), and wherein the second network node is an edge application server (EAS).
31. The first network node of claim 29, wherein the processor is further configured to detect an ACR conditional on the list including an indication that the second network node is to perform an ACR detection.
32. The first network node of claim 29, wherein the processor is further configured to transmit a selection notification to the second network node on the condition that the second network node has subscribed to notifications.
33. The first network node of claim 29, wherein the service continuity capability information indicates at least a capability of the first network node, a capability of the second network node, or a capability of the WTRU.
34. A wireless transmit / receive unit (WTRU), the WTRU comprising: A processor, the processor being configured to: When an application context relocation (ACR) event is detected, transmitting a first ACR coordination message to a first network node, wherein the ACR event is detected according to an ACR procedure; receiving a second ACR coordination message from the first network node; generating an ACR execute message based on the second ACR coordination message, wherein the ACR execute message is generated according to the ACR procedure; as well as The ACR execution message is transmitted to at least one of the first network node or the second network node.
35. The WTRU of claim 34, wherein the first ACR coordination message is an ACR coordination request and the second ACR coordination message is an ACR coordination response message.
36. The WTRU of claim 34, wherein the second ACR coordination message is at least one of an ACR coordination notification message or an ACR coordination response message.
37. The WTRU of claim 34, wherein the second ACR coordination message indicates that ACR execution is to be performed by the WTRU.
38. The WTRU of claim 34, wherein the processor is further configured to detect the ACR event.
39. The WTRU of claim 34, wherein the processor is configured to detect the ACR event under the condition that the ACR procedure indicates a procedure for detecting ACR at the WTRU.
40. The WTRU of claim 34, wherein the processor is further configured to receive a selection response message from the first network node, wherein the selection response message indicates the ACR procedure.
41. The WTRU of claim 34, wherein the first network node is a first edge enabler server (EES), and wherein the second network node is a second EES or an edge configuration server (ECS).
42. A first network node, the first network node comprising: A processor, the processor being configured to: receiving a first application context relocation (ACR) coordination message from at least one of a wireless transmit / receive unit (WTRU) or a second network node; determining an entity for performing an ACR procedure, wherein the entity is one of the first network node, the second network node, or the WTRU; determining a first coordination decision based on the determined entity and an identity of the WTRU; determining a second coordination decision based on the determined entity and the identification of the second network node; transmitting a second ACR coordination message to the WTRU, wherein the second ACR coordination message indicates the first coordination decision; and A third ACR coordination message is transmitted to the second network node, wherein the third ACR coordination message indicates the second coordination decision.
43. The first network node of claim 42, wherein the first coordination decision indicates that the WTRU is an ACR execution entity, and wherein the second coordination decision indicates that the second network node is to wait for ACR execution.
44. The first network node of claim 42, wherein the first coordination decision indicates that the WTRU is to wait for ACR execution, and wherein the second coordination decision indicates that the second network node is an ACR execution entity.
45. The first network node of claim 42, wherein the first coordination decision indicates that the WTRU is to wait for ACR execution, and wherein the second coordination decision indicates that the second network node is to wait for ACR execution.
46. The first network node of claim 42, wherein the processor is further configured to detect an ACR event.
47. The WTRU of claim 42, wherein the processor is configured to detect the ACR event under the condition that the ACR procedure indicates a procedure for detecting an ACR at the first network node.
48. The WTRU of claim 42, wherein the first network node is a first edge enabler server (EES), and wherein the second network node is at least one of a second EES, an edge application server (EAS), or an edge configuration server (ECS).
