Utilizing rating information for customizing LTM mobility with service specific preferences

Abstract

A wireless transmit / receive unit (WTRU) may receive a configuration associated with a plurality of candidate cells. The WTRU may send, for example, a request for handover rating information (HRI) for a plurality of candidate cells to a network. The request may include service description information associated with a service running at the WTRU. The WTRU may receive a response from the network. The response may include an HRI for the plurality of candidate cells. The HRI may include an indication of how appropriate each of the plurality of candidate cells is to be a target cell for the WTRU. The WTRU may select a candidate cell from the plurality of candidate cells based on the HRI. The WTRU may send an indication of the selected candidate cell to the network.

Description

[0001] Cross-references to related applications This application claims the benefit of U.S. Provisional Application No. 63 / 525,194, filed July 6, 2023, the entire contents of which are incorporated herein by reference. Background Technology

[0002] For example, compared to traditional L3 or conditional handover, there may be mechanisms and procedures for L1 / L2-based inter-cell mobility with the overall goal of reducing latency. L3 and conditional handover procedures may include delays, for example, due to the exchange of measurement reports and the reception of target configurations. LTM can allow for the rapid application of candidate cell configurations and / or dynamic switching between secondary and primary cells (SCells), for example, without the need for Radio Resource Control (RRC) signaling.

[0003] RAN2 supports baseline procedures for L1 / 2 triggered mobility (LTM). Baseline procedures may include one or more of LTM preparation, early synchronization, LTM execution, and / or LTM completion. Figure 2 An example of the baseline procedure is depicted in the document. Summary of the Invention

[0004] A Wireless Transmit / Receive Unit (WTRU) can receive configuration. This configuration can be associated with candidate cells. The WTRU can, for example, send a request to the network. This request can be rating information for the candidate cells. The request can include service description information. The WTRU can, for example, receive a response from the network. This response can include rating information for the candidate cells. The WTRU can, for example, send an indication to the network. This indication can include the selected candidate cells.

[0005] The request (e.g., a request to the network) may include one or more of a first identifier of the service associated with the WTRU, a second identifier of the service associated with the handover rating information (HRI), and / or a third identifier of the predicted service. The request (e.g., a request to the network) may include a list of one or more candidate cells and / or an indication of the handover rating information (HRI). The indication of the HRI may be associated with one or more candidate cells.

[0006] The WTRU can send measurement reports to, for example, a base station. These measurement reports can be Layer 1 (L1) measurement reports. The WTRU can receive Media Access Control (MAC) control elements (CEs). The MAC CE can include instructions for handover to the base station. The WTRU can, for example, perform a Random Channel Access (RACH) procedure on the base station.

[0007] The WTRU can receive requests for rating information. These requests can be for candidate cells. The WTRU can, for example, send a measurement report to the base station. This measurement report may include rating information.

[0008] (For example, firstly) the WTRU may receive configuration. This configuration may be associated with a candidate cell. (For example, firstly) the WTRU may send a request. This request may be rating information for the candidate cell. The request may include service description information. The WTRU may receive multicast messages. The multicast message may include rating information for the candidate cell and / or an indication from another anchor WTRU.

[0009] The multicast message may include an indication that one or more other (e.g., second) WTRUs are included in the cluster. For example, when the first WTRU is an anchor WTRU, the (e.g., first) WTRU may send a sidelink message to one or more of the other (e.g., second) WTRUs. This sidelink message may include an indication of the selected target cell. The (e.g., first) WTRU may, for example, reply to a sidelink message from one or more of the other (e.g., second) WTRUs. This sidelink message reply may include the selected target cell. The (e.g., first) WTRU may send an indication to the network. The indication to the network may include the selected target cell.

[0010] For example, when (e.g., the first) WTRU is not the anchor WTRU, (e.g., the first) WTRU can receive a sidelink message from the anchor WTRU. This sidelink message may include an indication of the selected target cell. (e.g., the first) WTRU can, for example, send a sidelink message reply to the anchor WTRU. This sidelink message reply may include the selected target cell.

[0011] (For example, firstly) the WTRU may send a measurement report to the base station. This measurement report may be a Layer 1 (L1) measurement report. (For example, firstly) the WTRU may receive a Media Access Control (MAC) control element (CE). The MAC CE may include an indication to hand over to the base station. (For example, firstly) the WTRU may execute a RACH procedure on the base station.

[0012] The WTRU can receive configurations associated with multiple candidate cells. The WTRU can, for example, send a request to the network for handover rating information (HRI) for the multiple candidate cells. This request may include service description information associated with the service running at the WTRU. The WTRU can receive a response from the network. This response may include the HRIs of the multiple candidate cells.

[0013] The HRI can include an indication of how suitable each of a plurality of candidate cells is to become a target cell for the WTRU. The HRI can be associated with and / or based on a service, such as (e.g., at the WTRU) a service that is in operation and / or (e.g., at the WTRU) a predicted service. For example, the HRI can be based on (e.g., sent by the WTRU) service description information. The WTRU can select a candidate cell from a plurality of candidate cells based on the HRI. The WTRU can send an indication of the selected candidate cell to the network. This indication can include selection information associated with the selection of the candidate cell. The selection information associated with the selection of the candidate cell can include one or more of the following: a confidence interval associated with the selected candidate cell, an error tolerance associated with the selected candidate cell, and / or an accuracy coefficient associated with the selected candidate cell.

[0014] HRI may include one or more of the following: an indication of the number of active services at the WTRU, an indication of the number of services the WTRU intends to operate after a handover (HO), or an indication of interference levels and / or radio link-related measurements associated with multiple candidate cells. HRI may be specific to the services operating at the WTRU.

[0015] The request to the network may include one or more of the following: a first identifier of the service associated with the WTRU, a second identifier of the service associated with the HRI, and / or a third identifier of the predicted service. The WTRU may receive a request for rating information for the selected candidate cell. The WTRU may perform measurements on the selected candidate cell. The WTRU may send a measurement report to the network. This measurement report may include the measurement HRI associated with the selected candidate cell. The WTRU may send a sidelink message to one or more other WTRUs. This sidelink message may include an indication of the selected candidate cell.

[0016] The configuration associated with multiple candidate cells can include the configuration associated with the selected candidate cell. The WTRU can receive the Media Access Control (MAC) control element (CE) associated with the selected candidate cell. The WTRU can determine the configuration to apply to the selected candidate cell. The WTRU can perform a random access procedure with the selected candidate cell.

[0017] A request for an HRI may include a first request for an HRI. The WTRU may receive a second request for an HRI from the selected candidate cell. The second request for an HRI may include a request for information associated with a cell previously connected to the WTRU. The WTRU may send a response to the second request for an HRI to the selected candidate cell. This response may include HRIs from one or more of the selected candidate cell and / or cells previously connected to the WTRU. Attached Figure Description

[0018] Figure 1A This is a system diagram illustrating an example communication system in which one or more of the disclosed embodiments may be implemented.

[0019] Figure 1B The illustration shows a method according to one embodiment. Figure 1A The diagram shows a system diagram of an example wireless transmit / receive unit (WTRU) used in a communication system.

[0020] Figure 1C The illustration shows a method according to one embodiment. Figure 1A The diagram illustrates a system diagram of an example radio access network (RAN) and an example core network (CN) used in the communication system.

[0021] Figure 1D The illustration shows a method according to one embodiment. Figure 1A The illustrated system diagram shows yet another example RAN and yet another example CN used in the communication system.

