[go: up one dir, main page]

WO2025010343A1 - Procédés d'exploitation d'informations d'évaluation de recours au levier financier pour personnaliser une mobilité ltm avec des préférences spécifiques à un service - Google Patents

Procédés d'exploitation d'informations d'évaluation de recours au levier financier pour personnaliser une mobilité ltm avec des préférences spécifiques à un service Download PDF

Info

Publication number
WO2025010343A1
WO2025010343A1 PCT/US2024/036749 US2024036749W WO2025010343A1 WO 2025010343 A1 WO2025010343 A1 WO 2025010343A1 US 2024036749 W US2024036749 W US 2024036749W WO 2025010343 A1 WO2025010343 A1 WO 2025010343A1
Authority
WO
WIPO (PCT)
Prior art keywords
wtru
hri
cell
request
candidate cell
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2024/036749
Other languages
English (en)
Inventor
Ognen OGNENOSKI
Brian Martin
Filipe CONCEICAO
Alain Mourad
Milind Kulkarni
Benoit Pelletier
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2025010343A1 publication Critical patent/WO2025010343A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H04W36/008355—Determination of target cell based on user equipment [UE] properties, e.g. UE service capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring

Definitions

  • L1/L2 based inter-cell mobility may be mechanisms and procedures for L1/L2 based inter-cell mobility for reducing the latency as an overarching goal, for example when compared to conventional L3 or conditional handover.
  • L3 and conditional handover procedures may include delay, for example because of exchange of measurement reports and receipt of target configurations.
  • LTM may allow fast application of configurations for candidate cells and/or dynamic switching between a Secondary Cell (SCell) and a Primary Cell (PCell), for example without radio resource control (RRC) signalling.
  • SCell Secondary Cell
  • PCell Primary Cell
  • RRC radio resource control
  • RAN2 supported the baseline procedure for L1/2 Triggered Mobility (LTM).
  • the baseline procedure may include one or more of LTM preparation, early sync, LTM execution, and/or LTM completion.
  • An example of the baseline procedure is depicted in FIG.2.
  • a wireless transmit/receive unit may receive a configuration.
  • the configuration may be associated with a candidate cell.
  • the WTRU may send a request, for example to a network.
  • the request may be for rating information for the candidate cell.
  • the request may include service description information.
  • the WTRU may receive a response, for example from the network.
  • the response may include the rating information for the candidate cell.
  • the WTRU may send an indication, for example to the network.
  • the indication may include a selected candidate cell.
  • the request may include one or more of a first identifier for a service associated with the WTRU, a second identifier for a service associated with a handover rating information (HRI), and/or a third identifier associated with a predicted service.
  • the request may include a list of one or more candidate cells and/or an indication of a handover rating information (HRI).
  • the indication of an HRI may be associated with the one or more candidate cells.
  • the WTRU may send a measurement report, for example to a base station.
  • the measurement report may be a layer 1 (L1) measurement report.
  • the WTRU may receive a medium access control (MAC) control element (CE)
  • the MAC CE may include an indication of handover to a base station.
  • the WTRU may perform a random channel access (RACH) procedure, for example on the base station.
  • RACH random channel access
  • the WTRU may receive a request for rating information.
  • the request for rating information may be for the candidate cell.
  • the WTRU may send a measurement report, for example to a base station.
  • the measurement report may include the rating information.
  • a (e.g., first) WTRU may receive a configuration.
  • the configuration may be associated with a candidate cell.
  • the (e.g., first) WTRU may send a request.
  • the request may be for rating information for the candidate cell.
  • the request may include service description information.
  • the WTRU may receive a multicast message.
  • the multicast message may include the rating information for the candidate cell and/or an indication of another an anchor WTRU.
  • the multicast message may include an indication that one or more other (e.g , second) WTRUs are included in a cluster.
  • the (e.g., first) WTRU may send a sidelink message to one or more of the other (e.g., second) WTRUs, for example when the first WTRU is the anchor WTRU.
  • the sidelink message may include an indication of a selected target cell.
  • the (e.g., first) WTRU may receive a sidelink message reply, for example from one or more of the other (e.g., second) WTRUs.
  • the sidelink message reply may include the selected target cell.
  • the (e.g., first) WTRU may send an indication to a network.
  • the indication to the network may include the selected target cell.
  • the (e g., first) WTRU may receive a sidelink message from the anchor WTRU, for example when the (e.g., first) WTRU is not the anchor WTRU.
  • the sidelink message may include an indication of a selected target cell.
  • the (e.g., first) WTRU may send a sidelink message reply, for example to the anchor WTRU.
  • the sidelink message reply may include the selected target cell.
  • the (e.g., first) WTRU may send a measurement report, for example to a base station.
  • the measurement report may be a layer 1 (L1) measurement report.
  • the (e.g., first) WTRU may receive a medium access control (MAC) control element (CE).
  • the MAC CE may include an indication of handover to a base station
  • the (e.g., first) WTRU may perform a RACH procedure on the base station.
  • a WTRU may receive a configuration associated with a plurality of candidate cells.
  • the WTRU may send, for example to a network, a request for handover rating information (HRI) for the plurality of candidate cells.
  • the request may include service description information associated with services running at the WTRU.
  • the WTRU may receive a response from the network.
  • the response may include the HRI for the plurality of candidate cells.
  • the HRI may include an indication of how suitable each of the plurality of candidate cells is to become a target cell for the WTRU.
  • the HRI may be associated with and/or based on a service, for example a running service (e.g., at the WTRU) and/or a predicted service (e.g., at the WTRU).
  • the HRI may be based on service description information (e.g., sent by the WTRU).
  • the WTRU may select a candidate cell of the plurality of candidate cells based on the HRI.
  • the WTRU may send an indication of the selected candidate cell to the network.
  • the indication may include selection information associated with the selection of the candidate cell.
  • the selection information associated with the selection of the candidate cell may include one or more of a confidence interval associated with the selected candidate cell, an error margin associated with the selected candidate cell, and/or an accuracy coefficient associated with the selected candidate cell.
  • the HRI may include one or more of an indication of a number of active services at the WTRU, an indication of a number of services the WTRU intends to run after the execution of a handover (HO), or an indication of an interference level and/or radio link related measurements associated with the plurality of candidate cells.
  • the HRI may be specific to the services running at the WTRU.
  • the request to the network may include one or more of a first identifier for a service associated with the WTRU, a second identifier for a service associated with HRI, and/or a third identifier associated with a predicted service.
  • the WTRU may receive a request for rating information of the selected candidate cell.
  • the WTRU may perform measurements on the selected candidate cell.
  • the WTRU may send a measurement report to the network.
  • the measurement report may include measured HRI associated with the selected candidate cell.
  • the WTRU may send a sidelink message to one or more other WTRUs.
  • the sidelink message may include the indication of the selected candidate cell.
  • the configuration associated with a plurality of candidate cells may include a configuration associated with the selected candidate cell.
  • the WTRU may receive a medium access control (MAC) control element (CE) associated with the selected candidate cell.
  • the WTRU may determine to apply the configuration associated with the selected candidate cell.
  • the WTRU may perform a random access procedure with the selected candidate cell.
  • MAC medium access control
  • CE control element
  • the request for HRI may include a first request for HRI.
  • the WTRU may receive a second request for HRI from the selected candidate cell.
  • the second request for 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 HRI to the selected candidate cell.
  • the response may include the HRI for one or more of the selected candidate cell and/or the cell previously connected to the WTRU.
  • FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
  • WTRU wireless transmit/receive unit
  • FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
  • FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
  • FIG. 2 is a diagram illustrating an example LTM baseline procedure.
  • FIG. 3 is a diagram illustrating an example LTM execution of a reference WTRU.
  • FIG. 4 is a diagram illustrating an example of a message sequence LTM execution of a reference WTRU.
  • FIG. 5 is an example HRI table.
  • FIG. 6 is a diagram illustrating an example of LTM execution of a cluster of WTRUs.
  • FIGS. 7A and 7B illustrate example diagrams of a message sequence LTM execution of a cluster of WTRUs.
  • FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 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 uniqueword DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT UW DTS-s OFDM zero-tail uniqueword DFT-Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a ON 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a WTRU.
  • the communications systems 100 may also include a base station 114a and/or a base station 114b.
  • Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the GN 106/115, the Internet 110, and/or the other networks 112.
  • the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 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).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
  • a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., a eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the ON 106/115.
  • the RAN 104/113 may be in communication with the ON 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the ON 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • the RAN 104/113 and/or the ON 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT.
  • the CN 106/115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112.
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multimode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG 1B is a system diagram illustrating an example WTRU 102.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others.
  • GPS global positioning system
  • the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ Ml MO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g. , a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the 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.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • a gyroscope an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the 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 either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
  • the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1C 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 are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 110
  • the ON 106 may facilitate communications with other networks.
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
  • the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
  • the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA (e.g., only one station) may transmit at any given time in a given BSS.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac.
  • 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11 n,
  • 802.11 ac, 802.11 af, and 802.11 ah include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g , MTC type devices) that support (e.g., only support) a 1 MHz mode, 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 sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
  • STAs e.g , MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment
  • the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 113 may also be in communication with the CN 115.
  • the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode- Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the ON 115 shown in FIG. 1 D 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. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • MTC machine type communication
  • the AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating WTRU IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to one or more of: 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, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the 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 in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • a WTRU may perform a baseline procedure.
  • the baseline procedure may include one or more of long term evolution (LTE) preparation, early sync, layer 1 (L1) / layer 2 (L2) based inter-cell mobility (LTM) execution, and/or LTM completion, for example for each stage.
  • LTM preparation may include a WTRU sending a measurement report, for example to a base station (e.g., gNB).
  • the measurement report may be used for LTM candidate preparation.
  • the base station may use the measurement report for preparing LTM candidates.
  • the WTRU may be in an RRC_CONNECTED state.
  • One or more LTM candidates may be configured, for example using an RRC configuration.
  • the WTRU may determine and/or confirm that the configuration is completed. Early sync may include a synchronization being completed with one or more candidate cells, for example for both for the uplink and downlink directions.
  • LTM execution may include a WTRU sending an L1 measurement report.
  • the L1 measurement report may be used for making an LTM decision, for example regarding which cell should be selected as a target.
  • the WTRU may determine which cell to select (e.g., as a target) based on the measurement report.
  • the selected cell indication may be indicated using a cell switch command (e.g., MAC CE).
  • the WTRU may detach from the source cell and/or apply one or more target configurations, for example upon reception of the MAC CE.
  • LTM completion may include a WTRU indicating a successful completion of the LTM cell switch, for example to the selected target cell.
  • Solutions herein may be applicable to the LTM execution stage, for example during the LTM decision step. However, aspects of the solutions herein may be extrapolated for higher layer mobility procedures. These aspects may be highlighted in the solution sections.
  • LTM decisions may not consider WTRU service-specific information and/or may not leverage information from previous executions (e.g., handovers performed from other WTRUs or the reference WTRU).
  • LTM may operate at the lower layers (e.g., triggered by a DU).
  • Upper layer information e.g., service specific information
  • LTM may have no access to information from a database that keeps track of past executions. There may be some (e.g., a certain degree of) visibility and/or access for the lower layers to utilize information from the higher layers.
  • the utilization of data-driven approaches and/or adoption of artificial intelligence (Al) for optimization may facilitate access to information from past experiences.
  • Systems and methods as herein may utilize premises and/or methods for leveraging rating information, for example for customizing the LTM decision with a service-specific preference(s).
  • the systems and methods may enhance the baseline LTM decision, for example in the LTM execution stage with rating information from previous executions and/or with service-specific information. Additionally, or alternatively, the systems and methods may enable service-specific handover(s) for the WTRU and/or service-specific load balancing for the network (e.g., thus improving service quality).
  • a wireless transmit/receive unit may receive a configuration.
  • the configuration may be associated with a candidate cell.
  • the WTRU may send a request, for example to a network (e.g., base station).
  • the request may be for rating information for the candidate cell.
  • the request may include service description information.
  • the WTRU may receive a response, for example from the network.
  • the response may include the rating information for the candidate cell.
  • the WTRU may send an indication, for example to the network.
  • the indication may include a selected candidate cell.
  • the request may include one or more of a first identifier for a service associated with the WTRU, a second identifier for a service associated with a handover rating information (HRI), and/or a third identifier associated with a predicted service.
  • the request (e.g., to the network) may include a list of one or more candidate cells and/or an indication of a handover rating information (HRI).
  • the indication of an HRI may be associated with the one or more candidate cells.
  • the WTRU may send a measurement report, for example to a base station.
  • the measurement report may be a layer 1 (L1) measurement report.
  • the WTRU may receive a medium access control (MAC) control element (CE)
  • the MAC CE may include an indication of handover to a base station.
  • the WTRU may perform a random channel access (RACH) procedure, for example on the base station.
  • RACH random channel access
  • the WTRU may receive a request for rating information.
  • the request for rating information may be for the candidate cell.
  • the WTRU may send a measurement report, for example to a base station.
  • the measurement report may include the rating information.
  • a WTRU may indicate a selected target cell and/or relevant information for the selection, for example based on rating information and/or service specific information.
  • the WTRU may complete LTM preparation and/or early sync stage.
  • the WTRU may receive one or more candidate configurations and/or establish Downlink (DL) and Uplink (UL) synchronization with (e.g., all) candidate cells from the source and/or current base station (e.g., gNB).
  • the WTRU may send a request for rating information, for example for candidate cells. Service description information may be included in the request.
  • the WTRU may receive a response.
  • the response may include rating information, for example from the network for candidate cells.
  • the WTRU may indicate, for example to the network, a selected candidate cell and/or relevant information for the selection of the candidate cell.
  • the WTRU may send an L1 measurement report to the gNB.
  • the WTRU may receive a MAC CE.
  • the MAC CE may indicate that handover to a target gNB should be executed.
  • the WTRU may perform RACH on the target gNB.
  • the WTRU may receive a request for rating information and/or rating-related information, for example from the target gNB.
  • the WTRU may send a measurement report with the rating information and/or rating-related information.
  • the rating information and/or rating-related information may include service description information, for example to the target base station (e.g , gNB).
  • a (e.g., first) WTRU may receive a configuration.
  • the configuration may be associated with a candidate cell.
  • the (e.g., first) WTRU may send a request.
  • the request may be for rating information for the candidate cell.
  • the request may include service description information.
  • the WTRU may receive a multicast message.
  • the multicast message may include the rating information for the candidate cell and/or an indication of an anchor WTRU.
  • the multicast message may include an indication that one or more other (e.g., second) WTRUs are included in a cluster.
  • the (e.g., first) WTRU may send a sidelink message to one or more of the other (e.g., second) WTRUs, for example when the first WTRU is the anchor WTRU.
  • the sidelink message may include an indication of a selected target cell.
  • the (e.g., first) WTRU may receive a sidelink message reply, for example from one or more of the other (e.g., second) WTRUs.
  • the sidelink message reply may include the selected target cell.
  • the (e.g., first) WTRU may send an indication to a network.
  • the indication to the network may include the selected target cell.
  • the (e.g., first) WTRU may receive a sidelink message from the anchor WTRU, for example when the (e.g., first) WTRU is not the anchor WTRU.
  • the sidelink message may include an indication of a selected target cell.
  • the (e.g., first) WTRU may send a sidelink message reply, for example to the anchor WTRU.
  • the sidelink message reply may include the selected target cell.
  • the (e.g., first) WTRU may send a measurement report, for example to a base station.
  • the measurement report may be a layer 1 (L1) measurement report.
  • the (e.g., first) WTRU may receive a medium access control (MAC) control element (CE).
  • the MAC CE may include an indication of handover to a base station.
  • the (e.g., first) WTRU may perform a RACH procedure on the base station.
  • a WTRU may coordinate a cluster of WTRUs. Additionally, or alternatively, the WTRU may report one or more selections of target cells and/or relevant information for these selections, for example using rating information and/or service specific information for all WTRUs.
  • the WTRU may complete LTM preparation and/or early sync stage. For example, the WTRU may receive one or more candidate configurations and/or establish DL and UL synchronization with (e.g., all) candidate cells from the source and/or current base station (e.g., gNB).
  • the WTRU may send a request for rating information for candidate cells.
  • the request may include service description information.
  • the WTRU may receive a message, for example a multicast message.
  • the multicast message may include one or more of rating information for candidate cells, an indication about anchor WTRU, and/or remaining WTRUs that are part of the cluster.
  • An anchor WTRU may send a sidelink message to (e.g., all in the cluster) WTRUs.
  • the sidelink message may indicate the selected target cell and/or relevant information for the selection.
  • the anchor WTRU may receive one or more sidelink message replies from one or more (e.g., all) WTRUs in the cluster.
  • the one or more sidelink messages may include a selected target cell and/or relevant information for the selection.
  • the anchor WTRU may indicate, for example to the network, the selected candidate cells and/or relevant information for the selection of the candidate cells from (e.g., all) WTRUs in the cluster (e.g., including the anchor WTRUs selection).
  • a non-anchor WTRU may receive a sidelink message, for example from the anchor WTRU.
  • the sidelink message may include the selected target cell and/or relevant information for the selection.
  • the non-anchor WTRU may send a sidelink message.
  • the sidelink message may contain the selected target and/or relevant information for the selection.
  • a WTRU may send an L1 measurement report to the gNB.
  • the WTRU may receive a MAC CE, for example to indicate that handover to a target gNB should be executed.
  • the WTRU may perform RACH on the target base station (e.g, gNB), for example before handover.
  • a handover (HO) / cell switch may include 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), for example in a connected state.
  • LTM may refer to (layer 1 / layer 2) L1/L2 lower layer triggered mobility (LTM).
  • An LTM procedure may enable a preconfigured RRC reconfiguration to be performed upon receiving a trigger via L1/L2 signaling.
  • Higher layer mobility may include a baseline handover procedure and/or the conditional handover (CHO) in 3GPP, for example where a serving cell change may be triggered by layer 3 (L3) measurements and/or done by RRC.
  • Service Descriptors may provide a description of the services that may be started/stopped/restarted on a WTRU.
  • SDs may be similar to, a function of, and/or equal to QoS Flow ID in 3GPP.
  • Handover Rating Information may include a value that indicates how suitable a particular cell is for performing a service-based handover (e.g., how suitable is the cell to satisfy the requirements expressed with the service descriptors).
  • the value may be determined and/or provided (e.g., to the WTRU) by the network.
  • the value may be a numerical value.
  • the numerical value may include a range, for example between 0 and 5.
  • a higher rating (e.g., 5) may indicate a more suitable cell for handover.
  • An HRI Table may include a database, that for example may be located at the network side.
  • the HRI table may include entries including one or more of a cell ID, a service descriptor(s), and/or an HRI rating(s).
  • a cluster of WTRUs may include WTRUs that have established sidelink communication and/or follow a similar mobility pattern (e.g., fleet of drones, and/or group of vehicles, etc.).
  • a WTRU in the cluster of WTRUs may report one or more HRI values, for example after completing handover.
  • the WTRU may report the one or more HRI values to one or more other WTRUs in the cluster.
  • the 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.
  • a WTRU may indicate a selected target cell and/or relevant information for the selection, for example based on rating information and/or service specific information.
  • the WTRU may complete LTM preparation and/or an early sync stage which, for example may result in receiving one or more candidates’ configurations and/or establish Downlink (DL) and Uplink (UL) synchronization with (e.g., all) candidate cells from the source/current base station (e.g, gNB).
  • DL Downlink
  • UL Uplink
  • the WTRU may send a request for rating information, for example for one or more candidate cells.
  • the request may include service description information.
  • the WTRU may receive a response with rating information, for example from the network for candidate cells.
  • the WTRU may indicate (e.g., to the network) a selected candidate cell and/or relevant information for the selection of the candidate cell.
  • the WTRU may send an L1 measurement report, for example to the base station (e.g., gNB).
  • the WTRU may receive a MAC CE.
  • the MAC CE may indicate that handover to a target base station (e.g., gNB) should be executed.
  • the WTRU may perform RACH, for example on the target base station (e.g., gNB).
  • the WTRU may receive a request for rating information and/or rating-related information, for example from the target base station (e.g., gNB).
  • the WTRU may send a measurement report, for example to the base station (e.g., gNB).
  • the measurement report may include one or more of rating information and/or rating-related information. Rating information may include service description information
  • a WTRU may report information to the network for handover (HO), for example based on rating information and/or service specific descriptors.
  • the WTRU may be configured to send a request for information (e.g., from the network) for one or more candidate cells.
  • the WTRU may request HRI information for one or more cells.
  • the request may contain information related to one or more of a list of candidate cells for which HRI information is needed, one or more identifier for a service running on the WTRU, one or more identifier for a service which the WTRU may run after executing HO, and/or one or more predictions for (e.g., all) services the WTRU may run after executing HO.
  • the one or more identifiers for the service running on the WTRU may be related to (e.g., relevant for) the HRI rating.
  • the one or more identifiers for the services the WTRU may run after executing HO may be related to (e.g., relevant for) the HRI rating.
  • the WTRU may be configured with a target RRC reconfiguration, for example during the LTM preparation phase. Additionally, or alternatively, the WTRU may be configured to perform downlink and uplink synchronization, for example before a handover trigger is received.
  • the WTRU may receive a response to the request, for example from the network.
  • the response may include information related to one or more of a rating value for a particular cell, rating value(s) for a subset of cells from the candidate cell list, rating value(s) for all cells from the candidate list, and/or predicted rating values (e.g., time predictions) of the subcases mentioned herein using artificial intelligence (Al).
  • the rating value for a particular cell may indicate the suitability of the cell to be a target cell for the WTRU.
  • the rating value(s) for a subset of cells from the candidate cell list may indicate the suitability of each of the cells in the subset to become a target cell for the WTRU.
  • the HRI may be associated with and/or based on a service, for example a running service (e.g., at the WTRU) and/or a predicted service (e.g., at the WTRU).
  • a service for example a running service (e.g., at the WTRU) and/or a predicted service (e.g., at the WTRU).
  • the HRI may be based on service description information (e.g., sent by the WTRU).
  • the rating value(s) for all cells from the candidate cell list may indicate the suitability of each of the cells in the subset to become a target cell for the WTRU.
  • the predicted rating value(s) Al may include an empirical and/or probabilistic model, which for example may be trained offline and/or made available to the WTRU.
  • the WTRU may determine the target cell from the cells provided in the candidate cell list, for example based on the rating value(s) received.
  • the WTRU may use one or more parameters, (e.g., WTRU-11 , WTRU-I2, WTRU-I3, WTRU-I4, and/or WTRU-I5), for example to determine the selected the target cell.
  • the one or more parameters may include a number of active services at the WTRU.
  • WTRU-11 may include a number of active services at the WTRU.
  • the services may include services that the WTRU actively runs at the time instant when the decision needs to be performed.
  • the one or more parameters may include a number of services that the WTRU intends to run after the execution of the HO.
  • WTRU-I2 may include a number of services that the WTRU intends to run after the execution of the HO.
  • the services may be scheduled to run at the WTRU, but for example may not be reported to the network.
  • the one or more parameters may include interference level and/or radio link related measurements from (e.g., all) candidate cells that the WTRU has available, for example at the time when the decision is performed and/or predictions the WTRU has made for these (e.g., time predictions) relevant for after the HO execution.
  • WTRU-I3 may include interference level and/or radio link related measurements from (e.g., all) candidate cells that the WTRU has available.
  • the one or more parameters may include a (e.g., any) preconfigured mobility model and/or prediction(s) of the mobility.
  • WTRU-I4 may include any preconfigured mobility model and/or predictions of the mobility.
  • the one or more parameters may include information from any pre-configuration of data radio bearers (DRBs) at the WTRU, for example at the time when the decision is performed (e.g., which may not be fully available at the network side).
  • WTRU-I5 may include information from any pre-configuration of data radio bearers (DRBs) at the WTRU.
  • the WTRU may indicate a decision based on the one or more of the parameters (e.g., minlnfo), (e.g., for WTRU-11, WTRU-I2, WTRU-I3, WTRU-I4, and/or WTRU-I5).
  • the WTRU may indicate a decision to the network as a separate transmission or as part of the L1 measurement report.
  • the indication of the decision may include one or more of indication of a cell, reporting information regarding the cell indication, and/or precision metric(s).
  • the WTRU may select the indicated cell as a potential target cell (e.g., bestCell).
  • Reporting information regarding the cell indication may be based on reporting criteria and/or may include a (e.g., main) reason for the decision of selecting a potential target cell.
  • Precision metric(s) may include one or more of confidence interval(s), error margin(s), and/or accuracy coefficient(s), for example related to the bestCell and/or minlnfo.
  • the WTRU may receive an L1 Cell switch command (e.g., MAC CE) from the network.
  • the L1 cell switch command may indicate to the WTRU to switch to the target cell, for example a cell for which bestCell and/or minlnfo is available at the network.
  • the WTRU may perform one or more of detaching from the source base station (e.g., gNB), applying the target configuration(s), and/or executing the RACH procedure.
  • the WTRU may receive a request for HRI from the selected target cell, for example after the execution of the HO.
  • the request may include a network request (e.g. , to the WTRU) to report a rating for the executed HO.
  • a base station may send the request to the WTRU.
  • the request may contain information related to one or more of the information about the cell to which the WTRU was attached previously, time information for when to generate the reply to the request (e.g., X time after the execution of the HO, X time before triggering another LTM procedure, and/or etc.), and/or condition(s) for generating the reply to the request (e.g., when the WTRU is idle for certain amount of time and has no data to send, radio link quality above threshold to make sure the reply is delivered, and/or etc.).
  • time information for when to generate the reply to the request e.g., X time after the execution of the HO, X time before triggering another LTM procedure, and/or etc.
  • condition(s) for generating the reply to the request e.g., when the WTRU is idle for certain amount of time and has no data to send, radio link quality above threshold to make sure the reply is delivered, and/or etc.
  • the WTRU may send a response to the received request for HRI (e.g., as described herein) to the network, for example to update the HRI table.
  • the response may contain information related to one or more of cell entry, service descriptors or a subset of service descriptors, any combination of descriptors described herein (e.g., WTRU-11 , WTRU-I2, WTRU-I3, WTRU-I4, WTRU- I5), and or an actual rating value as estimated by the WTRU.
  • Cell entry may include an indication of which cell the WTRU was previously connected to (e.g., prior to executing the HO for which the rating value is delivered to the network).
  • the service descriptors or the subset of service descriptors may include service descriptors or a subset of service descriptors that were active and relevant prior to executing the HO for which the rating value is delivered to the network.
  • the WTRU may send a report.
  • the report may be generated as an output, for example from a standardized measurement procedure at the WTRU.
  • the report may be specified and/or configured by the network (e.g., similar to a buffer status report).
  • the WTRU may convey the HRI rating value of the executed handover to the network using the report.
  • the WTRU may receive a request from the network to report the service descriptor(s) relevant for a ratingbased decision, and/or send the service descriptor(s) to the network as a reply to the request.
  • the service descriptor(s) may be used by the network to calculate the rating value and/or to update the HRI table.
  • the WTRU may receive a request from the network to report (e.g., relevant) information associated with the one or more of the parameters, (e.g., for WTRU-11 , WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5). These one or more parameters may be used by the network to calculate the rating value and/or to update the HRI table.
  • the WTRU may report requested information from the network, for example for HRI management during HO based on rating information and service specific descriptors.
  • the WTRU may receive a request for service descriptors and/or any (e.g., relevant) information associated with the one or more parameters (e.g., for WTRU-11 , WTRU-I2, WTRU-I3, WTRU-I4, and/or WTRU-I5) from the network prior to the LTM decision execution.
  • the WTRU may respond to the request by sending all or part of the information related to the service descriptor(s), for example in a single transmission or in multiple transmissions prior to the LTM decision execution. Additionally, or alternatively, the WTRU may respond to the request by sending information associated with the one or more parameters (e.g , for WTRU-11, WTRU-I2, WTRU-I3, WTRU-I4, and/or WTRU-I5) to the network, for example in a single transmission or in multiple transmissions prior to the LTM decision execution.
  • the one or more parameters e.g , for WTRU-11, WTRU-I2, WTRU-I3, WTRU-I4, and/or WTRU-I5
  • the WTRU may be configured with conditions or triggers for the response (e.g., reporting) (e.g , on L1 layer and/or higher layer triggers).
  • the WTRU may send the response (e.g., reporting) autonomously, for example after detecting a change and/or meeting a condition.
  • the WTRU may send the response (e.g., report) including important (e.g., the main) information and/or factor (e.g., reason) for the decision to select a particular target cell.
  • the WTRU may indicate (e.g., relevant) information and/or WTRU service descriptor(s) to the network, for example for baseline handover and/or conditional handover based on rating information and service specific descriptors.
  • the systems and methods described herein may be extrapolated and/or applied to the baseline handover procedure as discussed herein.
  • the WTRU may receive user data from a service cell.
  • the WTRU may (e.g., then) recieve a measurement control message.
  • the measurement control message may include a measurement configuration parameter(s) and/or reporting condition(s).
  • the network may configure the WTRU to request HRI for the target cells, for example in the measurement control message.
  • the WTRU may include the HRI rating in a report.
  • the WTRU may receive the HRI rating from the network.
  • the WTRU may send the response (e.g., report) (e.g., once reporting conditions are met), for example after receiving the HRI rating from the network. Additionally, or alternatively, the WTRU may check the existing reporting conditions.
  • the WTRU may send the measurement report with the content needed for the handover decision, for example to the network.
  • the measurement report may contain indication(s) for selected target cell and/or relevant information and/or service descriptor(s) as described herein.
  • the WTRU may execute the handover, for example after receiving the handover command.
  • the WTRU may execute the handover by one or more detaching from the source cell, synchronizing with the target cell, and/or initiating initial access.
  • Systems and methods for updating the HRI rating as described herein may be applied for any and/or all the solutions herein.
  • the methods for updating the HRI rating as described herein may be applied when the WTRU indicates relevant information and/or its service descriptors to the network, for example for baseline handover and/or conditional handover based on rating information and/or service specific descriptors.
  • a WTRU may coordinate a cluster of WTRUs and/or report selection(s) of target cell(s) and/or (e.g., relevant) information for the selection(s), for example using rating information and/or service specific information for (e.g., all) WTRUs.
  • the WTRU may complete LTM preparation and/or early sync stage.
  • the WTRU may (e.g., then) receive candidate(s) configuration (s) and/or establish DL and UL synchronization with candidate cell(s) from the source and/or current base station (e.g., gNB).
  • the WTRU may send a request for rating information for candidate cells.
  • the request may include service description information.
  • the WTRU may receive a multicast message, for example including rating information for (e.g., all) candidate cell(s) and/or an indication of an anchor WTRU and non-anchor (e.g., other) WTRUs that are part of the cluster.
  • An anchor WTRU may send a sidelink message to (e.g., all) WTRUs.
  • the sidelink message may indicate the selected target cell and/or relevant information for the selection.
  • the anchor WTRU may receive sidelink message replies from (e.g., all) WTRUs in the cluster, for example regarding their selected target cell and/or relevant information for their selection.
  • the anchor WTRU may indicate to the network the selected candidate cell(s) and/or relevant information for the selection of the candidate cells from (e g., all) WTRUs in the cluster (e.g., including the anchor WTRU selection.)
  • a non-anchor WTRU may receive a sidelink message, for example from the anchor WTRU.
  • the sidelink message may include an indication of the selected target cell and/or relevant information for the selection.
  • the non- anchor WTRU may send a sidelink message.
  • the sidelink message may include the selected target and/or relevant information for the selection.
  • the WTRU may send an L1 measurement report to the base station (e.g., gNB).
  • the WTRU may receive a MAC CE.
  • the MAC CE may indicate that handover to a target base station (e.g., gNB) should be executed.
  • the WTRU may perform RACH on the target base station (e.g., gNB)
  • a WTRU may report information to the network, for example for (e.g., all) WTRUs in the cluster that are performing HO based on rating information and service specific descriptors.
  • the WTRU e.g., a WTRU in a cluster
  • the WTRU may be configured by the network to send a request for information for candidate cells.
  • the WTRU may determine which candidate cells to include in the request for information, for example by determining for which candidate cells to request HRI information.
  • the WTRU may request the information for candidate cells for which the WTRU determines to include in the request for information, for example HRI rating information.
  • One or more requests from (e.g., all) the WTRUs in the cluster may contain information related to one or more of a list of candidate cells for which HRI rating information is needed, identifier(s) for the service(s) running on the WTRU (e.g., relevant for the HRI rating), identifier(s) for the service(s) the WTRU may run after executing the HO (e.g., relevant for the HRI rating), and/or predictions for (e.g., all) service(s) the WTRU may run after executing the HO.
  • the WTRU may receive a response to the request, for example from the network.
  • the response may include a multicast message. Additionally, or alternatively, the response may include information related to one or more of a rating value for a (e.g., particular) cell, rating values for a subset of cells from the candidate cell list, rating values for (e.g., all) cells from the candidate cell list, predicted rating value(s) (e.g., time predictions) of the subcases mentioned herein using a pre-trained Al algorithm, and/or an ID (e.g., identifier) determining the anchor WTRU for the cluster.
  • a rating value for a e.g., particular
  • rating values for a subset of cells from the candidate cell list rating values for (e.g., all) cells from the candidate cell list
  • predicted rating value(s) e.g., time predictions
  • ID e.g., identifier
  • the rating value for the particular cell may indicate the suitability of the cell to become a target cell for the WTRU.
  • the rating values for a subset of cells from the candidate cell list may indicate the suitability of the cells in the subset to become a target cell for the WTRU.
  • the rating values for (e.g., all) cells from the candidate cell list may indicate the suitability of each of the cells in the subset to become a target cell for the WTRU.
  • the predicted rating value(s) may include one or more of a pre-trained Al, an empirical model, and/or probabilistic model, which for example may be made available to the WTRU offline and/or before the LTM procedure has started.
  • the WTRU may determine the target cell from the cells provided in the candidate cell list based on the rating values received.
  • the WTRU may use the one or more parameters (e.g., for WTRU-11, WTRU-I2, WTRU-I3, WTRU-I4, and/or WTRU-I5).
  • the WTRU may be selected as an anchor WTRU.
  • the anchor WTRU may use sidelink communication(s) with (e.g., all) WTRUs to send the decision for the selected target cell and/or the service descriptors and/or the one or more parameters (e.g., for WTRU-11 , WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5), for example based on which it has made the decision.
  • sidelink communication(s) with (e.g., all) WTRUs to send the decision for the selected target cell and/or the service descriptors and/or the one or more parameters (e.g., for WTRU-11 , WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5), for example based on which it has made the decision.
  • the WTRU may select a reply from all the WTRUs in the corresponding cluster, for example where each WTRU has sent a message in the sidelink stating its own decision for the selected target cell and/or the service descriptors and/or the one or more parameters, (e.g., for WTRU-11 , WTRU-I2, WTRU-I3, WTRU- I4, WTRU-I5) based on which it has made the decision.
  • the anchor WTRU may indicate to the network as a separate transmission or as part of the L1 measurement report, for all the WTRUs in the cluster (e.g., including the anchor WTRU).
  • the indication of the decision may include one or more of indication of a cell, reporting information regarding the cell indication, and/or precision metric(s).
  • the WTRU may select the indicated cell as a potential target cell (e.g., bestCell_forWTRUJnCluster).
  • Reporting information regarding the cell indication may be based on reporting criteria and/or include a (e.g., main) reason for the selection of the target cell.
  • Precision metric(s) may include one or more of confidence interval(s), error margin(s), and/or accuracy coefficient , for example related to the bestCellJorWTRUJnCluster and minlnfoJorWTRUJnCluster.
  • a WTRU may not be selected as an anchor WTRU.
  • the WTRU not selected as an anchor WTRU may receive a request from the anchor WTRU, for example over sidelink.
  • the anchor WTRU may send the request including one or more of information regarding the decision for the selected target cell, the service descriptors, and/or the one or more parameters (e.g., for WTRU-11 , WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5) based on which it has made the decision.
  • the WTRU may reply to the anchor WTRU using sidelink message.
  • the reply may include the WTRU decision for the selected target cell and/or the service descriptors and/or the one or more parameters (e.g., for WTRU-11, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5) based on which it has made the decision.
  • the one or more parameters e.g., for WTRU-11, WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5
  • a WTRU may receive an L1 cell switch command (e.g., MAC CE), for example from the network.
  • the WTRU may receive the L1 switch command after executing the LTM decision (e.g., for which bestCell_forWTRUJnCluster and/or minlnfo_forWTRUJnCluster for all WTRUs in the cluster is available at the network).
  • the WTRUs may perform detach from the source base station (e.g., gNB).
  • the WTRU may apply the target configuration(s).
  • the WTRU may execute the RACH procedure.
  • An HRI table may be updated for a cluster.
  • the anchor WTRU may receive a request for HRI from the selected target cell, for example after the execution of the HOs.
  • the network may sent a request to the anchor WTRU to report the rating for the executed HOs.
  • the request may contain an indication of the cell to which the WTRU(s) were previously attached. Additionally, or alternatively, the indication may include time information for generating the reply to the request (e.g., X time after the execution of the HO, and/or X time before triggering another LTM procedure, etc.) and/or one or more conditions for generating the reply to the request.
  • a condition may include the anchor WTRU being idle for a predetermined amount of time and/or having no data to send. Additionally, or alternatively, a condition may include a radio link quality above threshold, for example to make sure the reply is delivered.
  • the anchor WTRU may send a response to the received request for HRI, for example to the network.
  • the network may use the to update the HRI table.
  • the response may include one or more of cell entry, service descriptor(s), and/or or a subset of service descriptor(s).
  • the subset of service descriptor(s) may include service descriptor(s) that were active and/or relevant prior to executing the HO for each of the WTRUs for which the rating value is delivered to the network.
  • the response may additionally, or alternatively, include the one or more of parameters (e.g., for WTRU-11 , WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5), and/or the (e.g., actual) rating value as estimated by the each of the WTRUs.
  • Cell entry may include information associated with which cell each of the WTRUs was previously connected (e.g., prior to executing the HO for which the rating value is delivered to the network).
  • the anchor WTRU may send a report.
  • the anchor WTRU may create the report as an output, for example from a standardized measurement procedure at the WTRU.
  • the report may be specified and/or configured by the network (e.g., similar to a buffer status report).
  • the WTRU may send an indication of the HRI rating value of the executed handover to the network for (e.g., all) WTRUs in the cluster, for example in the report.
  • the anchor WTRU may receive a request from the network to report the service descriptor(s) (e.g., relevant service descriptor(s)) for the rating-based decision.
  • the anchor WTRU may send the service descriptor(s) (e.g., relevant service descriptor(s)) for the rating-based decision, for example to the network as a reply to the request.
  • the network may use the service descriptor(s) to calculate the rating value and/or to update the HRI table for (e.g., all) WTRUs in the cluster.
  • the anchor WTRU may receive a request from the network to report one or more of the one or more of parameters (e.g., for WTRU-11 , WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5).
  • the network may use the one or more parameters to calculate the rating value and/or to update the HRI table for all WTRUs in the cluster.
  • the report may include an indication of the cluster.
  • the report may include indications (e.g., identifiers) of WTRUs in the cluster, for example for HO based on rating information and/or service specific descriptor(s).
  • the WTRUs from a cluster may receive a multicast request for service descriptors and/or the one or more parameters (e.g., for WTRU-11 , WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5).
  • the WTRUs from a cluster may receive the multicast request from the network, for example prior to the LTM decision execution. Additionally, or alternatively, the WTRUs from a cluster may specify the anchor WTRU for (e.g., all) the WTRU in the cluster.
  • the anchor WTRU may respond to the request, for example by sending information related to the service descriptors (e.g., in par or in full) and/or the one or more parameters (e.g., for WTRU-11 , WTRU-I2, WTRU-I3, WTRU-I4, WTRU-I5).
  • the anchor WTRU response may include auxiliary information sent to the network in a single or multiple transmissions, for example prior to the LTM decision execution for (e.g., all) WTRUs in the cluster.
  • FIG. 2 is a diagram illustrating an example LTM baseline procedure 200.
  • the WTRU 202 and a base station 204 may perform LTM preparation 206.
  • the WTRU 202 may be in RRC_CONNECTED mode.
  • the WTRU 202 may send a measurement report, for example to the base station 204.
  • the base station may perform LTM candidate preparation, for example based on the measurement report.
  • the base station 204 may send an RRC reconfiguration message (e.g., LTM candidate configuration), for example to the WTRU 202.
  • the WTRU 202 may send an RRC reconfiguration complete message to the base station 204, for example in response to the RRC reconfiguration message.
  • the WTRU 202 and base station 204 may perform an early sync.
  • the WTRU 202 and/or base station 204 may perform DL/UL synchronization with one or more candidate cells.
  • the WTRU 202 and the base station 204 may perform LTM execution.
  • the WTRU 202 may send an L1 measurement report, for example to the base station 204.
  • the base station 204 may make an LTM decision.
  • the base station 204 may send a cell switch command (e.g., MAC CE) to the WTRU 202.
  • the WTRU 202 may detach from the source and/or apply target configurations.
  • the WTRU 202 and/or base station 204 may perform a RACH procedure.
  • FIG. 3 is a diagram illustrating an example 300 LTM execution of a reference WTRU. Coverage of four cells with base stations are labelled as 'X', 'Q', ‘ Y’, and 7'.
  • a reference user e.g., WTRU
  • LTM procedure e.g., HO-4
  • base station e.g., gNB
  • base station e.g., gNB
  • Y 310 candidate cells available and/or with an established early sync for both uplink and downlink.
  • base station e.g., gNB
  • gNB base station
  • Q 308 e.g., HO-1
  • the WTRU-1 316 may provide one or more of an update for the HRI table for the cell entry Q/coverage area 312 (e.g., the selected target cell), cell entry Q/coverage area 312 service descript
  • WTRU-3322 may perform an LTM procedure at time t ⁇ 0. Additionally, or alternatively, WTRU-3 322 may provide one or more of an update for the HRI table for the cell entry Y/coverage area 314 (e.g., the selected target cell), cell entry Y/coverage area 314 service descriptors (e.g., S2), and/or the actual value of the rating.
  • FIG. 4 is a diagram illustrating an example of a message sequence LTM execution 400 of a reference WTRU.
  • WTRU-4402 e.g., the reference WTRU
  • WTRU-4 402 may be configured by the network to send a request for HRI, for example specifying the candidate cells (e.g., Q, Y) and/or its service descriptors (e.g., S2).
  • WTRU-4402 may check candidate cells (e.g., Q and Y).
  • WTRU-4 402 may send a request for HRI, for example to the network 404.
  • the network may send a response to the WTRU-4 402, for example for the rating values for Q and Y cells for the service descriptor S2 (e.g., in the provided values for cell Q, the values from HO-1 and HO-2 may be included, and/or in the provided values for cell Y, the values from HO-3 may be included).
  • WTRU-4402 may select the cell Y, for example based on the rating value related to service descriptor S2.
  • the WTRU-4402 and/or the network 404 may indicate the best cell (e.g., Y) and/or an indication (e.g., mininfo) of why the cell is the best cell (e.g., based on S2 descri ptor(s)).
  • the cell selection may be performed/done the network.
  • the network may consider the suggested decision from the WTRU-4 as an input and/or considered at the LTM decision.
  • WTRU-4 402 may send an L1 measurement report to the network 404.
  • the network 404 may send an L1 cell switch command (e.g., MAC CE) to the WTRU-4 402.
  • the WTRU-4 402 may detach from the source and/or apply target configurations.
  • the WTRU-4 402 and/or the network 404 may perform a RACH procedure.
  • FIG. 5 is an example HRI table 500.
  • cells are provided, for example cell Q and cell Y.
  • service descriptors are provided.
  • One or more service descriptors may correspond to a (e.g., each) cell. For example, service descriptors S1 , S2, ....
  • HRI ratings are provided.
  • One or more HRI ratings may correspond to a (e.g., each) cell and/or a (e.g., each) service descriptor.
  • one HRI e.g., R1
  • one service descriptor e.g., Si for cell Q.
  • FIG. 6 is a diagram illustrating an example of LTM execution 600 of a cluster of WTRUs. Coverage of four cells with base station (e.g., gNB)s labelled as 'X', 'O’, ‘Y’, and 7' is shown.
  • base station e.g., gNB
  • base station e.g., gNB
  • base station e.g., gNB
  • base station e.g., gNB
  • Q 608 e.g., HO-1
  • WTRU-1 616 may provide an update for one or more of the HRI table for the cell entry Q/coverage area 612 (e.g., the selected target cell), cell entry Q/coverage area service descriptors (e.g., Si), and/or the actual value for the rating.
  • base station e.g., gNB
  • gNB base station
  • gNB gNB
  • Q 608 at time t ⁇ 0 (e.g., HO-2).
  • WTRU-2 618 may provide an update for one or more of the HRI table for the same cell entry Q/coverage area 612 (e.g., the selected target cell), cell entry Q/coverage area service descriptors
  • FIGS. 7A and 7B illustrate an example diagram of a message sequence LTM execution 700 of a cluster of WTRUs 702.
  • the WTRUs 702 in the cluster may start an LTM procedure, for example as shown in the message sequence diagram in FIG. 6.
  • the (e.g., all) WTRUs 702 in the cluster may have been configured by the network 704 to send a request for HRI, for example specifying the candidate cells (e.g , Q, Y) and associated service descriptors (e.g., Si - for all WTRUs 702, apart from S3 - for WTRU-4-4).
  • the network may send back a response for the rating values for Q and Y cells for the service descriptor Si and S3 (e.g., in the provided values for cell Q, the values from HO-1 and HO-2 may be included, and/or in the provided values for cell Y, the values from HO-3 may be included).
  • the response from the network may be a multicast HRI message
  • the multicast HRI message may contain the rating value(s) and/or an anchor WTRU from the cluster (e.g., WTRU-4-5), for example specified by the network 704.
  • the anchor WTRU may indicate the decision of the selected cell (e.g., Q) and/or the reason why this cell has been selected (e.g., Si).
  • the anchor WTRU may receive one or more replies from (e.g., all) WTRUs in the cluster about their decisions.
  • the WTRUs e.g., all WTRUs
  • the anchor WTRU may (e.g., then) send a message about the decision and/or the reason(s) why this decision has been made for (e.g., all) the WTRUs in the cluster.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Une unité d'émission/réception sans fil (WTRU) peut recevoir une configuration associée à une pluralité de cellules candidates. La WTRU peut envoyer, par exemple à un réseau, une requête d'informations d'évaluation de transfert (HRI) pour la pluralité de cellules candidates. La requête peut comprendre des informations de description de service associées à des services s'exécutant au niveau de la WTRU. La WTRU peut recevoir une réponse en provenance du réseau. La réponse peut comprendre les HRI pour la pluralité de cellules candidates. Les HRI peuvent comprendre une indication de la manière dont chaque cellule candidate de la pluralité de cellules candidates doit devenir une cellule cible pour la WTRU. La WTRU peut sélectionner une cellule candidate de la pluralité de cellules candidates sur la base des HRI. La WTRU peut envoyer une indication de la cellule candidate sélectionnée au réseau.
