Mobility history reporting by wireless serving nodes

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a wireless service node may determine mobility history information associated with the wireless service node, wherein the mobility history information is associated with relative mobility between the wireless service node and one or more reported cells; and send the mobility history information associated with the wireless service node to a child node of the wireless service node. Many other aspects are provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 000,192, filed on March 26, 2020, entitled “MOBILITY HISTORY REPORTING BY A WIRELESS SERVING NODE,” and U.S. Non-Provisional Patent Application No. 17 / 191,397, filed on March 3, 2021, entitled “MOBILITY HISTORY REPORTING BY A WIRELESS SERVING NODE,” which are hereby incorporated by reference into this document. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and techniques and apparatus for mobility history reporting by a wireless serving node. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support 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 multiple base stations (BSs) that can support communications for multiple user equipments (UEs). A UE may communicate with a BS via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a BS to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Head, Transmit Receive Point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user devices to communicate at the city, country, region and even global level. NR, also known as 5G, is a set of enhancements to the LTE mobile standard released by 3GPP. NR aims to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards, which use orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and support beamforming, multiple-input multiple-output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR and other wireless access technologies remain very useful. Summary of the invention

[0007] In some aspects, a wireless communication method performed by a first wireless node including a wireless service node may include: determining mobility history information associated with the wireless service node, wherein the mobility history information is associated with relative mobility between the wireless service node and one or more reported cells; and sending the mobility history information associated with the wireless service node to a second wireless node.

[0008] In some aspects, a method of wireless communications performed by a wireless service node may include: receiving, from a parent node of the wireless service node, mobility history information associated with the parent node, wherein the mobility history information is associated with relative mobility between the parent node and one or more reported cells; and performing an action based at least in part on receiving the mobility history information associated with the parent node.

[0009] In some aspects, a first wireless node including a wireless service node for wireless communication may include a memory and one or more processors operably coupled to the memory. The memory and the one or more processors may be configured to: determine mobility history information associated with the wireless service node, wherein the mobility history information is associated with relative mobility between the wireless service node and one or more reported cells; and send the mobility history information associated with the wireless service node to a child node of the wireless service node.

[0010] In some aspects, a wireless service node for wireless communication may include a memory and one or more processors operably coupled to the memory. The memory and the one or more processors may be configured to: receive, from a parent node of the wireless service node, mobility history information associated with the parent node, wherein the mobility history information is associated with relative mobility between the parent node and one or more reported cells; and perform an action based at least in part on receiving the mobility history information associated with the parent node.

[0011] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a wireless service node, the one or more instructions may cause the one or more processors to: determine mobility history information associated with the wireless service node, wherein the mobility history information is associated with relative mobility between the wireless service node and one or more reported cells; and send the mobility history information associated with the wireless service node to a child node of the wireless service node.

[0012] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a wireless service node, the one or more instructions may cause the one or more processors to: receive, from a parent node of the wireless service node, mobility history information associated with the parent node, wherein the mobility history information is associated with relative mobility between the parent node and one or more reported cells; and perform an action based at least in part on receiving the mobility history information associated with the parent node.

[0013] In some aspects, an apparatus for wireless communication may include: a component for determining mobility history information associated with the apparatus, wherein the mobility history information is associated with a relative mobility between the apparatus and one or more reporting cells; and a component for sending the mobility history information associated with the apparatus to a subnode of the apparatus.

[0014] In some aspects, an apparatus for wireless communication may include: a component for receiving mobility history information associated with a parent node of the apparatus from the parent node, wherein the mobility history information is associated with a relative mobility between the parent node and one or more reporting cells; and an apparatus for performing an action based at least in part on receiving the mobility history information associated with the parent node.

[0015] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as substantially described herein with reference to and illustrated by the drawings and description.

[0016] 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 disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, their organization and methods of operation, and related advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects are described in the present disclosure by the description of some examples, it will be understood by those skilled in the art that these 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 embodiments or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing equipment, medical devices, or devices supporting artificial intelligence). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. The device incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or adders). The aspects described herein are intended to be practiced in devices, components, systems, distributed arrangements, or end-user devices of various sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description of the above brief summary may be made with reference to some aspects, some of which are shown in the accompanying drawings. However, it should be noted that the accompanying drawings only show certain typical aspects of the present disclosure and should not be considered as limiting the scope thereof, as the description may admit of other equally effective aspects. The same reference numerals in different drawings may represent the same or similar elements.

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

[0020] Figure 2 is a diagram illustrating an example of communication between a base station and a UE in a wireless network according to the present disclosure.

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

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

[0023] Figure 5 is a diagram illustrating an example of a mobility history report according to the present disclosure.

[0024] Figure 6 and Figure 7 is a diagram illustrating an example process performed, for example, by a wireless node in accordance with the present disclosure. DETAILED DESCRIPTION

[0025] Various aspects of the present disclosure will be described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented 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 to make the present disclosure thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings herein, it should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect disclosed herein, whether implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method, which is practiced using other structures, functions, or structures and functions in addition to or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein can be embodied by one or more elements of the claims.

[0026] Several aspects of telecommunication systems will now be described 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, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and design constraints on the overall system.

[0027] It should be noted that although various aspects may be described herein using terms generally associated with 5G or NR radio access technologies (RATs), various aspects of the present disclosure can be applied to other RATs, such as 3G RATs, 4G RATs, and / or RATs beyond 5G (e.g., 6G).

[0028] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. In addition to the actual example, the wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network. The wireless network 100 may include a plurality of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR BS, Node B, gNB, 5G Node B (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0029] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). The BS of a macro cell may be referred to as a macro BS. The BS of a pico cell may be referred to as a pico BS. The BS of a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, BS 110a may be a macro BS of macro cell 102a, BS 110b may be a pico BS of pico cell 102b, and BS 110c may be a femto BS of femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably herein.

[0030] In some aspects, the cells need not be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as direct physical connections, virtual networks, etc. using any suitable transport network.

[0031] The wireless network 100 may also include a relay station. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and deliver data transmissions to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown, a relay base station 110d may communicate with a macro BS 110a and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay base station may also be referred to as a relay BS, a relay station, a relay, or the like.

[0032] The wireless network 100 may be a heterogeneous network including different types of BSs, such as a macro BS, a pico BS, a femto BS, a relay BS, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0033] A network controller 130 may be coupled to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other, for example, directly or indirectly via a wireless or wired backhaul.

[0034] UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. UEs may also be referred to as access terminals, terminals, mobile stations, subscriber units, stations, etc. UEs may be cellular phones (e.g., smart phones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablet computers, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices or equipment, biosensors / devices, wearable devices (smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), entertainment devices (e.g., music or video devices, or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system devices, or any other suitable device configured to communicate via wireless or wired media.

[0035] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node may provide a connection to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as client equipment (CPE). UE 120 may be included in a housing that houses the components of UE 120. In some aspects, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0036] Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific RAT and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, channel, etc. Each frequency can 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 can be deployed.

[0037] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary for communicating with each other) using one or more bypass channels. For example, UE 120 may 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, etc.), mesh networks, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations performed by base station 110 as described elsewhere herein.

[0038] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, frequency bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 can communicate using an operating frequency band having a first frequency range (FR1) from 410 MHz to 7.125 GHz, and / or can communicate using an operating frequency band having a second frequency range (FR2) from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a "below 6 GHz" frequency band. Similarly, FR2 is also often referred to as a "millimeter wave" frequency band, although it is different from the extremely high frequency (EHF) frequency band (30 GHz–300 GHz) determined by the International Telecommunication Union (ITU) as a "millimeter wave" frequency band. Therefore, unless otherwise stated, it should be understood that the term "below 6 GHz" and the like, if used herein, can broadly represent frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise stated, it should be understood that the term "millimeter wave", etc., if used herein, can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is expected that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0039] As mentioned above, Figure 1 are provided as examples. Other examples may be related to Figure 1 Different than described.

[0040] Figure 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0041] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and generate synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). If applicable, a 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, and may provide T output symbol streams to T modulators (MOD) 232a through 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

[0042] At UE 120, antennas 252a to 252r may receive downlink signals from base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data of UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of the UE 120 may be included in the housing 284 .

[0043] 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 base station 110 via the communication unit 294.

[0044] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or may be included in one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays, etc. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include coplanar antenna element sets and / or non-coplanar antenna element sets. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements within a single housing and / or antenna elements within multiple housings. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antennas coupled to one or more transmit and / or receive components (e.g., Figure 2 One or more antenna elements of one or more components).

[0045] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 254) of the UE 120 may be included in a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modulator and / or demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. A processor (e.g., controller / processor 280) and memory 282 may use the transceiver to perform aspects of any of the methods described herein (e.g., as described in reference to Figure 5-Figure 7 described).

[0046] At the base station 110, uplink signals from the UE 120 and other UEs, if applicable, may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, and further processed by the receive processor 238 to obtain decoded data and control information delivered by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 for scheduling the UE 120 for downlink and / or uplink communications. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of the base station 110 may be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modulator and / or demodulator 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. A processor (e.g., controller / processor 240) and memory 242 may use the transceiver to perform aspects of any of the methods described herein (e.g., as described in reference to Figure 5-Figure 7 described).