[0022] Figure 2 This is a diagram illustrating an example LTM baseline procedure.

[0023] Figure 3 This is a diagram illustrating the example LTM execution with reference to WTRU.

[0024] Figure 4 This is a diagram illustrating an example of message sequence LTM execution with reference to WTRU.

[0025] Figure 5 This is a sample HRI table.

[0026] Figure 6 This is a diagram illustrating an example of LTM execution in a WTRU cluster.

[0027] Figure 7A and 7B The diagram illustrates an example of message sequence LTM execution in a WTRU cluster. Detailed Implementation

[0028] Figure 1AThis is a schematic diagram illustrating an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multi-access system that provides content such as voice, data, video, messages, and broadcasts to multiple wireless users. The communication system 100 enables 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 Unique Word DFT Spread Spectrum OFDM (ZT UWDTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0029] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, Public Switched Telephone Network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 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 user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as WTRUs.

[0030] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), node B, eNode B, home node B, home eNode B, gNB, NR node B, site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are each depicted as a single element, it should be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0031] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in a desired spatial direction.

[0032] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116. Air interface 116 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0033] More specifically, as described above, the communication system 100 can be a multi-access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish air interfaces 115 / 116 / 117 using Wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​UL Packet Access (HSUPA).

[0034] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which may use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro) to establish air interface 116.

[0035] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can establish an air interface 116 using a new radio (NR).

[0036] In one embodiment, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can jointly implement LTE radio access and NR radio access, for example, using the dual connectivity (DC) principle. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can 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).

[0037] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0038] For example, Figure 1A Base station 114b can be a wireless router, home node B, home eNodeB, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drone use), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can be directly connected to the Internet 110. Therefore, base station 114b may not need to access the Internet 110 via CN 106 / 115.

[0039] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, and / or perform advanced security functions such as user authentication. Although in Figure 1AAlthough not shown, it should be understood that RAN104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which may utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0040] CN 106 / 115 can also serve as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT.

[0041] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capabilities (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). For example... Figure 1A The WTRU 102c shown can be configured to communicate with base station 114a, which may employ cellular-based radio technology, and to communicate with base station 114b, which may employ IEEE 802 radio technology.

[0042] Figure 1B This is a system diagram illustrating example WTRU 102. (Example:) Figure 1B As shown, among other things, WTRU 102 may include, in particular, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and / or other peripheral devices 138, etc. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0043] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple 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. Processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, which may be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0044] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmitting / receiving element 122 can be, for example, a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF and optical signals. It should be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0045] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmit / receive elements 122. More specifically, WTRU 102 may employ MIMO technology. Thus, in one embodiment, WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals on air interface 116.

[0046] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, for example, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.

[0047] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Furthermore, the processor 118 can access and store information from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a user identification module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access and store information from memory that is not physically located on WTRU 102 (e.g., a server or home computer (not shown)).

[0048] The processor 118 can receive power from the power supply 134 and can be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 can be any suitable device that powers the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0049] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information on the air interface 116 from base stations (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with the embodiments.

[0050] The processor 118 may be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or videos), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, attitude sensors, biosensors, and / or humidity sensors.

[0051] WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit 139 to reduce and / or substantially eliminate self-interference via hardware (e.g., a choke) or via signal processing by a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, WTRU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0052] Figure 1C This diagram illustrates a system diagram of RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.

[0053] RAN 104 may include eNode-Bs 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c on air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a.

[0054] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other on the X2 interface.

[0055] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing elements is described as part of CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0056] The MME 162 can connect to each of the eNode-Bs 162a, 162b, and 162c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for switching between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0057] The SGW 164 can connect to each of the eNode Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions such as anchoring the user plane during inter-eNode B handover, triggering paging when DL data is available to WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0058] SGW 164 can connect to PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks such as Internet 110, so as to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0059] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRU 102a, 102b, and 102c with access to a circuit-switched network such as PSTN 108, facilitating communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment. For example, CN 106 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRU 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0060] Despite WTRU in Figure 1A-1D While described as a wireless terminal, it is conceivable that, in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

[0061] In a representative embodiment, another network 112 may be a WLAN.

[0062] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or interface with a distributed system (DS) or another type of wired / wireless network that transmits traffic to and / or out of the BSS. Traffic originating outside the BSS destined for a STA can reach and be delivered to the STA via the AP. Traffic originating from a STA destined for an external BSS can be sent to the AP for delivery to the appropriate destination. For example, traffic between STAs within the BSS can be transmitted via the AP, where the source STA can send traffic to the AP, and the AP can deliver traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be transmitted between source and destination STAs (e.g., directly between them) using Direct Link Establishment (DLS). In some representative embodiments, the DLS can use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to here as an "ad-hoc" communication mode.

[0063] When using 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of a fixed width (e.g., a wide bandwidth of 20 MHz) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, each STA, including the AP, can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0064] High-throughput (HT) STAs can communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels.

[0065] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data passes through a segment resolver, which splits the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. These streams can be mapped onto two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0066] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carrier in 802.11af and 802.11ah are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV whitespace (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support metering-type control / machine-type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only) certain and / or limited bandwidths. MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0067] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include channels that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA among all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, for STAs that support (e.g., only support) the 1 MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports the 1 MHz operating mode) is transmitting to the AP, the entire available band can be considered busy, even if most of the available band remains idle and can be available.

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

[0069] Figure 1D This diagram illustrates a system diagram of RAN 113 and CN 115 according to one embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

[0070] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c on air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, for example, gNB 180a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0071] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable digitization. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can differ for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a variable number of OFDM symbols and / or a continuously variable absolute time).

[0072] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, while also communicating / connecting with another RAN such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, as well as one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can act as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0073] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing user plane data to User Plane Functions (UPF) 184a and 184b, and routing control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other on the Xn interface.

[0074] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0075] AMF 182a and 182b can connect to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, and so on. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the service types used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency Time (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, services for Machine Type Communication (MTC) access, and / or so on. AMF 162 can provide control plane functions for switching between RAN 113 and other RANs (not shown) that employ other radio technologies such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies such as WiFi.

[0076] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure the routing of services through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0077] UPF 184a and 184b can be connected to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N3 interface. This N3 interface provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices. UPF 184 and 184b can 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, and providing mobility anchors.

[0078] CN 115 can facilitate communication with other networks. For example, CN 115 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 115 and PSTN 108. Furthermore, CN 115 can provide WTRUs 102a, 102b, and 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 one embodiment, WTRUs 102a, 102b, and 102c may be connected to local data networks (DNs) 185a and 185b via the N3 interface to UPFs 184a and 184b and the N6 interface between UPFs 184a and 184b and DNs 185a and 185b.

[0079] Given Figure 1A-1D as well as Figure 1A-1D The corresponding descriptions herein indicate that one or more of the following functions can be performed by one or more emulation devices (not shown): WTRU 102a-d, base station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0080] Simulation devices can be designed to perform tests on one or more other devices in laboratory and / or carrier network environments. 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. Simulation devices can be directly coupled to another device for testing purposes and / or can perform tests using over-the-air wireless communication.

