Mobility for mobile integrated access and backhaul cells

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive an indication that a cell is associated with a mobile integrated access and backhaul (IAB) state. The UE may perform a cell selection or reselection operation based at least in part on an onboard state between the UE and the cell and based at least in part on the cell being associated with the mobile IAB state. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 484,910, filed on February 14, 2023, entitled “MOBILITY FOR AMOBILEINTEGRATED ACCESS AND BACKHAUL CELL,” and U.S. Non-Provisional Patent Application No. 18 / 433,772, filed on February 6, 2024, entitled “MOBILITY FOR A MOBILEINTEGRATED ACCESS AND BACKHAUL CELL,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for mobility of mobile integrated access and backhaul cells. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink and uplink communications. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving an indication that a cell is associated with a mobile integrated access and backhaul (IAB) state indicating that the cell is a mobile cell. The method may include performing a cell selection or reselection operation based at least in part on an onboard state between the UE and the cell and at least in part on the cell being associated with the mobile IAB state, wherein the onboard state indicates that the UE is onboard a mobile entity.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE may include: a memory; and one or more processors coupled to the memory. The one or more processors may be configured to receive an indication that a cell is associated with a mobile IAB state indicating that the cell is a mobile cell. The one or more processors may be configured to perform a cell selection or reselection operation based at least in part on an onboard state between the UE and the cell and at least in part on the cell being associated with the mobile IAB state, wherein the onboard state indicates that the UE is onboard a mobile entity.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive an indication that a cell is associated with a mobile IAB state indicating that the cell is a mobile cell. The instruction set, when executed by one or more processors of the UE, may cause the UE to perform a cell selection or reselection operation based at least in part on an onboard state between the UE and the cell and at least in part on the cell being associated with the mobile IAB state, wherein the onboard state indicates that the UE is onboard a mobile entity.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication that a cell is associated with a mobile IAB state indicating that the cell is a mobile cell. The apparatus may include means for performing a cell selection or reselection operation based at least in part on an onboard state between the apparatus and the cell and at least in part on the cell being associated with the mobile IAB state, wherein the onboard state indicates that the UE is onboard a mobile entity.

[0011] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the accompanying drawings.

[0012] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the following detailed description may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily used as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0013] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporated into the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and compositions. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order that the above-mentioned features of the present disclosure may be fully understood, a more particular description of the invention briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not therefore to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0015] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0016] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0017] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0018] Figure 4 is a diagram illustrating an example of a radio access network according to the present disclosure.

[0019] Figure 5 is a diagram illustrating an example of an integrated access and backhaul (IAB) network architecture according to the present disclosure.

[0020] Figure 6An example of a wireless network in which a UE can support a communication mode according to the present disclosure is illustrated.

[0021] Figure 7 is a diagram illustrating an example of signaling associated with determination of an onboard status and cell selection or reselection according to the present disclosure.

[0022] Figure 8 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0023] Figure 9 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0024] A user equipment (UE) can access a wireless network via a cell provided by a network node, such as an integrated access and backhaul (IAB) node. In some deployments, the network node (and the cell provided by the network node) can be mobile, meaning that the network node and the entity to which it is attached or associated can move. The UE can be onboard the entity to which the network node is attached, meaning that the UE can move with the network node and the cell. This can be referred to as the UE having an onboard state with respect to the network node. In some examples, the UE can be in radio resource control (RRC) idle mode or RRC inactive mode, meaning that the UE performs cell selection and reselection operations so that the UE remains camped on a cell. Legacy cell selection and reselection operations can be suboptimal for a UE associated with an onboard state, as the UE is likely to remain within the coverage of a mobile IAB node and is likely to detect many different cells due to cell selection measurements. However, the UE may not have information indicating that the UE is associated with an onboard state. Consequently, the UE cannot perform cell selection and reselection operations appropriate for a UE associated with an onboard state, which reduces the efficiency of network resource usage and results in unnecessary cell selection or reselection operations.

[0025] Some of the techniques described herein provide cell selection and reselection operations based at least in part on an onboard state between a UE and a cell and at least in part on the cell being associated with a mobile IAB state (e.g., the cell being associated with a mobile IAB node). For example, a UE may receive an indication that a cell is associated with a mobile IAB state. The UE may perform cell selection or reselection operations based at least in part on the cell being associated with the mobile IAB state and at least in part on the onboard state between the UE and the cell. By performing cell selection or reselection operations based at least in part on the mobile IAB state and the onboard state, network resource usage efficiency is improved and unnecessary cell selection or reselection operations are reduced.

[0026] Some of the techniques described herein provide for determining that a UE is associated with an onboard state with respect to a cell. For example, the UE may determine that the UE is associated with an onboard state based on detecting the cell for a first threshold length of time. For another example, the UE may determine that the UE is associated with an onboard state based on camping on the cell for a second threshold length of time. By determining at the UE that the UE is associated with an onboard state, processing load and complexity at the cell are reduced.

[0027] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claims.

[0028] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] Although various aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0030] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (illustrated as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (illustrated as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0031] In some examples, network node 110 is or includes a network node (such as an RU) that communicates with UE 120 via a radio access link. In some examples, network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, network node 110 (such as a converged network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0032] In some examples, network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​network node 110 and / or a network node subsystem serving that coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 associated with the femtocell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macrocell may be referred to as a macro network node. A network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0033] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0034] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110 d (e.g., a relay network node) may communicate with a network node 110 a (e.g., a macro network node) and a UE 120 d to facilitate communications between the network node 110 a and the UE 120 d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0035] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0036] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0037] UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0038] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0039] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0040] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0041] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0042] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0043] With the above examples in mind, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0044] In some aspects, UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive an indication that a cell is associated with a mobile integrated access and backhaul (IAB) state; and perform a cell selection or reselection operation based at least in part on an onboard state between the UE and the cell and at least in part on the cell being associated with a mobile IAB state. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0045] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0046] Figure 22 is a diagram illustrating example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with the UE 120.