PCT/US2024/036749 2023-07-06 2024-07-03 Procédés d'exploitation d'informations d'évaluation de recours au levier financier pour personnaliser une mobilité ltm avec des préférences spécifiques à un service Pending WO2025010343A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363525194P 2023-07-06 2023-07-06
US63/525,194 2023-07-06

Publications (1)

Publication Number Publication Date
WO2025010343A1 true WO2025010343A1 (fr) 2025-01-09

Family

ID=91968869

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/036749 Pending WO2025010343A1 (fr) 2023-07-06 2024-07-03 Procédés d'exploitation d'informations d'évaluation de recours au levier financier pour personnaliser une mobilité ltm avec des préférences spécifiques à un service

Country Status (1)

Country Link
WO (1) WO2025010343A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140004841A1 (en) * 2011-02-10 2014-01-02 Evolution Systems Ltd. Method and system of analyzing a plurality of cells of a cellular telecommunication network
WO2019019903A1 (fr) * 2017-07-28 2019-01-31 Oppo广东移动通信有限公司 Procédé et un dispositif de signalisation d'informations de mesurage, et terminal et support de stockage
US20220070752A1 (en) * 2019-01-16 2022-03-03 Lg Electronics Inc. Method and apparatus for mobility management in wireless communication system
CN115623547A (zh) * 2021-07-16 2023-01-17 维沃移动通信有限公司 条件切换处理方法、装置及相关设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140004841A1 (en) * 2011-02-10 2014-01-02 Evolution Systems Ltd. Method and system of analyzing a plurality of cells of a cellular telecommunication network
WO2019019903A1 (fr) * 2017-07-28 2019-01-31 Oppo广东移动通信有限公司 Procédé et un dispositif de signalisation d'informations de mesurage, et terminal et support de stockage
US20220070752A1 (en) * 2019-01-16 2022-03-03 Lg Electronics Inc. Method and apparatus for mobility management in wireless communication system
CN115623547A (zh) * 2021-07-16 2023-01-17 维沃移动通信有限公司 条件切换处理方法、装置及相关设备