[0081] One or more simulation devices may perform one or more functions, including all functions, rather than being implemented / deployed as part of a wired and / or wireless communication network. For example, simulation devices may be used to test test scenarios in laboratory and / or non-deployment (e.g., testing) wired and / or wireless communication networks to implement the testing of one or more components. One or more simulation devices may be test devices. Simulation devices may transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0082] The WTRU can perform baseline procedures. For example, for each phase, the baseline procedure may include one or more of Long Term Evolution (LTE) preparation, early synchronization, Layer 1 (L1) / Layer 2 (L2) based inter-cell mobility (LTM) execution, and / or LTM completion. LTM preparation may include the WTRU sending a measurement report, for example, to a base station (e.g., a gNB). The measurement report can be used for LTM candidate preparation. For example, a base station can use the measurement report to prepare an LTM candidate.

[0083] The WTRU can be in an RRC_CONNECTED (RRC connected) state. One or more LTM candidates can be configured, for example, using RRC configuration. The WTRU can determine and / or acknowledge configuration completion. Early synchronization can include, for example, the completion of synchronization with one or more candidate cells in both the uplink and downlink directions. LTM execution can include the WTRU sending an L1 measurement report. The L1 measurement report can be used to make LTM decisions, for example, about which cell should be selected as the target. For example, the WTRU can determine which cell to select (e.g., as the target) based on the measurement report. A cell handover command (e.g., MAC CE) can be used to indicate the selected cell. For example, upon receiving a MAC CE, the WTRU can detach from the source cell and / or apply one or more target configurations. LTM completion can include the WTRU indicating, for example, the successful completion of an LTM cell handover to the selected target cell.

[0084] The solution presented in this paper can be applied to the LTM execution phase, such as during the LTM decision-making step. However, aspects of the solution can be extrapolated to higher-level mobility procedures. These aspects will likely be highlighted in the solutions section.

[0085] LTM decisions may not consider WTRU service-specific information and / or may not utilize information from previous executions (e.g., switching from other WTRUs or reference WTRUs). For example, LTM may operate at a lower level (e.g., triggered by a DU). Higher-level information (e.g., service-specific information) may not be readily accessible and / or available. Alternatively or additionally, LTM may not have access to information from a database tracking past executions. Some (e.g., a degree of) visibility and / or access to lower levels may exist to utilize information from higher levels. Additionally or alternatively, using data-driven approaches and / or employing artificial intelligence (AI) for optimization can facilitate access to information from past experience.

[0086] The systems and methods described herein can utilize premises and / or methods for fully leveraging rating information, such as for customizing LTM decisions with one or more service-specific preferences. The systems and methods can, for example, enhance baseline LTM decisions by utilizing rating information from previous executions and / or by utilizing service-specific information during the LTM execution phase. Additionally or alternatively, the systems and methods can implement service-specific switching (one or more) for WTRUs and / or service-specific load balancing for the network (e.g., thus improving service quality).

[0087] A Wireless Transmit / Receive Unit (WTRU) can receive configuration. This configuration can be associated with candidate cells. The WTRU can, for example, send a request to a network (e.g., a base station). This request can be rating information for the candidate cells. The request can include service description information. The WTRU can, for example, receive a response from the network. This response can include rating information for the candidate cells. The WTRU can, for example, send an indication to the network. This indication can include the selected candidate cells.

[0088] The request (e.g., a request to the network) may include one or more of a first identifier of the service associated with the WTRU, a second identifier of the service associated with the handover rating information (HRI), and / or a third identifier of the predicted service. The request (e.g., a request to the network) may include a list of one or more candidate cells and / or an indication of the handover rating information (HRI). The indication of the HRI may be associated with one or more candidate cells.

[0089] The WTRU can, for example, send measurement reports to the base station. The measurement report can be a Layer 1 (L1) measurement report. The WTRU can receive Media Access Control (MAC) control elements (CEs). The MAC CE can include an indication to hand over to the base station. The WTRU can, for example, perform a Random Channel Access (RACH) procedure on the base station.

[0090] The WTRU can receive requests for rating information. These requests can be for candidate cells. The WTRU can, for example, send measurement reports to the base station. These measurement reports can include rating information.

[0091] The WTRU can indicate the selected target cell and / or information related to that selection, such as rating information and / or service-specific information. The WTRU can complete the LTM preparation and / or early synchronization phases. For example, the WTRU can receive one or more candidate configurations from (e.g., all) candidate cells from the source and / or current base station (e.g., gNB) and / or establish downlink (DL) and uplink (UL) synchronization with (e.g., all) candidate cells. The WTRU can send a request for, for example, rating information for the candidate cells. Service description information can be included in this request.

[0092] The WTRU can receive responses. These responses may include, for example, rating information from the network used for candidate cells. The WTRU can, for example, indicate to the network the selected candidate cell and / or relevant information used for selecting the candidate cell. The WTRU can send an L1 measurement report to the gNB. The WTRU can receive a MAC CE. The MAC CE may indicate that a handover to the target gNB should be performed. The WTRU can perform a RACH on the target gNB. The WTRU can, for example, receive requests for rating information and / or rating-related information from the target gNB. The WTRU can send a measurement report containing rating information and / or rating-related information. The rating information and / or rating-related information may include, for example, service description information for the target base station (e.g., the gNB).

[0093] (For example, firstly) the WTRU can receive configuration. This configuration can be associated with a candidate cell. (For example, firstly) the WTRU can send a request. This request can be rating information for a candidate cell. The request can include service description information. The WTRU can receive multicast messages. The multicast messages can include rating information for the candidate cell and / or instructions for anchor WTRUs.

[0094] Multicast messages may include indications that one or more other (e.g., second) WTRUs are included in the cluster. For example, when the first WTRU is an anchor WTRU, the (e.g., first) WTRU may send sidelink messages to one or more of the other (e.g., second) WTRUs. The sidelink messages may include indications of a selected target cell. The (e.g., first) WTRU may, for example, receive a sidelink message reply from one or more of the other (e.g., second) WTRUs. This sidelink message reply may include the selected target cell. The (e.g., first) WTRU may send an indication to the network. The indication to the network may include the selected target cell.

[0095] For example, when the (e.g., first) WTRU is not the anchor WTRU, the (e.g., first) WTRU can receive sidelink messages from the anchor WTRU. The sidelink messages may include an indication of the selected target cell. The (e.g., first) WTRU may, for example, send a sidelink message reply to the anchor WTRU. This sidelink message reply may include the selected target cell.

[0096] (For example, firstly) the WTRU may send a measurement report to the base station. This measurement report may be a Layer 1 (L1) measurement report. (For example, firstly) the WTRU may receive a Media Access Control (MAC) control element (CE). The MAC CE may include an indication to hand over to the base station. (For example, firstly) the WTRU may execute a RACH procedure on the base station.

[0097] WTRUs can coordinate WTRU clusters. Additionally or alternatively, WTRUs can report one or more selections of target cells and / or information related to those selections, such as rating information for all WTRUs and / or service-specific information. WTRUs can perform LTM preparation and / or early synchronization phases. For example, a WTRU can receive one or more candidate configurations from (e.g., all) candidate cells from a source and / or current base station (e.g., gNB) and / or establish DL and UL synchronization with those (e.g., all) candidate cells.

[0098] A WTRU can send a request for rating information for a candidate cell. This request may include service description information. A WTRU can receive messages, such as multicast messages. These multicast messages may include rating information for the candidate cell, instructions regarding the anchor WTRU, and / or one or more of the remaining WTRUs that are part of the cluster.