[0047] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or frequency upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0048] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use the demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols, if applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine, among other things, a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0049] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0050] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more groups of antenna elements, and / or one or more antenna arrays, etc. An antenna panel, antenna group, group of antenna elements, and / or antenna array may include one or more antenna elements (within a single housing or multiple housings), a group of coplanar antenna elements, a group of non-coplanar antenna elements, and / or be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0051] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to execute the instructions herein (eg, reference Figures 4 to 9 ) any aspects of any method described in the method.

[0052] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component (shown as DEMOD) of modem 232), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions herein (e.g., reference 242). Figures 4 to 9 ) any aspects of any method described in the method.

[0053] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components in the may perform one or more techniques associated with cell selection and reselection, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the may perform or direct e.g. Figure 8 800 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 8 The process 800 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0054] In some aspects, the UE 120 includes means for receiving (e.g., using the antenna 252, modem 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) an indication that a cell is associated with a mobile IAB state; and / or means for performing (e.g., using the antenna 252, modem 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) cell selection or reselection operations based at least in part on an onboard state between the UE and the cell and at least in part on the cell being associated with a mobile IAB state. Means for the UE 120 to perform the operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0055] Although Figure 2 The blocks in FIG. 2 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0056] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0057] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated architecture or a decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also known as an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0058] A converged base station (e.g., a converged network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually spread across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among others.

[0059] Base station type operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Each unit of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0060] Figure 3 FIG2 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links (such as via an F1 interface). Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0061] Each of the units (including the CU 310, DU 330, RU 340) and the near-RT RIC 325, the non-RT RIC 315, and the SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0062] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among others. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0063] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers, at least in part according to a functional split (such as that defined by 3GPP). In some aspects, the one or more higher PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and the like. In some aspects, the DU 330 may also host one or more lower PHY layers, such as those implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0064] Each RU 340 may implement low-layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as low-layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0065] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0066] The non-RT RIC 315 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0067] In some implementations, the non-RT RIC 315 can receive parameters or external enrichment information from an external server in order to generate an AI / ML model to be deployed in the near-RT RIC 325. Such information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or through the creation of RAN management policies (such as A1 interface policies).

[0068] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0069] Figure 4 is a diagram illustrating an example 400 of a radio access network according to the present disclosure.

[0070] As shown by reference numeral 405, a traditional (e.g., 3G, 4G, or LTE) radio access network may include multiple network nodes 410 (e.g., base stations) (illustrated as access nodes (ANs)), wherein each network node 410 communicates with a core network via a wired backhaul link 415 (such as a fiber optic connection). The network node 410 may communicate with a UE 420 via an access link 425 (which may be a wireless link). In some aspects, Figure 4 The network node 410 shown may be Figure 1 The network node 110 is shown. In some aspects, Figure 4 The UE 420 shown may be Figure 1UE 120 is shown.

[0071] As shown in the reference numeral 430, the radio access network may include a wireless backhaul network, sometimes referred to as an integrated access and backhaul (IAB) network. In an IAB network, at least one network node is an anchor network node 435 that communicates with the core network via a wired backhaul link 440 (such as a fiber optic connection). The anchor network node 435 may also be referred to as an IAB donor (or IAB-donor). The IAB network may include one or more non-anchor network nodes 445, sometimes referred to as relay nodes, relay base stations, or IAB nodes (or IAB-nodes). The non-anchor network node 445 may communicate directly or indirectly with the anchor base station 435 via one or more backhaul links 450 (e.g., via one or more non-anchor network nodes 445) to form a backhaul path to the core network for carrying backhaul traffic. The backhaul link 450 may be a wireless link. The anchor network node 435 and / or the non-anchor network node 445 may communicate with one or more UEs 455 via an access link 460 (which may be a wireless link for carrying access traffic). In some aspects, Figure 4 The anchor network node 435 and / or the non-anchor network node 445 shown may be Figure 1 The network node 110 is shown. In some aspects, Figure 4 The UE 455 shown may be Figure 1 UE 120 is shown.

[0072] As shown by reference numeral 465, in some aspects, a radio access network including an IAB network may use millimeter wave technology and / or directional communication (e.g., beamforming) for communications between network nodes and / or UEs (e.g., between two network nodes, between two UEs, and / or between a network node and a UE). For example, a wireless backhaul link 470 between network nodes may use millimeter wave signals to carry information and / or may use beamforming to be oriented toward a target network node. Similarly, a wireless access link 475 between a UE and a network node may use millimeter wave signals and / or may be oriented toward a target wireless node (e.g., a UE and / or a network node). In this way, inter-link interference may be reduced.

[0073] Figure 4 The configuration of the network nodes and UEs in are shown as examples, and other examples are also contemplated. For example, Figure 4 The one or more base stations illustrated may be replaced by one or more UEs that communicate via a UE-to-UE access network (e.g., a peer-to-peer network or a device-to-device network). In this case, an anchor node may refer to a UE that communicates directly with a network node (e.g., an anchor network node or a non-anchor network node).

[0074] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0075] Figure 5 is a diagram illustrating an example 500 of an IAB network architecture according to the present disclosure.

[0076] like Figure 5 As shown, the IAB network may include an IAB donor 505 (shown as IAB-donor) connected to the core network via a wired connection (shown as wired backhaul). For example, the Ng interface of the IAB donor 505 may terminate at the core network. Additionally or alternatively, the IAB donor 505 may be connected to one or more devices of the core network that provide a core access and mobility management function (AMF). In some aspects, the IAB donor 505 may include a network node 110, such as an anchor network node, as described above in conjunction with Figure 4 As described. As shown in the figure, the IAB donor 505 may include a CU, which may perform access node controller (ANC) functions and / or AMF functions. The CU may configure the DU of the IAB donor 505 and / or may configure one or more IAB nodes 510 (e.g., a mobile terminal (MT) and / or a DU of the IAB node 510) connected to the core network via the IAB donor 505. Therefore, the CU of the IAB donor 505 may control and / or configure the entire IAB network connected to the core network via the IAB donor 505, such as by using control messages and / or configuration messages (e.g., radio resource control (RRC) configuration messages or F1 application protocol (F1-AP) messages).