[0047] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the may perform one or more techniques associated with mobility history reporting of a wireless service node, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Figure 6 The process of 600 Figure 7 The operations of process 700 and / or other processes described herein may be performed. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, 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, when one or more instructions are executed by one or more processors of base station 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion and / or interpretation), it may cause one or more processors, UE 120 and / or base station 110 to perform or direct, for example Figure 6 The process of 600 Figure 7The operations of process 700 and / or other processes described herein. In some aspects, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0048] In some aspects, a first wireless node including a wireless service node may include: components for determining mobility history information associated with the wireless service node, wherein the mobility history information is associated with relative mobility between the wireless service node and one or more reported cells; and components for sending the mobility history information associated with the wireless service node to a second wireless node. In some aspects, these components may include in conjunction with Figure 2 One or more components of the UE 120 described herein, such as the controller / processor 280, the transmit processor 264, the TX MIMO processor 266, the MOD 254, the antenna 252, the DEMOD 254, the MIMO detector 256, the receive processor 258, etc. In some aspects, these components may include a combination of Figure 2 One or more components of base station 110 are depicted, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and the like.

[0049] In some aspects, a wireless service node may include: means for receiving, from a parent node of the wireless service node, mobility history information associated with the parent node, wherein the mobility history information is associated with a relative mobility between the parent node and one or more reported cells; and means for performing an action based at least in part on receiving the mobility history information associated with the parent node. In some aspects, these means may include in conjunction with Figure 2 One or more components of the UE 120 described herein, such as the controller / processor 280, the transmit processor 264, the TX MIMO processor 266, the MOD 254, the antenna 252, the DEMOD 254, the MIMO detector 256, the receive processor 258, etc. In some aspects, these components may include a combination of Figure 2 One or more components of base station 110 are depicted, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and the like.

[0050] Although Figure 2The blocks in the 200 are illustrated as distinct components, but the functionality described above with respect to the blocks may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functionality described for 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.

[0051] As mentioned above, Figure 2 are provided as examples. Other examples may be related to Figure 2 Different than described.

[0052] Figure 3 is a diagram illustrating an example 300 of a radio access network according to the present disclosure.

[0053] As shown by reference numeral 305, a traditional (e.g., 3G, 4G, or LTE) radio access network may include multiple base stations 310 (e.g., access nodes (ANs)), each of which communicates with a core network via a wired backhaul link 315 such as a fiber optic connection. The base stations 310 may communicate with UEs 320 via access links 325, which may be wireless links. In some aspects, Figure 3 The base station 310 shown may be Figure 1 The base station 110 is shown. In some aspects, Figure 3 The UE 320 shown may be Figure 1 UE 120 is shown.

[0054] As shown in the reference numeral 330, 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 base station is an anchor base station 335, which communicates with the core network via a wired backhaul link 340, such as a fiber connection. The anchor base station 335 may also be referred to as an IAB-donor (or IAB-donor). The IAB network may include one or more non-anchor base stations 345, sometimes referred to as relay base stations or IAB nodes (or IAB-nodes). The non-anchor base station 345 may communicate directly or indirectly with the anchor base station 335 via one or more backhaul links 350 (e.g., via one or more non-anchor base stations 345) to form a backhaul path to the core network for carrying backhaul traffic. The backhaul link 350 may be a wireless link. The anchor base station (or multiple) 335 and / or the non-anchor base station (or multiple) 345 may communicate with one or more UEs 355 via an access link 360, which may be a wireless link for carrying access traffic. In some aspects, Figure 3 The anchor base station 335 and / or the non-anchor base station 345 shown may be Figure 1 The base station 110 is shown. In some aspects, Figure 3 The UE 355 shown may be Figure 1 UE 120 is shown.

[0055] As shown in the reference numeral 365, in some aspects, the radio access network including the IAB network can utilize millimeter wave technology and / or directional communication (e.g., beamforming) to communicate between base stations and / or UEs (e.g., between two base stations, between two UEs, and / or between a base station and a UE). For example, a wireless backhaul link 370 between base stations can use millimeter wave signals to carry information and / or can use beamforming to point to a target base station. Similarly, a wireless access link 375 between a UE and a base station can use millimeter wave signals and / or can point to a target wireless node (e.g., a UE and / or a base station). In this way, inter-link interference can be reduced.

[0056] Figure 3 The configuration of the base station and UE in is shown as an example, and other examples are conceivable. For example, Figure 3 The one or more base stations shown in can be replaced by one or more UEs communicating 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 can refer to a UE that communicates directly with a base station (e.g., an anchor base station or a non-anchor base station).

[0057] As mentioned above, Figure 3 are provided as examples. Other examples may be related to Figure 3 Different than described.

[0058] Figure 4 is a diagram illustrating an example 400 of an IAB network architecture according to the present disclosure.

[0059] like Figure 4As shown, the IAB network may include an IAB host 405 (shown as an IAB host) connected to the core network via a wired connection (shown as a wired backhaul). For example, the Ng interface of the IAB host 405 may terminate at the core network. Additionally or alternatively, the IAB host 405 may be connected to one or more devices (e.g., AMF) that provide core access and mobility management functions of the core network. In some aspects, the IAB host 405 may include a base station 110, such as an anchor base station, as described above in conjunction with 3. As shown, the IAB host 405 may include a central unit (CU) that may perform access node controller (ANC) functions and / or AMF functions. The CU may configure the distributed unit (DU) of the IAB host 405 and / or may configure one or more IAB nodes 410 (e.g., MTs and / or DUs of the IAB nodes 410) connected to the core network via the IAB host 405. Thus, the CU of the IAB host 405 may control and / or configure the entire IAB network connected to the core network via the IAB host 405, such as by using control messages and / or configuration messages (e.g., Radio Resource Control (RRC) configuration messages or F1 Application Protocol (F1AP) messages).

[0060] like Figure 4 As further shown in the figure, the IAB network may include IAB nodes 410 (shown as IAB node 1, IAB node 2 and IAB node 3) connected to the core network via an IAB host 405. As shown in the figure, the IAB node 410 may include a mobile terminal (MT) function (sometimes also referred to as a UE function (UEF)), and may include a DU function (sometimes also referred to as an access node function (ANF)). The MT function of an IAB node 410 (e.g., a child node) may be controlled and / or scheduled by another IAB node 410 (e.g., a parent node of the child node) and / or an IAB host 405. The DU function of an IAB node 410 (e.g., a parent node) may control and / or schedule other IAB nodes 410 (e.g., a child node of the parent node) and / or UE 120. Therefore, the DU may be referred to as a scheduling node or a scheduling component, and the MT may be referred to as a scheduled node or a scheduled component. In some aspects, the IAB host 405 may include the DU function but not the MT function. That is, the IAB host 405 may configure, control and / or schedule the communication of the IAB node 410 and / or the UE 120. The UE 120 may include only the MT function, but not the DU function. That is, the communication of the UE 120 may be controlled and / or scheduled by the IAB host 405 and / or the IAB node 410 (e.g., the parent node of the UE 120).

[0061] When the first node controls and / or schedules the communication of the second node (for example, when the first node provides the DU function for the MT function of the second node), the first node can be referred to as the parent node of the second node, and the second node can be referred to as the child node of the first node. The child node of the second node can be referred to as the grandchild node of the first node. Therefore, the DU function of the parent node can control and / or schedule the communication of the child node of the parent node. The parent node can be the IAB host 405 or the IAB node 410, and the child node can be the IAB node 410 or the UE 120. The communication of the MT function of the child node can be controlled and / or scheduled by the parent node of the child node.

[0062] like Figure 4 As further shown in FIG. 4 , the link between UE 120 (e.g., which has only MT functionality but no DU functionality) and IAB host 405, or the link between UE 120 and IAB node 410, may be referred to as access link 415. Access link 415 may be a wireless access link that provides wireless access to the core network to UE 120 via IAB host 405 and optionally via one or more IAB nodes 410. Therefore, Figure 4 The network shown may be referred to as a multi-hop network or a wireless multi-hop network.

[0063] like Figure 4 As further shown in the figure, the link between the IAB host 405 and the IAB node 410 or between two IAB nodes 410 can be referred to as a backhaul link 420. The backhaul link 420 can be a wireless backhaul link that provides wireless access to the core network to the IAB node 410 via the IAB host 405 and optionally via one or more other IAB nodes 410. And / or space resources can be shared between the access link 415 and the backhaul link 420. In some aspects, the backhaul link 420 can be a primary backhaul link or an auxiliary backhaul link (e.g., a backup backhaul link). In some aspects, if the primary backhaul link fails, becomes congested and / or becomes overloaded, as well as other situations, the auxiliary backhaul link can be used. For example, if the primary backhaul link between the IAB node 2 and the IAB node 1 fails, the backup link 425 between the IAB node 2 and the IAB node 3 can be used for backhaul communication. As used herein, a node or wireless node can refer to the IAB host 405 or the IAB node 410.

[0064] In the IAB network, network resources (e.g., time resources, frequency resources, space resources, etc.) used for wireless communication can be shared between the parent link 425 of the IAB node 410 (shown as link 420 / 425 for IAB node 1) and the child link 430 of the IAB node 410 (shown as link 420 / 430 for IAB node 1). When the IAB node 410 uses time division multiplexing (TDM) between the parent link 425 and the child link 430, the IAB node 410 is subject to a half-duplex constraint, which means that the IAB node 410 cannot send and receive information at the same time (e.g., cannot communicate via the parent link 425 of the IAB node 410 and the child link 430 of the IAB node 410 at the same time). This limitation may result in high latency in communication.

[0065] In order to reduce the latency, increase robustness and expand the coverage of the IAB network, the IAB network may be over-deployed. For example, there may be multiple IAB hosts 405 and / or IAB nodes 410 with overlapping coverage, there may be multiple routes from a specific UE 120 and / or IAB node 410 to another IAB node and / or IAB host 405, etc. For example, because millimeter wave communication has high signal attenuation during propagation, IAB nodes 410 with overlapping coverage can be deployed to extend the coverage in the IAB network and mitigate such signal attenuation. In addition, because millimeter wave communication is susceptible to link blocking and link failure, IAB nodes 410 with overlapping coverage can be deployed to improve the robustness of the IAB network.

