Methods, architectures, apparatuses and systems for prediction-based mobility triggering in wireless networks

Abstract

Programs, methods, architectures, apparatuses, systems, devices, and computer program products for handover processes use network predictive measurements. For example, a wireless transmit / receive unit (WTRU) may receive a handover command. The WTRU may receive a first set of measurements from a network. For example, the first set may be predictive measurements. The network may generate a first set using artificial intelligence and / or machine learning models. The WTRU may obtain (e.g., measure and / or predict) a second set of measurements. The first set of measurements and / or the second set of measurements may be associated with (e.g., the same) a first time interval and / or a confidence level. Based on a comparison between the first set and the second set, the WTRU may determine (i) to perform a handover within the second time interval, and / or (ii) to send feedback information. For example, the WTRU may determine an ideal time at which the handover is actually performed.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of (i) U.S. Provisional Patent Application No. 63 / 395,519 filed on August 5, 2022, and (ii) 63 / 410,727 filed on September 28, 2022, and (iii) 63 / 421,903 filed on November 2, 2022; each of which is incorporated herein by reference. Technical Field

[0002] The present disclosure generally relates to the fields of communications, software, and coding, including, for example, methods, architectures, devices, and systems for triggering a mobility procedure, such as a cellular handover (HO), based on network predictions, such as predicted signal levels of serving and / or neighbor cells. More specifically, after receiving a HO command from the network or detecting a triggering condition for a conditional HO, an ideal time to actually perform the HO can be determined. Background Art

[0003] Cellular HO may encounter failures due to being performed too late, performed too early, or to the wrong cell. A solution would be desirable to address such scenarios where HO may fail. Summary of the invention

[0004] In a representative embodiment, a wireless transmit / receive unit (WTRU) may receive information indicating a network predicted first set of radio measurements and a timestamp. The WTRU may receive configuration information indicating a handover (HO) window and a time offset for a target cell. The WTRU may perform and / or predict a second set of radio measurements based on the timestamp. The WTRU may send information indicating an evaluation of the network predicted first set of radio measurements and a second set of radio measurements at one or more first times no later than a time offset before the HO window. The one or more first times may be based on the HO window and the time offset. The WTRU may perform a HO to the target cell based on the configuration information at a second time within the HO window. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] A more detailed understanding can be obtained from the following detailed description given by way of example in conjunction with the accompanying drawings. As with the detailed description, the drawings in such drawings are examples. Therefore, the drawings (FIG.) and detailed description should not be considered limiting, and other equally effective examples are possible. In addition, like reference numerals ("ref.") in the drawings indicate like elements, and among them: Figure 1A is a system diagram illustrating an example communication system; Figure 1B It is a diagram that can be Figure 1AA system diagram of an example wireless transmit / receive unit (WTRU) for use within the communication system is shown; Figure 1C It is a diagram that can be Figure 1A A system diagram of an example radio access network (RAN) and an example core network (CN) used within the illustrated communication system; Figure 1D It is a diagram that can be Figure 1A A system diagram of a further example RAN and a further example CN used within the illustrated communication system; Figure 2 is a process diagram illustrating an example RRC reconfiguration sequence; Figure 3 is a process diagram illustrating an example RRC recovery sequence; Figure 4 is a list illustrating examples of a plurality of events associated with a measurement report trigger; Figure 5 is a timing diagram illustrating an example of measurement report triggering; Figure 6 is a process diagram illustrating an example cell level mobility sequence; Figure 7 is a system diagram illustrating an overview of what happens to a WTRU over time in the context of a handover; Figure 8 is a block diagram illustrating an example of obtaining a network prediction of RSRP; Fig. 9 is a block diagram illustrating an example of obtaining a WTRU prediction of RSRP; Fig.10 is a block diagram illustrating an example of obtaining a WTRU prediction of a UL buffer status; Fig.11 is a block diagram illustrating an example of obtaining a WTRU prediction of a number of retransmissions; Fig.12 is a timing diagram illustrating an example of a network prediction process; Fig.13 is a timing diagram illustrating examples of fixed and variable RSRP boundaries; Fig.14 is a system diagram illustrating an overview of what happens to a WTRU over time in the context of utilizing a predicted handover; Fig.15 is a timing diagram illustrating an example of a handover process utilizing prediction; Fig.16 is a timing diagram illustrating an example of handover triggering for different handover types and WTRU prediction lengths; Fig.17is a flow chart illustrating an example of a layer 3 (L3) communication process according to certain embodiments; Fig.18 is a flow chart illustrating an example of a layer 3 (L3) communication process according to certain embodiments; Fig.19 is a process diagram illustrating an example feedback and HO procedure for a WTRU; Fig. 20 is a process diagram illustrating an example HO procedure for a WTRU; Fig.21 is a process diagram illustrating an example feedback process for a WTRU; Fig. 22 is a process diagram illustrating an example admission control process for a first base station; Fig.23 is a process diagram illustrating an example HO procedure for a WTRU; Fig.24 is a process diagram illustrating an example HO procedure for a WTRU; and Fig.25 is a process diagram illustrating an example feedback process for a base station. DETAILED DESCRIPTION

[0006] In the following specific embodiments, many specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples can be practiced without some or all of the specific details set forth herein. In other cases, well-known methods, processes, components and circuits have not yet been described in detail to avoid blurring the following description. Further, the embodiments and examples not specifically described herein can be replaced by or in combination with the embodiments and other examples described herein, disclosed or otherwise explicitly, implicitly and / or inherently provided (collectively referred to as "providing") to practice. Although various embodiments are described and / or claimed herein, wherein devices, systems, equipment, etc. and / or any of its elements perform operations, processes, algorithms, functions, etc. and / or any part thereof, it is to be understood that any embodiments described and / or claimed herein assume that any device, system, equipment, etc. and / or any of its elements are configured to perform any operations, processes, algorithms, functions, etc. and / or any part thereof.

[0007] Example Communication System The methods, devices, and systems provided herein are well suited for communications involving both wired and wireless networks. Figures 1A to 1D An overview of various types of wireless devices and infrastructure is provided in which various elements of the network can utilize, perform, be arranged according to, and / or be adapted for and / or configured for the methods, apparatus, and systems provided herein.

[0008] Figure 1A 1 is a system 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 by sharing 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 (ZT) unique word (UW) discrete Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0009] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, although it will be appreciated 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 transmit and / or receive wireless signals and may include (or be) a 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 context), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, 102d may be interchangeably referred to as a UE.

[0010] 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 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 any of a base transceiver station (BTS), a Node B (NB), an eNode-B (eNB), a home Node B (HNB), a home eNode-B (HeNB), a gNode-B (gNB), a NR Node B (NR NB), a site controller, an access point (AP), a wireless router, and the like. Although the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0011] 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 transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of a licensed spectrum and an unlicensed spectrum. A cell may provide coverage for a specific geographic area for a wireless service, 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 one embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology, and multiple transceivers may be used for each or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0012] 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, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0013] 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 116. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink Packet Access (HSUPA).

[0014] In one 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).

[0015] 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).

[0016] 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 dual connectivity (DC) principles. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0017] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi)), 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 Evolution (GERAN), etc.

[0018] Figure 1A The base station 114b in the example may be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In one 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 any of a small cell, a pico cell, or a femto cell. 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.

[0019] The RAN 104 / 113 may communicate 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 calls, Internet connectivity, video distribution, etc. and / or perform advanced security functions, such as user authentication. Although Figure 1A Not shown, but 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, which may 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 may employ any of GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi radio technologies.

[0020] The CN 106 / 115 may also act 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 using 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 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 / 114 or a different RAT.

[0021] 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 the base station 114b, which may employ an IEEE 802 radio technology.

[0022] 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 keyboard 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 elements / peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the above elements while remaining consistent with an embodiment.

[0023] 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 coding, 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 will be appreciated that the processor 118 and the transceiver 120 may be integrated together, such as in an electronic package or chip.

[0024] The transmission / reception element 122 can be configured to transmit signals to a base station (e.g., base station 114a) or receive signals from a base station via an air interface 116. For example, in one embodiment, the transmission / reception element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmission / reception element 122 can be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In one embodiment, the transmission / reception element 122 can be configured to transmit and / or receive both RF and optical signals. It will be appreciated that the transmission / reception element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0025] Although the transmit / receive element 122 Figure 1B Although depicted as a single element in the figure, the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an 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.

[0026] 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. Thus, for example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate, for example, via multiple RATs, such as NR and IEEE 802.11.

[0027] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keyboard 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), and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, the keyboard 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, or the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0028] 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-chromium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0029] 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. 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 in addition to or in lieu of the information from the GPS chipset 136. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0030] The processor 118 may be further coupled to other components / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functionality, and / or wired or wireless connectivity. For example, the components / peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (e.g., for photos and / or videos), 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. Component / 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.

[0031] 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 uplink (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 to reduce and / or substantially eliminate self-interference via hardware (e.g., choke) or via signal processing performed by a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WTRU 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 uplink (e.g., for transmission) or ...

[0032] 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 employs E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0033] The RAN 104 may include eNode-Bs 160a, 160b, 160c, although it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-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 an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0034] Each of the eNode-Bs 160a, 160b, and 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 the uplink (UL) and / or downlink (DL), etc. Figure 1C As shown, eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

[0035] 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 (PGW) 166. While each of the foregoing elements is depicted as being part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by entities other than the CN operator.

[0036] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c 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.

[0037] The SGW 164 may be connected to each of the eNode 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-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the contexts of the WTRUs 102a, 102b, 102c, and the like.

[0038] 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.

[0039] 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 and / or wireless networks owned and / or operated by other service providers.

[0040] Although the WTRU Figures 1A to 1D Although described as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may use (eg, temporarily or permanently) a wired communications interface with a communications network.

[0041] In a representative embodiment, other network 112 may be a WLAN.

[0042] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STAs) 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 into the BSS and / or carries traffic out of the BSS. Traffic originating from outside the BSS to the STA may be reached by the AP and may be delivered to the STA. Traffic from the STA to a destination outside the BSS may be sent to the AP so as to be delivered to the corresponding destination. Traffic between STAs within the BSS may be sent by the AP, for example, where the source STA may send traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as peer traffic. Peer traffic may be sent between the source and destination STAs (e.g., directly between them) using a direct link setup (DLS). 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 (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

[0043] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP can transmit beacons on a fixed channel (such as a primary channel). The primary channel can be a fixed width (e.g., a 20MHz wide bandwidth) or a width that is dynamically set via signaling. The primary channel can be an operating channel of the BSS and can be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access with collision avoidance (CSMA / CA) can be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) including the AP can sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA can back off. One STA (e.g., only one station) can transmit at any given time in a given BSS.

[0044] A high throughput (HT) STA may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and an adjacent or non-adjacent 20 MHz channel to form a 40 MHz wide channel.

[0045] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz 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 (which can be referred to as 80+80 configurations). For 80+80 configurations, after channel coding, data can be passed through a segment parser that can divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be done separately on each stream. The stream can be mapped to two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to a media access control (MAC) layer, an entity, etc.

[0046] The operation mode below 1 GHz is supported by 802.11af and 802.11ah. The channel operation bandwidth and carrier are reduced in 802.11af and 802.11ah relative to the channel operation bandwidth and carrier used in 802.11n and 802.11ac. 802.11af supports 5MHz bandwidth, 10MHz bandwidth and 20MHz bandwidth in the TV white space (TVWS) spectrum, and 802.11ah supports 1MHz bandwidth, 2MHz bandwidth, 4MHz bandwidth, 8MHz bandwidth and 16MHz bandwidth using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, for example, limited capabilities, including support for (e.g., only support for) certain and / or limited bandwidths. MTC devices may include batteries whose battery life is above a threshold (e.g., to maintain a very long battery life).

[0047] A WLAN system that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) includes a channel that can be designated as a primary channel. 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 the STA that supports the minimum bandwidth operating mode among 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) 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, due to a STA (which only supports the 1MHz operating mode) transmitting to the AP, the entire available band may be considered busy, even if most of the band is still idle and can be available.

[0048] In the United States, the available frequency band that 802.11ah can use is from 902MHz to 928MHz. In South Korea, the available frequency band is from 917.5MHz to 923.5MHz. In Japan, the available frequency band is from 916.5MHz to 927.5MHz. Depending on the country code, the total bandwidth available for 802.11ah is 6MHz to 26MHz.

[0049] 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.

[0050] The RAN 113 may include gNBs 180a, 180b, 180c, although 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 an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the WTRUs 102a, 102b, 102c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In one embodiment, gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, gNB 180a may transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In one embodiment, gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) techniques. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0051] The WTRUs 102a, 102b, 102c may use transmissions associated with scalable numerology. 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 various or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).