[0077] like Figure 5As further shown, the IAB network may include IAB nodes 510 (shown as IAB-Node 1, IAB-Node 2, and IAB-Node 3) connected to the core network via an IAB donor 505. As shown, the IAB nodes 510 may include mobile termination (MT) functionality (sometimes also referred to as UE functionality (UEF)) and may include DU functionality (sometimes also referred to as access node functionality (ANF)). The MT functionality of an IAB node 510 (e.g., a child node) may be controlled and / or scheduled by another IAB node 510 (e.g., the child node's parent node) and / or by the IAB donor 505. The DU functionality of an IAB node 510 (e.g., a parent node) may control and / or schedule other IAB nodes 510 (e.g., the parent node's child nodes) and / or UE 120. Thus, the DU may be referred to as a scheduling node or scheduling component, and the MT may be referred to as a scheduled node or scheduled component. In some aspects, the IAB donor 505 may include the DU functionality but not the MT functionality. That is, the IAB donor 505 may configure, control, and / or schedule communications for the IAB node 510 and / or the UE 120. The UE 120 may include only the MT functionality and not the DU functionality. That is, the communications of the UE 120 may be controlled and / or scheduled by the IAB donor 505 and / or the IAB node 510 (e.g., the parent node of the UE 120).

[0078] When a first node controls and / or schedules communications for a second node (e.g., when the first node provides DU functionality for the MT functionality of the second node), the first node may be referred to as the parent node of the second node, and the second node may be referred to as the child node of the first node. The child node of the second node may be referred to as the grandchild node of the first node. Thus, the DU functionality of the parent node may control and / or schedule communications for the child node of the parent node. The parent node may be the IAB donor 505 or the IAB node 510, and the child node may be the IAB node 510 or the UE 120. Communications of the MT functionality of the child node may be controlled and / or scheduled by the parent node of the child node.

[0079] like Figure 5 As further shown, the link between the UE 120 (e.g., which has only MT functionality and not DU functionality) and the IAB donor 505 or between the UE 120 and the IAB node 510 may be referred to as an access link 515. The access link 515 may be a wireless access link that provides the UE 120 with radio access to the core network via the IAB donor 505 and, optionally, one or more IAB nodes 510. Thus, Figure 5 The illustrated network may be referred to as a multi-hop network or a wireless multi-hop network.

[0080] like Figure 5 As further shown, the link between the IAB donor 505 and the IAB node 510 or between two IAB nodes 510 may be referred to as a backhaul link 520. The backhaul link 520 may be a wireless backhaul link that provides radio access to the core network to the IAB node 510 via the IAB donor 505 and, optionally, via one or more other IAB nodes 510. In an IAB network, network resources (e.g., time resources, frequency resources, and / or spatial resources) for wireless communication may be shared between the access link 515 and the backhaul link 520. In some aspects, the backhaul link 520 may be a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link). In some aspects, if the primary backhaul link fails, becomes congested, and / or becomes overloaded, etc., the secondary backhaul link may be used. For example, if the primary backhaul link between IAB-node 2 and IAB-node 1 fails, the backup link 525 between IAB-node 2 and IAB-node 3 may be used for backhaul communication. As used herein, a node or wireless node may be referred to as an IAB donor 505 or an IAB node 510 .

[0081] In some aspects, the node may be a mobile IAB node. The mobile IAB node may include an IAB node (e.g., IAB donor 505 or IAB node 510) associated with (e.g., attached to, moving with) a mobile entity, such as a vehicle (e.g., a bus, train, ship, airship, balloon, etc.). In some aspects, the mobile IAB node may not provide connectivity to downstream IAB nodes (e.g., only to UEs). The mobile IAB node may provide a cell via which the UE 120 may establish an access link 515 with the mobile IAB node. In some cases, the UE 120 may move with the mobile IAB node (and therefore the cell provided by the mobile IAB node), e.g., because the UE 120 is located in or on the mobile entity. In some other cases, the UE 120 may not move with the mobile IAB node, e.g., because the UE 120 is not located in or on the mobile entity. The IAB node may send an indication that the IAB node is a mobile IAB node. For example, the IAB node may send the indication via broadcast system information, RRC signaling, etc. UE 120 may perform various operations based at least in part on the indication, as described elsewhere herein.

[0082] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0083] Figure 6An example 600 of a wireless network (e.g., wireless network 100) in which a UE (e.g., UE 120) can support additional communication modes according to the present disclosure is illustrated. The UE can be communicatively connected to one or more network nodes 110 in the wireless network. For example, the UE can be connected to one or more network nodes 110 in a dual connectivity configuration. In this case, the first network node 110 can serve the UE as a primary node, and the second network node 110 can serve the UE as a secondary node.

[0084] like Figure 6 As shown, the UE may support a connected communication mode (e.g., RRC active mode 602), an idle communication mode (e.g., RRC idle mode 604), and an inactive communication mode (e.g., RRC inactive mode 606). The RRC inactive mode 606 may reside functionally between the RRC active mode 602 and the RRC idle mode 604.

[0085] The UE may transition between different modes based at least in part on various commands and / or communications received from one or more network nodes 110. For example, the UE may transition from RRC active mode 602 or RRC inactive mode 606 to RRC idle mode 604 based at least in part on receiving an RRC Release communication. For another example, the UE may transition from RRC active mode 602 to RRC inactive mode 606 based at least in part on receiving an RRC Release communication with a suspendConfig. For another example, the UE may transition from RRC idle mode 604 to RRC active mode 602 based at least in part on receiving an RRC Setup Request communication. For another example, the UE may transition from RRC inactive mode 606 to RRC active mode 602 based at least in part on receiving an RRC Resume Request communication.

[0086] When transitioning to RRC inactive mode 606, the UE and / or one or more network nodes 110 may store UE context (e.g., access stratum (AS) context and / or higher layer configuration). This permits the UE and / or one or more network nodes 110 to apply the stored UE context when the UE transitions from RRC inactive mode 606 to RRC connected mode 602 to resume communication with one or more network nodes 110, which reduces the latency of transitioning to RRC connected mode 602 relative to transitioning from RRC idle mode 604 to RRC connected mode 602.