[0099] An anchor WTRU can send sidelink messages to WTRUs (e.g., all WTRUs in the cluster). Sidelink messages can indicate a selected target cell and / or information related to that selection. An anchor WTRU can receive one or more sidelink message replies from one or more (e.g., all) WTRUs in the cluster. One or more sidelink messages can include the selected target cell and / or information related to that selection. An anchor WTRU can, for example, indicate to the network a selected candidate cell and / or information related to selecting a candidate cell from (e.g., all) WTRUs in the cluster (e.g., including anchor WTRU selection).

[0100] Non-anchor WTRUs can receive sidelink messages, for example, from anchor WTRUs. Sidelink messages may include the selected target cell and / or information related to that selection. Non-anchor WTRUs can also send sidelink messages. Sidelink messages may include the selected target and / or information related to that selection.

[0101] The WTRU can send L1 measurement reports to the gNB. The WTRU can receive MAC CEs, for example, to indicate that a handover to the target gNB should be performed. For example, the WTRU can perform a RACH on the target base station (e.g., the gNB) before the handover.

[0102] Handover (HO) / cell transition can include, for example, transferring an ongoing connection of a WTRU from one cell (e.g., belonging to a source gNB) to another cell (e.g., belonging to a target gNB) while in a connected state. LTM can be referred to as (Layer 1 / Layer 2) L1 / L2 lower-layer triggered mobility (LTM). The LTM procedure allows a pre-configured RRC reconfiguration to be executed upon triggering via L1 / L2 signaling.

[0103] Higher-layer mobility may include baseline handover procedures and / or conditional handover (CHO) in 3GPP, where serving cell changes may be triggered by Layer 3 (L3) measurements and / or performed by RRC. Service descriptors (SDs) provide a description of a service that can be started / stopped / restarted on the WTRU. For example, an SD may be similar to, a function of, and / or equivalent to a QoS flow ID in 3GPP.

[0104] Handover rating information (HRI) can include a value indicating how well a particular cell is suited for performing a service-based handover (e.g., how well the cell is suited to meet the requirements expressed by a service descriptor). This value can be determined and / or provided by the network (e.g., to the WTRU). The value can be numerical. The numerical value can include a range, such as between 0 and 5. A higher rating (e.g., 5) can indicate a cell that is more well-suited for handover.

[0105] Alternatively or concurrently, this value can be calculated using WTRU-based information and / or enable service load balancing. The HRI table may include a database, for example, located on the network side. The HRI table may include entries comprising one or more of the following: cell ID, service descriptor(s), and / or one or more HRI ratings. A cluster of WTRUs may include WTRUs that have established sidelink communication and / or follow similar mobility patterns (e.g., drone fleets and / or vehicle groups). WTRUs in a cluster may report one or more HRI values, for example, after a handover is completed. WTRUs may report one or more HRI values ​​to one or more other WTRUs in the cluster. One or more HRI values ​​may include multiple HRI values. For example, each of the HRI values ​​may be associated with one or more service descriptors.

[0106] The WTRU can indicate the selected target cell and / or relevant information for that selection, such as rating information and / or service-specific information. The WTRU can complete the LTM preparation and / or early synchronization phases, which can, for example, lead to the reception of configurations for one or more candidate cells from the source / current base station (e.g., gNB) and / or the establishment of downlink (DL) and uplink (UL) synchronization with (e.g., all) candidate cells.

[0107] The WTRU can send a request for rating information for, for example, one or more candidate cells. This request may include service description information. The WTRU can receive a response with rating information, for example, from a network used for candidate cells. The WTRU can (e.g., to the network) indicate the selected candidate cells and / or information related to the selection of candidate cells. The WTRU can, for example, send an L1 measurement report to a base station (e.g., a gNB).

[0108] The WTRU can receive a MAC CE. The MAC CE can indicate that a handover to the target base station (e.g., gNB) should be performed. The WTRU can, for example, perform a RACH on the target base station (e.g., gNB). The WTRU can, for example, receive requests for rating information and / or rating-related information from the target base station (e.g., gNB). The WTRU can, for example, send a measurement report to the base station (e.g., gNB). The measurement report may include one or more of the rating information and / or rating-related information. The rating information may include service description information.

[0109] The WTRU can report information for handover (HO) to the network, for example, based on rating information and / or service-specific descriptors. The WTRU can be configured to send requests for information (e.g., from the network) about one or more candidate cells. For example, the WTRU can request HRI information for one or more cells. This request may contain information relating to one or more of the following: a list of candidate cells for which HRI information is required; one or more identifiers of services currently running on the WTRU; one or more identifiers of services the WTRU can run after performing an HO; and / or one or more predictions of services (e.g., all) that the WTRU can run after performing an HO. The one or more identifiers of services currently running on the WTRU may be related to HRI ratings (e.g., related to HRI ratings). The one or more identifiers of services the WTRU can run after performing an HO may be related to HRI ratings (e.g., related to HRI ratings).

[0110] For example, during the LTM preparation phase, the WTRU can be configured for target RRC reconfiguration. Alternatively, the WTRU can be configured to perform downlink and uplink synchronization, for example, before receiving a handover trigger.

[0111] The WTRU may receive a response to the request, for example, from the network. This response may include information related to one or more of the following: a rating value for a specific cell, rating values(s) from a subset of cells in the candidate cell list, rating values(s) from all cells in the candidate list, and / or a rating value (e.g., time prediction) based on artificial intelligence (AI) for the sub-case mentioned herein. A rating value for a specific cell may indicate the cell's suitability to be a target cell for the WTRU. Rating values(s) from a subset of cells in the candidate cell list may indicate the suitability of each cell in that subset to be a target cell for the WTRU. An HRI may be associated with and / or based on a service, such as (e.g., at the WTRU) a service that is in operation and / or (e.g., at the WTRU) a predicted service. For example, an HRI may be based on (e.g., sent by the WTRU) service description information. Rating values(s) from all cells in the candidate cell list may indicate the suitability of each cell in the subset to be a target cell for the WTRU. The rating values ​​predicted by AI (one or more) may include empirical and / or probabilistic models, which may be trained offline and / or made available for WTRU.

[0112] The WTRU can determine the target cell from a list of candidate cells, for example, based on the received rating(s) values(s). For example, the WTRU can use one or more parameters (e.g., WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, and / or WTRU-I5) to determine the selected target cell.

[0113] One or more parameters may include the number of active services at the WTRU. For example, WTRU-I1 may include the number of active services at the WTRU. Services may include services that the WTRU actively runs at the time when a decision needs to be made. One or more parameters may include the number of services that the WTRU intends to run after a HO (House of Interest) is performed. For example, WTRU-I2 may include the number of services that the WTRU intends to run after a HO is performed. Services may be scheduled to run at the WTRU, but may not be reported to the network, for example. One or more parameters may include interference level and / or radio link-related measurements from candidate cells that are available to the WTRU (e.g., all), such as the time at which the decision is performed and / or predictions that the WTRU has made regarding the post-HO performance (e.g., time predictions). For example, WTRU-I3 may include interference level and / or radio link-related measurements from candidate cells that are available to the WTRU (e.g., all). One or more parameters may include (e.g., any) pre-configured mobility models and / or one or more mobility predictions. For example, WTRU-I4 may include any pre-configured mobility models and / or mobility predictions. One or more parameters may include any pre-configured information from the data radio bearer (DRB) at the WTRU, such as the time when the decision is made (e.g., it may not be fully available on the network side). For example, WTRU-I5 may include any pre-configured information from the data radio bearer (DRB) at the WTRU.