[0066] In some cases, in order to improve the reliability of transmission in the IAB network, packets can be sent along multiple paths to a destination (e.g., an IAB node, an IAB host, a UE, etc.). For example, PDCP duplication can be used at the CU and / or the UE to improve reliability. However, PDCP duplication can result in significant overhead. Some techniques and devices described herein enable network coding to be used in the IAB network. Network coding improves reliability while using less resource overhead than PDCP duplication.

[0067] As mentioned above, Figure 4 are provided as examples. Other examples may be related to Figure 4 Different than described.

[0068] In LTE, if capable, the UE can track the cells where the UE resides in idle and / or connected mode. This mobility history information can be reported to the network, which can use the information to better estimate the mobility state of the UE and adjust the UE's parameters accordingly. The network can also use the submitted information for more efficient network planning and management. NR has also been developed to include a similar process for UE to submit mobility history information.

[0069] In NR, as part of the mobile IAB, the NR network may have cells that are mobile - cells that may be moving. It has been recognized that having a reliable estimate of the relative mobility state between users and cells may be useful for optimizing various signaling and procedures. For example, it has been proposed that the available mobility information and measurements may be used to classify different users and / or their UEs based on their mobility relative to a given cell. Such classification may be used, for example, to prioritize services and resource management for one group over another, to optimally set various parameters for the operation of different groups, etc.

[0070] In some aspects of the techniques and apparatus described herein, a wireless service node (e.g., a wireless node, a base station, a mobile base station, a child node, a parent node, etc.) may send a mobility history report to a child node (e.g., a UE, a wireless node, a base station, a mobile base station, etc.). The mobility history report may include mobility history information that may be used by the wireless node and / or the network to select a cell, manage a mobile cell and corresponding resources, etc. In some aspects, the mobility history information may include an entry time corresponding to a time when the wireless service node enters a visited cell, an exit time corresponding to a time when the wireless service node exits a visited cell, a duration of time that the wireless service node visits the cell, etc. In this manner, aspects of the techniques described herein may facilitate tracking activity patterns of wireless service nodes, which may facilitate more efficient management of resources allocated by and / or to the wireless service node.

[0071] In some aspects, the mobility history information may include mobility state information associated with the wireless service node. In some aspects, the mobility state information associated with the wireless service node may include planned mobility state information. The planned mobility state information may include information associated with the planned and / or predicted future mobility of the wireless service node. In some aspects, the planned mobility state information may include the duration of the cell provided by the wireless service node that will have the current motion state, the next motion state of the cell, the next mobility level, etc. In this way, the child node and / or other network nodes can use the planned and / or predicted mobility state information to more effectively allocate resources, perform handovers, perform cell reselection, etc.

[0072] Figure 5 is a diagram illustrating an example 500 of a mobility history report according to the present disclosure. As shown, a wireless service node 505 may communicate with a set of child nodes 510 (shown as "child node A," "child node B," ..., "child node N").

[0073] In some aspects, the wireless service node 505 may be a parent node of the set of child nodes 510. In some aspects, the wireless service node 505 may include a UE, a DU of an IAB node, an MT component of an IAB node, etc. In some aspects, the child nodes of the set of child nodes 510 may include a UE, a DU of an IAB node, an MT component of an IAB node, etc.

[0074] As indicated by reference numeral 515, the wireless node 520 providing the reported cell 525 may transmit the mobility state information associated with the reported cell 525, and the wireless service node 505 may receive the mobility state information associated with the reported cell 525. The reported cell 525 may include a cell about which the wireless service node 505 reports mobility history information to one or more sub-nodes in the set of sub-nodes 510.

[0075] The wireless service node 505 may report mobility history information associated with any number of reported cells. The reported cells may include mobile cells, stationary cells, cells that the wireless service node 505 has visited, neighboring cells that have been detected by the visited cells and / or the wireless service node 505, and the like. In some aspects, the wireless service node 505 may be a mobile wireless IAB node, and the reported cells 525 may be cells that the wireless service node 505 camps on. The cells that the wireless service node 505 camps on may include cells that the wireless service node has visited for a duration that satisfies a camping threshold.

[0076] In some aspects, the mobility state information may indicate a cell ID associated with the reported cell 525, a motion state of the reported cell 525, a mobility level of the reported cell, etc. The motion state and / or mobility level may correspond to a specific point in time, a specific time period, etc. The motion state of the reported cell 525 may indicate whether the reported cell 525 is (or was) moving or stationary. The mobility level of the reported cell 525 may indicate the motion speed of the reported cell 525. In some aspects, the mobility level may indicate whether the reported cell 525 is or was moving at one of a defined speed or speed range set. In some aspects, the defined speed or speed range set may include slow, medium, and fast.

[0077] As indicated by reference numeral 530, the wireless service node 505 may determine mobility history information associated with the wireless service node 505. In some aspects, the mobility history information may be associated with relative mobility between the wireless service node 505 and one or more reported cells 525. In some aspects, the mobility history information may indicate a cell ID associated with the reported cell 525, a duration of time that the wireless service node 505 visited the reported cell 525, an entry time corresponding to a time when the wireless service node 505 entered the reported cell 525, an exit time corresponding to a time when the wireless service node 505 exited the reported cell 525, mobility state information associated with the reported cell 525, and the like. In some aspects, the mobility history information may include mobility state information associated with the reported cell 525.

[0078] As described above, the reported cells may include detected neighboring cells. The detected neighboring cells may be neighboring cells relative to the visited cell, another detected cell, a cell 535 provided by the wireless service node 505, etc. In some aspects, the mobility history information may indicate a cell ID associated with the detected neighboring cell, a duration for which the detected neighboring cell has been detectable, etc.

[0079] In some aspects, the mobility history information may indicate a node ID associated with one or more child nodes of the child node set 510, a duration that the child node has visited a cell 535 provided by the wireless service node 505, one or more additional node IDs associated with one or more additional child nodes of the wireless service node 505, a duration that additional child nodes corresponding to the additional child nodes have been connected to the cell 535 provided by the wireless service node 505, and the like.

[0080] In some aspects, the mobility history information may indicate mobility state information associated with the wireless service node 505. In some aspects, the mobility state information associated with the wireless service node 505 may indicate: a motion state of a cell 535 provided by the wireless service node 505, wherein the motion state indicates whether the cell 535 provided by the wireless service node 505 is (or was) mobile or stationary; a mobility level of the cell 535 provided by the wireless service node 505, and the like.

[0081] In some aspects, the mobility state information associated with the wireless service node 505 may include historical mobility state information. The historical mobility state information may indicate a change in the motion state of the cell 535 provided by the wireless service node 505, a time corresponding to a change in the motion state of the cell 535 provided by the wireless service node 505, a change in the mobility level of the cell 535 provided by the wireless service node 505, a time corresponding to a change in the mobility level of the cell 535 provided by the wireless service node 505, and the like.

[0082] In some aspects, the mobility state information associated with the wireless service node 505 may include planned mobility state information. The planned mobility state information may indicate a duration for which the cell 535 provided by the wireless service node 505 will have a current motion state, a minimum duration for which the cell 535 provided by the wireless node 505 will have a current motion state, a maximum duration for which the cell 535 provided by the wireless node 505 will have a current motion state, a next motion state to which the cell 535 provided by the wireless node 505 will change, a duration for which the cell 535 provided by the wireless node 505 will have a next motion state, a minimum duration for which the cell 535 provided by the wireless node 505 will have a next motion state, a maximum duration for which the cell 535 provided by the wireless node 505 will have a next motion state, a duration for which the cell 535 provided by the wireless node 505 will have a current mobility level, a next mobility level to which the cell 535 provided by the wireless node 505 will change, a duration for which the cell 535 provided by the wireless node 505 will have a next mobility level, a minimum duration for which the cell 535 provided by the wireless node 505 will have a next mobility level, a maximum duration for which the cell 535 provided by the wireless node 505 will have a next mobility level, and the like.

[0083] In some aspects, the planned mobility state information may indicate movement direction information associated with the cell 535 provided by the wireless node 505, a cell ID associated with a next desired cell to be visited by the wireless service node 505, etc. In some aspects, the wireless service node 505 may determine the next desired cell based at least in part on the movement direction information associated with repeated travel of the wireless service node 505 along a particular route.

[0084] As indicated by reference numeral 540, the wireless service node 505 may send an indication that mobility history information is available, and one or more subnodes in the set of subnodes 510 may receive the indication that mobility history information is available. The indication may be carried in a system information block (SIB). In some aspects, the SIB may be SIB 1.

[0085] As shown by reference numeral 545, the wireless service node 505 may send the mobility history information, and one or more subnodes in the subnode set 510 may receive the mobility history information. In some aspects, sending the mobility history information may include broadcasting the mobility history information in a SIB. In some aspects, the SIB may include a traditional SIB or a new dedicated SIB. In some aspects, the mobility history information may be carried in a radio resource control (RRC) message.

[0086] In some aspects, the wireless service node 505 may send the mobility history information to a subset of the set of child nodes 510. In some aspects, the subset of child nodes may include fewer child nodes than all of the child nodes in the set of child nodes 510. In some aspects, the subset of child nodes may include one or more child IAB nodes of the set of child nodes 510. In some aspects, the wireless service node 505 may send the mobility history information to wireless nodes other than the child nodes of the wireless service node 505.