[0052] 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 without accessing other RANs (e.g., such as, eNode-Bs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize 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 WTRUs 102a, 102b, 102c may communicate / connect to the gNBs 180a, 180b, 180c while also communicating / connecting to another RAN, such as the eNode-Bs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may act as a mobility anchor for the WTRUs 102a, 102b, 102c and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput to serve the WTRUs 102a, 102b, 102c.

[0053] Each of the gNBs 180a, 180b, 180c may be associated with a specific 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.

[0054] 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 at least one data network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by entities other than the CN operator.

[0055] 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, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. Network slicing may be used by the AMF 182a, 182b, for example, to customize CN support for the WTRU 102a, 102b, 102c based on the type of service 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 massive mobile broadband (eMBB) access, services for 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-APro, and / or non-3GPP access technologies, such as Wi-Fi.

[0056] 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 traffic routing through the UPF 184a, 182b. 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.

[0057] 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, for example, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184a, 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.

[0058] 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 and / or wireless networks owned and / or operated by other service providers. In an embodiment, the WTRUs 102a, 102b, 102c may be connected to a local data network (DN) 185a, 185b through the UPF 184a, 184b via an N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0059] Given that Figures 1A to 1D as well as Figures 1A to 1D 102a to 102d, base stations 114a to 114b, eNode-Bs 160a to 160c, MMEs 162, SGWs 164, PGWs 166, gNBs 180a to 180c, AMFs 182a to 182b, UPFs 184a to 184b, SMFs 183a to 183b, DNs 185a to 185b, and / or any other element / device described herein. A simulation device may be one or more devices configured to simulate one or more or all of the functions described herein. For example, a simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0060] The simulation device can be designed to implement one or more tests of other devices in a laboratory environment and / or in a carrier network environment. For example, one or more simulation devices can perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device can be directly coupled to another device for the purpose of testing and / or can use over-the-air wireless communications to perform testing.

[0061] One or more simulation devices can perform one or more or all functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used for test scenarios in a test lab and / or non-deployed (e.g., testing) wired and / or wireless communication networks to enable testing of one or more components. One or more simulation devices can be test devices. Direct RF coupling and / or wireless communication via RF circuits (e.g., which can include one or more antennas) can be used by the simulation device to transmit and / or receive data.

[0062] introduce In certain representative embodiments, the WTRU 102 may be configured with any of the following: (1) a handover (HO) message, (2) a serving cell and / or neighbor cell signal level predicted (e.g., by the network), (3) a first duration / interval (or an indication thereof), and / or (4) a second duration / interval (or an indication thereof). For example, the predicted cell signal level may be based on artificial intelligence (AI) and / or machine learning (ML). The WTRU 102 may perform a HO for the second duration if the signal level predicted (e.g., by the network) satisfies (e.g., within a certain error level, range, or margin) a (e.g., actual) measurement performed or predicted by the WTRU 102 for (or during) the first duration.

[0063] In certain representative embodiments, the WTRU 102 may send feedback information regarding predicted services provided by the network and / or neighbor signal levels. For example, the feedback information may be triggered (e.g., sent) under the condition that there is a mismatch (e.g., exceeding a certain error level, range, or margin) between the predicted signal level and the (e.g., actual) measurement performed or predicted by the WTRU 102 (e.g., within a first duration).

[0064] In certain representative embodiments, a network (eg, RAN) node may perform enhanced admission control by validating admission of a WTRU based on a prediction of a time when the WTRU 102 will be handed over (eg, performing a HO) (eg, in the future).

[0065] Overview The following acronyms may be used in this article: ACK BLER Block Error Rate BWP Bandwidth Part CAP Channel Access Priority CAPC Channel Access Priority Level CCA Clear Channel Assessment CCE Control Channel Element CE Control Elements CG The authorization or cell group configured CHO Conditional Transfer CLI cross-linking interference CP Cyclic Prefix CP-OFDM Conventional OFDM (depends on cyclic prefix) CQI Channel Quality Indicator CRC Cyclic Redundancy Check CSI Channel State Information CW Competition Window CWS Contention Window Size CO channel occupancy DAI Downstream Assignment Index DAPS Dual Access Protocol Stack DCI Downlink Control Information DFI Downlink Feedback Information DG Dynamic Authorization DL Downlink DM-RS Demodulation Reference Signal DRB Data Radio Bearer eLAA Enhanced License Assisted Access FeLAA further enhanced licensed assisted access HARQ Hybrid Automatic Repeat Request KPI Key Performance Indicator LAA License Assisted Access LBT Listen before talking LTE Long Term Evolution, e.g. from 3GPP LTE Release 8 and above NACK Negative ACK MCS Modulation Coding Scheme MIMO Multiple Input Multiple Output NR New Radio OFDM Orthogonal Frequency Division Multiplexing PHY Physical Layer PID Process ID PO Paging time PRACH Physical Random Access Channel PSS Primary Sync Signal RA Random Access (or procedure) RACH Random Access Channel RAR Random Access Response RCU Radio Access Network Central Unit RF Radio Front End RLF Radio Link Failure RLM Radio Link Monitoring RNTI Radio Network Identifier RO RACH Timing RRC Radio Resource Control RRM Radio Resource Management RS reference signal RSRP Reference Signal Received Power RSSI Received Signal Strength Indicator SDU Service Data Unit SL Side Link SRS Sounding Reference Signal SS Sync Signal SSB Synchronous Signal Block SSS Auxiliary Sync Signal SWG Switching Gap (in self-contained subframe) SPS Semi-persistent Scheduling SUL Supplementary Uplink TB Transfer Block TBS Transport Block Size TRP Transmission / Reception Point TSC Time Sensitive Communications TSN Time Sensitive Networking UL Uplink URLLC Ultra-Reliable Low Latency Communications WBWP Wide Bandwidth Part WLAN Wireless Local Area Network and related technologies (IEEE 802.xx domain).

[0066] The HO failure KPI may (e.g., always) suffer from degradation to some extent. For example, in 3GPP, HO failures are classified into three categories: too early HO, too late HO, and HO to the wrong cell. In many instances, these failures may be due to incorrect network configuration and / or signaling delays required for mobility operations. Incorrect configuration may lead to unnecessary resource reservation at the target HO node. Mobility decisions are based on measurements, and Uu latency may create a gap between the WTRU radio experience and the corresponding network perception. As an example, the problem in this context is too late HO. AI / ML techniques can be used to solve these problems.

[0067] In certain representative embodiments, the HO evaluation strategy transfer from the network to the WTRU may be based on an AI / ML approach. For example, the network (e.g., a network entity) may predict HO related configurations and WTRU measurements. The predicted HO strategy (e.g., a HO command and the network predicted measurements on which the HO is based) may be sent to the WTRU 102 along with evaluation criteria (e.g., duration and / or time information of the predicted measurements). The WTRU 102 may verify the provided predicted measurements (e.g., by comparing the predicted measurements with current and / or actual measurements) over a certain duration or interval. Under the condition that the WTRU 102 determines that there is a satisfactory match (e.g., the deviation or difference (such as mean square error) between the predicted measurements and the actual measurements is below a certain level), the WTRU 102 will execute the HO command (e.g., within a certain duration after the verification period). Under the condition that the WTRU 102 determines that there is no satisfactory match (e.g., the deviation or difference is above a certain level), the WTRU 102 may avoid performing the HO and may send feedback information to the network. For example, the feedback may be information such as measurements performed by the WTRU 102 and / or the error level between the provided predicted measurements and the measurements performed by the WTRU 102.

[0068] Measurement configuration In certain representative embodiments, the WTRU 102 (e.g., in RRC_Connected) may be configured by the network to perform measurements and report the measurements back to the network (e.g., according to a specific configuration). For example, the configuration may be provided and / or indicated (e.g., measuring and / or reporting) via signaling (e.g., using an RRCReconfiguration or RRCResume message). Figure 2 is a process diagram illustrating an RRC reconfiguration sequence 200. At 202, the network may send an RRCReconfiguration message to the WTRU 102. At 204, the WTRU 102 may respond with an RRCReconfigurationComplete message. Figure 3is a process diagram illustrating an RRC recovery sequence 300. At 302, the WTRU 102 may send a RRCResumeRequest (or RRCResumeRequest1) message to the network. At 304, the network may send a RRCResume message to the WTRU 102. At 306, the WTRU 102 may respond with a RRCResumeComplete message.

[0069] In certain representative embodiments, the WTRU 102 may perform RS measurements, such as any of SSB, CSI-RS, SRS, etc., using a network-provided configuration.

[0070] For example, the network may configure the WTRU 102 to report any of the following measurement information based on the SS / PBCH block(s): -Measurement of each SS / PBCH block; - Measurements based on each cell of (multiple) SS / PBCH blocks; and / or -(multiple) SS / PBCH block indices.

[0071] For example, the network may configure the WTRU 102 to report any of the following measurement information based on the CSI-RS resources: - Measurement of each CSI-RS resource; - Measurement based on each element of the CSI-RS resource(s); and / or -CSI-RS resource measurement identifier.

[0072] For example, the network may configure the WTRU 102 to perform any of the following types of measurement information (e.g., for NR SL and / or V2X SL): -CBR measurement.

[0073] For example, the network may configure the WTRU 102 to report any of the following CLI measurement information based on the SRS resources: - Measurement of each SRS resource; and / or -(multiple) SRS resource indexes.

[0074] For example, the network may configure the WTRU 102 to report any of the following CLI measurement information based on the CLI-RSSI resource: - Measurement of each CLI-RSSI resource; and / or -(multiple) CLI-RSSI resource indexes.

[0075] Measurement report configuration In certain representative embodiments, the measurement report configuration may include any of the following: - Reporting criteria: the criteria(s) that trigger the WTRU 102 to send a measurement report, such as periodicity and / or single event description; - RS type: the RS used by the WTRU 102 for beam and cell measurement results, such as SSB or CSI-RS; and / or - Report format: the number of each cell and / or each beam included by the WTRU 102 in the measurement report (e.g., RSRP) and other associated information, such as the maximum number of cells to be reported and the maximum number of beams per cell.

[0076] In certain representative embodiments, WTRU measurement reporting may be configured by the network to be triggered based on any of the following: Periodic Reports: ReportInterval::=ENUMERATED{ms120,ms240,ms480,ms640,ms1024,ms2048,ms5120,ms10240,ms20480,ms40960,min1,min6,min12,min30} Event triggered by: ReportInterval::=ENUMERATED{ms120,ms240,ms480,ms640,ms1024,ms2048,ms5120,ms10240,ms20480,ms40960,min1,min6,min12,min30}, which can be associated with other criteria. Figure 4 is a list illustrating a plurality of events associated with a measurement report trigger. Figure 4 Details of the list of reporting triggering events shown can be found in 3GPP TS 36.331 Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol Specification v17.2.0 (2022-09). For example, Figure 4 Any event in can be used as a criterion. Those skilled in the art should be familiar with Figure 4 The events listed in .

[0077] For example, the measurement report may be triggered based on an event criterion being met and / or a timer interval (eg, a timer value) of a ReportInterval amount of time having expired (eg, expired). Figure 5is a timing diagram illustrating measurement report triggering. As an example, a periodic report may be triggered under the condition that a ReportInterval has expired and / or expired. As another example, an event-triggered report may occur under the condition that one or more event criteria have been met (e.g., event A1 condition is met and / or event A3 condition is met).

[0078] The network may use the measurement reports to determine whether to trigger cell level mobility.The time required for the network to receive the measurement reports and issue a handover (HO) command (RRC reconfiguration) needs to be considered and is referred to herein as air interface latency.

[0079] Mobility In certain representative embodiments, cell-level mobility may require and / or use (eg, explicit) RRC signaling for triggering, such as for HO.

[0080] Figure 6 is a process diagram illustrating a cell-level mobility sequence. Inter-gNB HO may include Figure 6 180b). At 602, the source gNB (e.g., 180a) may initiate a HO and send a HO request message to a target gNB (e.g., 180b) over an Xn interface. At 604, the target gNB may perform admission control. At 606, the target gNB may provide the (e.g., new) RRC configuration as part of the HO request confirm message in 606. At 608, the source gNB may provide (e.g., indicate) the RRC configuration to the WTRU 102 by sending (e.g., forwarding) an RRCReconfiguration message received in the HO request confirm message. For example, the RRCReconfiguration message may include a cell ID and other (e.g., all) information for accessing the target cell (e.g., so that the WTRU can access the target cell without reading system information). In some representative embodiments, information for contention-based and / or contention-free random access (e.g., required) may be included in the RRCReconfiguration message. The access information to the target cell may include beam-specific information. At 610, the WTRU 102 may move (e.g., handover) the RRC connection to the target gNB. At 612, the WTRU 102 may reply with an RRCReconfigurationComplete message to the target gNB.

[0081] exist Figure 6 , a handover preparation phase between gNBs (e.g., RAN nodes) - where 602 and 606 are the source gNB requesting the target gNB to accommodate WTRU 102, and the target node responding to the source node - confirming that it can accommodate WTRU102.

[0082] In certain representative embodiments, different (e.g., three) types of HO may occur. The first two types of HO (i.e., legacy HO and DAPS HO) are triggered immediately upon the WTRU 102 receiving the RRCReconfiguration message in 608. In the case of the third type of HO (i.e., CHO), the WTRU 102 receives a configuration of a group of cells and associated radio conditions to monitor (e.g., HO triggering criteria). Once one or more criteria are met for a given cell of the group, the WTRU 102 may trigger a HO to the given cell.

[0083] In certain representative embodiments, HO failures may be classified into three categories or types: (1) too late, (2) too early, and (3) wrong cell. In the case of HO too late, the WTRU 102 receives the HO command, but RLF occurs in the source cell before the WTRU 102 is able to trigger the HO to the target cell. In the case of HO too early, the WTRU 102 is able to trigger the HO to the target cell and the HO either fails due to poor radio conditions at the target cell or it succeeds but fails shortly thereafter. In the case of HO to the wrong cell, the HO fails at the target cell and there are other and / or better candidate cells in terms of radio conditions. HO failures may occur due to misconfiguration of the WTRU 102 and may include misconfiguration of the target cell, HO timing, and / or triggering criteria used to evaluate radio conditions.