[0114] The WTRU can indicate a decision based on one or more parameters (e.g., minInfo) for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, and / or WTRU-I5. For example, the WTRU can indicate the decision to the network as a separate transmission or as part of an L1 measurement report. The indication of the decision may include cell indication, reporting information about the cell indication, and / or one or more accuracy metrics. The WTRU can select the indicated cell as a potential target cell (e.g., bestCell). The reporting information about the cell indication may be based on reporting criteria and / or may include the (e.g., primary) reasons for the decision to select a potential target cell. One or more accuracy metrics may include, for example, one or more confidence intervals, one or more error tolerances, and / or one or more accuracy coefficients related to bestCell and / or minInfo.

[0115] The WTRU can receive L1 cell switching commands (e.g., MAC CE) from the network. The L1 cell switching command can instruct the WTRU to switch to a target cell, such as bestCell and / or minInfo, which is available at the network. The WTRU can perform one or more of the following: separation from the source base station (e.g., gNB), application of target configuration(s), and / or execution of RACH procedures.

[0116] For example, after performing a HO (Hope of Interest), the WTRU can receive a request for HRI (Hyperritory Rating) from the selected target cell. This request may include a network request (e.g., to the WTRU) to report the rating of the performed HO. For example, the base station may send a request to the WTRU.

[0117] The request may contain information related to one or more of the following: information about the cell to which the WTRU was previously attached, timing information about when a response to the request will be generated (e.g., X time after HO execution, X time before triggering another LTM procedure, and / or so on), and / or one or more conditions for generating a response to the request (e.g., radio link quality is above a threshold to ensure a response is delivered when the WTRU has been idle for a certain amount of time and has no data to send, and / or so on).

[0118] Systems and methods for updating HRI ratings may exist. The WTRU may send a response to a received request for HRI to the network (e.g., as described herein), for example, to update the HRI table. This response may contain information related to one or more of the following: cell entries, service descriptors or subsets of service descriptors, any combination of descriptors described herein (e.g., WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5), and / or the actual rating value estimated by the WTRU.

[0119] Cell entries may include an indication of which cell the WTRU previously connected to (e.g., before performing a HO to deliver its rating value to the network). Service descriptors or subsets of service descriptors may include service descriptors or subsets of service descriptors that were active and associated with the HO to perform a HO to deliver their rating value to the network.

[0120] The WTRU can send reports. These reports can be generated as output, for example, from standardized measurements at the WTRU. The reports can be specified and / or configured by the network (e.g., similar to buffer status reports). The WTRU can use these reports to communicate the HRI rating value of the performed switch to the network.

[0121] The WTRU can receive requests from the network for reports relating to rating-based decisions (one or more) of service descriptors, and / or send one or more service descriptors to the network in response to such requests. The network can use the service descriptors (one or more) to calculate rating values ​​and / or update the HRI table.

[0122] WTRU can receive requests from the network for information (e.g., related information) reported with one or more parameters (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5). The network can use these parameters to calculate rating values ​​and / or update the HRI table.

[0123] WTRUs can report information requested from the network, such as HRI management based on rating information and service-specific descriptors during HO. Prior to LTM decision execution, WTRUs may receive requests from the network for service descriptors and / or any (e.g., related) information associated with one or more parameters (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, and / or WTRU-I5).

[0124] The WTRU may respond to the request by sending all or part of the information associated with one or more service descriptors in a single or multiple transmissions prior to the execution of the LTM decision, for example. Alternatively, the WTRU may respond to the request by sending information associated with one or more parameters (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, and / or WTRU-I5) to the network in a single or multiple transmissions prior to the execution of the LTM decision, for example.

[0125] The WTRU can be configured (e.g., triggered at L1 layer and / or higher) with conditions or triggers for a response (e.g., reporting). The WTRU can autonomously send a response (e.g., reporting), for example, after detecting a change and / or fulfilling a condition. The WTRU can send a response (e.g., reporting) that includes important (e.g., primary) information and / or factors (e.g., reasons) for the decision to select a particular target cell.

[0126] The WTRU can indicate (e.g., about) information and / or (one or more) WTRU service descriptors to the network, such as for baseline handover and / or conditional handover based on rating information and service-specific descriptors. The systems and methods described herein can be extrapolated and / or applied to baseline handover procedures as discussed herein. The WTRU can receive user data from the serving cell. The WTRU can (e.g., then) receive measurement control messages. These measurement control messages may include (one or more) measurement configuration parameters and / or (one or more) reporting conditions.

[0127] The network can configure the WTRU to request the HRI of the target cell, for example, in a measurement control message. The WTRU can include an HRI rating in its report. The WTRU can receive the HRI rating from the network. For example, after receiving the HRI rating from the network, the WTRU can send a response (e.g., a report) (e.g., once the reporting conditions are met). Alternatively, the WTRU can check existing reporting conditions.

[0128] The WTRU may, for example, send a measurement report to the network containing the information required for handover decisions. This measurement report may include indications of selected target cells as described herein and / or related information and / or one or more service descriptors.

[0129] A WTRU can perform a handover, for example, upon receiving a handover command. A WTRU can perform a handover by one or more of the following: separating from the source cell, synchronizing with the target cell, and / or initiating initial access.

[0130] The systems and methods described herein for updating HRI ratings can be applied to any and / or all solutions described herein. For example, when a WTRU instructs a network, for instance, on information and / or its service descriptors related to baseline switching and / or conditional switching based on rating information and / or service-specific descriptors, the methods described herein for updating HRI ratings can be applied.

[0131] WTRUs may use, for example, rating information and / or service-specific information of all WTRUs to coordinate WTRU clusters and / or report selections of one or more target cells and / or information regarding the selections of one or more cells.

[0132] The WTRU can complete the LTM preparation and / or early synchronization phases. The WTRU can (e.g., then) receive candidate configurations from one or more candidate cells from the source and / or current base station (e.g., gNB) and / or establish DL and UL synchronization with one or more candidate cells. The WTRU can send a request for rating information for the candidate cells. This request may include service description information. The WTRU can receive multicast messages, such as those including (e.g., rating information for all one or more) candidate cells and / or indications from anchor WTRUs and non-anchor (e.g., other) WTRUs as part of a cluster.