[0087] As shown in the reference numeral 550, the wireless service node 505 may send an indication of a change in mobility history information, and one or more subnodes in the subnode set 510 may receive the indication. In some aspects, the wireless service node 505 may determine that one or more aspects of the mobility history information have changed since it was sent to the one or more subnodes. For example, the mobility state of the reported cell may indicate that the reported cell is stationary. After sending the mobility state information to the subnode, the wireless service node may determine that the reported cell has begun to move, in which case the mobility state of the reported cell has changed. The wireless service node 505 may send an indication of the change to the subnode, wherein the indication indicates that the reported cell is in motion. In some aspects, the indication of the change in mobility history information may be carried in downlink control information (DCI), a media access control (MAC) control element (MAC-CE), etc.

[0088] In some aspects, the mobility history information may be carried in a SIB, and an indication of a change in the mobility history information may be carried in a dedicated system information (SI) update. In some aspects, a dedicated SI update may be sent to each subnode in the set of subnodes 510. In some aspects, a dedicated SI update may be sent to a subset of the set of subnodes 510. The subset of the set of subnodes 510 may include fewer subnodes than all of the subnodes of the set of subnodes 510. In some aspects, a dedicated SI update may be sent using a short message.

[0089] In some aspects, the dedicated SI update may be sent using an extended SI update indication. The extended SI update indication may include a dedicated short message. In some aspects, the extended SI update indication may include a dedicated paging radio network temporary identifier (RNTI), one or more dedicated physical downlink control channel (PDCCH) resources, dedicated content of a traditional short message, a traditional short message in which one or more reserved bits are used for a dedicated SI update, a traditional short message in which one or more unused bits are used for a dedicated SI update, etc.

[0090] In some aspects, the extended SI update indication may be carried in a paging physical downlink shared channel (PDSCH). In some aspects, the extended SI update indication may indicate that the SIB carrying the mobility history information has been updated. In some aspects, the change of the mobility history information may be explicitly indicated in the paging PDSCH.

[0091] According to various aspects, some wireless service nodes 505 may support mobility history information reporting, while other wireless service nodes 505 may not. In some aspects, the wireless service node 505 supports mobility history information reporting based at least in part on the wireless service node 505 including a distributed unit of a wireless IAB node. In some aspects, the wireless service node may be a mobile wireless node, and the wireless service node 505 may support mobility history information reporting based at least in part on the wireless service node 505 including a DU of a mobile wireless IAB node.

[0092] As mentioned above, Figure 5 are provided as examples. Other examples may be related to Figure 5 Different than described.

[0093] Figure 6 6 is a diagram illustrating an example process 600 performed, for example, by a wireless service node in accordance with the present disclosure. Example process 600 is an example of operations associated with mobility history reporting of a wireless service node performed by a wireless service node (e.g., wireless service node 505, base station 110, UE 120, etc.).