[0084] exist Figure 6 At 608 in FIG. 5 , the WTRU 102 may trigger a HO (e.g., a legacy HO or a DAPS HO) after (e.g., immediately) receiving the RRCReconfiguration message. In the case where the HO fails and belongs to the too late HO failure category, it is obvious that the RRC reconfiguration message may have been sent to the WTRU 102 too late.

[0085] In the case of conventional HO and CHO, when performing HO, the WTRU releases the connection with the source cell before establishing a link to the target cell (e.g., UL and DL transmissions in the source cell are terminated before the WTRU starts communicating with the target cell). This results in an interruption time of about tens of milliseconds in the communication between the WTRU and the network.

[0086] Figure 7 is a system diagram illustrating an overview of what happens to a WTRU over time in the context of a handover. The WTRU 102 may have a trajectory 702 corresponding to the WTRU 102 moving across a first cell 704 and then to a second cell 706.

[0087] During time period 708, the WTRU's serving cell is the first cell 704, and both uplink and downlink transmissions of the WTRU 102 are directed toward the first cell 704. At time 702, the WTRU 102 receives a HO command from the network, or the CHO criteria are met, and the WTRU 102 immediately triggers the HO. Time period 712 is a period of interrupted communication between the WTRU 102 and the network, which includes non-optimal points for UL handover without regard to radio, QoS, or UL buffer related states. Finally, during time period 714, the second cell 706 is the WTRU's 102 serving cell, and both its uplink and downlink transmissions are now directed toward the second cell 706.

[0088] like Figure 5 As can be seen in FIG. 5 , even after the HO is triggered and / or performed, the WTRU 502 is within the coverage of the first cell 706 for a considerable period of time. Further, the HO may be triggered in response to events other than radio conditions (e.g., load balancing, network energy saving, etc.), where the radio conditions of the source cell are still good, or even better than those of the target cell. Therefore, it is not always necessary to perform a HO (e.g., CHO) immediately, which may result in unnecessary UL data interruption (e.g., for bearers with very strict latency requirements).

[0089] Therefore, when the WTRU 102 is provided with a HO command from the network or CHO conditions are met, it would be beneficial to determine and then utilize the optimal time (eg, time of day) to perform the HO, such as when the HO does not have to be performed immediately due to radio conditions.

[0090] Statistical Aspects of Machine Learning Estimation accuracy over time Among other functions, a machine learning (ML) model may, for example, be able to forecast or predict future values ​​of a given quantity (e.g., a parameter). A prediction may be associated with a timestamp value (e.g., a time instance). For example, a timestamp may be summarized as a future time step (e.g., not yet occurred). With each predicted value, an error or deviation that the predicted value may have may be estimated (e.g., always). In certain representative embodiments, the estimated error may be calculated (e.g., recursively). For example, the longer the time range associated with the predicted value, the worse (e.g., larger) the estimate may be expected to be. As an example, in principle, an ML model that outputs a prediction (e.g., a sample) at time step t+4 may be expected to have both an estimated value for the prediction (e.g., a sample) and an error estimate associated therewith, which is more accurate than a pair of predictions and errors at a more distant future time step (e.g., t+7).

[0091] Prediction Interval With predictive inference, a prediction interval can be an estimate of an interval where future observations will fall with a certain probability given what has been observed (e.g., via measurement, sampling, etc.). In certain representative embodiments, the ML model can output an interval associated with the prediction, which can be based on a probability P (e.g., associated with the prediction and / or interval). For example, assuming a probability given by P = 0.95 or 95%, the model can output a window of values ​​where it is estimated that the predicted value for any future time step will fall within the given window with a probability of 95%. In general, different values ​​of the confidence probability may generate different prediction windows (e.g., intervals).

[0092] In the case of HO to the wrong cell and too early HO, the HO failure may be related to the fact that the network does not have a correct grasp of what is happening in the radio conditions experienced by the WTRU 102. The network may send RRC reconfiguration messages to the WTRU based on the measurements that the WTRU receives in the measurement reports. These may follow a periodic or event triggered pattern. The period may be configurable via parameters and if the period is too long, there may be gaps between measurement reports where the network does not know what signal conditions the WTRU 102 measured. If the period is too short, then the WTRU 102 may continue to trigger measurement reports, increasing the signaling overhead. For event based measurement reporting, the reports may be based on a limited number of events and if the thresholds are not configured correctly, the WTRU may be too late to trigger sending the measurements.

[0093] Additionally, and particularly for the case of CHO, there may also be resource reservation issues. When the WTRU 102 is configured for CHO, the source node may request the target node to accommodate the WTRU 102. If the result of the admission control of the target node is to accommodate the WTRU 102, then resources may be reserved (e.g., immediately) because there may be no mechanism to optimize the resource reservation time to match the HO performed by the WTRU 102.

[0094] Using AI / ML techniques, models can be trained to accurately predict measurements, and therefore predict and improve network HO configurations. It may be desirable to allow the WTRU 102 to receive improvements in predicted measurements from the network, so that the WTRU 102 can evaluate the radio conditions it is experiencing against the radio conditions predicted by the network. Doing so may narrow the timing gap that exists between the WTRU measuring at the network, reporting the HO decision, and then providing the HO command to the WTRU 102.

[0095] and network prediction Examples of various predictive capabilities based on AI / ML techniques that may be performed at the WTRU 102 or the network are described below.

[0096] In a simple mobility scenario, a WTRU 102 in mobility may measure the RSRP of the current serving cell and report it to the network. If the WTRU 102 is moving to an area close to the serving cell edge, it may measure and note that the RSRP value is decreasing. These values ​​may be communicated to the network via measurement reports so that the network may decide whether a HO to a different cell is necessary.

[0097] For the purposes of the following discussion, it may be assumed that the WTRU 102 and / or the network have a pre-trained AI / ML model that is capable of generating predictions of air interface measurements (e.g., RSRP, RSRQ, SINR, etc.) of serving and / or neighbor cells (e.g., any detectable cells), WTRU UL buffer levels, and / or QoS-related metrics.

[0098] In certain representative embodiments, the radio conditions experienced at the WTRU 102 may be based on actual measurements performed by the WTRU 102 over time. In an example mobility scenario, the WTRU 102 (e.g., in mobility) may determine the RSRP of the current serving cell and report the determined RSRP to the network. If the WTRU 102 is moving to an area close to a serving cell edge, it may determine that the RSRP values ​​are decreasing (e.g., for the serving cell). These RSRP values ​​may be communicated to the network via measurement reports so that the network can make a decision (e.g., regarding whether to issue a HO command).

[0099] In certain representative embodiments, it may be assumed that the network has a pre-trained AI / ML model that may be used to generate predictions of air interface measurements (e.g., RSRP, RSRQ, SINR, etc.) of the serving and / or neighbor cells (or any other cells). For example, the predicted measurements may be used to anticipate radio conditions that the WTRU 102 may experience, instead of or before the WTRU 102 reports actual measurements.

[0100] For example, prediction of radio conditions is a tool used to anticipate the radio conditions that the WTRU 102 will experience, rather than waiting for the WTRU 102 to report the radio conditions.

[0101] For example, the prediction of the UL buffer level is a tool for anticipating the UL service requirements of the WTRU 102. It is contemplated herein that the UL buffer level may be predicted as a whole (e.g., for the WTRU 102), and / or for one or more PDU sessions (e.g., established between the UPF 184 in the CN 115 and the WTRU 102), and / or for one or more DRBs (e.g., a PDU session may have one or more DRBs), and / or for one or more QoS Flow Identifiers (QFIs) (e.g., each DRB may have one or more QFIs).

[0102] For example, QoS-related prediction is a tool used to anticipate certain QoS-related metrics.

[0103] In order to generate more meaningful predictions in this context, in certain embodiments, it makes sense for the WTRU 102 and / or the network to make predictions in a time series manner. This means that from the moment the prediction is triggered, the AI / ML model will generate several prediction outputs at a certain granularity and / or time step in the future time span.

[0104] In certain representative embodiments, the network may predict (e.g., using a trained AI / ML model) radio interface measurements (e.g., RSRP) at the WTRU 102 in a time series manner. For example, from a timer that triggers the network prediction, the WTRU 102 may generate several prediction outputs within a (e.g., future) time span, such as at a certain granularity or time step.

[0105] Figure 8 is a block diagram illustrating an example of obtaining network predictions. Figure 8 As shown, a network entity (e.g., a gNB, etc.) may be provided with a trained ML model (and / or AI model) 802. In certain representative embodiments, the ML model 802 may use past (multiple) measurements, current (multiple) measurements, and / or other parameters or measurements as input. The measurements may include, for example, Figure 8 The RSRP and / or other measurement quantities described herein (e.g., RSRQ, SINR, etc.) in the time series may be measured. For example, the RSRP measurement may be an actual measurement reported by the WTRU 102 for the current time "t". The ML model 802 using the inputs may generate one or more predicted (e.g., RSRP) measurements in the time series as output 804. For example, where the current time is "t", the one or more predicted measurements may be for time intervals of "t+1", "t+2", to "t+t_fb", such as where 1 is a unit value of time (e.g., based on milliseconds or transmission time intervals). As another example, the predicted measurements may be related to Figure 8 The error values ​​in are associated (e.g. paired).

[0106] In certain representative embodiments, the network may obtain a prediction for only one time point (e.g., "t+1"), or may obtain a prediction for several time steps (e.g., from "t+1" to "t+t_fb") (e.g., extended over several time steps). In some scenarios, a time series sequence of predicted output values ​​may be beneficial compared to a single value prediction, because it may be difficult to match the prediction to the events configured by the network when a single prediction point is used.

[0107] In certain representative embodiments, the WTRU 102 may be configured to predict future measurements based on current and / or historical measurements. For example, the WTRU 102 may be configured with a trained AI / ML model that is capable of generating predictions of radio interface radio signal levels. In an example, the AI / ML model at the WTRU 102 may be implementation-based. In another example, the WTRU 102 may obtain the AI / ML model from the network.

[0108] Fig. 9 is a block diagram illustrating an example of obtaining a WTRU prediction of RSRP. Fig.10 is a block diagram illustrating an example of obtaining a WTRU prediction of UL buffer status. Fig.11 is a block diagram illustrating an example of obtaining a WTRU prediction of the number of retransmissions.

[0109] At the WTRU 102, the AI / ML model may be configured to take current and / or historical measurements (such as RSRP) as input, such as Figure 8 and 9 Other current and / or historical measurements can be used as inputs, such as Fig.10 and 11 shown.

[0110] For example, Fig. 9 A machine learning model 902 is shown for generating outputs 904 predicting RSRP at various future times (e.g., time t+1, t+2, ... t+n), each output including an error in the prediction (e.g., error1, error2, ... errorn) and / or an estimated accuracy of the prediction.

[0111] For example, Fig.10 A machine learning model 1002 is shown for generating outputs 1004 predicting UL buffer states at various future times (e.g., time t+1, t+2, ... t+n), each output including a predicted error (e.g., error1, error2, ... error n) and / or an estimated accuracy of the prediction.