[0133] An anchor WTRU can send sidelink messages to (e.g., all) WTRUs. These sidelink messages can indicate the selected target cell and / or information related to that selection. An anchor WTRU can receive sidelink message replies from (e.g., all) WTRUs in the cluster, such as information about their selected target cells and / or information related to their selection. An anchor WTRU can indicate to the network one or more selected candidate cells and / or information related to the selection of candidate cells from (e.g., all) WTRUs in the cluster (e.g., including the anchor WTRU's selection).

[0134] A non-anchor WTRU can, for example, receive sidelink messages from an anchor WTRU. These sidelink messages may include an indication of the selected target cell and / or relevant information for the selection. A non-anchor WTRU can also send sidelink messages. These sidelink messages may include the selected target and / or relevant information for the selection.

[0135] The WTRU can send L1 measurement reports to a base station (e.g., gNB). The WTRU can receive MAC CEs. The MAC CEs can indicate that a handover to the target base station (e.g., gNB) should be performed. The WTRU can perform RACH on the target base station (e.g., gNB).

[0136] WTRUs can report information to the network, for example, about (e.g., all) WTRUs in the cluster that are performing HO based on rating information and service-specific descriptors. WTRUs (e.g., WTRUs in the cluster) can be configured by the network to send requests for information about candidate cells. WTRUs can determine, for example, which candidate cells to include in the request for information by determining which candidate cells are for which HRI information. A WTRU can request another WTRU to determine the information about candidate cells to include in the request for information (e.g., HRI rating information).

[0137] One or more requests from (e.g., all) WTRUs in the cluster may contain information related to one or more of the following: a list of candidate cells for which HRI rating information is required; identifiers (e.g., related to HRI rating) of (one or more) services (one or more) currently running on the WTRU; identifiers (e.g., related to HRI rating) of (one or more) services (one or more) that the WTRU may run after performing an HO; and / or predictions of (one or more) services (e.g., all) that the WTRU may run after performing an HO.

[0138] The WTRU may receive a response to the request, for example, from the network. This response may include a multicast message. Alternatively or additionally, the response may include information relating to one or more of the following: (e.g., a specific) cell rating, ratings of a subset of cells from a candidate cell list, ratings of (e.g., all) cells from the candidate cell list, ratings predicted (e.g., time predictions) for one or more of the sub-cases mentioned herein using a pre-trained AI algorithm, and / or the ID (e.g., an identifier) ​​of the anchor WTRU of the cluster.

[0139] A specific cell's rating value can indicate its suitability as a target cell for the WTRU. Rating values ​​from a subset of cells in the candidate cell list can indicate the suitability of cells in that subset as target cells for the WTRU. Rating values ​​from (e.g., all) cells in the candidate cell list can indicate the suitability of each cell in that subset as a target cell for the WTRU. One or more predicted rating values ​​can include one or more of pre-trained AI, empirical models, and / or probabilistic models, which may be available to the WTRU, for example, offline and / or before the LTM procedure has begun.

[0140] The WTRU can determine a target cell from a list of candidate cells based on received rating values. The WTRU can use one or more parameters (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, and / or WTRU-I5). The WTRU can be selected as the anchor WTRU. The anchor WTRU can use sidelink communication with (e.g., all) the WTRUs(one or more) to send a decision and / or service descriptor for the selected target cell and / or one or more parameters, such as those already used to make that decision (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5).

[0141] Alternatively, the WTRU may respond selectively from all WTRUs in the corresponding cluster, where each WTRU has already sent a message in the sidelink declaring its own decision regarding the selected target cell and / or service descriptor and / or one or more parameters based on which it made that decision (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5). For all WTRUs in the cluster (e.g., including the anchor WTRU), the anchor WTRU may indicate this to the network as a separate transmission or as part of an L1 measurement report. The decision indication may include cell indication, reporting information about the cell indication, and / or one or more accuracy metrics.

[0142] WTRU can select the indicated cell as a potential target cell (e.g., bestCell_forWTRU_inCluster (the best cell for WTRU in the cluster)). Reporting information about the cell indication can be based on reporting criteria and / or include the (e.g., primary) reasons for the selection of the target cell. One or more accuracy metrics may include, for example, one or more confidence intervals, one or more error tolerances, and / or one or more accuracy coefficients related to bestCell_forWTRU_inCluster and minInfo_forWTRU_inCluster.

[0143] A WTRU may not be selected as the anchor WTRU. A WTRU that is not selected as the anchor WTRU can, for example, receive a request from the anchor WTRU via a sidelink. The anchor WTRU can send a request that includes one or more of the following: information about the decision regarding the selected target cell, a service descriptor, and / or one or more parameters based on which the decision was made (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5). The WTRU can reply to the anchor WTRU using a sidelink message. This reply may include the WTRU decision regarding the selected target cell and / or a service descriptor and / or one or more parameters based on which the decision was made (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5).

[0144] WTRUs (e.g., anchored and / or non-anchored WTRUs) can receive L1 cell transition commands (e.g., MACCE) from the network, for example. WTRUs can receive L1 transition commands after performing LTM decisions (e.g., for this purpose, bestCell_forWTRU_inCluster and / or minInfo_forWTRU_inCluster for all WTRUs in the cluster are available at the network). WTRUs can perform decoupling from the source base station (e.g., gNB). WTRUs can apply one or more target configurations. WTRUs can perform RACH procedures.

[0145] The HRI table can be updated for the cluster. The anchor WTRU can receive requests for HRI from the selected target cell, for example, after performing a HO. The network can send a request to the anchor WTRU to report a rating for the performed HO. This request may include indications of one or more cells to which the WTRU was previously attached. Alternatively or additionally, the indication may include timing information for generating a response to the request (e.g., X time after performing the HO, and / or X time before triggering another LTM procedure, etc.) and / or one or more conditions for generating a response to the request. Conditions may include the anchor WTRU being idle for a predetermined amount of time and / or having no data to transmit. Alternatively or additionally, conditions may include radio link quality above a threshold, for example, to ensure that a response is delivered.

[0146] An anchor WTRU can, for example, send a response to the network in response to a received request for an HRI. The network can use this response to update the HRI table. The response may include cell entries, one or more service descriptors, and / or one or more subsets of service descriptors. The subset of service descriptors may include one or more service descriptors that were active and / or associated with each of the WTRUs before their rating values ​​were delivered to the network's HO. Alternatively or additionally, the response may include (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5) parameters and / or one or more of the (e.g., actual) rating values ​​estimated by each of the WTRUs. Cell entries may include information about which cell each of the WTRUs was previously (e.g., before their rating values ​​were delivered to the network's HO).

[0147] Anchor WTRUs can send reports. Anchor WTRUs can create reports as output, for example, from standardized measurements at the WTRU. These reports can be specified and / or configured by the network (e.g., similar to buffer status reports). For example, in a report, a WTRU can send an indication to the network of an HRI rating value for a switch performed on (e.g., all) WTRUs in the cluster.

[0148] An anchor WTRU can receive requests from the network for one or more service descriptors (e.g., one or more related service descriptors) used for rating-based decisions. The anchor WTRU can, for example, send one or more service descriptors (e.g., one or more related service descriptors) to the network in response to such requests. The network can use the service descriptors to compute rating values ​​and / or update the HRI table for all WTRUs in the cluster.

[0149] An anchor WTRU can receive requests from the network for one or more parameters of a report (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5). The network can use one or more parameters to calculate rating values ​​and / or update the HRI table for all WTRUs in the cluster.

[0150] The report may include cluster indications. The report may include indications of WTRUs within the cluster (e.g., identifiers), such as indications for HOs based on rating information and / or (one or more) service-specific descriptors. Alternatively or additionally, WTRUs from the cluster may receive multicast requests for service descriptors and / or (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5) one or more parameters. WTRUs from the cluster may receive multicast requests from the network, for example, prior to LTM decision execution. Alternatively or additionally, WTRUs from the cluster may designate anchor WTRUs for (e.g., all) WTRUs in the cluster.

[0151] An anchor WTRU may respond to a request, for example, by sending information relating to (e.g., some or all) the service descriptor and / or (e.g., for WTRU-I1, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5) one or more parameters. An anchor WTRU response may include auxiliary information sent to the network in one or more transmissions, for example, prior to the execution of LTM decisions for (e.g., all) WTRUs in the cluster.

[0152] Figure 2 This diagram illustrates an example LTM baseline procedure 200. WTRU 202 and base station 204 can perform LTM preparation 206. At 208, WTRU 202 can be in RRC_CONNECTED mode. At 210, WTRU 202 can, for example, send a measurement report to base station 204. At 212, the base station can, for example, perform LTM candidate preparation based on the measurement report. At 214, base station 204 can, for example, send an RRC reconfiguration message (e.g., LTM candidate configuration) to WTRU 202. At 216, for example, in response to the RRC reconfiguration message, WTRU 202 can send an RRC reconfiguration complete message to base station 204.