[0087] In some cases, the UE may be communicatively connected with a new primary node (e.g., a primary node that is different from the last serving primary node when the UE transitioned to the RRC idle mode 604 or RRC inactive mode 606) when transitioning from the RRC idle mode 604 or RRC inactive mode 606 to the RRC active mode 602. In this case, the new primary node may be responsible for identifying the secondary node for the UE in the dual connectivity configuration.

[0088] When the UE initially camps on a cell, the UE may start in RRC idle mode 604. "Cell selection" is a mobility procedure that allows the UE to identify the cell on which to camp. Cell selection is applicable after the UE is powered on, after the UE leaves RRC active mode 602, and after the UE returns to a coverage area. While camped on a cell, the UE may read system information, perform a registration area update with the core network, apply discontinuous reception (DRX) for paging, and monitor the physical downlink control channel (PDCCH) for downlink control information (DCI) or core network paging. The UE may switch from camping on one cell to camping on another cell by performing cell reselection. Cell reselection is a mobility procedure for a UE that is in RRC idle mode 604 or RRC inactive mode 606. Cell selection may include scanning radio frequency channels within a supported frequency band of the UE according to a synchronization raster; searching for one or more synchronization signal blocks at each carrier frequency; identifying the strongest cell based on the search for the one or more synchronization signal blocks; and camping on the strongest cell if the strongest cell is a "suitable cell" or an "acceptable cell." Cell reselection may include performing measurements on a set of cells, ranking the set of cells based at least in part on the measurements, and camping on a cell selected from the ranked set of cells. Cell selection and reselection may be performed according to various rules and criteria, such as an Srxlev criterion, an Squal criterion, a Qrlxevmin criterion, a Qqualmin criterion, a prioritization rule (indicating that particular cells or types of cells should be prioritized or deprioritized for selection or reselection), a reselection timer (e.g., which may correspond to a mobility state of the UE), a time interval for measurements, and the like.

[0089] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0090] Figure 77 is a diagram illustrating example 700 of signaling associated with determining an onboard state and selecting or reselecting a cell according to the present disclosure. Example 700 includes a UE (e.g., UE 120) and a network node (e.g., network node 110, IAB donor 505, IAB node 510). The network node may be a mobile IAB node, as described above. The network node may implement a cell. It should be understood that references to communications between a UE and a network node also include the same communications between the UE and a cell implemented by the network node, and vice versa. Operations described herein as being performed by a cell may be performed by the network node that implements the cell.

[0091] As indicated by reference numeral 705, the network node may output, and the UE may receive, an indication that a cell is associated with a mobile IAB state. For example, the indication may indicate that the network node is a mobile IAB node. The network node may output the indication via any suitable form of signaling, such as broadcast system information (e.g., system information block 1 (SIB1), RRC signaling, etc.). In some aspects, the indication may indicate one or more cells associated with the mobile IAB state. In some aspects, the indication may indicate cells associated with the mobile IAB state other than the cell implemented by the network node outputting the indication. For example, the indication may identify a list of candidate cells having a mobile IAB state. For example, the UE may receive assistance information indicating one or more cells or frequencies that may have a mobile IAB state (e.g., may belong to a mobile cell). This information may be provided in system information (SI) (e.g., SIB2, SIB3, SIB4, or another SIB) broadcast by the cell on which the UE is camped, provided in a dedicated RRC message (such as an RRC release message) when the UE connects to the network, provided via a reconfiguration message, or provided in an operations, administration, and maintenance (OAM) configuration. Providing a list of cells with a mobile IAB state may reduce the power consumption of the UE associated with obtaining the SIB of each neighboring cell to determine whether each neighboring cell sends an indication of a mobile IAB state. In some aspects, the UE may attempt to read system information from one or more cells (e.g., neighboring cells) to determine whether the one or more cells are associated with a mobile IAB state. For example, the UE may read the system information before performing initial access with one or more cells. The UE may use the system information to identify the onboard state with one or more cells, as described below.

[0092] As shown by reference numeral 710, the UE may identify an onboard status between the UE and a cell (e.g., a network node). Identifying the onboard status may occur before selecting a cell to camp on (e.g., during measurements on the cell), immediately before selecting a cell to camp on, or after selecting a cell to camp on. In some aspects, the onboard status between the UE and the cell may indicate that the UE is onboard a mobile entity attached to or associated with the network node. In some aspects, the onboard status between the UE and the cell may indicate that the UE is expected to remain in the coverage area of ​​the cell for a threshold length of time.

[0093] As indicated by reference numeral 715, in some aspects, the UE may identify the onboard state based on detecting a cell for a first threshold length of time. For example, the UE may detect the cell for a first threshold length of time and may identify the onboard state in response to detecting the cell for the first threshold length of time. The first threshold length of time may be configurable (e.g., the network node may output and the UE may receive configuration information indicating the first threshold length of time). In some aspects, the onboard state is based at least in part on detecting the cell for the first threshold length of time while the UE is camped on another cell not associated with the mobile IAB state. For example, the other cell may be a stationary cell (e.g., a cell not implemented by a mobile IAB node). Thus, the UE may identify the onboard state based at least in part on observing the mobile IAB cell for a second threshold length of time while camped on the stationary cell. During identification of the onboard state, the UE may be in a normal mobility state, a medium mobility state, or a high mobility state (e.g., as defined in 3GPP Technical Specification 38.304). The mobility state may correspond to the frequency with which the UE reselects (camps on) a new cell within a configured time interval. In some aspects, the determination of the onboard state based on the detection of a cell for a first threshold length of time may be applicable to all mobility states (including a normal mobility state, a medium mobility state, or a high mobility state). In some other aspects, the determination of the onboard state based on the detection of a cell for a first threshold length of time may be applicable to a proper subset of mobility states (e.g., one or more of a normal mobility state, a medium mobility state, or a high mobility state). For example, the UE may determine the onboard state based on the detection of a cell for a first threshold length of time only when the UE is in a medium mobility state or a high mobility state. Additionally or alternatively, parameters used to determine the onboard state (such as the length of the first threshold length of time, a measurement threshold, a measurement offset, etc.) may be derived from the UE's current mobility state.