Similar Documents

Publication Publication Date Title
US12302237B2 (en) Network slice reselection
EP3711447A1 (fr) Fonctionnement en double connectivité dans un état inactif
WO2021163665A1 (fr) Procédés, appareil et systèmes pour sessions d'unités de données de protocole d'accès multiple
WO2020033562A1 (fr) Procédés et appareils de synchronisation dans un système sans fil
WO2020069182A1 (fr) Procédés de synchronisation de liaison latérale pour v2x en nr
US20250168638A1 (en) Personal internet of things network connectivity
EP4548637A1 (fr) Configuration d'événement de mesure pour permettre une mobilité l1/2 et un rapport de mesure à l'aide d'un ce mac
WO2024073316A1 (fr) Déclenchement de rapport cqi de cellule candidate
EP4500946A1 (fr) Système et procédés pour prendre en charge un flux et un profil de qos auto-adaptatifs
EP4500963A1 (fr) Sélection d'une route dans un système de communication sans fil
WO2025010343A1 (fr) Procédés d'exploitation d'informations d'évaluation de recours au levier financier pour personnaliser une mobilité ltm avec des préférences spécifiques à un service
EP4666272A1 (fr) Rapport de trajet de vol mis à jour partiel/delta
WO2024173338A1 (fr) Trajet de vol/point de cheminement de repli préconfiguré
AU2024223908A1 (en) Partial/delta updated flight path reporting
EP4666270A1 (fr) Demande explicite d'état de trajet de vol
WO2024173340A1 (fr) Trajectoire de vol/point de cheminement de repli indiqués en réseau
WO2024173330A1 (fr) Demande explicite d'état de trajet de vol
WO2024031055A1 (fr) Procédés de prise en compte de conditions de scell pendant une mobilité conditionnelle
WO2025208008A1 (fr) Association d'un utilisateur humain à un abonnement
WO2025072890A1 (fr) Procédés de gestion d'attribution d'adresse ip pour connexion de relais u2u à sauts multiples
WO2025151435A1 (fr) Configuration de wtru pour réglages de rrt plus rapides
WO2024238542A1 (fr) Découverte, sélection et fourniture de service en périphérie à l'aide d'informations de serveur d'application en périphérie (eas) partagé et d'un serveur d'activation en périphérie (ees) d'ancrage
EP4666271A1 (fr) Déclencheur conditionnel pour une indication de mise à jour de trajectoire de vol
EP4659498A1 (fr) Sélection d'une configuration d'autocommutateur conditionnel pour unité d'émission/réception sans fil à relais de réseau
WO2024173317A1 (fr) Déclencheur conditionnel pour une indication de mise à jour de trajectoire de vol

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24746881

Country of ref document: EP

Kind code of ref document: A1