[0153] At 218, WTRU 202 and base station 204 can perform early synchronization. At 220, WTRU 202 and / or base station 204 can perform DL / UL synchronization with one or more candidate cells.

[0154] At 222, WTRU 202 and base station 204 can perform LTM execution. At 224, WTRU 202 can, for example, send an L1 measurement report to base station 204. At 226, base station 204 can make an LTM decision. At 228, base station 204 can send a cell handover command (e.g., MAC CE) to WTRU 202. At 230, WTRU 202 can be decoupled from the source and / or apply target configuration. At 232, WTRU 202 and / or base station 204 can execute RACH procedures.

[0155] At point 234, LTM completion may occur. At point 236, WTRU 202 and / or base station 204 may perform LTM completion.

[0156] Figure 3 This diagram illustrates the execution of LTM for example 300 with reference to a WTRU. The coverage of four cells with base stations is labeled 'X', 'Q', 'Y', and 'Z'. The reference user (e.g., WTRU) in this scenario could be WTRU-4 302. At time t=0, WTRU-4 is connected to base station (e.g., gNB) =X 304. Coverage area 306 of base station X 304 may exist. At time t=1, WTRU-4 302 can trigger an LTM procedure (e.g., HO-4) where base station (e.g., gNB) =Q 308 and base station (e.g., gNB) =Y 310 are available candidate cells and / or early synchronization for both uplink and downlink is established. Coverage area 312 of base station Q 308 and / or coverage area 314 of base station Y 310 may exist.

[0157] At time t < 0, WTRU-1 316 may have already executed an LTM procedure (e.g., HO-1) from base station (e.g., gNB) = X 304 to base station (e.g., gNB) = Q 308. Alternatively or additionally, WTRU-1 316 may provide one or more updates to the HRI table for the actual values ​​of cell entry Q / coverage area 312 (e.g., the selected target cell), cell entry Q / coverage area 312 service descriptor (e.g., S1), and / or rating. The service descriptor may be associated with one or more services (e.g., those currently in operation) on the WTRU.

[0158] The WTRU-2 318 can perform an LTM procedure (e.g., HO-2) from base station (e.g., gNB) = Z 320 to base station (e.g., gNB) = Q 308 at time t < 0. Alternatively, the WTRU-2 318 can provide updates to one or more of the HRI tables for the actual values ​​of the same cell entry Q / coverage area 312 (e.g., the selected target cell), the cell entry Q / coverage area 312 service descriptor (e.g., S1; S2), and / or rating.

[0159] WTRU-3 322 can execute the LTM procedure at time t < 0. Alternatively or additionally, WTRU-3 322 can provide updates to one or more of the HRI tables for the actual values ​​of cell entry Y / coverage area 314 (e.g., the selected target cell), cell entry Y / coverage area 314 service descriptor (e.g., S2), and / or rating. For example, before t = 0, the network may have already updated entries in the HRI tables from WTRU-1 316, WTRU-2 318, and / or WTRU-3 322.

[0160] Figure 4 This diagram illustrates an example of LTM execution 400 using a reference WTRU message sequence. At time t=1, WTRU-4402 (e.g., reference WTRU) can begin the LTM procedure, for example, as follows: Figure 2 The message sequence diagram is shown in the diagram. Network 404 (e.g., gNB) may (e.g., initially) include base station (e.g., gNB) = X. WTRU-4 402 may be configured by the network to send a request for HRI, for example, specifying a candidate cell (e.g., Q, Y) and / or its service descriptor (e.g., S2).

[0161] WTRU-4 402 can examine candidate cells (e.g., Q and Y). At 406, WTRU-4 402 can, for example, send a request for HRI to network 404. At 408, the network can send a response to WTRU-4 402, for example, a rating value for cell Q and service descriptor S2 (e.g., the value provided for cell Q may include values ​​from HO-1 and HO-2, and / or the value provided for cell Y may include a value from HO-3). WTRU-4 402 can receive a rating value R=1 for cell Q and service descriptor S2 and / or a rating value R=5 for cell Y and service descriptor S2.

[0162] WTRU-4 402 can select cell Y, for example, based on a rating value associated with service descriptor S2. At 410, WTRU-4 402 and / or network 404 can indicate the optimal cell (e.g., Y) and / or an indication of why that cell is the optimal cell (e.g., mininfo) (e.g., based on one or more S2 descriptors). Cell selection can be performed / completed on the network. The network can treat the decision proposed by WTRU-4 as input and / or consider it at the LTM decision. A MAC CE can be sent to base station (e.g., gNB) = Y for cell handover. WTRU-4 can use access to base station (e.g., gNB) = Y to provide updates to the HRI table based on H0-4, for example, after a period of time (e.g., a scheduled time).

[0163] At 412, WTRU-4 402 can send L1 measurement reports to network 404. At 414, network 404 can send L1 cell switching commands (e.g., MAC CE) to WTRU-4 402. WTRU-4 402 can be decoupled from the source and / or have target configuration applied. At 416, WTRU-4 402 and / or network 404 can execute RACH procedures.

[0164] Figure 5 This is example HRI table 500. At 502, cells are provided, such as cell Q and cell Y. At 504, service descriptors are provided. One or more service descriptors may correspond to (e.g., each) a cell. For example, service descriptors S1, S2, ..., Sn may correspond to cell Q. At 506, HRI ratings are provided. One or more HRI ratings may correspond to (e.g., each) a cell and / or (e.g., each) a service descriptor. For example, an HRI (e.g., R1) may correspond to a service descriptor (e.g., S1 for cell Q).

[0165] Figure 6This diagram illustrates an example of LTM execution 600 for a WTRU cluster. It shows coverage of four cells with base stations (e.g., gNBs) labeled 'X', 'Q', 'Y', and 'Z'. The reference user cluster 602 in this scenario may include WTRU-4-1, WTRU-4-2, WTRU-4-3, WTRU-4-4, and / or WTRU-4-5. At time t=0, all WTRUs in cluster 602 may have established one or more sidelink communications and / or all WTRUs may be connected to base station (e.g., gNB) = X 604. At time t=1, a WTRU from cluster 602 may trigger an LTM procedure and / or send one or more HRI requests, where base station (e.g., gNB) = Q 608 and / or base station (e.g., gNB) = Y 610 is a candidate cell and / or early synchronization for both uplink and downlink has been established.

[0166] At time t < 0, WTRU-1 616 may execute an LTM procedure (e.g., HO-1) from base station (e.g., gNB) = X 604 to base station (e.g., gNB) = Q 608. Alternatively, WTRU-1 616 may provide updates to one or more of the HRI tables for the actual values ​​of cell entry Q / coverage area 612 (e.g., the selected target cell), cell entry Q / coverage area service descriptor (e.g., S1), and / or rating. WTRU-2 618 may have already executed an LTM procedure (e.g., HO-2) from base station (e.g., gNB) = Z 620 to base station (e.g., gNB) = Q 608 at time t < 0. Alternatively, WTRU-2 618 may provide updates to one or more of the HRI tables for the actual values ​​of the same cell entry Q / coverage area 612 (e.g., the selected target cell), cell entry Q / coverage area service descriptor (e.g., S1; S2; S3), and / or rating.