[0094] As mentioned, the UE may identify an onboard state based at least in part on detecting a cell for a first threshold length of time. "Detecting a cell" may include detecting a signal transmitted by the cell. In some aspects, "detecting a cell" may include performing a measurement. For example, when the UE detects a signal transmitted by the cell and when a measurement of the signal (e.g., an RSRP measurement, an RSRQ measurement, an Srxlev measurement, an Squal measurement, or a combination thereof) meets a measurement threshold, the UE may detect the cell. Additionally or alternatively, the UE may detect the cell when a change in the measurement of the signal is below a threshold.

[0095] As shown in reference numeral 720, in some aspects, the UE may identify the cell as being onboard (or may maintain the cell as being onboard) based at least in part on being camped on the cell for a second threshold time length. In some aspects, the second threshold time length may be different from the first threshold time length. For example, the second threshold time length (e.g., the duration of time for declaring or maintaining the onboard state while already camped on the cell) may be shorter than the first threshold time length (e.g., the duration of time for identifying the cell as having the onboard state when the UE initially camps on the stationary cell). The length of the second threshold time length may be configurable (e.g., the UE may receive configuration information indicating the length of the second threshold time length). In some aspects, the length of the second threshold time length may be based at least in part on the mobility state of the UE. For example, the length of the second threshold time length may be different in a first mobility state (e.g., a high mobility state) than in a second mobility state (e.g., a normal mobility state).

[0096] As indicated by reference numeral 725, the UE may perform a cell selection or reselection operation based at least in part on the onboard state and at least in part on the cell being associated with the mobile IAB state. Details regarding the cell selection operation and the cell reselection operation are provided below.

[0097] In some aspects, the UE may prioritize the selection or reselection of a cell associated with a mobile IAB state over a stationary cell. For example, the UE may perform this prioritization by assigning a higher (or highest) absolute priority to a cell or frequency associated with a mobile IAB state. In this example, a rule may be defined that indicates that the highest priority is assigned to a cell associated with a mobile IAB state (or to an associated frequency), or appropriate parameters (e.g., an offset, or a scaling factor, or an absolute value) may be configured to apply to a cell (or associated frequency) associated with a mobile IAB state. In some aspects, the higher absolute priority may be configurable (e.g., the UE may assign a configured absolute priority to a given cell or frequency associated with a mobile IAB state). For another example, when ranking cells for cell reselection (e.g., based at least in part on RSRP measurements of the cells), a cell associated with a mobile IAB state may be assigned a higher (e.g., configurable) or highest ranking relative to a stationary cell. In this example, a rule indicating that the highest ranking is assigned to a cell associated with the mobile IAB state (or to an associated frequency) may be defined, or appropriate parameters (e.g., an offset, a scaling factor, or an absolute value) may be configured for ranking cells associated with the mobile IAB state (or associated frequencies). As another example, the UE may select a cell with the mobile IAB state for which a value (e.g., an R value, which may be obtained from the RSRP measurement quantity Q meas , Qoffset value and / or Qoffset temp The value is derived) is within a range of cells having the best value (eg, a range indicated by a rangeToBestCell parameter or a parameter similar to rangeToBestCell).

[0098] In some aspects, the UE may determine a mobility state based at least in part on the onboard state (as described above). For example, upon identifying the onboard state, the UE may assume a changed mobility state. For example, the UE may camp on a stationary cell and may determine a medium mobility state or a high mobility state. Upon entering the onboard state, the UE may determine a normal mobility state (e.g., it is expected that the UE will camp on the same cell for a relatively long period of time because the UE has an onboard state for that cell). This may have an impact on a reselection timer or hysteresis value for a cell selection operation or a cell reselection operation, as described elsewhere herein. For example, the UE may modify the reselection timer or hysteresis value. In some aspects, parameters used to determine the mobility state may be based at least in part on the onboard state. For example, parameters used to determine the mobility state (such as a time duration or a number of reselections) may be adjusted or selected based on the mobility state (e.g., different values ​​of the parameters may be used for different mobility states). As another example, a rule may be defined such that reselection between cells associated with the onboard state is not counted in the parameters used to determine the mobility state. For example, the UE may not consider continuous reselection of a mobile IAB cell for the mobility state detection criteria. This may avoid unnecessary promotion of the mobility state when the cell identifier of the mobile IAB cell changes, for example, due to a handover of a DU of the mobile IAB cell from one CU to another.

[0099] In some aspects, as mentioned above, the UE may reselect from a first cell associated with the mobile IAB node to a second cell associated with the mobile IAB node. For example, the UE may have an onboard state with respect to the first cell. For example, this may occur because the DU of the mobile IAB node may migrate from the first CU to the second CU (thereby causing a change in the cell identifier from the first cell to the second cell) or due to a cell identifier conflict causing a change in the cell identifier from the first cell to the second cell. In this example, when reselecting from the first cell associated with the mobile IAB node to the second cell associated with the mobile IAB node, the UE may maintain the onboard state. Additionally or alternatively, the UE may reset a timer associated with the onboard state (e.g., a second threshold time length) and may identify whether the UE is associated with the onboard state with respect to the second cell. For example, the UE may reset its timer and attempt to determine whether the UE has an onboard state with respect to the newly selected mobile IAB cell.