[0112] For example, Fig.11A machine learning model 1102 is shown for generating outputs 11 predicting the number of retransmissions (e.g., #) at various future times (e.g., time t+1, t+2, ... t+n), each output including a predicted error (e.g., error1, error2, ... error n) and / or an estimated accuracy of the prediction.

[0113] In some embodiments, a prediction may also be generated for only one point in time.

[0114] In many scenarios, having a forecast with a time series output may be beneficial compared to a single value forecast, as it may be difficult to match the forecast to only a single forecast point (e.g. an event with a network configuration with only a single forecast point). For the case of the UL buffer, evaluating the UL buffer value over the time span may be relevant for certain decision making processes detailed in subsequent sections. This may also be true for QoS related aspects.

[0115] However, these are practical issues beyond the scope of this disclosure. The triggering of the prediction is also beyond the scope of this disclosure. However, several exemplary implementations of these two aspects are mentioned below (e.g., (1) whether the model resides at the WTRU or in the network, and (2) whether a single prediction is made or a time series prediction is made).

[0116] In certain embodiments, the WTRU 102 may be configured to predict future measurements based on current and / or historical measurements. For example, the WTRU 102 may be configured with a trained AI / ML model capable of generating predictions. The AI / ML model at the WTRU 102 may be implementation-dependent. In another embodiment, the WTRU 102 may obtain the AI / ML model from the network. In certain embodiments, the AI / ML model may be configured to take current and / or historical input values ​​as input. In certain embodiments, the AI / ML model may be configured to obtain additional inputs, such as WTRU location information, WTRU mobility, and the like. In certain embodiments, the AI / ML model may be configured to generate a single-value prediction, such as an output value at a single future time instance t. In certain embodiments, the AI / ML model may be configured to predict a series of predicted values ​​corresponding to multiple future time instances t+1, t+2, and so on up to t+n.

[0117] In certain representative embodiments, the AI / ML model may be configured to obtain additional inputs (e.g., to supplement signal measurements), such as WTRU location information, WTRU mobility information, etc. As an example, the AI / ML model may be configured to produce a single value prediction (e.g., RSRP) at a future time instance "t+1". In another example, the AI / ML model may be configured to predict a series of (e.g., RSRP) values ​​corresponding to future time instances "t+1", "t+2", etc. up to "t+t_fb", where t_fb is the time at which the WTRU report will be fed back to the network.

[0118] Fig.12 1200 is a timing diagram illustrating an example of a network prediction process. In certain representative embodiments, at 1202, the network may predict a (e.g., specific) HO strategy (e.g., process) for the WTRU 102. For example, the predicted HO strategy may include any of the HO type (e.g., DAPS HO, legacy HO, CHO), one or more any target cells (e.g., in the case of CHO), and / or one or more radio interface quantities (such as RSRP, as an example). In some representative embodiments, the prediction may be output in different forms (e.g., multiple time steps for a given interval). For example, the network may predict a measurement quantity (e.g., a radio interface quantity such as RSRP) as any of the following: (1) a single value for each time step (e.g., for all time steps), (2) a single value for each time step (e.g., for a subset of time steps), (3) a single value for each time step (e.g., for a single time step), (4) a series of values ​​for each time step (e.g., for all time steps), (5) a series of values ​​for each time step (e.g., for a subset of time steps), (6) a series of values ​​for each time step (e.g., for a single time step), or (7) a combination thereof. For example, a series of values ​​may be predicted as @t+1-[RSRP1-,RSRP1 + ], @t+2-[RSRP2 - ,RSRP2 + ]……@t+t_fb-[RSRPt_fb - ,RSRPt_fb + ], where the subscript - and + Indicates that a value is added or subtracted from a central reference value to create a window. For example, the predicted measurement quantity may be linked or associated with any one of a specific cell and / or a cell group (e.g., generated for different cells, where a set / subset of predicted RSRP values ​​is associated with a specific cell). Fig.12 As shown, the last time step of the prediction is indicated as t_fb.

[0119] In certain representative embodiments, at 1204 (e.g., time "t"), the network may send (e.g., configure, indicate, or otherwise provide) a (e.g., pre-emptive) HO command to the WTRU 102. For example, at Figure 6 At 608 in FIG. 1 , the HO command may be sent to the WTRU 102 as a message or in a message, or via any other message. The WTRU 102 may not immediately trigger the HO as in conventional legacy and DAPS HO cases. In some representative embodiments, the HO command may include, indicate (e.g., implicitly or explicitly), or be associated with any of the following: (1) one or more predicted measurement quantities (e.g., Fig.12 1202), (2) a time value (e.g., t_fb) that may serve as the last time step, (3) a (e.g., configured) window for the WTRU 102 to determine the HO decision, (4) a configuration for the WTRU 102 to evaluate and provide feedback on the received network prediction (e.g., using actual measurements or WTRU-generated prediction values), and / or (5) one or more conditions for the WTRU 102 to trigger the HO (e.g., within the window). For example, the window may be indicated as any of the following: (1) a range, (2) a difference (e.g., a delta) from a time value (e.g., t_fb), (3) a geographic location or region, (4) a distance or range to a current location (e.g., when the configuration was received), (5) a distance or range to a location where the WTRU 102 was at the time value (e.g., t_fb), and / or (6) a distance or range to a location where the WTRU 102 was at another time.

[0120] In certain representative embodiments, Fig.12 At 1206 in, the WTRU 102 may be configured with a window or determine the window (e.g., evaluation and feedback time interval). For example, the WTRU 102 may confirm (e.g., determine) whether the WTRU 102 experiences (e.g., measures and / or predicts) a network predicted (e.g., radio interface) condition. As an example, under the condition that the WTRU 102 determines that the HO decision is valid (e.g., the network predicted condition is met), the WTRU 102 may perform the HO (e.g., HO command). For example, under the condition that the WTRU 102 determines that the HO decision is invalid (e.g., the network predicted condition is not met), the WTRU 102 may not perform the HO (e.g., HO command). In some representative embodiments, under the condition that the WTRU 102 determines that the HO decision is invalid, the WTRU 102 may provide (e.g., trigger) feedback to the network. As an example, the network may configure the WTRU 102 to not perform the HO later based on the feedback information.

[0121] In certain representative embodiments, the network may make mobility decisions based on measurements received from multiple WTRUs. Taking into account the latency of the air interface, the RRC signaling of the measurement reports from the WTRU 102 to the network, and any resulting network-triggered RRCReconfiguration decisions, there may be a minimum time required for the transmission of these two messages and additional computation time for evaluation and decision making, even at a minimum. As an example, Fig.12 The time "t_fb" at 1208 in 1204 may serve as a time margin required for the network to receive and evaluate the measurements, make a decision regarding the mobility policy, and / or configure the WTRU 102 for HO. For example, the network may (e.g., carefully) select a value for this parameter such that the time margin is similar to the latency of signaling two messages over the air interface. For example, after time t_fb, the WTRU HO decision may be irreversible (e.g., because there may not be enough time to signal another reconfiguration or HO command to the WTRU 102).

[0122] In certain representative embodiments, the WTRU 102 may be configured, provided, or otherwise instructed to Fig.12 1208 and 1210 in FIG. 1209 . The reconfiguration window may act as a limit for the WTRU 102 to trigger a HO. Between 1208 and 12010, the WTRU 102 may trigger a HO at any time (e.g., once the HO condition is met or a time value thereafter, the HO trigger is triggered). When the WTRU 102 determines when exactly to trigger the HO, several options may be considered. For example, the WTRU 102 may have some data to send in a buffer that may (e.g., ideally or preferably) be sent before the HO to avoid the HO interrupting the transmission of the data. It will be appreciated by those skilled in the art that the WTRU 102 may consider other situations that may affect when the WTRU 102 determines to trigger a HO.

[0123] Evaluate In certain representative embodiments, the WTRU 102 may receive (e.g., from the network) a configuration for evaluating and / or feeding back information related to network predictions. For example, the evaluation of network predictions may use actual measurements and / or WTRU-generated predictions. By evaluating the network predictions, the WTRU 102 may determine whether what the network predicted with respect to radio conditions (e.g., quantities such as RSRP) will occur or has actually occurred, such as the predicted network conditions being within an acceptable range of measurements obtained by the WTRU 102 at the radio interface.

[0124] For example, the WTRU 102 may perform the evaluation using actual measurements, which may be compared to received network predictions. As an example, to evaluate a predicted value or range of RSRP associated with time step "t+3", the WTRU 102 may use actual measurements obtained by the WTRU 102 (e.g., at "t+3").

[0125] For example, the WTRU 102 may perform an evaluation using WTRU-generated predictions, which may be compared to received network predictions. As an example, to evaluate a predicted value or range of RSRP associated with time step "t+3", the WTRU 102 may use predicted measurements obtained by the WTRU 102 (e.g., before "t+3").

[0126] For example, the WTRU 102 may perform the evaluation using a combination of actual measurements and WTRU-generated predictions, which may be combined and compared to received network predictions.

[0127] In certain representative embodiments, the WTRU 102 may determine to trigger prediction in the absence of a network configuration, or may trigger prediction based on a received network configuration.

[0128] For example, the network may provide a configuration that includes (e.g., indicates) options for the WTRU 102 to trigger a prediction (e.g., as described herein), the options including any of the following: (1) triggering a prediction immediately upon receiving an RRCReconfiguration (e.g., within Figure 6 608 and / or Fig.12 1204 in the figure), (2) a specific timestamp that triggers the prediction, (3) a time value that triggers the prediction from the time the configuration is received (e.g., counting milliseconds, symbols, time slots, subframes, and / or other time intervals), (4) a specific geographic location that triggers the prediction, and / or (5) a specific geographic area that triggers the prediction (e.g., triggered upon entering the area).

[0129] feedback In certain representative embodiments, the WTRU 102 may provide (eg, report or indicate) feedback (eg, measurement information and / or evaluation information) to the network. The feedback may be based on evaluation results and / or predicted measurements received by the WTRU 102 from the network for comparison purposes.

[0130] In certain representative embodiments, the WTRU 102 may use one or more time-related triggers for feedback. For example, the WTRU 102 may be configured to trigger feedback to the network (e.g., at each time step until or at t_fb). For example, the WTRU 102 may be configured to trigger feedback to the network at a specific time (e.g., t_fb). For example, the WTRU 102 may be configured to trigger feedback to the network in a subset of time steps (e.g., in a [t; t_fb] window).

[0131] In certain representative embodiments, the WTRU 102 may use one or more triggers based on real (e.g., non-predicted) measurements. For example, the WTRU 102 may be configured to trigger feedback to the network under the condition that a mismatch (e.g., outside a threshold or range) is determined (e.g., detected) between one or more received measurement predictions and one or more actual measurements (such as for a cell or a group of cells). For example, the WTRU 102 may be configured to trigger feedback to the network under the condition that a mismatch (e.g., outside a threshold or range) is determined (e.g., detected) between received predicted measurements in a prediction window and one or more actual measurements (such as for a cell or a group of cells). For example, the WTRU 102 may be configured to trigger feedback to the network under the condition that a rate of change between (e.g., consecutive and / or non-consecutive) time steps of actual measurements is above or below a threshold (or range) (such as for a cell or a group of cells).

[0132] For example, the WTRU 102 may be configured to trigger feedback to the network using (e.g., any) combination of measurement evaluations for different cells and taking into account any of the examples mentioned above. As an example using RSRP, the WTRU 102 may trigger feedback under the following conditions: (i) the rate of change of the RSRP of a first cell in consecutive time steps is above a (e.g., first) threshold, and (ii) the rate of change of the RSRP of a second cell in at least x number of time steps is below a (e.g., second) threshold. Other examples may use other measurement quantities other than RSRP and / or may use RSRP in combination with other measurement quantities.

[0133] In certain representative embodiments, the WTRU 102 may use one or more triggers based on WTRU predicted measurements. For example, the aforementioned trigger examples using actual measurements made by the WTRU 102 may be used instead of or in combination with WTRU predicted measurements to trigger feedback. As another example, the WTRU 102 may be configured to trigger feedback to the network based on one or more network predicted estimation errors being above a certain threshold (e.g., regardless of the RSRP comparison between the network measurement of RSRP and the WTRU measurement). As another example, the WTRU 102 may be configured not to trigger feedback to the network based on one or more network predicted estimation errors being below a certain threshold (e.g., regardless of the RSRP comparison between the network measurement of RSRP and the WTRU measurement). As another example, the WTRU 102 may be configured to trigger feedback to the network based on one or more WTRU predicted estimation errors being below a certain threshold (e.g., regardless of the RSRP comparison between the network measurement of RSRP and the WTRU measurement). As another example, the WTRU 102 may be configured to trigger feedback to the network based on one or more WTRU predicted estimation errors being below a certain threshold (e.g., regardless of the RSRP comparison between the network measurement of RSRP and the WTRU measurement). As another example, the WTRU 102 may be configured to trigger feedback to the network based on one or more WTRU predicted estimation errors being below a certain threshold (e.g., regardless of the RSRP comparison between the network measurement of RSRP and the WTRU measurement). As another example, the WTRU 102 may be configured to trigger feedback to the network based on an average WTRU predicted estimation error being lower than an average network predicted estimation error (e.g., regardless of a RSRP comparison between the network measurement of RSRP and the WTRU measurement). As another example, the WTRU 102 may be configured to trigger feedback to the network based on one or more WTRU predicted estimation errors being lower than a network predicted estimation error (e.g., regardless of a RSRP comparison between the network measurement of RSRP and the WTRU measurement). For example, the WTRU prediction and / or network prediction may be associated with any of: (1) all time steps of a WTRU evaluation and / or feedback window, (2) a (contiguous and / or non-contiguous) subset of the time steps of a WTRU evaluation and / or feedback window, and / or (3) individual time steps of a WTRU evaluation and / or feedback window.

[0134] Report Signaling In certain representative embodiments, the WTRU 102 may deliver (e.g., send) feedback to the network each time feedback is triggered, may accumulate feedback values ​​and deliver corresponding feedback information at a certain point in time (e.g., deliver all feedback information at once), and / or deliver corresponding feedback information gradually during the evaluation window (e.g., periodically). For example, any feedback triggered from the WTRU 102 to the network may mean that the HO is not ideal (e.g., for the current radio interface conditions). For example, the network may configure the WTRU 102 to decide not to trigger the HO after the time "t_fb" if any of the feedback options have been triggered. For example, if any of the feedback options have been triggered, the network may configure the WTRU 102 with any conventional HO procedures during the evaluation window. For example, the network may reconfigure the WTRU 102 with a more recent prediction, such as in another preventive HO command.

[0135] Using the predicted WTRU to network feedback content In certain representative embodiments, the WTRU 102 may deliver (e.g., send) feedback to the network that may (e.g., should) identify any of the following: (1) the corresponding cell (or cells), (2) one or more measurements (e.g., actual or predicted), such as starting and / or ending RSRP values ​​and / or minimum and / or maximum RSRP values, and (3) one or more time steps for the measurements, such as a single time value and / or a change in a time value, which may be indicative of a range window associated with the measurement.

[0136] Prediction Interval In certain representative embodiments, prediction intervals may be incorporated. As described herein, the AI / ML model may be implementation specific and / or vendor specific, or it may be obtained by the WTRU 102 from the network, or the network may deliver the model to the WTRU 102. The prediction intervals and time spans for prediction-related capability exchanges may be relevant, such as for implementation specific and / or vendor specific ML models. For example, the same trained model may not be suitable for generating predictions for the same WTRU 102 in different situations.

[0137] To address the prediction gap, additional information may be incorporated into the WTRU configuration, evaluation, and feedback to the NW as described herein.

[0138] Fig.131300 is a timing diagram illustrating an example of fixed and variable RSRP boundaries. In other examples, the boundaries may correspond to other radio interface quantities and / or measurements. For example, the WTRU 102 may be configured, indicated, and / or determined any of a fixed upper boundary 1302, a fixed lower boundary 1304, a predicted (e.g., variable) upper boundary 1306, and / or a predicted (e.g., variable) lower boundary 1308. Fig.13 As shown, the WTRU 102 may predict an upper boundary (e.g., a threshold) 1306, such as for RSRP, at a corresponding confidence value (e.g., x%). Fig.13 As shown, the WTRU 102 may predict a lower boundary (eg, threshold) 1308, such as for RSRP, at a corresponding confidence value (eg, x%). For example, different boundaries and / or thresholds may be associated with different confidence levels and / or intervals.

[0139] exist Fig.13 In the example shown, the prediction bounds (e.g., confidence intervals) may remain fixed over time (e.g., semi-static), or they may change (e.g., dynamically, such as predicted by the WTRU 102). Each of the upper and lower bounds may change differently (e.g., diverge or converge over time). Fig.13 In , the time scale is universal and is expressed over a number of samples (eg, time slots) from t to t+n.

[0140] In certain representative embodiments, RSRP evaluation (such as when performing or determining to perform HO) may take into account any one of the RSRP associated with the serving cell falling below a (e.g., first) threshold and / or the RSRP of a neighbor cell becoming above a (e.g., second) threshold.

[0141] As an example, in Fig.12 In the embodiment of the present invention, the network may generate (e.g., predict) a series of values ​​of a measurement quantity (e.g., a radio interface quantity such as RSRP). The values ​​may be output in different forms (e.g., for multiple time steps at a given interval). For example, the network may predict the measurement quantity as any of: a series of values ​​for each time step (e.g., for all time steps), a series of values ​​for a portion of the time steps (e.g., for a subset of the time steps), and / or a series of values ​​for certain time steps (e.g., for a single time step). In certain representative embodiments, the generated values ​​may be associated with a confidence value (or range). For example, the network may configure, instruct, or otherwise signal the predicted measurement information and a confidence value corresponding to the prediction (e.g., as a decimal value or a percentage) to the WTRU 102. As an example, the confidence value may apply to any (e.g., all) prediction ranges for any (e.g., all) time steps. In some embodiments, the confidence value and / or range may change over time.

[0142] As another example, the WTRU 102 may receive (e.g., from the network) a configuration for evaluating and / or feeding back information related to network predictions. For example, the evaluation of network predictions may use actual measurements and / or prediction results generated by the WTRU. The WTRU 102 may also be configured with various triggers for reporting actual measurements and / or predicted measurement feedback, and may include any of the following triggers.

[0143] In certain representative embodiments, the WTRU 102 may be configured, instructed and / or signaled to use triggers based on real measurements, such as for reporting information to the network. For example, upon detection and / or determination of a mismatch between a received predicted upper boundary of a window and one or more real measurements (such as for a cell and / or a group of cells), the WTRU 102 may trigger feedback to the network.

[0144] For example, the WTRU 102 may trigger feedback to the network upon detection and / or determination of a mismatch between a received predicted lower boundary of a window and one or more actual measurements (such as for a cell and / or a group of cells).

[0145] In certain embodiments, multiple triggers may be configured and / or applied using different combinations for different time steps. For example, the WTRU 102 may trigger feedback for a mismatch detected using an upper boundary in a first time step (e.g., t+1), and / or trigger feedback for a mismatch detected using a lower boundary in a second time step (e.g., t+2), and / or trigger feedback for any detected mismatch in a third time step (e.g., t+3).

[0146] In certain representative embodiments, the WTRU 102 may be configured, instructed and / or signaled to use a trigger based on a WTRU predicted measurement, such as for reporting information to the network. For example, for a given time step, the WTRU 102 may trigger feedback based on the WTRU predicted value being less than (or greater than) a deviation compared to a network predicted value (e.g., for the same confidence percentage).

[0147] For example, for a given time step, the WTRU 102 may trigger feedback based on the WTRU prediction value being less than (or greater than) the deviation for (eg, only for) the upper bound compared to the network prediction value (eg, for the same confidence percentage).

[0148] For example, for a given time step, the WTRU 102 may trigger feedback based on the WTRU prediction value being less than (or greater than) the offset for (eg, only for) the lower bound compared to the network prediction value (eg, for the same confidence percentage).

[0149] For example, for a given time step, the WTRU 102 may not trigger feedback based on the WTRU prediction being less than (or greater than) the offset compared to the network prediction (eg, for the same confidence percentage).

[0150] For example, for a given time step, the WTRU 102 may trigger feedback based on the WTRU prediction value being less than (or greater than) a deviation for (eg, only for) an upper bound compared to the network prediction value (eg, for different confidence percentages).

[0151] For example, for a given time step, the WTRU 102 may trigger feedback based on the WTRU prediction value being less than (or greater than) a deviation for (eg, only for) a lower bound compared to the network prediction value (eg, for different confidence percentages).

[0152] For example, for a given time step, the WTRU 102 may not trigger feedback based on the WTRU prediction being less than (or greater than) the offset compared to the network prediction (eg, for different confidence percentages).

[0153] Triggered Handover In certain representative embodiments, the WTRU 102 may determine that within a reconfiguration window (e.g., Fig.12 The handover is triggered within the time interval corresponding to 1208 to 1210 in FIG.

[0154] Fig.14 is a system diagram illustrating an overview of what happens to a WTRU over time in the context of a handover utilizing prediction. For comparison purposes, Fig.14 Similar to Figure 7 In certain representative embodiments, the WTRU 102 may determine to perform (eg, trigger) a handover based on the predictions described herein.

[0155] exist Fig.14 1404, the WTRU 102 may have a trajectory 1402 corresponding to the WTRU 102 moving across a first cell 1404 and then moving to a second cell 1406. The time intervals 1408, 1410, and 1412 may correspond to Fig. 9 , 10 and the time span over which the AI / ML model in 11 generates the corresponding prediction.

[0156] For example, with Figure 7 Similar to the time interval 708, Fig.14 The time interval 1416 in represents the following time: during this time, the WTRU's serving cell is the first cell 1404 and both the WTRU's uplink transmission and downlink transmission are towards the first cell 1404. Figure 7 Similar to time 710 in Fig.14 At time 1418 in FIG. 14 , the WTRU 102 receives a HO command from the network or determines that a trigger condition for a previously configured CHO is met.

[0157] Fig.14 The time interval 1420 in represents the period during which the WTRU 102 waits before performing a HO or CHO (e.g., within a duration also referred to as a reconfiguration window or HO window). Specifically, the WTRU 102 will decide within this reconfiguration window 1420 when exactly to perform a HO, rather than immediately performing a HO or CHO as in a conventional HO or CHO. The duration of the reconfiguration window 1420 may be provided by the network (e.g., based on network predictions of serving and / or target cell signal levels) and / or determined by the WTRU 102 (e.g., using actual or predicted measurements of serving and / or target cell signal levels). For example, the exact moment to perform a HO may depend on current and predicted UL buffer conditions (e.g., conditions regarding bearers that are delay sensitive and whose QoS may be significantly affected by any HO interruption).

[0158] exist Fig.14 , time 1424 represents an example point at which the WTRU may make a decision to perform a HO. In this particular example, time 1424 may correspond to Fig.10 The time when the AI / ML model makes a UL buffer status prediction.

[0159] Fig.14 The time interval 1426 in represents a period during which the WTRU's serving cell is the second cell 1406 and both its uplink and downlink transmissions are towards the second cell 1406 .

[0160] Fig.15 is a timing diagram 1500 illustrating an example of a handover process utilizing prediction.

[0161] At 1502, the network predicts (e.g., based on air interface measurements) a possible reconfiguration window for the WTRU 102 to perform a HO. The network will then send (e.g., at time t-3) an RRC reconfiguration message (or any other message) with any required configuration aspects to the WTRU.

[0162] At 1504, the WTRU 102 may initiate a reconfiguration window (eg, Fig.141420 in). During time interval 1506, the WTRU may send a measurement report message (or any other message) to the network to provide feedback, such as on a reconfiguration window predicted by the network. During this period between 1502 and 1504, the network may request the WTRU 102 (or may make internal decisions) to trigger predictions that may (a) assist in validating information received by the network and / or (b) assist in its own internal decision-making process. Thus, during the time period at 1506 between the times at 1502 and 1504, the WTRU 102 may trigger any prediction of the future value of any quantity relevant to such purpose. For example, the WTRU 102 may trigger one or more AI / ML models, such as during Fig. 9 , 10 and / or 11 to perform its prediction). In certain representative embodiments, as Fig.15 As shown, the WTRU may obtain predictions within time spans 1508, 1510, and / or 1512 from the AI / ML model. In other representative embodiments, the WTRU may obtain predictions within time spans 1504 (e.g., Fig.15 The prediction starts at time "t" in .

[0163] exist Fig.15 , the time at 1514 (eg, t+n) represents the end of the reconfiguration window 1516 (eg, from the start at time "t" to the end at time "t+n").

[0164] Within the reconfiguration window 1516, the WTRU 102 will trigger a HO. For purposes of explanation, the reconfiguration window is referred to herein as a time window. In other examples, the reconfiguration window may be defined in other ways, including any of the following: (i) a time range, (ii) a change amount (e.g., a change amount from t-3 or t), (iii) a geographic location area (e.g., defined by any of GPS, x / y / z coordinate system, indoor positioning system, etc.), (iv) a change amount from the WTRU's location (e.g., using any of GPS, x / y / z coordinate system, indoor positioning system, etc.), (v) a distance to the current location when the configuration is received, (vi) a distance to the location where the WTRU will be at a given time (e.g., t-3 or t), (vii) a distance to the location where the WTRU will be at any other time step, and / or (viii) an air interface difference between any time steps (e.g., [RSRP1@t; RSRP2] or [RSRQ1; RSRQ2], etc.).

[0165] exist Fig.15 The WTRU may perform a HO at 1518. For example, this may correspond to the time when the WTRU initiates the HO, which will be some short interval after the WTRU makes the decision to perform the HO.

[0166] Finally, the WTRU sends feedback information to the network at 1520. Providing feedback information from the relevant feedback process may occur at a time after performing the HO and / or after the end of the reconfiguration window (eg, after time "t+n").

[0167] Example of a triggered handover Fig.16 is a timing diagram 1600 illustrating an example of handover triggering for different HO types and WTRU prediction lengths.

[0168] In certain representative embodiments, the network may indicate to the WTRU 102 information associated with the reconfiguration window. Fig.16 In the example, a reconfiguration window may be provided within the time interval [t; t+n]. The network expects the WTRU 102 to perform a HO at any time within the window. As a first example, the WTRU 102 may determine to perform (e.g., trigger) a HO at time "t+3", as shown at 1602. This may apply to any HO type.

[0169] As a second example, the reconfiguration window may initially be provided within the time interval [t; t+n]. The WTRU 102 may evaluate and correct the reconfiguration window based on its own prediction. The WTRU 102 may decide that a better reconfiguration window is [t; t+n-1]. For example, the WTRU may have received an RRC reconfiguration message that implies (e.g., indicates) a HO and may have triggered a prediction that resulted in a decision that the window should be [t; t+n-1] at 1604.

[0170] As a third example, the WTRU may receive an RRC reconfiguration that implies (e.g., indicates) DAPS HO and may provide a reconfiguration window within the time interval [t; t+n]. The WTRU may decide to perform (e.g., trigger) an UL handover and request to release the source cell at time "t+3".

[0171] trigger In certain representative embodiments, the WTRU 102 may determine a specific time within the reconfiguration window to trigger a HO.

[0172] like Fig.16 As shown, the reconfiguration window may be provided within a time interval [t; t+n].

[0173] The WTRU may decide to perform a HO (or a UL handover in the case of a DAPS HO) when the first of any one or more of the conditions listed below is met. For example, the one or more conditions may be provided based on UL buffer related criteria, air interface radio condition related criteria, and / or QoS related criteria. These conditions may be related to current conditions, network predicted conditions, and / or WTRU predicted conditions. These conditions may be specified, predetermined, and / or provided by the network (e.g., as part of reconfiguration information).

[0174] In certain representative embodiments, one or more conditions may be associated with a current UL buffer state (e.g., level, value, amount). For example, a condition may be any of the following: (i) the current UL buffer for a particular data radio bearer, PDU session, and / or QFI falls below a threshold; (ii) the current UL buffer for a set of data radio bearers, PDU sessions, and / or QFIs falls below a threshold; (iii) the current UL buffer for any combination of (multiple) any data radio bearers, (multiple) any PDU sessions, and / or (multiple) QFIs falls below a threshold; (iv) the current UL buffer level decreases at more than a specific rate for any combination listed in (i), (ii), or (iii), such as for any consecutive time steps; and / or (v) the current UL buffer level decreases at more than a specific rate for any combination listed in (i), (ii), or (iii), such as for any non-consecutive time steps in any given set of time steps (e.g., QFIx decreases at more than a specific rate over a period of 3 time steps).

[0175] In certain representative embodiments, one or more conditions may be associated with a predicted UL buffer state (e.g., level, value, amount). For example, a condition may be any of the following: (i) the current UL buffer is less than or equal to the minimum value of the network predicted UL buffer; the current UL buffer level is less than or equal to the minimum value of the UL buffer predicted by the WTRU; (ii) the current UL buffer level is greater than or equal to the minimum value of the averages between the WTRU and network predicted UL buffer levels at a given time step; (iii) the current UL buffer level is less than or equal to the minimum value of the averages between the WTRU and network predicted UL buffer levels at two different time steps (e.g., one time step is associated with the minimum value predicted by the WTRU and the second time step is associated with the minimum value predicted by the network); (iv) the current UL buffer is less than or equal to the minimum value of the predicted UL buffer minus delta_xy (e.g., where the delta is associated with a particular prediction accuracy, such as where the minimum predicted UL buffer value is y bytes with x% accuracy). (v) the current UL buffer level is less than or equal to the minimum value of the predicted UL buffer level minus delta_xyz (for example, in the case where the variation is associated with certain radio conditions, such as in the case where the minimum predicted UL buffer value is y bytes, where RSRP=x or RSRQ=x or RSRQ=x and RSRP=z, then there is delta_xyz associated with the trigger criterion); and / or (vi) the current UL buffer level is less than or equal to the minimum value of the predicted UL buffer minus delta_xyz (for example, in the case where the variation is associated with certain QoS conditions, such as in the case where the minimum predicted UL buffer value is y bytes, where packet error rate=x or current packet delay=x or packet error rate=x and packet delay=z, then there is delta_xyz associated with the trigger criterion).

[0176] In certain representative embodiments, one or more conditions may be related to a radio condition (e.g., level, value, quantity). For example, a condition may be any of the following: (i) the current radio condition (e.g., RSRP) drops below a threshold; (ii) the current radio condition (e.g., RSRP) decreases by more than a specific rate between any consecutive time steps; (iii) the current radio condition (e.g., RSRP) decreases by more than a specific rate between any non-consecutive time steps (e.g., RRP or SNR decreases by more than a specific rate within a period of 3 time steps); and / or (iv) any combination of air interface measurements and thresholds or drop rates.

[0177] In certain representative embodiments, one or more conditions may be associated with QoS (eg, level, value, amount). For example, the condition may be any of the following: (i) the UL throughput drops below a threshold; (ii) the UL throughput decreases at a specific rate in consecutive time steps; (iii) the UL throughput decreases at a specific rate in non-consecutive time steps; (iv) the DL throughput drops below a threshold; (v) the DL throughput decreases at a specific rate in consecutive time steps; (vi) the DL throughput decreases at a specific rate in non-consecutive time steps; (vii) the number of retransmissions at any applicable layer is above a threshold; (viii) the number of retransmissions at any applicable layer increases at a specific rate in any consecutive time steps; (ix) the number of retransmissions at any applicable layer increases at a specific rate in non-consecutive time steps; (x) the packet delay becomes above a threshold; (xi) the packet delay increases at a specific rate in any consecutive time steps; (xii) the packet delay increases at a specific rate in any non-consecutive time steps; (xiii) the packet error rate becomes above a threshold; (xiv) the packet error rate increases at a specific rate in any consecutive time steps; and / or (xv) the packet error rate increases at a specific rate in any non-consecutive time steps.

[0178] In certain representative embodiments, the WTRU 102 may combine any of the above-listed conditions to perform a HO (eg, in any possible combination).

[0179] In certain representative embodiments, if all conditions are not met (or otherwise indicated to apply) and the end of the reconfiguration window is reached, the WTRU 102 will reconfigure the device at the end of the reconfiguration window (e.g. Fig.16 The time “t+n” in (a) triggers HO.

[0180] feedback like Fig.15 As shown, for example, the WTRU 102 may send feedback to the network via a measurement report (or other message) between times 1502 and 1504, and may also send feedback in 1520 after the HO process is completed. In the case of the timing in 1520, the WTRU must send the feedback to the target RAN node, which in turn must send it to the source RAN node. Currently, the 5G specification does not keep the WTRU context (e.g., different protocol stack layer configuration) active at the source node after the HO, but this may be an option in the future. Therefore, it is considered that the feedback sent in 1520 can be sent to both the source and target RAN nodes. If the feedback is sent to the target, then the target must forward the information to the source RAN node.

[0181] Preprocessing feedback In certain representative embodiments, the feedback that the WTRU sends to the network between the time in 1502 and the time in 1504 may include the complete prediction (e.g., predicted values ​​for each time step) that the network requires the WTRU to perform, such as any of the kinds of predictions described herein. In certain representative embodiments, the feedback that the WTRU sends to the network between the time in 1502 and the time in 1504 may include only a subset of the values. In certain representative embodiments, the feedback that the WTRU sends to the network between the time in 1502 and the time in 1504 may include a subset of values ​​for QoS related metrics, one value for a radio interface measurement (e.g., RSRP), and / or another subset of values ​​for UL buffers. In certain other embodiments, the feedback may include any combination of QoS, radio interface, and / or UL buffer information, such as for a single point in time, a set of points in time, and / or a subset of points in time.

[0182] In certain representative embodiments, the network may not send any configuration information to the WTRU, and the WTRU may be configured (eg, implicitly by lack of configuration) to trigger the prediction and perform the entire process autonomously.

[0183] In certain representative embodiments, the network may configure the WTRU to use a specific reconfiguration window and send information about one, some, or all of the listed prediction values ​​as feedback information before the reconfiguration window begins.

[0184] Post-processing feedback In certain representative embodiments, the feedback that the WTRU sends to the network after the HO is completed (e.g., after the reconfiguration window in 1520) may include any of the following. For example, the feedback may include any of the following: (i) The number of packets sent to the source RAN node after the start of the reconfiguration window but before the HO; (i) the number of packets sent to the source RAN node after the reconfiguration window starts and until feedback is sent; (iii) the number of packets retransmitted to the source RAN node before HO; (iv) the number of packets retransmitted to the source RAN node after the start of the reconfiguration window and until feedback is sent; (v) the available UL delay budget at each time step; (vi) the delay budget available for each time-step group (where time-step groups can have any granularity); (vii) the average UL delay budget for each time step group (where the time step group can have any granularity) after the start of the reconfiguration window but before the HO; (viii) the average UL delay budget for each time step group (where the time step group may have any granularity) after the reconfiguration window starts and until the feedback is sent; (ix) Same as (v) to (viii), except UL packet delay; (x) Same as (v) to (viii), except for UL packet error rate; (xi) Same as (v) to (viii), except for UL throughput; (xii) Same as (v) to (viii), except for DL ​​throughput; (xiii) Same as in (v) to (viii), except any number of retransmission packets in UL and / or DL ​​(e.g., at the source RAN node); (xiv) same as in (v) to (viii), except that the UL buffer levels (e.g. for one, all, a subset or a combination of any data radio bearer(s), PDU session(s) and / or QFI(s)) may or may not be averaged over a group of time steps, including after the start of the reconfiguration window but before HO and / or after the start of the reconfiguration window and until feedback is sent; and / or (xv) Same as in items 5 to 8, except that any air interface measurements are averaged or not averaged within a time step group, both after the start of the reconfiguration window but before HO and / or after the start of the reconfiguration window and until feedback is sent.

[0185] Layer 3 Process Fig.17 1700 is a flow chart illustrating an example of an L3 communication process in accordance with certain embodiments. In certain representative embodiments, a source RAN node 1702 (e.g., a gNB 180) may determine that the WTRU 102 performs a HO to a target RAN node 1704 (e.g., a gNB 180), as described herein at 1706. For example, the source RAN node 1702 may request (e.g., sending a HO request via an Xn interface) a target RAN node 1704 (e.g., a gNB 180), or multiple target RAN nodes (e.g., gNBs) in the case of CHO, to accommodate the WTRU 102. The source RAN node 1702 may include a time value (e.g., t_fb) associated with a starting point after which the WTRU 102 may determine to perform a HO.

[0186]

[00106] In certain representative embodiments, at 1708, the one or more target RAN nodes 1704 may perform admission control upon receiving the HO request. For example, an (e.g., implicit or explicit) indication of a time value (e.g., t_fb) associated with a time interval (e.g., the start of the time interval) in which the HO may be performed may help resolve the resource reservation issues mentioned above, such as for a CHO type of HO. The target RAN node(s) 1704 may use the received request to identify whether the WTRU 102 may be accommodated at that time. For example, the target RAN node(s) 1704 may utilize AI / ML techniques to predict future resource states. In this way, the admission control process may be enhanced.

[0187] In certain representative embodiments, any target RAN node 1704 may rely on historical information from the WTRU 102 to utilize AI / ML techniques, such as predicting a time interval (e.g., t_fb) for HO execution. At 1710, any of the target RAN nodes 1704 may provide feedback information about the prediction (e.g., before the HO request). The feedback information may be sent to the source RAN node 1702 (e.g., as a HO request confirmation message using an Xn interface). For example, the feedback information may include a time value t_fb'. The time value may be a separate time value, or may be a change from the received t_fb.

[0188] In certain representative embodiments, the source RAN node 1702 may configure the WTRU 102 with the HO command described herein. For example, the WTRU 102 may Fig.17 The RRC reconfiguration is received at 1712 in HO Command. For example, the reception by the WTRU 102 may mark the beginning of an evaluation and / or feedback window associated with the HO command.

[0189] For example, in Fig.17 At 1714, the network (eg, source RAN node 1702) may instruct the WTRU 102 to perform inference and generate a prediction. At 1712, input information for generating the WTRU prediction may be included in the RRC reconfiguration.

[0190] In certain representative embodiments, the WTRU 102 may send measurement information to a source RAN node, such as Fig.17 1716 and 1718 in the RRC measurement reports. For example, each of the measurement reports may be a message that the WTRU 102 may send to the network during the evaluation and / or feedback window 1720. For example, in some cases, the measurement reports may be optional and may trigger feedback information at the WTRU 102, as described herein.

[0191] In certain representative embodiments, at the end of the evaluation and / or feedback window (e.g., at t_fb), a reconfiguration window 1722 may begin. During the reconfiguration window 1722, the WTRU 102 may determine whether (and when) to perform a HO within the reconfiguration window 1722. For example, the WTRU 102 may perform a HO at a first time during the reconfiguration window and may send an RRC reconfiguration complete message to the target RAN node at 1724. As another example, the WTRU 102 may perform a HO at a second time during the reconfiguration window and may send an RRC reconfiguration complete message to the target RAN node at 1726. Although Fig.17 Multiple RRC reconfiguration complete messages are shown, but the messaging at 1724 and 1726 is to illustrate that the WTRU 102 may trigger the conclusion of the HO at different times during the reconfiguration window 1722, as described herein.

[0192] Fig.18 is a flow chart 1800 illustrating an example of a layer 3 (L3) communication process in accordance with certain embodiments.

[0193] At 1802, the source RAN node 1702 decides to perform a process in which the WTRU 102 will determine when to perform a HO (e.g., CHO) according to the principles described above and request a HO (e.g., CHO) to accommodate the WTRU from the target node(s) 1704. The source RAN node 1702 may have reached a reconfiguration time window, and if so, this information may be included in the HO request sent to the target node(s) 1704 at 1802 along with any predictions.

[0194] At 1804, the admission control function at the target RAN node(s) 1704 may be modified because, although the target node 1704 may receive the reconfiguration window [t; t+n] from the WTRU 102 within the HO request message and accept the window, it may alternately shorten or increase the reconfiguration window. For example, it may reduce / increase the window in a non-negotiable manner. Alternatively, it may only send a recommendation for increasing or decreasing the window. In some embodiments, it may send back a completely new window specification. In other embodiments, it may send back a change value applied from the end of the original specified window, or a change value applied from the beginning of the original specified window. In yet other embodiments, it may send a time shift value (e.g., if the original specified window is [t; t+n], the target node may shift the window two seconds after [t+2; t+n+2]. At 1810, the target node may include any such window modification information.

[0195] At 1810, the target RAN node(s) 1704 may send a HO request confirm message with the modified window or any feedback to the source node 1702 in any manner described herein.

[0196] At 1812, the source RAN node 1702 may send an RRC reconfiguration message to the WTRU 102 to reconfigure the WTRU 102, such as based on Fig.15 Any of the embodiments described in. The receipt of the reconfiguration information at 1812 marks the beginning of the evaluation and feedback window 1814.

[0197] At 1816, the WTRU may optionally send feedback to the network as described herein.

[0198] At 1818, the WTRU 102 may trigger a HO or uplink handover (eg, in the case of DAPS) at any point within the reconfiguration window 1820 using any of the triggers described herein.

[0199] At 1820, the WTRU 120 sends an RRC reconfiguration complete message to the source node 1702. The RRC reconfiguration message may include any of the feedback information described in detail herein.

[0200] At 1822, the WTRU 102 may send feedback to the network using the next measurement report or any other message via the target node 1704. The message may additionally be directed to the source RAN node 1702, in which case the target node 1704 will not need to forward the feedback information to the source node 1702.

[0201] In certain representative embodiments, as described herein, Figures 19 to 25 The features described in the accompanying drawings may be combined, omitted and / or modified in part or in whole.

[0202] Fig.191 is a process diagram illustrating an example feedback and HO process of a WTRU 102. At 1902, the WTRU 102 may receive (e.g., from a source cell) information indicating a network predicted first set of radio measurements and a timestamp. At 1904, the WTRU 102 may receive configuration information indicating a handover (HO) window (e.g., a reconfiguration window) and a time offset of a target cell. For example, the timestamp received at 1902 may correspond to a time interval before the HO window. At 1906, the WTRU may perform and / or predict a second set of radio measurements based on the timestamp. At 1908, the WTRU 102 may send information indicating an evaluation of (e.g., one or more) of the network predicted first set of radio measurements and a second set of radio measurements at one or more first times no later than the time offset before the HO window. For example, the one or more first times may be based on the HO window and the time offset. At 1910, the WTRU 102 may perform a HO to the target cell based on the configuration information at a second time within the HO window.

[0203] In certain representative embodiments, the information at 1902 and 1904 may be received together in an RRC message.

[0204] In certain representative embodiments, the information indicating the HO window may include a start time of the HO window and an end time of the HO window.

[0205] In certain representative embodiments, the HO window is a time interval (eg, for performing HO using the configuration information received at 1904).

[0206] In certain representative embodiments, the timestamp received at 1902 is no later than a time offset (eg, t_fb) before the HO window. For example, the latest timestamp may correspond to the latest measurement in the first set of measurements.

[0207] In certain representative embodiments, the HO window may be indicated as a number of milliseconds, time slots, or symbols.

[0208] In certain representative embodiments, the HO is a dual access protocol stack (DAPS) HO or a conditional HO, as described herein.

[0209] In certain representative embodiments, information indicating the HO window and / or the time offset may be included in a radio resource control (RRC) message (eg, an RRC reconfiguration message).

[0210] In certain representative embodiments, the WTRU 102 may determine one or more first times based on the HO window and the time offset. For example, the WTRU 102 may send the evaluation information at a (eg, last) first time that is no later than the time offset before the HO window.

[0211] In certain representative embodiments, the WTRU 102 may determine a second time (e.g., perform a HO at the second time) based on an uplink (UL) buffer measurement set satisfying a threshold. For example, the WTRU 102 may use UL buffer measurements and other WTRU measurements (e.g., radio and / or QoS measurements) described herein to determine the second time (e.g., trigger a HO within a HO window).

[0212] In certain representative embodiments, the WTRU 102 may perform and / or predict a UL buffer measurement set by the WTRU.

[0213] In certain representative embodiments, the UL buffer measurement set may be associated with one or more data radio bearers, one or more protocol data unit (PDU) sessions, and / or one or more quality of service flow identifiers (QFIs).

[0214] In certain representative embodiments, the WTRU 102 may determine (eg, perform) a set of UL buffer measurements during a time interval between the start of the HO window and a second time.

[0215] Fig. 20 is a process diagram illustrating an example HO procedure for the WTRU 102. At 2002, the WTRU 102 may receive information indicating a first set of network predicted measurements and a timestamp. At 2004, the WTRU may receive configuration information indicating a HO window and a time offset for a target cell (e.g., from a source cell). For example, the information at 2002 and 2004 may be received together in an RRC message (e.g., an RRC reconfiguration message). At 2006, the WTRU 102 may perform and / or predict a second set of measurements based on the timestamp received at 2002. At 2008, the WTRU 102 may perform a HO to the target cell during the HO window based on the configuration information, the first set of network predicted measurements, and the second set of measurements. For example, the first set of measurements and the second set of measurements may be used to trigger the HO, and the performance of the HO may be performed based on the configuration information.

[0216] Fig.21is a process diagram illustrating an example feedback process of the WTRU 102. At 2102, the WTRU 102 may receive information indicating a first set of network predicted measurements and a timestamp. At 2104, the WTRU 102 may receive configuration information indicating an HO window and a time offset for a target cell (e.g., from a source cell). For example, the information at 2102 and 2104 may be received together in an RRC message (e.g., an RRC reconfiguration message). At 2106, the WTRU 102 may perform and / or predict a second set of measurements based on the timestamp. At 2108, the WTRU 102 may send information indicating (e.g., one or more) evaluations of the first set of network predicted measurements and the second set of measurements at one or more first times that are no later than the time offset before the HO window. For example, the one or more first times may be based on the HO window and the time offset. For example, the first times may be (e.g., both) before (e.g., no later than) a time equal to the time offset before the start of the HO window.

[0217] Fig. 22 is a process diagram illustrating an example admission control process of a first base station (e.g., gNB 180). At 2202, a first base station (e.g., associated with a target cell) may receive information indicating a handover (HO) window for a WTRU 102 from a second base station (e.g., associated with a source cell). For example, the first base station may receive a HO request as described herein. At 2204, the first base station may determine whether to accommodate a HO of the WTRU 102 from the second base station during the HO window. For example, the first base station may determine whether sufficient resources are available to accommodate the WTRU 102 when the HO is to be performed (e.g., during the HO window). As part of the determination at 2204, such resources may be reserved. At 2206, assuming that the HO request is acceptable, the first base station may send information indicating that the HO window is accepted and / or information indicating a modification of the HO window to the second base station. For example, the first station may send a HO request confirmation message to the second base station, which includes information indicating the modification of the HO window.

[0218] Fig.23is a process diagram illustrating an example HO process of the WTRU 102. At 2302, the WTRU 102 may receive configuration information (e.g., from a source cell) indicating a handover (HO) window of a target cell. At 2304, the WTRU 102 may perform or predict a measurement set based on a timestamp. For example, the measurement set may include any one of uplink (UL) buffer measurement information, radio interface measurement information, and / or quality of service (QoS) measurement information. For example, the measurement set may correspond to the measured quantities at the indicated timestamp. At 2306, the WTRU 102 may determine the time to perform (e.g., trigger) an HO to the target cell within the HO window based on the measurement set. For example, the measurement set may be compared with another set of network predicted measurements. Various examples of WTRU evaluation and triggering are described herein. At 2308, the WTRU 102 may perform an HO to the target cell at the determined time within the HO window based on the configuration information.

[0219] In some representative embodiments, the WTRU 102 may provide pre - processing and / or post - processing feedback information related to the HO and / or the HO window. For example, the feedback information may include an evaluation associated with network predicted measurements and / or WTRU (e.g., predicted and / or performed) measurements.

[0220] Fig.24 is a process diagram illustrating an example HO process of the WTRU 102. At 2402, the WTRU 102 may receive configuration information indicating a handover (HO) window of a target cell. At 2404, the WTRU 102 may send one or more measurement reports at one or more first times not later than a time offset before the HO window. For example, at each first time, the WTRU may send a corresponding measurement report (e.g., associated with one or more measurements). At 2406, the WTRU 102 may perform and / or predict a measurement set. For example, the measurement set may include any one of uplink (UL) buffer measurement information (e.g., set), radio interface measurement information (e.g., set), and / or quality of service (QoS) measurement information (e.g., set). At 2408, the WTRU 102 may perform an HO to the target cell at a time within the HO window based on the configuration information and the measurement set. For example, the time to perform the HO may be based on the measurement set obtained at 2406.

[0221] Fig.252506, the base station may receive (e.g., pre-process) the feedback information. For example, the base station may receive (e.g., from the WTRU 102) feedback information indicating an evaluation of the first set of network predicted radio measurements at one or more first times no later than the time offset before the HO window. At 2508, the base station may receive (e.g., post-process) feedback information associated with the WTRU 102 performing a HO during the HO window from a second base station associated with the target cell.

[0222] In certain representative embodiments, as described herein, Figures 19 to 25 The features described in the accompanying drawings may be combined, omitted and / or modified in part or in whole.

[0223] In certain representative embodiments, a WTRU 102 may implement a method or perform a process that includes receiving information indicating a handover (HO) command from a first base station (e.g., associated with a source cell). The WTRU 102 may receive information indicating a first set of network predicted measurements associated with the HO command. The WTRU 102 may obtain a second set of measurements associated with one or more second base stations (e.g., candidate cells). The WTRU 102 may perform a HO to one of the second base stations (e.g., associated with a target cell) on the condition that the first set of network predicted measurements and the second set of measurements satisfy one or more first criteria.

[0224] For example, the WTRU 102 may receive one or more RSs from the one or more second base stations.The second set of measurements may be based on the one or more RSs received from the one or more second base stations.

[0225] For example, the WTRU 102 may predict one or more RS values ​​associated with one or more second base stations.The second set of obtained measurements may be based on the predicted one or more RS values.

[0226] For example, the information indicating the HO command may be a reconfiguration message. The reconfiguration message may include information indicating any of the following: (i) one or more second base stations, (ii) a first time interval associated with the first set of network predicted measurements and / or the second set of measurements, (iii) a second time interval for performing the HO, (iv) one or more first criteria, and / or (v) a confidence interval associated with the first time interval and / or the first set of network predicted measurements.

[0227] For example, the performance of the HO may include performing a random access channel (RACH) procedure with one of the second base stations.

[0228] For example, the performance of the HO may include sending a reconfiguration complete message to one of the second base stations.

[0229] For example, the WTRU 102 may send feedback information associated with at least the second set of measurements to the first base station, conditional upon the network predicting that the first set of measurements and / or the second set of measurements meet one or more second criteria.

[0230] For example, under the condition that the network predicts that the first set of measurements and the second set of measurements do not meet one or more first criteria, the WTRU 102 may send feedback information associated with at least the second set of measurements to the first base station.

[0231] For example, the HO command may be any one of a conventional HO command, a dual access protocol stack (DAPS) HO command, or a conditional HO (CHO) command.

[0232] For example, the WTRU 102 may receive information indicating one or more configurations of the RS.

[0233] For example, the WTRU 102 may receive information indicating a measurement configuration for a second set of measurements.

[0234] For example, the WTRU 102 may receive information indicating a reporting configuration for feedback information.

[0235] For example, one or more predicted RS values ​​associated with one or more second base stations may (eg, determined by the WTRU to) satisfy a configured confidence interval.

[0236] For example, the one or more second criteria may include at least one measurement in the second set of measurements falling outside a window corresponding to the configured confidence interval.

[0237] For example, for the same time point and / or the same confidence interval, the one or more second criteria may include that a difference between at least one measurement in the second set of measurements and at least one measurement in the first set of network prediction measurements is greater than a threshold.

[0238] For example, a threshold value may be associated with an upper limit of a confidence interval.

[0239] For example, a threshold value may be associated with a lower limit of a confidence interval.

[0240] For example, for the same time point and / or the same confidence interval, the one or more first criteria may include that a difference between at least one measurement in the second set of measurements and at least one measurement in the first set of network prediction measurements is less than a threshold.

[0241] For example, a threshold value may be associated with an upper limit of a confidence interval.

[0242] For example, a threshold value may be associated with a lower limit of a confidence interval.

[0243] In certain representative embodiments, a base station (e.g., associated with a source cell) may send a handover (HO) request to one or more other base stations, the HO request including information indicating a time interval for the HO of the WTRU. The base station may send information indicating the HO command to the WTRU. The base station may obtain a first set of network prediction measurements associated with the HO command. The base station may send the first set of network prediction measurements to the WTRU. For example, the WTRU may use the first set of network prediction measurements described herein.

[0244] For example, the base station may receive, from the WTRU, feedback information associated with at least a second set of measurements obtained by the WTRU based on the HO command.

[0245] For example, sending the first set of network prediction measurements may include a confidence interval within which the first set of network prediction measurements is obtained.

[0246] For example, feedback information may be received from the WTRU under conditions where one or more criteria associated with the confidence interval are not met, such as when the WTRU does not perform a HO command (eg, within the HO window).

[0247] In certain representative embodiments, the WTRU 102 may implement a method or perform a process that includes receiving an instruction from a network to perform a handover (HO). The WTRU 102 may receive configuration information of a reconfiguration window from the network, the reconfiguration window including a window within which the WTRU should perform the HO. The WTRU 102 may analyze one or more of an uplink (UL) buffer status, a quality of service (QoS) parameter, and a radio condition to determine a time to perform the HO within the reconfiguration window. The WTRU 102 may perform the HO at the determined time.

[0248] For example, analysis of conditions may include analyzing current conditions.

[0249] For example, analysis of conditions may include using AI / ML models to predict future conditions.

[0250] For example, the WTRU 102 may evaluate the performance of the HO over multiple parameters and time. The WTRU may transmit feedback information associated with the evaluation results to the network.

[0251] For example, the feedback information may include any of the following: the number of packets transmitted to the source RAN node during the reconfiguration window before the HO; the number of packets transmitted to the source RAN node after the start of the reconfiguration window and before the feedback information is transmitted; the number of packets retransmitted to the source RAN node before the HO; the number of packets retransmitted to the source RAN node after the start of the reconfiguration window before the feedback information is transmitted; and the UL delay budget available at each time step.

[0252] For example, the feedback information may include a prediction made at the WTRU of any of uplink (UL) buffer status, quality of service (QoS) parameters, and / or radio conditions to determine when to perform the HO within the reconfiguration window.

[0253] For example, the WTRU 102 may determine the configuration of a reconfiguration window (eg, HO window) at the WTRU 102. The WTRU 102 may choose to use a reconfiguration window configuration received from the network or a reconfiguration window configuration determined at the WTRU.

[0254] Summarize Although features and elements are described above in specific combinations, it will be appreciated by those skilled in the art that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited in terms of the specific embodiments described in the present application, which are intended to be illustrations of various aspects. Without departing from its spirit and scope, many modifications and changes can be made, which will be obvious to those skilled in the art. Any element, action or instruction used in the specification of the present application should not be interpreted as being essential or indispensable to the present invention, unless so clearly specified. In addition to those listed herein, by the above description, the functionally equivalent methods and devices within the scope of the present disclosure will be obvious to those skilled in the art. These modifications and changes are intended to fall within the scope of the appended claims. The present disclosure is limited to the items of the appended claims and the full range of equivalents enjoyed by the claims. It should be understood that the present disclosure is not limited to a particular method or system.

[0255] For simplicity, the above embodiments are discussed with respect to the terminology and structure of devices supporting wireless communication (e.g., radio wave transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems using other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0256] It should also be understood that the terms used herein are used only to describe specific embodiments and are not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, a single image, and / or a plurality of images displayed on a time basis. As another example, when referred to herein, the term "user equipment" and its abbreviation "UE", the term "remote" and / or the term "head-mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmission and / or reception unit (WTRU), (ii) any of many embodiments of a WTRU, (iii) a wirelessly-enabled and / or wiredly-enabled device (e.g., sharable via a mobile phone) configured with, among other things, some or all of the structure and functionality of a WTRU, (iii) a wirelessly-enabled and / or wiredly-enabled device configured with less than all of the structure and functionality of a WTRU, or (iv), etc. This document is about Figures 1A to 1D Details of an example WTRU are provided that may represent any WTRU described herein. As another example, various disclosed embodiments are described above and below herein as utilizing a head mounted display. Those skilled in the art will appreciate that devices other than head mounted displays may be utilized and that some or all of the present disclosure and various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to flow information to provide an adapted reality experience.

[0257] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and 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, caches, semiconductor memory devices, magnetic media (such as internal hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

[0258] Variations of the methods, devices, and systems provided above are possible without departing from the scope of the present invention. In view of the various embodiments that may be applied, it should be understood that the illustrated embodiments are merely examples and should not be considered to limit the scope of the following claims. For example, the embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery, etc.) to provide any suitable voltage.

[0259] In addition, in the embodiments provided above, processing platforms, computing systems, controllers and other devices are mentioned. These devices may include at least one central processing unit ("CPU") and memory. According to the practice of those skilled in the art of computer programming, references to symbolic representations of actions and operations or instructions may be performed by various CPUs and memories. Such actions and operations or instructions may be referred to as "being executed", "being executed by a computer" or "being executed by a CPU".

[0260] Those of ordinary skill in the art will appreciate that actions and symbolically represented operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits, which can cause the resulting transformation or reduction of electrical signals, and the data bits are maintained at memory locations in the memory system, thereby reconfiguring or otherwise changing the operation of the CPU, as well as other processing of signals. The memory location that holds the data bit is a physical location with specific electrical, magnetic, optical, or organic properties corresponding to or representing the data bit. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs can support the provided methods.

[0261] The data bits may also be maintained on a computer-readable medium, including magnetic disks, optical disks, and any other volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage system that can be read by the CPU. The computer-readable medium may include cooperating or interconnected computer-readable media that reside exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that embodiments are not limited to the above-described memories, and other platforms and memories may support the provided methods.

[0262] In an illustrative embodiment, any operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0263] There is little difference between hardware and software implementations of aspects of the system. The use of hardware or software is typically (but not always, as in certain contexts, the choice between hardware and software may become important) a design choice that represents a cost-versus-efficiency trade-off. There may be various vehicles through which the processes and / or systems and / or other technologies described herein (e.g., hardware, software, and / or firmware) may be implemented, and the preferred vehicle may vary with the context in which the processes and / or systems and / or other technologies are deployed. For example, if the implementer determines that speed and accuracy are most important, the implementer may select a primarily hardware and / or firmware vehicle. If flexibility is most important, the implementer may select a primarily software implementation. Alternatively, the implementer may select some combination of hardware, software, and / or firmware.

[0264] The above specific embodiments have been described various embodiments of devices and / or processes by using block diagrams, flow charts and / or examples. Since such block diagrams, flow charts and / or examples include one or more functions and / or operations, it is understood by those skilled in the art that each function and / or operation in such block diagrams, flow charts or examples can be implemented individually and / or collectively by a variety of hardware, software, firmware or almost any combination thereof. In one embodiment, several parts of the subject matter described herein can be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs) and / or other integrated formats. However, those skilled in the art will appreciate that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in an integrated circuit as one or more computer programs running on one or more computers (e.g., implemented as one or more programs running on one or more computer systems), implemented as one or more programs running on one or more processors (e.g., implemented as one or more programs running on one or more microprocessors), implemented as firmware or almost any combination thereof, and in view of the present disclosure, designing circuits and / or writing code for software and / or firmware will be well within the skills of those skilled in the art. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a variety of forms of program products, and that the illustrative embodiments of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to actually perform the distribution. Examples of signal-bearing media include (but are not limited to) the following: recordable media such as floppy disks, hard drives, CDs, DVDs, digital tapes, computer memory, etc.; and transmission media such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0265] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner described herein, and then to integrate such described devices and / or processes into data processing systems using engineering practices. That is, at least a portion of the devices and / or processes described herein can be integrated into data processing systems via a reasonable number of experiments. Those skilled in the art will recognize that a typical data processing system can typically include one or more of the following: a system unit housing, a video display device, a memory (such as, volatile and non-volatile memory), a processor (such as, a microprocessor and a digital signal processor), a computing entity (such as, an operating system, a driver, a graphical user interface and an application), one or more interactive devices (such as, a touch pad or a screen) and / or a control system including a feedback loop and a control motor (e.g., a feedback for sensing position and / or speed, a control motor for moving and / or adjusting components and / or quantities). A typical data processing system can be implemented using any suitable commercially available components, such as those components typically found in data computing / communication and / or network computing / communication systems.

[0266] The subject matter described herein sometimes illustrates different components that are included in or connected to different other components.It should be understood that this depicted architecture is only an example, and in fact, many other architectures that realize the same function can be realized.In the sense of concept, any arrangement of the components that realize the same function is effectively "associated" so that the desired function can be realized.Therefore, any two components that are combined to realize a specific function herein can be regarded as "associated" with each other so that the desired function is realized, regardless of the architecture or intermediate components.Similarly, any two components so associated can also be regarded as "operably connected" or "operably coupled" to each other to realize the desired function, and any two components that can be so associated can also be regarded as "operably coupled" to each other to realize the desired function.The specific example of operably coupling includes but is not limited to components that can be physically paired and / or physically interacted and / or components that can be wirelessly interacted and / or wirelessly interacted and / or components that can interact logically and / or components that can interact logically.

[0267] With respect to the use of substantially any plural and / or singular terms herein, those skilled in the art can translate from the plural to the singular and / or from the singular to the plural as appropriate for the context and / or application. For clarity, various singular / plural arrangements may be expressly set forth herein.

[0268] Those skilled in the art will understand that, in general, the terms used herein, and particularly in the appended claims (e.g., the bodies of the appended claims), are generally intended to be "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "comprising" should be interpreted as "including but not limited to," etc.). Those skilled in the art will further understand that if a specific number of an introduced claim listing is intended, such intent will be explicitly listed in the claim, and if no such listing is present, such intent does not exist. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and / or the description herein may include the use of the introductory phrases "at least one" and "one or more" to introduce claim listings. However, the use of such phrases should not be interpreted as implying that an introduction to a claim recitation by the indefinite article "a" or "an" will include that any particular claim of such introduced claim recitation is limited to including only one embodiment of such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" or "an" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce a claim recitation. In addition, even if specific numbers of an introduced claim recitation are explicitly recited, those skilled in the art will recognize that such recitation should be interpreted as meaning at least the recited numbers (e.g., the unmodified recitation of "two recitations" without other modifiers means at least two recitations, or two or more recitations). Furthermore, in those cases where a convention similar to “at least one of A, B, and C, etc.” is used, generally speaking, such construction is intended in the sense that a person skilled in the art would understand the convention (e.g., “a system having at least one of A, B, and C” includes but is not limited to a system having only A, a system having only B, a system having only C, a system having A and B together, a system having A and C together, a system having B and C together, and / or a system having A, B, and C together, etc.). In those cases where a convention similar to “at least one of A, B, or C, etc.” is used, generally speaking, such construction is intended in the sense that a person skilled in the art would understand the convention (e.g., “a system having at least one of A, B, or C” includes but is not limited to a system having only A, a system having only B, a system having only C, a system having A and B together, a system having A and C together, a system having B and C together, and / or a system having A, B, and C together, etc.).Those skilled in the art will further understand that almost any transitional word and / or phrase presenting two or more alternative terms, whether in the specification, claims or drawings, should be understood to consider the possibility of including one of the terms, any one of the terms, or both of the terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B". Further, as used herein, the term "any of..." followed by a list of multiple items and / or multiple categories of items is intended to include "any one", "any combination", "any multiple" and / or "any combination of multiple" in the items and / or multiple categories, either alone or in combination with other items and / or other categories of items. In addition, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "quantity" is intended to include any number, including zero. Moreover, as used herein, the term "multiple" is intended to be synonymous with "plurality".

[0269] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0270] As will be understood by those skilled in the art, for any and all purposes, such as, in providing a written description, all ranges disclosed herein also encompass any and all possible sub-ranges and combinations of sub-ranges thereof. Any listed range can be easily identified as fully describing the same range and enabling the same range to be divided into at least equal half, one-third, one-quarter, one-fifth, one-tenth, etc. As a non-limiting example, each range discussed herein can be easily divided into lower third, middle third, and upper third, etc. As will be understood by those skilled in the art, such as, "up to", "at least", "greater than", "less than", etc., all languages ​​include the enumerated numbers, and refer to the range that can be subsequently divided into the above-mentioned sub-ranges. Finally, as will be understood by those skilled in the art, the range includes each individual member. Therefore, for example, a group with 1 to 3 units refers to a group with 1, 2 or 3 units. Similarly, a group with 1 to 5 units refers to a group with 1, 2, 3, 4 or 5 units.