[0167] The WTRU-3 622 can execute the LTM procedure at time t < 0. Alternatively or additionally, the WTRU-3 622 can provide updates to one or more of the HRI tables for the actual values ​​of cell entry Y / coverage area 614 (e.g., the selected target cell), cell entry Y / coverage area service descriptor (e.g., S1; S3), and / or rating. Prior to t = 0, the network may have already updated entries in the HRI tables from the WTRU-1 616, WTRU-2 618, and / or WTRU-3 622.

[0168] Figure 7A and 7BThe diagram illustrates an example of message sequence LTM execution 700 for a WTRU 702 cluster. At time t=1, the WTRU 702 in the cluster can begin the LTM procedure, for example as follows: Figure 6 The message sequence diagram is shown in the diagram. (e.g., all) WTRU 702s in the cluster may have been configured by network 704 to send requests for HRIs, such as specifying candidate cells (e.g., Q, Y) and associated service descriptors (e.g., S1 for all WTRU 702s except S3 for WTRU-4-4). The network may send back rating values ​​for cells Q and Y, and for service descriptors S1 and S3 (e.g., the values ​​provided for cell Q may include values ​​from HO-1 and HO-2, and / or the values ​​provided for cell Y may include a value from HO-3).

[0169] For Q and / or S1, the rating value can be R=10, while for Q and S2, the rating value can be R=2. For Y and / or S1, the rating value can be R=2, and for Y and / or S3, the rating value can be R=10. The response from the network can be a multicast HRI message. The multicast HRI message can contain, for example, an anchor WTRU (e.g., WTRU-4-5) and / or (one or more) rating values ​​from the cluster, as specified by network 704. The anchor WTRU can indicate the decision for the selected cell (e.g., Q) and / or the reason why this cell was selected (e.g., S1).

[0170] An anchor WTRU can receive one or more responses from (e.g., all) WTRUs in the cluster regarding its decisions. WTRUs (e.g., all WTRUs) can make the same decisions as the anchor, except that, for example, WTRU-4-4 might have already chosen cell Y based on a rating value associated with its own service descriptor (e.g., S3). The anchor WTRU can (e.g., then) send messages about that decision and / or the reasons why this decision was made for (e.g., all) WTRUs in the cluster.

Claims

1. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: Receive configurations associated with multiple candidate cells; Send a request to the network for handover rating information (HRI) for the plurality of candidate cells, the request including service description information associated with the service running at the WTRU; A response is received from the network, the response including an HRI for the plurality of candidate cells, wherein the HRI includes an indication of how suitable each of the plurality of candidate cells is to become a target cell of the WTRU, and wherein the HRI is based on the service description information; Candidate cells are selected from the plurality of candidate cells based on the HRI; and Send an indication of a selected candidate cell to the network, wherein the indication includes selection information associated with the selection of the candidate cell.

2. The method according to claim 1, wherein, The HRI includes one or more of the following: an indication of the number of active services at the WTRU, an indication of the number of services the WTRU intends to operate after a handover (HO), or an indication of interference levels and / or radio link-related measurements associated with the plurality of candidate cells.

3. The method according to claim 1, wherein, The HRI is specific to the service running at the WTRU.

4. The method according to claim 1, wherein, The request for the network further includes one or more of the following: a first identifier of the service associated with the WTRU, a second identifier of the service associated with the HRI, or a third identifier of the predicted service.

5. The method of claim 1, further comprising: Receive a request for rating information for the selected candidate cells; Perform measurements on the selected candidate cells; as well as A measurement report is sent to the network, the measurement report including the measurement HRI associated with the selected candidate cell.

6. The method of claim 1, further comprising sending a sidelink message to one or more other WTRUs, wherein, The sidelink message includes an indication of the selected candidate cell.

7. The method according to claim 1, wherein, The configuration associated with multiple candidate cells includes the configuration associated with the selected candidate cell, and the method further includes: Receive the Media Access Control (MAC) control element (CE) associated with the selected candidate cell; Determine the configuration associated with the application and the selected candidate cells; and Perform a random access procedure on the selected candidate cell.

8. The method according to claim 1, wherein, The request for HRI includes a first request for HRI, and the method further includes: Receive a second request for HRI from the selected candidate cell, the second request for HRI including a request for information associated with the cell previously connected to the WTRU.

9. The method of claim 8, further comprising sending a response to a second request for an HRI to a selected candidate cell, the response including an HRI from one or more of the selected candidate cells or cells previously connected to the WTRU.

10. The method according to claim 1, wherein, The selection information associated with the selection of the candidate cell includes one or more of the following: a confidence interval associated with the selected candidate cell, an error tolerance associated with the selected candidate cell, or an accuracy coefficient associated with the selected candidate cell.

11. A wireless transmit / receive unit (WTRU) including a processor, the processor being configured to: Receive configurations associated with multiple candidate cells; Send a request to the network for handover rating information (HRI) for the plurality of candidate cells, the request including service description information associated with the service running at the WTRU; Receive a response from the network, the response including HRIs for the plurality of candidate cells, wherein... The HRI includes an indication of how suitable each of the plurality of candidate cells is to become the target cell of the WTRU, and wherein the HRI is based on the service description information; Candidate cells are selected from the plurality of candidate cells based on the HRI; and Send an indication of a selected candidate cell to the network, wherein the indication includes selection information associated with the selection of the candidate cell.

12. The WTRU according to claim 11, wherein, The HRI includes one or more of the following: an indication of the number of active services at the WTRU, an indication of the number of services the WTRU intends to operate after a handover (HO), or an indication of interference levels and / or radio link-related measurements associated with the plurality of candidate cells.

13. The WTRU according to claim 11, wherein, The HRI is specific to the service running at the WTRU.

14. The WTRU according to claim 11, wherein, The request for the network further includes one or more of the following: a first identifier of the service associated with the WTRU, a second identifier of the service associated with the HRI, or a third identifier of the predicted service.

15. The WTRU according to claim 11, wherein, The processor is further configured to: Receive a request for rating information for the selected candidate cells; Perform measurements on the selected candidate cells; and A measurement report is sent to the network, the measurement report including the measurement HRI associated with the selected candidate cell.

16. The WTRU of claim 11, wherein, The processor is further configured to send sidelink messages to one or more other WTRUs, wherein the sidelink messages include an indication of the selected candidate cell.

17. The WTRU of claim 11, wherein, The configuration associated with multiple candidate cells includes the configuration associated with the selected candidate cell, wherein the processor is further configured to: Receive the Media Access Control (MAC) control element (CE) associated with the selected candidate cell; Determine the configuration associated with the application and the selected candidate cells; and Perform a random access procedure on the selected candidate cell.

18. The WTRU according to claim 11, wherein, The request for HRI includes a first request for HRI, wherein the processor is further configured to: Receive a second request for HRI from the selected candidate cell, the second request for HRI including a request for information associated with the cell previously connected to the WTRU.

19. The WTRU according to claim 18, wherein, The processor is further configured to send a response to a second request for an HRI to a selected candidate cell, the response including an HRI from one or more of the selected candidate cells or cells previously connected to the WTRU.

20. The WTRU of claim 11, wherein, The selection information associated with the selection of the candidate cell includes one or more of the following: a confidence interval associated with the selected candidate cell, an error tolerance associated with the selected candidate cell, or an accuracy coefficient associated with the selected candidate cell.

Images