[0100] In some aspects, the UE may relax measurements or suppress relaxed measurements based at least in part on the onboard state. Typically, when in a low mobility state (which is different from the normal mobility, medium mobility, and high mobility states mentioned above) (which can be defined as observing a change in measurements on the serving cell that is less than a threshold for a length of time), or when the UE is not near a cell edge (which can be defined as observing measurements of the serving cell (e.g., RSRP or RSRQ) that are above a threshold for a length of time), the UE may relax measurements (referred to herein as using a baseline measurement configuration). After residing on a cell with an onboard state, these conditions may be met, resulting in relaxed measurement scheduling (e.g., a reduced frequency of cell measurements for reselection operations). The configuration for performing relaxed measurements may be indicated by system information (e.g., SIB2). However, the cell identifier of a cell may change (e.g., due to migration of an IAB DU from one CU to another). If the cell identifier changes frequently, the timer parameters for cell reselection (e.g., T SearchDeltaP ) may be frequently reset, resulting in a lack of relaxation of measurements, which may be desirable when the cell identifier changes frequently. Conversely, if the cell identifier does not change frequently, the UE may relax measurements, which can save power. However, there are cases where the cell identifier changes frequently enough that non-relaxed measurement scheduling may be beneficial, but does not change so frequently that the UE avoids a low mobility state. Therefore, when the UE would actually benefit from performing more frequent measurements due to the changed cell identifier, the UE may relax measurements. In some aspects, the UE may not relax measurements when camping on a cell with an onboard state, which ensures that the UE can measure the cell when the cell identifier changes. In some other aspects, the UE may perform cell measurements according to a measurement configuration corresponding to the onboard state. For example, when an onboard condition is identified, the UE may apply parameters (e.g., detection parameters, measurement parameters, and / or evaluation parameters) corresponding to the onboard state for declaring a low mobility state or a "near cell edge" state. For another example, the UE may apply a scaling factor to the configuration for relaxed measurements in order to reduce the duration of the relaxed measurements or shorten the periodicity of measurements in the relaxed measurement state. As another example, a configuration (e.g., a relaxedMeasurement parameter in SIB2) may indicate a configuration for relaxed measurements that is specific to a cell associated with a mobile IAB state (e.g., a mobile IAB cell), or may indicate a configuration for relaxed measurements in a cell-specific manner (for a specific cell) or a frequency-specific manner (for a specific frequency). In some aspects, the UE may receive signaling (e.g., configuration information) indicating whether the UE should perform measurement relaxation according to a typical procedure (as defined above) or based at least in part on the onboard state.

[0101] In some aspects, the UE may not be associated with an onboard state regarding a cell. For example, the UE may determine that the conditions for the onboard state (as described above) are not met. In this example, the UE may use a legacy process for cell selection or cell reselection (e.g., a process not based on the onboard state). Alternatively, the UE may deprioritize selection or reselection of cells associated with a mobile IAB state, which reduces the likelihood that the UE will perform frequent cell reselection due to camping on a mobile IAB cell that is likely to move away from the UE.

[0102] about Figure 7 The illustrated signaling may be performed using any combination of system information (e.g., SIB1 or remaining minimum system information) sent by a cell with onboard status, system information (e.g., SIB2, SIB3, SIB4, or another SIB) broadcast by another cell (e.g., a stationed cell, a neighboring cell), or a dedicated RRC message (e.g., an RRC release message) provided by the UE's serving cell. In some aspects, regarding Figure 7 Any one or more of the described parameters or values ​​may be pre-configured or defined by a wireless communication specification.

[0103] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0104] Figure 8 is a diagram illustrating an example process 800, performed, for example, by a UE, according to the present disclosure. Example process 800 is an example in which a UE (eg, UE 120) performs operations associated with mobility of a mobile IAB cell.

[0105] like Figure 8 As shown, in some aspects, process 800 may include receiving an indication that a cell is associated with a mobile IAB state (block 810). For example, a UE (e.g., using Figure 9 The depicted receiving component 902 and / or communication manager 906) can receive an indication that a cell is associated with a mobile IAB state, as described above. The mobile IAB state can indicate that the cell is a mobile cell.

[0106] like Figure 8 As further shown, in some aspects, process 800 may include performing a cell selection or reselection operation based at least in part on an onboard state between the UE and the cell and at least in part on the cell being associated with a mobile IAB state (block 820). Figure 9The depicted communication manager 906) may perform cell selection or reselection operations based at least in part on an onboard state between the UE and the cell and at least in part on the cell being associated with a mobile IAB state, as described above. The onboard state may indicate that the UE is onboard a mobile entity.

[0107] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0108] In a first aspect, process 800 includes detecting a cell for a first threshold length of time, wherein the onboard status is based at least in part on detecting the cell for the first threshold length of time.

[0109] In a second aspect, alone or in combination with the first aspect, the onboard state is based at least in part on detecting a cell for a first threshold length of time while the UE is camped on another cell not associated with the Mobile IAB state.

[0110] In a third aspect, alone or in combination with one or more of the first and second aspects, process 800 includes receiving configuration information indicating a first threshold length of time.

[0111] In a fourth aspect, alone or in combination with one or more of the first to third aspects, performing a cell selection or reselection operation further comprises selecting a cell to camp on based at least in part on an onboard status.

[0112] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 800 includes receiving information indicating a set of candidate cells potentially associated with a mobile IAB state, including the cell.

[0113] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 800 includes camping on the cell for a second threshold length of time, wherein the onboard state is based at least in part on camping on the cell for the second threshold length of time.

[0114] In a seventh aspect, alone or in combination with one or more of aspects 1 to 6, the cell is a first cell, and performing a cell selection or reselection operation based at least in part on the onboard state further includes: reselecting a second cell associated with the mobile IAB state, and maintaining the onboard state with respect to the second cell.

[0115] In an eighth aspect, alone or in combination with one or more of aspects 1 to 7, the cell is a first cell, and performing a cell selection or reselection operation based at least in part on the onboard state further comprises: reselecting a second cell associated with the mobile IAB state, and resetting a timer associated with the second threshold time length.

[0116] In a ninth aspect, alone or in combination with one or more of aspects 1 to 8, performing cell selection or reselection operations based at least in part on the onboard status further comprises prioritizing selection or reselection of cells associated with a mobile IAB state.

[0117] In a tenth aspect, alone or in combination with one or more of aspects one to nine, performing a cell selection or reselection operation based at least in part on an onboard state further comprises modifying a reselection timer or a hysteresis timer based at least in part on entering the onboard state.

[0118] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, modifying the reselection timer is based at least in part on a mobility state parameter of the UE.

[0119] In a twelfth aspect, alone or in combination with one or more of aspects 1 to eleven, performing a cell selection or reselection operation based at least in part on an onboard state further comprises modifying parameters for determining a mobility state parameter of the UE based at least in part on the onboard state.