[0271] Furthermore, the claims should not be read as limited to the order or elements provided unless so stated. Furthermore, the use of the term "means for..." in any claim is intended to invoke or “means-plus-function” claim format, and any claim without the term “means for…” is not intended to be so.

Claims

1. A method implemented by a wireless transmit / receive unit (WTRU), include: receiving information indicating a first set of network predicted radio measurements and a timestamp; receiving configuration information indicating a handover (HO) window and a time offset of a target cell; performing and / or predicting, by the WTRU, a second set of radio measurements based on the timestamp; sending information indicating a network predicted evaluation of a first set of radio measurements and a second set of radio measurements at one or more first times no later than the time offset before the HO window, wherein the one or more first times are based on the HO window and the time offset; as well as At a second time within the HO window, a HO to the target cell is performed based on the configuration information. 2 . The method according to claim 1 , wherein the information indicating the HO window comprises a start time of the HO window and an end time of the HO window.

3. The method according to any one of claims 1 to 2, wherein the HO window is a time interval.

4. The method according to any one of claims 1 to 3, wherein the timestamp is no later than the time offset before the HO window.

5. The method according to any one of claims 1 to 4, wherein the HO window is indicated as a number of milliseconds, time slots or symbols.

6. The method according to any one of claims 1 to 5, wherein the HO is a Dual Access Protocol Stack (DAPS) HO or a Conditional HO.