[0094] like Figure 6As shown, in some aspects, process 600 may include determining mobility history information associated with the wireless service node, wherein the mobility history information is associated with relative mobility between the wireless service node and one or more reported cells (block 610). For example, as described above, the wireless service node (e.g., using receive processor 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may determine the mobility history information associated with the wireless service node. In some aspects, the mobility history information is associated with relative mobility between the wireless service node and one or more reported cells.

[0095] like Figure 6 As further shown in FIG. 6 , in some aspects, process 600 may include sending mobility history information associated with the wireless service node to the second wireless node (block 620). For example, as described above, the wireless service node (e.g., using transmit processor 220, transmit processor 264, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may send mobility history information associated with the wireless service node to the second wireless node.

[0096] Process 600 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.

[0097] In a first aspect, a wireless service node determines mobility history information based at least in part on the wireless service node comprising a distributed unit of a wireless integrated access and backhaul node.

[0098] In a second aspect, either alone or in combination with the first aspect, the wireless service node is a mobile wireless node, and the wireless service node determines the mobility history information based at least in part on the wireless service node comprising a distributed unit of a mobile wireless integrated access and backhaul node.

[0099] In a third aspect, alone or in combination with one or more of the first and second aspects, sending the mobility history information includes broadcasting the mobility history information in a SIB.

[0100] In a fourth aspect, alone or in combination with the third aspect, the SIB comprises a traditional SIB or a dedicated SIB.

[0101] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 600 includes sending an indication that mobility history information is available.

[0102] In a sixth aspect, alone or in combination with the fifth aspect, the indication is carried in a SIB.

[0103] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the SIB includes SIB1.

[0104] In an eighth aspect, either alone or in combination with one or more of aspects one to seven, the second wireless node is a subnode of a wireless service node, and sending the mobility history information to the subnode includes sending the mobility history information to a subset of subnodes of a set of subnodes of the wireless service node, the subset of subnodes including fewer subnodes than all subnodes in the set of subnodes.

[0105] In a ninth aspect, alone or in combination with the eighth aspect, the subset of child nodes includes one or more child IAB nodes of the set of child nodes.

[0106] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the mobility history information is carried in an RRC message.

[0107] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the wireless serving node is a mobile wireless IAB node, and the one or more reported cells include one or more visited cells.

[0108] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the wireless service node is a mobile wireless IAB node, and the one or more reported cells include one or more cells in which the wireless service node resides, and the one or more cells in which the wireless service node resides include one or more cells visited by the wireless service node during a duration that satisfies a residency threshold.

[0109] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the mobility history information indicates at least one of: a cell ID associated with a reported cell among one or more reported cells, a duration of a wireless service node's access to the reported cell, an entry time corresponding to a time when the wireless service node enters the reported cell, an exit time corresponding to a time when the wireless service node exits the reported cell, mobility state information associated with the reported cell, or a combination thereof.

[0110] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the mobility history information indicates at least one of: a cell ID associated with a reported cell among one or more reported cells, a motion state of the reported cell, a mobility level of the reported cell, or a combination thereof, wherein the motion state indicates whether the reported cell is mobile or stationary.

[0111] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the one or more reported cells include one or more detected neighboring cells, and the one or more detected neighboring cells include cells adjacent to the cell provided by the wireless service node and detected by the wireless service node.

[0112] In a sixteenth aspect, alone or in combination with the fifteenth aspect, the mobility history information indicates at least one of: a cell ID associated with a reported cell of the one or more reported cells, a duration for which the reported cell has been detectable, or a combination thereof.

[0113] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the one or more reported cells include: one or more mobile cells, one or more stationary cells, or a combination thereof.

[0114] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the mobility history information indicates at least one of: a node ID associated with the child node, a duration for which the child node has visited a cell provided by the wireless service node, one or more additional node IDs associated with one or more additional child nodes of the wireless service node, a duration for which an additional child node corresponding to one or more additional child nodes of the wireless service node has been connected to a cell provided by the wireless service node, or a combination thereof.

[0115] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the mobility history information indicates mobility state information associated with the wireless service node.

[0116] In the twentieth aspect, alone or in combination with the nineteenth aspect, the mobility state information associated with the wireless service node indicates at least one of: a motion state of a cell provided by the wireless service node, a mobility level of a cell provided by the wireless service node, or a combination thereof, wherein the motion state indicates whether the cell provided by the wireless service node is mobile or stationary.

[0117] In a twenty-first aspect, alone or in combination with one or more of the nineteenth to twentieth aspects, the mobility state information associated with the wireless service node includes historical mobility state information.

[0118] In the twenty-second aspect, alone or in combination with the twenty-first aspect, the historical mobility state information indicates at least one of: a change in a motion state of a cell provided by a wireless service node, wherein the motion state indicates whether the cell provided by the wireless service node is mobile or stationary; a time corresponding to a change in the motion state of the cell provided by the wireless service node; a change in the mobility level of the cell provided by the wireless service node; a time corresponding to a change in the mobility level of the cell provided by the wireless service node; or a combination thereof.

[0119] In a twenty-third aspect, alone or in combination with one or more of aspects 19 to 22, the mobility state information associated with the wireless service node includes planned mobility state information.

[0120] In the twenty-fourth aspect, alone or in combination with the twenty-third aspect, the planned mobility state information indicates at least one of: the duration of the current motion state that the cell provided by the wireless service node will have, the minimum duration of the current motion state that the cell provided by the wireless service node will have, the maximum duration of the current motion state that the cell provided by the wireless service node will have, the next motion state to which the cell provided by the wireless service node will change, the duration of the next motion state that the cell provided by the wireless service node will have, the minimum duration of the next motion state that the cell provided by the wireless service node will have, the maximum duration of the next motion state that the cell provided by the wireless service node will have, the duration of the current mobility level that the cell provided by the wireless service node will change to, the duration of the next mobility level that the cell provided by the wireless service node will have, the minimum duration of the next mobility level that the cell provided by the wireless service node will have, the maximum duration of the next mobility level that the cell provided by the wireless service node will have, or a combination thereof.

[0121] In aspect 25, alone or in combination with one or more of aspects 23 to 24, the planned mobility state information indicates at least one of: movement direction information associated with a cell provided by the wireless service node, a cell identifier associated with the next expected cell to be visited by the wireless service node, or a combination thereof.

[0122] In a twenty-sixth aspect, alone or in combination with the twenty-fifth aspect, process 600 includes determining a next desired cell based at least in part on direction of motion information associated with repeated travel of the wireless service node along a particular route.

[0123] In a twenty-seventh aspect, alone or in combination with one or more of the first to twenty-sixth aspects, process 600 includes sending an indication of a change in mobility history information.

[0124] In a twenty-eighth aspect, alone or in combination with the twenty-seventh aspect, an indication of a change in the mobility history information is carried in at least one of a DCI, a MAC-CE, or a combination thereof.

[0125] In a twenty-ninth aspect, alone or in combination with one or more of aspects twenty-seven to twenty-eight, the mobility history information is carried in a SIB, and an indication of a change in the mobility history information is carried in a dedicated SI update.

[0126] In a thirtieth aspect, either alone or in combination with the twenty-ninth aspect, a dedicated SI update is sent to: each subnode in a set of subnodes of a wireless service node, or a subset of the set of subnodes of a wireless service node, wherein the subset of the set of subnodes includes fewer subnodes than all of the subnodes in the set of subnodes.

[0127] In the thirty-first aspect, alone or in combination with one or more of the twenty-ninth to thirtieth aspects, the dedicated SI update is sent using a short message.

[0128] In a thirty-second aspect, alone or in combination with one or more of aspects twenty-ninth to thirty-first, a dedicated SI update is sent using an extended SI update indication.

[0129] In a thirty-third aspect, alone or in combination with the thirty-second aspect, the extended SI update indication comprises a dedicated short message.

[0130] In aspect 34, alone or in combination with aspect 33, the extended SI update indication includes at least one of: a dedicated paging RNTI, one or more dedicated PDCCH resources, dedicated content of a traditional short message, a traditional short message in which one or more reserved bits are used for a dedicated SI update, a traditional short message in which one or more unused bits are used for a dedicated SI update, or a combination thereof.

[0131] In a thirty-fifth aspect, alone or in combination with one or more of the thirty-third to thirty-fourth aspects, the extended SI update indication is carried in the paging PDSCH.

[0132] In a thirty-sixth aspect, alone or in combination with the thirty-fifth aspect, the extended SI update indication indicates a SIB that has been updated.

[0133] In a thirty-seventh aspect, alone or in combination with one or more of the thirty-fifth to thirty-sixth aspects, changes in the mobility history information are explicitly indicated in the paging PDSCH.

[0134] although Figure 6 Example blocks of process 600 are shown, but in some aspects, process 600 may include Figure 6 The blocks depicted in the process 600 may be more blocks, fewer blocks, different blocks, or blocks in a different arrangement. Additionally or alternatively, two or more blocks of process 600 may be performed in parallel.

[0135] Figure 7 7 is a diagram illustrating an example process 700 performed, for example, by a wireless service node in accordance with the present disclosure. Example process 700 is an example of operations associated with mobility history reporting of a wireless service node performed by a wireless service node (e.g., wireless service node 505, base station 110, UE 120, etc.).

[0136] like Figure 7 As shown, in some aspects, process 700 may include receiving, from a parent node of the wireless service node, mobility history information associated with the parent node, wherein the mobility history information is associated with a relative mobility between the parent node and one or more reported cells (block 710). For example, as described above, the wireless service node (e.g., using receive processor 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may receive, from the parent node of the wireless service node, mobility history information associated with the parent node. In some aspects, the mobility history information is associated with a relative mobility between the parent node and one or more reported cells.

[0137] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include performing an action based at least in part on receiving mobility history information associated with the parent node (block 720). For example, as described above, the wireless serving node (e.g., using transmit processor 220, transmit processor 264, receive processor 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may perform an action based at least in part on receiving mobility history information associated with the parent node.

[0138] Process 700 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.

[0139] In a first aspect, a parent node determines mobility history information based at least in part on the parent node comprising a distributed unit of a wireless integrated access and backhaul node.

[0140] In a second aspect, alone or in combination with the first aspect, the parent node is a mobile wireless node, and the parent node determines the mobility history information based at least in part on the parent node comprising a DU of a mobile wireless IAB node.

[0141] In a third aspect, alone or in combination with one or more of the first and second aspects, the mobility history information is broadcast in a SIB.

[0142] In a fourth aspect, alone or in combination with the third aspect, the SIB comprises a traditional SIB or a dedicated SIB.

[0143] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 700 includes receiving an indication that mobility history information is available.

[0144] In a sixth aspect, alone or in combination with the fifth aspect, the indication is carried in a SIB.

[0145] In a seventh aspect, alone or in combination with the sixth aspect, the SIB comprises SIB1.

[0146] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the wireless service node includes child nodes in a subset of child nodes of a set of child nodes of a parent node, and the subset of child nodes includes fewer child nodes than all child nodes in the set of child nodes.

[0147] In a ninth aspect, alone or in combination with the eighth aspect, the sub-node subset includes one or more sub-IAB nodes in the sub-node set.

[0148] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the mobility history information is carried in an RRC message.

[0149] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the parent node is a mobile wireless IAB node, and the one or more reported cells include one or more visited cells.

[0150] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the parent node is a mobile wireless IAB node, and the one or more reported cells include one or more cells in which the parent node resides, and the one or more cells in which the parent node resides include one or more cells visited by the parent node during a duration that satisfies a residence threshold.

[0151] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the mobility history information indicates at least one of: a cell ID associated with a reported cell among one or more reported cells, a duration of a parent node's access to the reported cell, an entry time corresponding to a time when the parent node enters the reported cell, an exit time corresponding to a time when the parent node exits the reported cell, mobility state information associated with the reported cell, or a combination thereof.

[0152] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the mobility history information indicates at least one of: a cell ID associated with a reported cell among one or more reported cells, a motion state of the reported cell, a mobility level of the reported cell, or a combination thereof, wherein the motion state indicates whether the reported cell is mobile or stationary.

[0153] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the one or more reported cells include one or more detected neighboring cells, and the one or more detected neighboring cells include cells adjacent to the cell provided by the parent node and detected by the parent node.

[0154] In a sixteenth aspect, alone or in combination with the fifteenth aspect, the mobility history information indicates at least one of: a cell ID associated with a reported cell of the one or more reported cells, a duration for which the reported cell has been detectable, or a combination thereof.

[0155] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the one or more reported cells include: one or more mobile cells, one or more stationary cells, or a combination thereof.

[0156] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the mobility history information indicates at least one of: a node ID associated with the wireless service node, a duration for which the wireless service node has visited a cell provided by a parent node, one or more additional node IDs associated with one or more additional child nodes of the parent node, a duration for which an additional child node corresponding to one or more additional child nodes of the parent node has been connected to a cell provided by the parent node, or a combination thereof.

[0157] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the mobility history information indicates mobility state information associated with a parent node.

[0158] In the twentieth aspect, alone or in combination with the nineteenth aspect, the mobility state information associated with the parent node indicates at least one of: a node ID associated with the wireless service node, a duration for which the wireless service node has accessed a cell provided by the parent node, one or more additional node IDs associated with one or more additional child nodes of the parent node, a duration for which an additional child node corresponding to one or more additional child nodes of the parent node has been connected to the cell provided by the parent node, or a combination thereof.

[0159] In a twenty-first aspect, alone or in combination with one or more of the nineteenth to twentieth aspects, the mobility state information associated with the parent node includes historical mobility state information.

[0160] In aspect 22, alone or in combination with aspect 21, the historical mobility state information indicates at least one of: a change in a motion state of a cell provided by a parent node, wherein the motion state indicates whether the cell provided by the wireless service node is mobile or stationary; a time corresponding to a change in the motion state of the cell provided by the parent node; a change in the mobility level of the cell provided by the parent node; a time corresponding to a change in the mobility level of the cell provided by the parent node; or a combination thereof.

[0161] In a twenty-third aspect, alone or in combination with one or more of aspects 19 to 22, the mobility state information associated with the parent node includes planned mobility state information.

[0162] In the twenty-fourth aspect, alone or in combination with the twenty-third aspect, the planned mobility state information indicates at least one of: the duration of the current motion state that the cell provided by the parent node will have, the minimum duration of the current motion state that the cell provided by the parent node will have, the maximum duration of the current motion state that the cell provided by the parent node will have, the next motion state to which the cell provided by the parent node will change, the duration of the next motion state that the cell provided by the parent node will have, the minimum duration of the next motion state that the cell provided by the parent node will have, the maximum duration of the next motion state that the cell provided by the parent node will have, the duration of the current mobility level that the cell provided by the parent node will change to, the duration of the next mobility level that the cell provided by the parent node will have, the minimum duration of the next mobility level that the cell provided by the parent node will have, the maximum duration of the next mobility level that the cell provided by the parent node will have, or a combination thereof.

[0163] In aspect 25, alone or in combination with one or more of aspects 23 to 24, the planned mobility state information indicates at least one of: movement direction information associated with a cell provided by a parent node, a cell ID associated with the next expected cell to be visited by the parent node, or a combination thereof.

[0164] In a twenty-sixth aspect, alone or in combination with the twenty-fifth aspect, determining a next desired cell is based at least in part on direction of motion information associated with repeated travel along a particular route.

[0165] In a twenty-seventh aspect, alone or in combination with one or more of the first to twenty-sixth aspects, process 700 includes receiving an indication of a change in mobility history information.

[0166] In a twenty-eighth aspect, alone or in combination with the twenty-seventh aspect, an indication of a change in the mobility history information is carried in at least one of a DCI, a MAC-CE, or a combination thereof.

[0167] In a twenty-ninth aspect, alone or in combination with one or more of aspects twenty-seven to twenty-eight, the mobility history information is carried in a SIB, and an indication of a change in the mobility history information is carried in a dedicated SI update.

[0168] In the thirtieth aspect, either alone or in combination with the twenty-ninth aspect, a dedicated SI update is sent to: each child node in a set of child nodes of a parent node, or a subset of the set of child nodes of a parent node, wherein the subset of the set of child nodes includes fewer child nodes than all child nodes of the set of child nodes.

[0169] In the thirty-first aspect, alone or in combination with one or more of the twenty-ninth to thirtieth aspects, the dedicated SI update is sent using a short message.

[0170] In a thirty-second aspect, alone or in combination with the thirty-first aspect, a dedicated SI update is sent using an extended SI update indication.

[0171] In a thirty-third aspect, alone or in combination with the thirty-second aspect, the extended SI update indication comprises a dedicated short message.

[0172] In aspect 34, alone or in combination with one or more of aspects 29 to 33, the extended SI update indication includes at least one of: a dedicated paging RNTI, one or more dedicated PDCCH resources, dedicated content of a traditional short message, a traditional short message in which one or more reserved bits are used for a dedicated SI update, a traditional short message in which one or more unused bits are used for a dedicated SI update, or a combination thereof.

[0173] In a thirty-fifth aspect, alone or in combination with one or more of the thirty-third to thirty-fourth aspects, the extended SI update indication is carried in the paging PDSCH.

[0174] In a thirty-sixth aspect, alone or in combination with the thirty-fifth aspect, the extended SI update indication indicates a SIB that has been updated.

[0175] In a thirty-seventh aspect, alone or in combination with one or more of the thirty-fifth to thirty-sixth aspects, changes in the mobility history information are explicitly indicated in the paging PDSCH.

[0176] although Figure 7 Example blocks of process 700 are shown, but in some aspects, process 700 may include more Figure 7 The blocks depicted in the process 700 may be more blocks, fewer blocks, different blocks, or blocks in a different arrangement. Additionally or alternatively, two or more blocks of process 700 may be executed in parallel.

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

[0178] Aspect 1: A method of wireless communication performed by a wireless service node in a network, comprising: determining mobility history information associated with the wireless service node, wherein the mobility history information is associated with relative mobility between the wireless service node and one or more reported cells; and sending the mobility history information associated with the wireless service node to a second wireless node.

[0179] Aspect 2: The method according to aspect 1, wherein the wireless service node determines the mobility history information at least in part based on the wireless service node comprising a distributed unit of a wireless integrated access and backhaul node.

[0180] Aspect 3: A method according to any one of Aspects 1 or 2, wherein the wireless service node is a mobile wireless node, and wherein the wireless service node determines the mobility history information at least in part based on the wireless service node comprising a distributed unit of a mobile wireless integrated access and backhaul node.

[0181] Aspect 4: The method according to any one of aspects 1-3, wherein sending the mobility history information comprises broadcasting the mobility history information in a system information block (SIB).

[0182] Aspect 5: The method according to aspect 4, wherein the SIB includes a legacy SIB or a dedicated SIB.

[0183] Aspect 6: The method according to any one of aspects 1-5, further comprising sending an indication that mobility history information is available.

[0184] Aspect 7: The method according to aspect 6, wherein the indication is carried in a system information block (SIB).

[0185] Aspect 8: The method according to aspect 7, wherein the SIB includes SIB 1.

[0186] Aspect 9: A method according to any one of Aspects 1-8, wherein the second wireless node includes a subnode of the wireless service node, wherein sending the mobility history information to the subnode includes sending the mobility history information to a subset of subnodes in a subnode set of the wireless service node, wherein the subnode subset includes fewer subnodes than all subnodes in the subnode set.

[0187] Aspect 10: The method according to aspect 9, wherein the subset of sub-nodes includes one or more sub-integrated access and backhaul nodes in the set of sub-nodes.

[0188] Aspect 11: The method according to any one of aspects 1 to 10, wherein the mobility history information is carried in a radio resource control message.

[0189] Aspect 12: The method according to any one of aspects 1-11, wherein the wireless serving node is a mobile wireless integrated access and backhaul node, and wherein the one or more reported cells include one or more visited cells.

[0190] Aspect 13: A method according to any one of Aspects 1-12, wherein the wireless service node is a mobile wireless integrated access and backhaul node, and wherein the one or more reported cells include one or more cells in which the wireless service node resides, wherein the one or more cells in which the wireless service node resides include one or more cells visited by the wireless service node during a duration that satisfies a residence threshold.

[0191] Aspect 14: A method according to any one of Aspects 1-13, wherein the mobility history information indicates at least one of: a cell identifier associated with a reported cell among one or more reported cells, a duration of a wireless service node's access to the reported cell, an entry time corresponding to a time when the wireless service node enters the reported cell, an exit time corresponding to a time when the wireless service node exits the reported cell, mobility state information associated with the reported cell, or a combination thereof.

[0192] Aspect 15: A method according to any one of Aspects 1-14, wherein the mobility history information indicates at least one of: a cell identifier associated with a reported cell among one or more reported cells, a motion state of the reported cell, a mobility level of the reported cell, or a combination thereof, wherein the motion state indicates whether the reporting cell is mobile or stationary.

[0193] Aspect 16: A method according to any one of Aspects 1-15, wherein the one or more reported cells include one or more detected neighboring cells, wherein the one or more detected neighboring cells include cells that are adjacent to the cell provided by the wireless service node and detected by the wireless service node.

[0194] Aspect 17: The method according to aspect 16, wherein the mobility history information indicates at least one of: a cell identifier associated with a reported cell among the one or more reported cells, a duration for which the reported cell has been detectable, or a combination thereof.

[0195] Aspect 18: The method according to any one of aspects 1-17, wherein the one or more reported cells include: one or more mobile cells, one or more stationary cells, or a combination thereof.

[0196] Aspect 19: A method according to any one of Aspects 1-18, wherein the second wireless node includes a child node of a wireless service node, and wherein the mobility history information indicates at least one of the following: a node identifier (ID) associated with the child node, a duration for which the child node has visited a cell provided by the wireless service node, one or more additional node IDs associated with one or more additional child nodes of the wireless service node, a duration for which an additional child node corresponding to one or more additional child nodes of the wireless service node has been connected to a cell provided by the wireless service node, or a combination thereof.

[0197] Aspect 20: The method according to any one of aspects 1-19, wherein the mobility history information indicates mobility state information associated with the wireless service node.

[0198] Aspect 21: A method according to Aspect 20, wherein the mobility state information associated with the wireless service node indicates at least one of the following: a motion state of a cell provided by the wireless service node, a mobility level of a cell provided by the wireless service node, or a combination thereof, wherein the motion state indicates whether the cell provided by the wireless service node is mobile or stationary.

[0199] Aspect 22: The method according to any one of aspects 20 or 21, wherein the mobility state information associated with the wireless service node includes historical mobility state information.

[0200] Aspect 23: A method according to Aspect 22, wherein the historical mobility state information indicates at least one of the following: a change in the motion state of a cell provided by a wireless service node, wherein the motion state indicates whether the cell provided by the wireless service node is mobile or stationary; a time corresponding to a change in the motion state of the cell provided by the wireless service node; a change in the mobility level of the cell provided by the wireless service node; a time corresponding to a change in the mobility level of the cell provided by the wireless service node; or a combination thereof.

[0201] Aspect 24: The method according to any one of aspects 20-23, wherein the mobility state information associated with the wireless service node includes planned mobility state information.

[0202] Aspect 25: A method according to Aspect 24, wherein the planned mobility state information indicates at least one of: a duration of a current motion state that a cell provided by a wireless service node will have, a minimum duration of a current motion state that a cell provided by a wireless service node will have, a maximum duration of a current motion state that a cell provided by a wireless service node will have, a next motion state to which a cell provided by a wireless service node will change, a duration of a next motion state that a cell provided by a wireless service node will have, a minimum duration of a next motion state that a cell provided by a wireless service node will have, a maximum duration of a next motion state that a cell provided by a wireless service node will have, a duration of a current mobility level that a cell provided by a wireless service node will change to, a duration of a next mobility level that a cell provided by a wireless service node will have, a minimum duration of a next mobility level that a cell provided by a wireless service node will have, a maximum duration of a next mobility level that a cell provided by a wireless service node will have, or a combination thereof.

[0203] Aspect 26: A method according to any one of Aspects 24 or 25, wherein the planned mobility state information indicates at least one of the following: movement direction information associated with a cell provided by the wireless service node, a cell identifier associated with a next desired cell to be visited by the wireless service node, or a combination thereof.

[0204] Aspect 27: The method according to aspect 26, further comprising determining a next desired cell based at least in part on movement direction information associated with repeated travel of the wireless service node along a particular route.

[0205] Aspect 28: The method according to any one of aspects 1-27, further comprising sending an indication of a change in the mobility history information.

[0206] Aspect 29: The method according to aspect 28, wherein the indication of the change of the mobility history information is carried in at least one of downlink control information, a medium access control (MAC) control element, or a combination thereof.

[0207] Aspect 30: A method according to any one of aspects 28 or 29, wherein the mobility history information is carried in a system information block (SIB), and wherein the indication of the change of the mobility history information is carried in a dedicated system information (SI) update.

[0208] Aspect 31: A method according to Aspect 30, wherein the dedicated SI update is sent to: each subnode in the subnode set of the wireless service node, or a subset of the subnode set of the wireless service node, wherein the subset of the subnode set includes fewer subnodes than all subnodes of the subnode set.

[0209] Aspect 32: The method according to any one of aspects 30 or 31, wherein the dedicated SI update is sent using a short message.

[0210] Aspect 33: The method according to any one of aspects 30-32, wherein the dedicated SI update is sent using an extended SI update indication.

[0211] Aspect 34: The method according to Aspect 33, wherein the extended SI update indication includes a dedicated short message.

[0212] Aspect 35: A method according to Aspect 34, wherein the extended SI update indication includes at least one of the following: a dedicated paging radio network temporary identifier, one or more dedicated physical downlink control channel resources, dedicated content of a traditional short message, a traditional short message in which one or more reserved bits are used for a dedicated SI update, a traditional short message in which one or more unused bits are used for a dedicated SI update, or a combination thereof.

[0213] Aspect 36: A method according to any one of aspects 34 or 35, wherein the extended SI update indication is carried in a paging physical downlink shared channel (PDSCH).

[0214] Aspect 37: The method according to aspect 36, wherein the extended SI update indication indicates the SIB that has been updated.

[0215] Aspect 38: The method according to any one of aspects 36 or 37, wherein the change of the mobility history information is explicitly indicated in the paging PDSCH.

[0216] Aspect 39: A wireless communication method performed by a wireless service node in a network, comprising: receiving mobility history information associated with the parent node from a parent node of the wireless service node, wherein the mobility history information is associated with the relative mobility between the parent node and one or more reported cells; and performing an action based at least in part on receiving the mobility history information associated with the parent node.

[0217] Aspect 40: The method according to aspect 39, wherein the parent node determines the mobility history information based at least in part on the parent node comprising a distributed unit of a wireless integrated access and backhaul node.

[0218] Aspect 41: A method according to any one of aspects 39 or 40, wherein the parent node is a mobile wireless node, and wherein the parent node determines the mobility history information at least in part based on the parent node comprising a distributed unit of a wireless integrated access and backhaul node.

[0219] Aspect 42: The method according to any one of aspects 39-41, wherein the mobility history information is broadcast in a system information block (SIB).

[0220] Aspect 43: The method according to aspect 42, wherein the SIB comprises a legacy SIB or a dedicated SIB.

[0221] Aspect 44: The method according to any one of aspects 39-43, further comprising receiving an indication that mobility history information is available.

[0222] Aspect 45: The method according to aspect 44, wherein the indication is carried in a system information block (SIB).

[0223] Aspect 46: The method according to aspect 45, wherein the SIB includes SIB 1.

[0224] Aspect 47: A method according to any one of aspects 39-46, wherein the wireless service node comprises a child node in a subset of child nodes of a set of child nodes of a parent node, wherein the subset of child nodes comprises fewer child nodes than all child nodes in the set of child nodes.

[0225] Aspect 48: The method according to aspect 47, wherein the subset of sub-nodes includes one or more sub-integrated access and backhaul nodes in the set of sub-nodes.

[0226] Aspect 49: The method according to any one of aspects 39-48, wherein the mobility history information is carried in a radio resource control message.

[0227] Aspect 50: The method according to any one of aspects 39-49, wherein the parent node is a mobile radio integrated access and backhaul node, and wherein the one or more reported cells include one or more visited cells.

[0228] Aspect 51: A method according to any one of Aspects 39-50, wherein the parent node is a mobile wireless integrated access and backhaul node, and wherein the one or more reported cells include one or more cells in which the parent node resides, wherein the one or more cells in which the parent node resides include one or more cells visited by the parent node during a duration that satisfies a residence threshold.

[0229] Aspect 52: A method according to any one of Aspects 39-51, wherein the mobility history information indicates at least one of: a cell identifier associated with a reported cell among one or more reported cells, a duration of a parent node's visit to the reported cell, an entry time corresponding to a time when the parent node enters the reported cell, an exit time corresponding to a time when the parent node exits the reported cell, mobility state information associated with the reported cell, or a combination thereof.

[0230] Aspect 53: A method according to any one of Aspects 39-52, wherein the mobility history information indicates at least one of: a cell identifier associated with a reported cell among one or more reported cells, a motion state of the reported cell, a mobility level of the reported cell, or a combination thereof, wherein the motion state indicates whether the reported cell is mobile or stationary.

[0231] Aspect 54: A method according to any one of Aspects 39-53, wherein the one or more reported cells include one or more detected neighboring cells, wherein the one or more detected neighboring cells include cells that are adjacent to the cell provided by the parent node and detected by the parent node.

[0232] Aspect 55: The method according to aspect 54, wherein the mobility history information indicates at least one of: a cell identifier associated with a reported cell among the one or more reported cells, a duration for which the reported cell has been detectable, or a combination thereof.

[0233] Aspect 56: A method according to any one of aspects 39-55, wherein the one or more reported cells include: one or more mobile cells, one or more stationary cells, or a combination thereof.

[0234] Aspect 57: A method according to any one of Aspects 39-56, wherein the mobility history information indicates at least one of the following: a node identifier (ID) associated with a wireless service node, a duration for which the wireless service node has visited a cell provided by a parent node, one or more additional node IDs associated with one or more additional child nodes of the parent node, a duration for which an additional child node corresponding to one or more additional child nodes of the parent node has been connected to the cell provided by the parent node, or a combination thereof.

[0235] Aspect 58: The method according to any one of aspects 39-57, wherein the mobility history information indicates mobility state information associated with a parent node.

[0236] Aspect 59: A method according to Aspect 58, wherein the mobility state information associated with the parent node indicates at least one of the following: a motion state of the cell provided by the parent node, a mobility level of the cell provided by the parent node, or a combination thereof, wherein the motion state indicates whether the cell provided by the parent node is mobile or stationary.

[0237] Aspect 60: The method according to any one of aspects 58 or 59, wherein the mobility state information associated with the parent node includes historical mobility state information.

[0238] Aspect 61: A method according to Aspect 60, wherein the historical mobility state information indicates at least one of: a change in the motion state of a cell provided by a parent node, wherein the motion state indicates whether the cell provided by the parent node is moving or stationary; a time corresponding to a change in the motion state of the cell provided by the parent node; a change in the mobility level of the cell provided by the parent node; a time corresponding to a change in the mobility level of the cell provided by the parent node; or a combination thereof.

[0239] Aspect 62: The method according to any one of aspects 58-61, wherein the mobility state information associated with the parent node includes planned mobility state information.

[0240] Aspect 63: A method according to Aspect 62, wherein the planned mobility state information indicates at least one of: the duration of the current motion state that the cell provided by the parent node will have, the minimum duration of the current motion state that the cell provided by the parent node will have, the maximum duration of the current motion state that the cell provided by the parent node will have, the next motion state to which the cell provided by the parent node will change, the duration of the next motion state that the cell provided by the parent node will have, the minimum duration of the next motion state that the cell provided by the parent node will have, the maximum duration of the next motion state that the cell provided by the parent node will have, the duration of the current mobility level that the cell provided by the parent node will change to, the duration of the next mobility level that the cell provided by the parent node will have, the minimum duration of the next mobility level that the cell provided by the parent node will have, the maximum duration of the next mobility level that the cell provided by the parent node will have, or a combination thereof.

[0241] Aspect 64: A method according to any one of Aspects 62 or 63, wherein the planned mobility state information indicates at least one of the following: movement direction information associated with a cell provided by a parent node, a cell identifier associated with a next desired cell to be visited by the parent node, or a combination thereof.

[0242] Aspect 65: The method of aspect 64, wherein the next desired cell is determined based at least in part on movement direction information associated with repeated travel of the parent node along a particular route.

[0243] Aspect 66: The method according to any one of aspects 39-65, further comprising receiving an indication of a change in the mobility history information.

[0244] Aspect 67: The method according to aspect 66, wherein the indication of the change of the mobility history information is carried in at least one of downlink control information, a medium access control (MAC) control element, or a combination thereof.

[0245] Aspect 68: A method according to any of aspects 66 or 67, wherein the mobility history information is carried in a system information block (SIB), and wherein the indication of the change of the mobility history information is carried in a dedicated system information (SI) update.

[0246] Aspect 69: A method according to Aspect 68, wherein the dedicated SI update is sent to: each child node in the set of child nodes of the parent node, or a subset of the set of child nodes of the parent node, wherein the subset of the set of child nodes includes fewer child nodes than all child nodes of the set of child nodes.

[0247] Aspect 70: The method according to any one of aspects 68 or 69, wherein the dedicated SI update is sent using a short message.

[0248] Aspect 71: The method according to aspect 70, wherein the dedicated SI update is sent using an extended SI update indication.

[0249] Aspect 72: The method according to Aspect 71, wherein the extended SI update indication includes a dedicated short message.

[0250] Aspect 73: A method according to Aspect 72, wherein the extended SI update indication includes at least one of the following: a dedicated paging radio network temporary identifier, one or more dedicated physical downlink control channel resources, dedicated content of a traditional short message, a traditional short message in which one or more reserved bits are used for a dedicated SI update, a traditional short message in which one or more unused bits are used for a dedicated SI update, or a combination thereof.

[0251] Aspect 74: A method according to any one of aspects 72 or 73, wherein the extended SI update indication is carried in a paging physical downlink shared channel (PDSCH).

[0252] Aspect 75: The method according to Aspect 74, wherein the extended SI update indication indicates the SIB that has been updated.

[0253] Aspect 76: A method according to any one of aspects 74 or 75, wherein the dedicated SI update is explicitly indicated in the paging PDSCH.

[0254] Aspect 77: An apparatus for wireless communication at a device, 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 the method of one or more aspects of aspects 1-38.

[0255] Aspect 78: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method of one or more aspects of aspects 1-38.

[0256] Aspect 79: An apparatus for wireless communication, comprising at least one component for performing the method of one or more of aspects 1-38.

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

[0258] Aspect 81: 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 the method of one or more aspects of aspects 1-38.

[0259] Aspect 82: An apparatus for wireless communication at a device, 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 the method of one or more aspects of aspects 39-76.

[0260] Aspect 83: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method of one or more aspects of aspects 39-76.

[0261] Aspect 84: An apparatus for wireless communication, comprising at least one component for performing the method of one or more of aspects 39-76.

[0262] Aspect 85: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more aspects of aspects 39-76.

[0263] Aspect 86: 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 the method of one or more aspects of aspects 39-76.

[0264] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit these aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0265] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware, firmware, and / or hardware and software. "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 programs, execution threads, processes and / or functions, and other examples, whether referred to as software, firmware, middleware, microcode, hardware description language or other. As used herein, the processor is implemented with a combination of hardware and / or hardware and software. Obviously, the system and / or method described herein can be implemented with a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, the operation and behavior of the system and / or method are described herein without reference to specific software codes, and it should be understood that software and hardware can be designed at least in part based on the description herein to implement the system and / or method.

[0266] As used herein, satisfying a threshold may refer to a value 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.

[0267] Even though particular combinations of features are recited in the claims and / or described in the specification, these combinations are not intended to limit the disclosure of the various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of the various aspects includes the combination of each dependent claim with every other claim in the claim set. A phrase referring to "at least one" of a series of items refers to any combination of those items, including single members. For example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc or any other order of a, b, and c)

[0268] Unless explicitly described, any element, action or instruction used in this article should not be interpreted as critical or essential. In addition, as used herein, the article "a" is intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.), and can be used interchangeably with "one or more". If only one item is referred to, the phrase "only one" or similar language is used. In addition, as used herein, the term "having" is intended to be an open term. In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated.

Claims

1. A first wireless node, comprising a wireless service node for wireless communication, comprising: Memory; as well as One or more processors, coupled to the memory, the one or more processors configured to cause the wireless service node to: determining mobility history information associated with the wireless service node, wherein the mobility history information is associated with previous relative mobility between the wireless service node and one or more reported cells; and The mobility history information associated with the wireless service node is sent to a second wireless node, wherein the second wireless node comprises a child node of the wireless service node, wherein the mobility history information comprises an indication of the one or more reported cells, wherein the one or more reported cells comprise one or more cells on which the wireless service node previously resided, and wherein the one or more cells on which the wireless service node previously resided comprise one or more cells visited by the wireless service node during a duration that satisfied a residency threshold.

2. The first wireless node according to claim 1, wherein: The wireless service node determines mobility history information based at least in part on the wireless service node comprising a distributed unit of a wireless integrated access and backhaul node.

3. The first wireless node according to claim 1, wherein: The wireless service node is a mobile wireless node, and wherein the wireless service node determines the mobility history information based at least in part on the wireless service node comprising a distributed unit of a mobile wireless integrated access and backhaul node.

4. The first wireless node according to claim 1, wherein: Sending the mobility history information includes broadcasting the mobility history information in a system information block SIB, wherein the SIB includes a legacy SIB or a dedicated SIB.

5. The first wireless node according to claim 1, wherein: The one or more processors are further configured to cause the wireless service node to send an indication that mobility history information is available.

6. The first wireless node according to claim 5, wherein: The indication is carried in the system information block SIB.

7. The first wireless node according to claim 1, wherein: Sending the mobility history information to the child nodes includes sending the mobility history information to a subset of child nodes of a set of child nodes of the wireless service node, and wherein the subset of child nodes includes fewer child nodes than all of the child nodes in the set of child nodes.

8. The first wireless node according to claim 7, wherein: The subset of sub-nodes includes one or more subset access and backhaul nodes of the set of sub-nodes.

9. The first wireless node according to claim 1, wherein: The mobility history information is carried in a radio resource control RRC message.

10. The first wireless node according to claim 1, wherein: The wireless serving node is a mobile wireless integrated access and backhaul node, and wherein the one or more reported cells include one or more visited cells.

11. The first wireless node according to claim 1, wherein: The mobility history information indicates at least one of the following: a cell identifier associated with a reported cell of the one or more reported cells, a motion state of the reported cell, wherein the motion state indicates whether the reported cell is moving or stationary, the duration that the wireless serving node visits the reported cell, an entry time corresponding to the time when the wireless serving node enters the reported cell, an exit time corresponding to the time at which the wireless serving node exits the reported cell, The reported mobility level of the cell, and Mobility state information associated with the reporting cell.

12. The first wireless node according to claim 1, wherein: The one or more reported cells include one or more detected neighboring cells, wherein the one or more detected neighboring cells include cells that are neighboring a cell provided by a wireless service node and detected by the wireless service node.

13. The first wireless node according to claim 12, wherein: The mobility history information indicates at least one of the following: a cell identifier associated with a reported cell of the one or more reported cells, and The duration that the reported cell can be detected.

14. The first wireless node of claim 1, wherein: The mobility history information indicates at least one of the following: The node identifier ID associated with the child node, the duration that the child node has been visiting the cell provided by the wireless serving node, one or more additional node IDs associated with one or more additional child nodes of the wireless serving node, a duration corresponding to an additional child node of the one or more additional child nodes of the wireless service node that the additional child node has been connected to a cell provided by the wireless service node, and Mobility state information associated with the wireless serving node.

15. The first wireless node according to claim 14, wherein: The mobility state information associated with the wireless service node indicates at least one of the following: a motion state of a cell provided by the wireless service node, wherein the motion state indicates whether the cell provided by the wireless service node is mobile or stationary, and The mobility level of the cell provided by the radio serving node.

16. The first wireless node of claim 14, wherein: The mobility state information associated with the wireless service node includes historical mobility state information, and wherein the historical mobility state information indicates at least one of the following: a change in a motion state of a cell provided by the wireless service node, wherein the motion state indicates whether the cell provided by the wireless service node is moving or stationary, a time corresponding to a change in the motion state of the cell provided by the wireless service node, changes in the mobility level of the cell provided by the radio serving node, and The time corresponding to a change in the mobility level of a cell provided by the wireless service node.

17. The first wireless node of claim 14, wherein: The mobility state information associated with the wireless service node includes planned mobility state information, and wherein the planned mobility state information indicates at least one of the following: The cell provided by the wireless service node will have a duration of the current motion state, The minimum duration that a cell provided by a wireless service node will have a current motion state, The cell provided by the wireless service node will have a maximum duration of the current motion state, the next motion state to which the cell provided by the wireless serving node will change, The cell provided by the wireless service node will have a duration of the next motion state, The cell provided by the wireless service node will have a minimum duration of the next motion state, The cell provided by the wireless service node will have a maximum duration of the next motion state, the duration that a cell provided by a wireless serving node will have the current mobility level, the next mobility level to which the cell provided by the wireless serving node will change, the duration for which the cell provided by the wireless serving node will have the next mobility level, the minimum duration that a cell provided by a wireless serving node will have the next mobility level, The maximum duration that a cell provided by a wireless serving node will have the next mobility level, Direction of motion information associated with the cell provided by the wireless serving node, and A cell identifier associated with a next desired cell to be visited by the wireless serving node.

18. The first wireless node according to claim 17, wherein: The one or more processors are further configured to cause the wireless service node to determine a next desired cell based at least in part on direction of motion information associated with repeated travel along a particular route.

19. The first wireless node of claim 1, wherein: The one or more processors are further configured to cause the wireless service node to send an indication of a change in mobility history information.

20. The first wireless node of claim 19, wherein: An indication of a change in the mobility history information is carried in at least one of the following: Downlink control information, and Media Access Control MAC control element.

21. The first wireless node of claim 19, wherein: The mobility history information is carried in a system information block SIB, and wherein an indication of a change of the mobility history information is carried in a dedicated system information SI update.

22. The first wireless node of claim 21, wherein: Dedicated SI updates are sent to: Each child node in the child node set of the wireless service node, or A subset of a set of child nodes of a wireless service node, wherein the subset of the set of child nodes includes fewer child nodes than all of the child nodes of the set of child nodes.

23. The first wireless node of claim 21, wherein: Dedicated SI updates are sent using short messages.

24. The first wireless node of claim 21, wherein: Dedicated SI updates are sent using the Extended SI Update Indication.

25. The first wireless node of claim 24, wherein: The extended SI update indication includes at least one of the following: Dedicated Paging Radio Network Temporary Identifier, one or more dedicated physical downlink control channel resources, Dedicated content for traditional short messages, A conventional short message in which one or more reserved bits are used for dedicated SI updates, and One or more unused bits are used for conventional short messages dedicated to SI updates.

26. The first wireless node of claim 24, wherein: The extended SI update indication is carried in the paging physical downlink shared channel PDSCH.

27. A wireless service node for wireless communication, comprising: Memory; as well as One or more processors, coupled to the memory, the one or more processors configured to cause the wireless service node to: receiving, from a parent node of the wireless service node, mobility history information associated with the parent node, wherein the mobility history information is associated with previous relative mobility between the parent node and one or more reported cells, wherein the mobility history information includes an indication of the one or more reported cells, wherein the one or more reported cells include one or more cells on which the parent node previously camped, and wherein the one or more cells on which the parent node previously camped include one or more cells visited by the parent node for a duration that satisfied a camp threshold; and An action is performed based at least in part on receiving the mobility history information associated with the parent node.

28. The wireless serving node of claim 27, wherein the wireless serving node is a mobile wireless integrated access and backhaul node, and wherein the one or more reported cells include one or more visited cells.

29. A wireless communication method performed by a first wireless node including a wireless service node in a network, comprising: determining mobility history information associated with the wireless service node, wherein the mobility history information is associated with previous relative mobility between the wireless service node and one or more reported cells, wherein the one or more reported cells include one or more cells on which the wireless service node previously camped, and wherein the one or more cells on which the wireless service node previously camped include one or more cells visited by the wireless service node for a duration that satisfied a camping threshold; and The mobility history information associated with the wireless service node is sent to a second wireless node, wherein the second wireless node comprises a child node of the wireless service node, and wherein the mobility history information comprises an indication of the one or more reported cells.

30. A wireless communication method performed by a wireless service node in a network, comprising: receiving, from a parent node of the wireless service node, mobility history information associated with the parent node, wherein the mobility history information is associated with previous relative mobility between the parent node and one or more reported cells, wherein the mobility history information includes an indication of the one or more reported cells, wherein the one or more reported cells include one or more cells on which the parent node previously camped, and wherein the one or more cells on which the parent node previously camped include one or more cells visited by the parent node for a duration that satisfied a camp threshold; and An action is performed based at least in part on receiving the mobility history information associated with the parent node.

Images