[0120] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, a cell selection or reselection operation is performed based at least in part on a mobility state parameter, and reselection between cells associated with a mobile IAB state is not included in the parameters used to determine the mobility state parameter.

[0121] In a fourteenth aspect, alone or in combination with one or more of aspects one to thirteen, performing a cell selection or reselection operation based at least in part on an onboard state further comprises performing cell measurements according to a baseline measurement configuration based at least in part on the onboard state.

[0122] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, performing a cell selection or reselection operation based at least in part on the onboard status further comprises performing cell measurements according to a measurement configuration corresponding to the onboard status.

[0123] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, process 800 includes receiving information indicating use of a measurement configuration corresponding to an onboard state.

[0124] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the measurement configuration is specific to at least one of: a cell associated with a mobile IAB state, a specific cell, or a specific frequency.

[0125] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, performing a cell selection or reselection operation based at least in part on the onboard status further comprises reselecting another cell not associated with the onboard status.

[0126] In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, process 800 includes performing another cell selection or reselection operation that deprioritizes cells associated with the mobile IAB state.

[0127] although Figure 8 Example blocks of process 800 are shown, but in some aspects, process 800 may include Figure 8 The blocks depicted may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0128] Figure 9 9 is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a UE, or a UE may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902, a sending component 904, and / or a communication manager 906, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 906 is a communication manager that is configured to communicate with one another. Figure 1 The described communication manager 140. As shown, the device 900 can communicate using a receiving component 902 and a sending component 904 with another device 908, such as a UE or a network node such as a CU, DU, RU, IAB node, or base station.

[0129] In some aspects, the apparatus 900 may be configured to perform the Figures 4 to 7 Additionally or alternatively, the apparatus 900 may be configured to perform one or more of the processes described herein (such as Figure 8 In some aspects, Figure 9 The device 900 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, one or more components of the UE described. Figure 9 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0130] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 908. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0131] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 908. In some aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 908. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 908. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0132] The communications manager 906 can support the operation of the receiving component 902 and / or the sending component 904. For example, the communications manager 906 can receive information associated with configuring the receipt of communications by the receiving component 902 and / or the sending of communications by the sending component 904. Additionally or alternatively, the communications manager 906 can generate and / or provide control information to the receiving component 902 and / or the sending component 904 to control the receipt and / or sending of communications.

[0133] Receiving component 902 can receive an indication that a cell is associated with a mobile IAB state.Communication manager 906 can perform a cell selection or reselection operation based at least in part on an onboard state between the UE and the cell and at least in part on the cell being associated with a mobile IAB state.

[0134] The communications manager 906 may detect the cell for a first threshold length of time, wherein the onboard status is based at least in part on detecting the cell for the first threshold length of time.

[0135] Receiving component 902 can receive configuration information indicating a first threshold length of time.

[0136] Receiving component 902 can receive information indicating a set of candidate cells potentially associated with the mobile IAB state, including the cell.

[0137] The communications manager 906 may camp on the cell for a second threshold length of time, wherein the onboard status is based at least in part on camping on the cell for the second threshold length of time.

[0138] Receiving component 902 can receive information indicating use of a measurement configuration corresponding to an onboard state.

[0139] The communications manager 906 may perform another cell selection or reselection operation that deprioritizes cells associated with the Mobile IAB state.

[0140] Figure 9 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 9 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 9 Two or more components shown may be implemented in a single component, or Figure 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The illustrated set of components (one or more) may be described as being executable by Figure 9 Another group of components is shown performing one or more functions.

[0141] The following provides an overview of some aspects of the disclosure:

[0142] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an indication that a cell is associated with a mobile integrated access and backhaul (IAB) state indicating that the cell is a mobile cell; and performing a cell selection or reselection operation based at least in part on an onboard state between the UE and the cell and at least in part on the cell being associated with the mobile IAB state, wherein the onboard state indicates that the UE is onboard a mobile entity.

[0143] Aspect 2: The method according to aspect 1, further comprising: detecting the cell for a first threshold time length, wherein the onboard status is based at least in part on detecting the cell for the first threshold time length.

[0144] Aspect 3: The method of aspect 2, wherein the onboard state is based at least in part on detecting the cell for the first threshold length of time while the UE is camped on another cell not associated with the mobile IAB state.

[0145] Aspect 4: The method according to aspect 2 further comprises receiving configuration information indicating the first threshold time length.

[0146] Aspect 5: The method according to any one of aspects 1 to 4, wherein performing the cell selection or reselection operation further comprises: selecting the cell to camp on based at least in part on the onboard status.

[0147] Aspect 6: The method according to any one of aspects 1 to 5, further comprising receiving information indicating a set of candidate cells potentially associated with the mobile IAB state, including the cell.

[0148] Aspect 7: The method according to any one of aspects 1 to 6, further comprising: camping on the cell for a second threshold time length, wherein the onboard state is at least partially based on camping on the cell for the second threshold time length.

[0149] Aspect 8: A method according to Aspect 7, wherein the cell is a first cell, and wherein performing the cell selection or reselection operation based at least in part on the onboard state further includes: reselecting a second cell associated with the mobile IAB state; and maintaining the onboard state with respect to the second cell.

[0150] Aspect 9: A method according to Aspect 7, wherein the cell is a first cell, and wherein performing the cell selection or reselection operation based at least in part on the onboard state also includes: reselecting a second cell associated with the mobile IAB state; and resetting a timer associated with the second threshold time length.

[0151] Aspect 10: The method according to any one of aspects 1 to 9, wherein performing the cell selection or reselection operation based at least in part on the onboard status further comprises: prioritizing selection or reselection of cells associated with the mobile IAB status.

[0152] Aspect 11: A method according to any one of aspects 1 to 10, wherein performing the cell selection or reselection operation based at least in part on the onboard state further comprises: modifying a reselection timer or a hysteresis timer based at least in part on entering the onboard state.

[0153] Aspect 12: The method of aspect 11, wherein modifying the reselection timer is based at least in part on a mobility state parameter of the UE.

[0154] Aspect 13: A method according to any one of Aspects 1 to 12, wherein performing the cell selection or reselection operation based at least in part on the onboard state further includes: modifying parameters used to determine the mobility state parameters of the UE based at least in part on the onboard state.