7. The method according to any one of claims 1 to 6, wherein the information indicating the HO window and / or the time offset is included in a Radio Resource Control (RRC) message.

8. The method according to any one of claims 1 to 7, further comprising: include: The one or more first times are determined based on the HO window and the time offset.

9. The method according to any one of claims 1 to 8, further comprising: include: The second time is determined based on an uplink (UL) buffer measurement set satisfying a threshold.

10. The method according to claim 9, further comprising: include: The UL buffer measurement set is performed and / or predicted by the WTRU.

11. The method according to any one of claims 9 to 10, wherein the UL buffer measurement set is associated with one or more data radio bearers, one or more protocol data unit (PDU) sessions and / or one or more quality of service flow identifiers (QFIs).

12. The method according to any one of claims 9 to 11, further comprising: include: The UL buffer measurement set is determined during a time interval between a start of the HO window and a second time.

13. A wireless transmit / receive unit (WTRU), include: Processors, memory, and transceivers configured to: receiving information indicating a first set of network predicted radio measurements and a timestamp; receiving configuration information indicating a handover (HO) window and a time offset of a target cell; performing and / or predicting, by the WTRU, a second set of radio measurements based on the timestamp; sending information indicating a network predicted evaluation of a first set of radio measurements and a second set of radio measurements at one or more first times no later than the time offset before the HO window, wherein the one or more first times are based on the HO window and the time offset; as well as At a second time within the HO window, a HO to the target cell is performed based on the configuration information.