[0155] Aspect 14: A method according to any one of aspects 1 to 13, wherein the cell selection or reselection operation is performed at least in part based on a mobility state parameter, and wherein reselection between cells associated with the mobile IAB state is not included in the parameters used to determine the mobility state parameter.

[0156] Aspect 15: The method of any one of Aspects 1 to 14, wherein performing the cell selection or reselection operation based at least in part on the onboard status further comprises: performing cell measurements according to a baseline measurement configuration based at least in part on the onboard status.

[0157] Aspect 16: The method according to any one of aspects 1 to 15, wherein performing the cell selection or reselection operation based at least in part on the onboard status further comprises: performing cell measurements according to a measurement configuration corresponding to the onboard status.

[0158] Aspect 17: The method according to aspect 16, further comprising receiving information indicating use of the measurement configuration corresponding to the onboard state.

[0159] Aspect 18: The method according to aspect 16, wherein the measurement configuration is specific to at least one of the following: a cell associated with the mobile IAB state, a specific cell, or a specific frequency.

[0160] Aspect 19: The method according to any one of aspects 1 to 18, wherein performing the cell selection or reselection operation based at least in part on the onboard status further comprises: reselecting another cell not associated with the onboard status.

[0161] Aspect 20: The method according to aspect 19, further comprising performing another cell selection or reselection operation to reduce the priority of the cell associated with the mobile IAB state.

[0162] Aspect 21: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in aspects 1 to 20.

[0163] Aspect 22: A device for wireless communication, the device comprising: a memory and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 20.

[0164] Aspect 23: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 20.

[0165] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 20.

[0166] Aspect 25: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 20.

[0167] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

[0168] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of different forms of hardware and / or hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, no reference is made herein to specific software code to describe the operation and behavior of the systems and / or methods, as those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0169] As used herein, "satisfying a threshold" may mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0170] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other arrangement of a, b, and c).

[0171] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "cluster" are intended to include one or more projects and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving an indication that a cell is associated with a mobile integrated access and backhaul (IAB) state indicating that the cell is a mobile cell; as well as A cell selection or reselection operation is performed based at least in part on an onboard status of the UE and at least in part on the cell being associated with the mobile IAB state, wherein the onboard status indicates that the UE is onboard a mobile entity.

2. The UE of claim 1 , wherein to perform the cell selection or reselection operation, the one or more processors are configured to select the cell to camp on based at least in part on the onboard status.

3. The UE of claim 1 , wherein to receive the indication, the one or more processors are configured to receive information indicating a set of candidate cells associated with the mobile IAB state. 4 . The UE of claim 3 , wherein the information indicating the set of candidate cells is in System Information Block 4 (SIB4). 5 . The UE of claim 1 , wherein to receive the indication, the one or more processors are configured to receive the indication in a system information block 1 (SIB1).

6. The UE of claim 1 , wherein to perform the cell selection or reselection operation based at least in part on the onboard state, the one or more processors are configured to prioritize selection or reselection of cells associated with the mobile IAB state.

7. The UE of claim 6, wherein to prioritize the selection or reselection, the one or more processors are configured to assign a highest priority to the cell associated with the mobile IAB state.

8. The UE of claim 1 , wherein the one or more processors are further configured to: Camping on the cell for a second threshold length of time, wherein the onboard status is based at least in part on camping on the cell for the second threshold length of time.

9. The UE of claim 8, wherein the cell is a first cell, and wherein to perform the cell selection or reselection operation based at least in part on the onboard status, the one or more processors are configured to: reselecting a second cell associated with the mobile IAB state; and The onboard state regarding the second cell is maintained.

10. The UE of claim 8, wherein the cell is a first cell, and wherein to perform the cell selection or reselection operation based at least in part on the onboard status, the one or more processors are configured to: reselecting a second cell associated with the mobile IAB state; and A timer associated with the second threshold time length is reset.

11. The UE of claim 1 , wherein to perform the cell selection or reselection operation based at least in part on the onboard state, the one or more processors are configured to modify a parameter used to determine a mobility state parameter of the UE based at least in part on the onboard state.

12. The UE of claim 1 , wherein the cell selection or reselection operation is based at least in part on a mobility state parameter, and wherein reselection between cells associated with the mobile IAB state does not factor into parameters used to determine the mobility state parameter.

13. The UE of claim 1 , wherein to perform the cell selection or reselection operation based at least in part on the onboard status, the one or more processors are configured to perform cell measurements according to a baseline measurement configuration based at least in part on the onboard status.

14. The UE of claim 1, wherein to perform the cell selection or reselection operation based at least in part on the onboard state, the one or more processors are configured to perform cell measurements according to a measurement configuration corresponding to the onboard state.

15. The UE of claim 1, wherein to perform the cell selection or reselection operation based at least in part on the onboard state, the one or more processors are configured to reselect another cell not associated with the onboard state.

16. The UE of claim 1 , wherein the one or more processors are further configured to: The cell is detected for a first threshold length of time, wherein the onboard status is based at least in part on detecting the cell for the first threshold length of time.

17. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an indication that a cell is associated with a mobile integrated access and backhaul (IAB) state indicating that the cell is a mobile cell; as well as A cell selection or reselection operation is performed based at least in part on an onboard status between the UE and the cell and based at least in part on the cell being associated with the mobile IAB state, wherein the onboard status indicates that the UE is onboard a mobile entity.

18. The method according to claim 17, further comprising: The cell is detected for a first threshold length of time, wherein the onboard status is based at least in part on detecting the cell for the first threshold length of time.

19. The method of claim 18, wherein the onboard state is based at least in part on detecting the cell for the first threshold length of time while the UE is camped on another cell not associated with the mobile IAB state.

20. A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: receiving an indication that a cell is associated with a mobile integrated access and backhaul (IAB) state indicating that the cell is a mobile cell; as well as A cell selection or reselection operation is performed based at least in part on an onboard status between the UE and the cell and based at least in part on the cell being associated with the mobile IAB state, wherein the onboard status indicates that the UE is onboard a mobile entity.

Images