14. The WTRU of claim 13, wherein the information indicating the HO window comprises a start time of the HO window and an end time of the HO window.

15. The WTRU of any one of claims 13 to 14, wherein the HO window is a time interval to perform HO to the target cell.

16. The WTRU of any one of claims 13 to 15, wherein the timestamp is no later than the time offset before the HO window.

17. The WTRU of any one of claims 13 to 16, wherein the HO window is indicated as a number of milliseconds, slots, or symbols.

18. The WTRU of any one of claims 13 to 17, wherein the HO is a dual access protocol stack (DAPS) HO or a conditional HO.

19. The WTRU of any one of claims 13 to 18, wherein the information indicating the HO window and / or the time offset is included in a radio resource control (RRC) message.

20. The WTRU of any one of claims 13 to 19, wherein the processor, memory, and transceiver are configured to: The one or more first times are determined based on the HO window and the time offset.

21. The WTRU of any one of claims 13 to 20, wherein the processor, memory, and transceiver are configured to: The second time is determined based on an uplink (UL) buffer measurement set satisfying a threshold.

22. The WTRU of claim 21, wherein the UL buffer measurement set comprises one or more current UL buffer levels and / or one or more predicted UL buffer levels.

23. The WTRU according to any one of claims 21 to 22, wherein the UL buffer measurement set is associated with one or more data radio bearers, one or more protocol data unit (PDU) sessions and / or one or more quality of service flow identifiers (QFIs).

24. The WTRU of any one of claims 21 to 23, wherein the processor, memory, and transceiver are configured to: The UL buffer measurement set is determined during a time interval between a start of the HO window and a second time.

Images