Mobility History Reporting in New Radio

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a wireless node may receive a mobility history report configuration for providing mobility history information associated with a visited cell; and a mobility history report containing the mobility history information is sent to a parent node of the wireless node based at least in part on the mobility history report configuration. Many other aspects are also provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims U.S. Provisional Patent Application No. 63 / 000,196, filed on March 26, 2020, entitled “MOBILITY HISTORY REPORTING IN NEW RADIO”; and U.S. Provisional Patent Application No. 63 / 022,907, filed on May 11, 2020, entitled “MOBILITY HISTORY REPORTING IN NEW RADIO”; and U.S. Non-Provisional Patent Application No. 17 / 211,609, filed on March 24, 2021, entitled “MOBILITY HISTORY REPORTING IN NEW RADIO”, which are expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and techniques and apparatus for mobility history reporting in new radio. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies that are capable of supporting communications 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 a city, country, regional, and even global level. NR, which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and by supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other wireless access technologies remain useful. Summary of the invention

[0007] In some aspects, a wireless node for wireless communication includes a memory and one or more processors coupled to the memory, and is configured to: receive a mobility history report configuration for providing mobility history information associated with a visited cell; and send a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes at least one of a pair of cell identifiers or a mobility parameter set, the pair of cell identifiers including a global cell identifier (ID) corresponding to the visited cell and a physical cell ID corresponding to the visited cell, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the wireless node enters the visited cell, an exit time corresponding to a time when the wireless node exits the visited cell, or a combination thereof.

[0008] In some aspects, a wireless node for wireless communication includes a memory and one or more processors coupled to the memory, and is configured to: receive a mobility history report including mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes at least one of a pair of cell identifiers or a mobility parameter set, the pair of cell identifiers including a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the child node enters the visited cell, an exit time corresponding to a time when the child node exits the visited cell, or a combination thereof; and perform an action based at least in part on the mobility history information.

[0009] In some aspects, a wireless communication method performed by a wireless node may include: receiving a mobility history report configuration for providing mobility history information associated with a visited cell; and sending a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the wireless node enters the visited cell, an exit time corresponding to a time when the wireless node exits the visited cell, or a combination thereof.

[0010] In some aspects, a method of wireless communication performed by a wireless node may include: receiving a mobility history report containing mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of the following: an entry time corresponding to a time when the child node enters the visited cell, an exit time corresponding to a time when the child node exits the visited cell, or a combination thereof; and performing an action based at least in part on the mobility history information.

[0011] In some aspects, a method of wireless communication performed by a wireless node may include: receiving a mobility history report configuration for providing mobility history information associated with a visited cell; and sending a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes tracking information associated with the visited cell.

[0012] In some aspects, a wireless communication method performed by a wireless node may include: receiving a mobility history report containing mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes tracking information associated with the visited cell; and performing an action based at least in part on the mobility history information.

[0013] In some aspects, a method of wireless communication performed by a wireless node may include: receiving a mobility history report configuration for providing mobility history information associated with a visited cell; and sending a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes: a global cell identifier (ID) corresponding to the visited cell and a physical cell ID corresponding to the visited cell.

[0014] In some aspects, a wireless communication method performed by a wireless node may include: receiving a mobility history report containing mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes: a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell; and performing an action based at least in part on the mobility history information.

[0015] In some aspects, a method of wireless communication performed by a wireless node may include: receiving a mobility history report configuration for providing mobility history information associated with a visited cell, wherein the mobility history report configuration indicates at least one of: periodic reporting of the mobility history information, semi-persistent reporting of the mobility history information, event-triggered reporting of the mobility history information, dynamic request reporting of the mobility history information, or a combination thereof; and sending a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration.

[0016] In some aspects, a method of wireless communication performed by a wireless node may include: sending a mobility history report configuration for providing mobility history information associated with a visited cell to a subnode of the wireless node, wherein the mobility history report configuration indicates at least one of: periodic reporting of the mobility history information, semi-persistent reporting of the mobility history information, event-triggered reporting of the mobility history information, dynamic request reporting of the mobility history information, or a combination thereof; and receiving a mobility history report containing the mobility history information from the subnode of the wireless node based at least in part on the mobility history report configuration.

[0017] In some aspects, a wireless node for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: receive a mobility history report configuration for providing mobility history information associated with a visited cell; and send a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the wireless node enters the visited cell, an exit time corresponding to a time when the wireless node exits the visited cell, or a combination thereof.

[0018] In some aspects, a wireless node for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: receive a mobility history report including mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the child node enters the visited cell, an exit time corresponding to a time when the child node exits the visited cell, or a combination thereof; and perform an action based at least in part on the mobility history information.

[0019] In some aspects, a wireless node for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: receive a mobility history report configuration for providing mobility history information associated with a visited cell; and send a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes tracking information associated with the visited cell.

[0020] In some aspects, a wireless node for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: receive a mobility history report including mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes tracking information associated with the visited cell; and perform an action based at least in part on the mobility history information.

[0021] In some aspects, a wireless node for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: receive a mobility history report configuration for providing mobility history information associated with a visited cell; and send a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes: a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell.

[0022] In some aspects, a wireless node for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: receive a mobility history report including mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes: a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell; and perform an action based at least in part on the mobility history information.

[0023] In some aspects, a wireless node for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: receive a mobility history report configuration for providing mobility history information associated with a visited cell, wherein the mobility history report configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof; and send a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration.

[0024] In some aspects, a wireless node for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: send a mobility history report configuration for providing mobility history information associated with a visited cell to a child node of the wireless node, wherein the mobility history report configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof; and receive a mobility history report containing the mobility history information from the child node of the wireless node based at least in part on the mobility history report configuration.

[0025] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless node, may cause the one or more processors to: receive a mobility history report configuration for providing mobility history information associated with a visited cell; and send a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of the following: an entry time corresponding to a time when the wireless node enters the visited cell, an exit time corresponding to a time when the wireless node exits the visited cell, or a combination thereof.

[0026] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless node, may cause the one or more processors to: receive a mobility history report containing mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the child node enters the visited cell, an exit time corresponding to a time when the child node exits the visited cell, or a combination thereof; and perform an action based at least in part on the mobility history information.

[0027] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless node, may cause the one or more processors to: receive a mobility history report configuration for providing mobility history information associated with a visited cell; and send a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes tracking information associated with the visited cell.

[0028] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless node, may cause the one or more processors to: receive a mobility history report containing mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes tracking information associated with the visited cell; and perform an action based at least in part on the mobility history information.

[0029] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless node, may cause the one or more processors to: receive a mobility history report configuration for providing mobility history information associated with a visited cell; and send a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes: a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell.

[0030] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless node, may cause the one or more processors to: receive a mobility history report containing mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes: a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell; and perform an action based at least in part on the mobility history information.

[0031] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless node, may cause the one or more processors to: receive a mobility history report configuration for providing mobility history information associated with a visited cell, wherein the mobility history report configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof; and send a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration.

[0032] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless node, may cause the one or more processors to: send a mobility history report configuration for providing mobility history information associated with a visited cell to a child node of the wireless node, wherein the mobility history report configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof; and receive a mobility history report containing the mobility history information from the child node of the wireless node based at least in part on the mobility history report configuration.

[0033] In some aspects, an apparatus for wireless communication may include: a component for receiving a mobility history report configuration for providing mobility history information associated with a visited cell; and a component for sending a mobility history report containing the mobility history information to a parent node of the apparatus based at least in part on the mobility history report configuration, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the apparatus enters the visited cell, an exit time corresponding to a time when the apparatus exits the visited cell, or a combination thereof.

[0034] In some aspects, an apparatus for wireless communication may include: a component for receiving a mobility history report including mobility history information associated with a visited cell from a child node of the apparatus, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the child node enters the visited cell, an exit time corresponding to a time when the child node exits the visited cell, or a combination thereof; and a component for performing an action based at least in part on the mobility history information.

[0035] In some aspects, an apparatus for wireless communication may include: a component for receiving a mobility history report configuration for providing mobility history information associated with a visited cell; and a component for sending a mobility history report including the mobility history information to a parent node of the apparatus based at least in part on the mobility history report configuration, wherein the mobility history information includes tracking information associated with the visited cell.

[0036] In some aspects, an apparatus for wireless communication may include: a component for receiving a mobility history report including mobility history information associated with a visited cell from a child node of the apparatus, wherein the mobility history information includes tracking information associated with the visited cell; and a component for performing an action based at least in part on the mobility history information.

[0037] In some aspects, an apparatus for wireless communication may include: a component for receiving a mobility history report configuration for providing mobility history information associated with a visited cell; and a component for sending a mobility history report containing the mobility history information to a parent node of the apparatus based at least in part on the mobility history report configuration, wherein the mobility history information includes: a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell.

[0038] In some aspects, an apparatus for wireless communication may include: a component for receiving a mobility history report including mobility history information associated with a visited cell from a child node of the apparatus, wherein the mobility history information includes: a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell; and a component for performing an action based at least in part on the mobility history information.

[0039] In some aspects, an apparatus for wireless communication may include: a component for receiving a mobility history report configuration for providing mobility history information associated with a visited cell, wherein the mobility history report configuration indicates at least one of: periodic reporting of the mobility history information, semi-persistent reporting of the mobility history information, event-triggered reporting of the mobility history information, dynamic request reporting of the mobility history information, or a combination thereof; and a component for sending a mobility history report containing the mobility history information to a parent node of the apparatus based at least in part on the mobility history report configuration.

[0040] In some aspects, an apparatus for wireless communication may include: a component for sending a mobility history report configuration for providing mobility history information associated with a visited cell to a subnode of the apparatus, wherein the mobility history report configuration indicates at least one of: periodic reporting of the mobility history information, semi-persistent reporting of the mobility history information, event-triggered reporting of the mobility history information, dynamic request reporting of the mobility history information, or a combination thereof; and a component for receiving a mobility history report containing the mobility history information from the subnode of the apparatus based at least in part on the mobility history report configuration.

[0041] 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 described herein with reference to and illustrated by the accompanying figures and description.

[0042] The foregoing has been fairly broadly summarized the features and technical advantages of examples according to the present disclosure 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 to achieve the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, their organization and methods of operation, and associated 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 the limitations of the claims.

[0043] 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 / purchase equipment, medical devices, or devices supported by 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 in combination with 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 summers). It is intended that the aspects described herein can be practiced in a variety of devices, components, systems, distributed arrangements, or end-user devices with different sizes, shapes, and structures. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be made by reference to various aspects, some of which are shown in the accompanying drawings. However, it should be noted that the attached drawings only show some typical aspects of the present disclosure and should not be considered as limiting the scope thereof, as the description may allow for other equivalent aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

[0046] Figure 2 is a schematic diagram illustrating an example of a base station communicating with a UE in a wireless network according to the present disclosure.

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

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

[0049] Figure 5 is a diagram illustrating an example of mobility history reporting in new radio according to the present disclosure.

[0050] Figure 6-Figure 13 is a diagram illustrating an example process performed, for example, by a wireless node according to the present disclosure. DETAILED DESCRIPTION

[0051] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be interpreted as being limited to any specific structure or function throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. Based on the teachings of this article, it will be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently 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 described herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover the use of various aspects disclosed herein together with other structures, functions, or structures and functions, or devices and methods practiced using other structures, functions, or structures and functions other than the various aspects disclosed herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

[0052] 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 detailed description below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

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

[0054] Figure 1 is a schematic diagram showing an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (NR) network and / or an LTE network, etc. The wireless network 100 may include a plurality of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE), and may also be referred to as an 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" may 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.

[0055] 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)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1In the example shown, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. In this document, the terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NR", and "cell" may be used interchangeably.

[0056] In some aspects, the cells may not necessarily be fixed, and the geographic area of ​​the cells may move according to the location of the mobile BS. In some aspects, the BSs may be interconnected to each other and / or to 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 or virtual networks) using any suitable transport network.

[0057] The wireless network 100 may also include a relay station. A relay station is an entity that can receive a data transmission from an upstream station (e.g., a BS or a UE) and send the data transmission 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 in FIG. 1 , a relay BS 110 d may communicate with a macro BS 110 a and a UE 120 d to facilitate communication between the BS 110 a and the UE 120 d. A relay BS may also be referred to as a relay station, a relay base station, a relay, or the like.

[0058] The wireless network 100 may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, 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 higher 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).

[0059] 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 directly or indirectly via a wireless or wired backhaul.

[0060] UE 120 (e.g., 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be fixed or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle-mounted component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0061] 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 and / or location tags that can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may, for example, provide a connection for or 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 customer premises equipment (CPE). UE 120 may be included in a housing that houses components of UE 120 (such as a processor component and / or a memory component). In some aspects, the processor component and the 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 operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0062] 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, frequency 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.

[0063] 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 sidelink 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 or vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. 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.

[0064] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using an operating band having a first frequency range (FR1) that may span 410 MHz to 7.125 GHz, and / or may communicate using an operating band having a second frequency range (FR2) that may span 24.25 GHz to 52.6 GHz. 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 "sub-6 GHz" band. Similarly, FR2 is often referred to as a "millimeter wave" band, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) that is identified as a "millimeter wave" band by the International Telecommunication Union (ITU). Therefore, unless otherwise specifically stated, it should be understood that the term "sub-6 GHz" and the like (if used herein) can broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise specifically stated, it should be understood that the term "millimeter wave" and the like (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 contemplated that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0065] As mentioned above, providing Figure 1 As an example. Other examples can be related to Figure 1 The description is different.

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

[0067] At the base station 110, the transmit processor 220 may receive data from the data source 212 for one or more UEs, 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 the 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)) and control information (e.g., CQI requests, grants, upper layer signaling), 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) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or 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 respective output symbol stream (e.g., for OFDM) 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.

[0068] At the UE 120, antennas 252a to 252r may receive downlink signals from the 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) to obtain received symbols. The 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. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a channel quality indicator (CQI) parameter, etc. In some aspects, one or more components of the UE 120 may be included in the housing 284.

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

[0070] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include, or may be included in, examples of one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays. 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 antenna elements coupled to one or more transmit and / or receive components (such as Figure 2 One or more antenna elements of one or more components).

[0071] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from a controller / processor 280. 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 or CP-OFDM), and transmitted to the base station 110. In some aspects, the modulator and demodulator (e.g., modulator / demodulator 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 antennas 252, modulators and / or demodulators 254, MIMO detectors 256, receive processors 258, transmit processors 264, and / or TX MIMO processors 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., as described in reference to Figure 5-Figure 13 described).

[0072] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information sent 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 to schedule the UE 120 for downlink and / or uplink communications. In some aspects, the modulator and demodulator (e.g., the modulator / demodulator 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 antennas 234, modulators and / or demodulators 232, MIMO detectors 236, receive processors 238, transmit processors 220, and / or TX MIMO processors 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., as described in reference to Figure 5-Figure 13 described).

[0073] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the UE 120 may perform one or more techniques associated with mobility history reporting in NR 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 process of 700 Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 The process of 1000 Fig.11 Process 1100, Fig.12 The process 1200 Fig.13 The operations of process 1300 and / or other processes as described herein. 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, the one or more instructions, when executed (e.g., directly or after compilation, conversion and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120 and / or base station 110 to perform or direct, for example, Figure 6 The process of 600 Figure 7 The process of 700 Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 The process of 1000 Fig.11 Process 1100, Fig.12 The process 1200 Fig.13 The process 1300 and / or operations of other processes as described herein. In some aspects, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0074] In some aspects, a wireless node may include: a component for receiving a mobility history report configuration for providing mobility history information associated with a visited cell; a component for sending a mobility history report including the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the wireless node enters the visited cell, an exit time corresponding to a time when the wireless node exits the visited cell, or a combination thereof, etc. In some aspects, such a component may include in conjunction with Figure 2One 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 modulator 254, the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, etc. In some aspects, such components may include a combination of Figure 2 One or more components of the 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.

[0075] In some aspects, a wireless node may include: means for receiving a mobility history report including mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the child node entered the visited cell, an exit time corresponding to a time when the child node exited the visited cell, or a combination thereof; means for performing an action based at least in part on the mobility history information, etc. In some aspects, such 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 modulator 254, the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, etc. In some aspects, such components may include a combination of Figure 2 One or more components of the 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.

[0076] In some aspects, a wireless node may include: a component for receiving a mobility history report configuration for providing mobility history information associated with a visited cell; a component for sending a mobility history report containing mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes tracking information associated with the visited cell, etc. In some aspects, such a component 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 modulator 254, the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, etc. In some aspects, such components may include a combination of Figure 2One or more components of the 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.

[0077] In some aspects, a wireless node may include: means for receiving a mobility history report including mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes tracking information associated with the visited cell; means for performing an action based at least in part on the mobility history information, etc. In some aspects, such 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 modulator 254, the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, etc. In some aspects, such components may include a combination of Figure 2 One or more components of the 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.

[0078] In some aspects, a wireless node may include: a component for receiving a mobility history report configuration for providing mobility history information associated with a visited cell; a component for sending a mobility history report containing mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes: a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell, etc. In some aspects, such a component may include combining 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 modulator 254, the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, etc. In some aspects, such components may include a combination of Figure 2 One or more components of the 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.

[0079] In some aspects, a wireless node may include: means for receiving, from a child node of the wireless node, a mobility history report including mobility history information associated with a visited cell, wherein the mobility history information includes: a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell; means for performing an action based at least in part on the mobility history information, etc. In some aspects, such 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 modulator 254, the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, etc. In some aspects, such components may include a combination of Figure 2 One or more components of the 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.

[0080] In some aspects, a wireless node may include: a component for receiving a mobility history report configuration for providing mobility history information associated with a visited cell, wherein the mobility history report configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamically requested reporting of mobility history information, or a combination thereof; and a component for sending a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration. In some aspects, such a component 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 modulator 254, the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, etc. In some aspects, such components may include a combination of Figure 2 One or more components of the 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.

[0081] In some aspects, a wireless node may include: a component for sending a mobility history report configuration for providing mobility history information associated with a visited cell to a child node of the wireless node, wherein the mobility history report configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof; a component for receiving a mobility history report containing mobility history information from a child node of the wireless node based at least in part on the mobility history report configuration, etc. In some aspects, such a component may include combining 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 modulator 254, the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, etc. In some aspects, such components may include a combination of Figure 2 One or more components of the 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.

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

[0083] As mentioned above, providing Figure 2 As an example. Other examples can be related to Figure 2 The description is different.

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

[0085] As shown by reference numeral 305, a conventional (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 an optical fiber 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.

[0086] As shown by 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 that communicates with a 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 335 and / or the non-anchor base station 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.

[0087] As shown by reference numeral 365, in some aspects, a radio access network including an IAB network may utilize millimeter wave technology and / or directional communication (e.g., beamforming) for communication 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 may use millimeter wave signals to carry information and / or may use beamforming to point to a target base station. Similarly, a wireless access link 375 between a UE and a base station may use millimeter wave signals and / or may point to a target wireless node (e.g., a UE and / or a base station). In this way, inter-link interference may be reduced.

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

[0089] As mentioned above, providing Figure 3 As an example. Other examples can be related to Figure 3 The description is different.

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

[0091] like Figure 4 As shown, the IAB network may include an IAB host 405 (shown as IAB-host) connected to the core network via a wired connection (shown as 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 of the core network that provide core access and mobility management functions (e.g., AMF). In some aspects, the IAB host 405 may include a base station 110, such as described above in conjunction with Figure 3 Anchor base station described. As shown in the figure, the IAB host 405 may include a central unit (CU) that can perform access node controller (ANC) functions and / or AMF functions. The CU can configure the distributed units (DUs) of the IAB host 405 and / or can configure one or more IAB nodes 410 connected to the core network via the IAB host 405 (e.g., MTs and / or DUs of the IAB nodes 410). Therefore, the CU of the IAB host 405 can 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).

[0092] like Figure 4As also 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 by the 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).

[0093] 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 may be referred to as the parent node of the second node, and the second node may be referred to as the child node of the first node. The child node of the second node may be referred to as the grandchild node of the first node. Therefore, the DU function of the parent node may control and / or schedule the communication of the child node of the parent node. The parent node may be the IAB host 405 or the IAB node 410, and the child node may be the IAB node 410 or the UE 120. The communication of the MT function of the child node may be controlled and / or scheduled by the parent node of the child node.

[0094] like Figure 4 As also shown in FIG. 4 , the link between the UE 120 (e.g., which has only MT functionality but not DU functionality) and the IAB host 405, or the link between the UE 120 and the IAB node 410, may be referred to as an access link 415. The access link 415 may be a wireless access link that provides the UE 120 with radio access to the core network via the 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.

[0095] like Figure 4As also shown in FIG. 4 , the link between the IAB host 405 and the IAB node 410 or between two IAB nodes 410 may be referred to as a backhaul link 420. The backhaul link 420 may be a wireless backhaul link that provides radio 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. In the IAB network, network resources (e.g., time resources, frequency resources, and / or space resources) for wireless communication may be shared between the access link 415 and the backhaul link 420. In some aspects, the backhaul link 420 may be a primary backhaul link or an auxiliary backhaul link (e.g., a backup backhaul link). In some aspects, in other examples, the auxiliary backhaul link may be used if the primary backhaul link fails, becomes congested, and / or becomes overloaded, etc. 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 may be used for backhaul communication. As used herein, a “node” or “wireless node” may refer to the IAB host 405 or the IAB node 410 .

[0096] Space resources, etc. may be shared between the parent link 425 (shown as link 420 / 425 for IAB node 1) of the IAB node 410 and the child link 430 (shown as link 420 / 430 for IAB node 1) of the IAB node 410. 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 constraint may result in high latency in communications.

[0097] In order to reduce 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 to the IAB host 405, and so on. For example, because millimeter wave communications have high signal attenuation during propagation, IAB nodes 410 with overlapping coverage may be deployed to expand coverage in the IAB network and mitigate such signal attenuation. In addition, because millimeter wave communications are susceptible to link blocking and link failures, IAB nodes 410 with overlapping coverage may be deployed to improve the robustness of the IAB network.

[0098] In some cases, in order to improve the reliability of transmission in the IAB network, packets can be sent to the destination (e.g., IAB node, IAB host, UE, etc.) along multiple paths. For example, packet data convergence protocol (PDCP) duplication can be used at the CU and / or UE to improve reliability. However, PDCP duplication results in a large 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.

[0099] As mentioned above, providing Figure 4 As an example. Other examples can be related to Figure 4 The description is different.

[0100] In LTE, if capable, the UE can keep track of the cells that the UE has camped on while 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 is also being developed to include a similar process for UEs to submit mobility history information.

[0101] In NR, and as part of the Mobile IAB, the NR network may have mobile cells, i.e. cells that may be moving. It has been recognized that having a reliable estimate of the relative mobility state between the UE and the cell is useful for optimizing various signaling and procedures. For example, it has been proposed that the available mobility information and measurements can be used to classify different UEs based on their relative mobility to a given cell. For example, this classification can be used to prioritize service and resource management of one group over another group, optimally set various parameters for operation of different groups, and so on.

[0102] In some aspects of the techniques and apparatus described herein, a wireless node (e.g., a UE, a child node, a parent node, etc.) may send a mobility history report to a parent node (e.g., 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 network to manage mobile cells and corresponding resources. In some aspects, the mobility history information may include an entry time corresponding to the time when the wireless node enters a visited cell, an exit time corresponding to the time when the wireless node exits a visited cell, a duration of time that the wireless node visits the cell, etc. In this way, aspects of the techniques described herein may facilitate tracking of activity patterns of wireless nodes, which may facilitate more efficient management of resources allocated to wireless nodes.

[0103] In some aspects, the mobility history information may include a global cell identification (ID) corresponding to the visited cell and a physical cell ID corresponding to the visited cell. In this way, when a particular cell moves, information about the movement of the particular cell can be tracked, thereby changing its physical cell ID. In some aspects, the collection and / or reporting of mobility history information associated with a cell may depend on the type of wireless node providing the cell, whether the cell is mobile, and the like. In this way, various aspects of the technology described herein may be effectively managed, thereby facilitating a reduction in signaling overhead, traffic, and the like.

[0104] Figure 5 5 is a diagram illustrating an example 500 of mobility history reporting in NR according to the present disclosure. As shown, a wireless node 505 and a parent node 510 may communicate with each other.

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

[0106] As indicated by reference numeral 515, the parent node 510 may transmit a mobility history report configuration for providing mobility history information associated with a visited cell 520, and the wireless node 505 may receive the mobility history report configuration. In some aspects, the visited cell 520 may be provided by a parent node 525 of the wireless node 505. In some aspects, the parent node 520 providing the visited cell 520 may include a DU of an IAB node, an MT component of an IAB node, etc. In some aspects, the mobility history report configuration may indicate periodic reporting of the mobility history information, semi-persistent reporting of the mobility history information, event-triggered reporting of the mobility history information, dynamic request reporting of the mobility history information, etc.

[0107] As indicated by reference numeral 530, the parent node 525 providing the visited cell 520 may transmit mobility state information associated with the visited cell 520, and the wireless node 505 may receive the mobility state information. The mobility state information may indicate, for example, whether the visited cell 520 is mobile when the wireless node 505 visits the visited cell 520.

[0108] The wireless node 505 may send a mobility history report and the parent node 510 may receive the mobility history report as indicated by reference numeral 535. The mobility history report may include mobility history information based at least in part on a mobility history report configuration.

[0109] In some aspects, as indicated above, the mobility history report configuration may indicate event-triggered reporting of the mobility history information. In some aspects, the wireless node 505 may detect an occurrence of a triggering event and send the mobility history report based at least in part on detecting the occurrence of the triggering event. In some aspects, detecting the occurrence of the triggering event may include determining that the wireless node 505 visited a certain number of cells within a time period after a previous transmission of the mobility history report, wherein the number of cells satisfies a threshold. In some aspects, detecting the occurrence of the triggering event may include determining that the wireless node visited a visited cell for a duration that satisfies the threshold.

[0110] In some aspects, detecting the occurrence of a triggering event may include determining that a visited cell has the same global cell ID as another cell, wherein a physical cell ID of the visited cell is different from a physical cell ID of the other cell. In some aspects, detecting the occurrence of a triggering event may include determining that a visited cell has the same physical cell ID as another cell, wherein the global cell ID of the visited cell is different from a global cell ID of the other cell.

[0111] In some aspects, such as Figure 5 As shown, the mobility history information may include a mobility parameter set indicating a cell ID associated with the visited cell 520, an entry time corresponding to the time when the wireless node 505 enters the visited cell 520, an exit time corresponding to the time when the wireless node 505 exits the visited cell 520, a duration of the wireless node 505 visiting the visited cell 520, and the like.

[0112] In some aspects, the mobility history information may include tracking information associated with the visited cell 520. The tracking information may include location information associated with the wireless node 505 when the wireless node 505 is visiting the visited cell 520. In some aspects, the wireless node 505 may determine that a dwell threshold is met, wherein the dwell threshold corresponds to a duration of time spent by the wireless node 505 visiting the visited cell 520, and include the location information in the tracking information based at least in part on determining that the dwell threshold is met. In some aspects, the visited cell 520 may include at least one of an IAB node, a mobile node, etc. In some aspects, the tracking information may include the location information based at least in part on the visited cell 520 including at least one of an IAB node, a mobile node, etc.

[0113] In some aspects, the mobility history information may include a global cell ID corresponding to the visited cell 520 and a physical cell ID corresponding to the visited cell 520. In some aspects, the visited cell 520 may include an IAB node, a mobile node, etc. In some aspects, the mobility history information may include the global cell ID and the physical cell ID based at least in part on the visited cell 520 including an IAB node, a mobile node, etc.

[0114] In some aspects of the above techniques and apparatus, a wireless node may send a mobility history report to a parent node. The mobility history report may include mobility history information that may be used by the network to manage mobile cells and corresponding resources. Aspects of the techniques discussed herein may facilitate tracking of activity patterns of wireless nodes, which may facilitate more efficient management of resources allocated to wireless nodes.

[0115] As mentioned above, providing Figure 5 As an example. Other examples can be related to Figure 5 The description is different.

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

[0117] like Figure 6 As shown, in some aspects, process 600 may include receiving a mobility history report configuration for providing mobility history information associated with a visited cell (block 610). For example, as described above, the wireless node (e.g., using receive processor 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may receive a mobility history report configuration for providing mobility history information associated with a visited cell.

[0118] like Figure 6 As also shown in FIG. 6 , in some aspects, process 600 may include, based at least in part on a mobility history report configuration, sending a mobility history report including mobility history information to a parent node of the wireless node, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the wireless node enters a visited cell, an exit time corresponding to a time when the wireless node exits the visited cell, or a combination thereof (block 620). For example, as described above, the wireless node (e.g., using transmit processor 220, transmit processor 264, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may send a mobility history report including mobility history information to a parent node of the wireless node based at least in part on a mobility history report configuration. In some aspects, the mobility history information includes a mobility parameter set. In some aspects, the mobility parameter set indicates at least one of: an entry time corresponding to a time when the wireless node enters a visited cell, an exit time corresponding to a time when the wireless node exits the visited cell, or a combination thereof.

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

[0120] In the first aspect, the mobility parameter set further indicates at least one of: a cell ID associated with the visited cell, a duration for the wireless node to visit the visited cell, or a combination thereof.

[0121] In a second aspect, alone or in combination with the first aspect, the mobility history information includes tracking information associated with a visited cell.

[0122] In a third aspect, alone or in combination with one or more of the first and second aspects, the tracking information includes mobility state information associated with the visited cell, the mobility state information at least indicating whether the visited cell is mobile when the wireless node visits the visited cell.

[0123] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the process 600 includes receiving mobility state information from a parent node providing a visited cell.

[0124] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the tracking information includes location information associated with the wireless node when the wireless node visits a visited cell.

[0125] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, process 600 comprises determining that a dwell threshold is met, wherein the dwell threshold corresponds to a duration spent by the wireless node visiting a visited cell, and wherein the tracking information comprises location information based at least in part on determining that the dwell threshold is met.

[0126] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, the visited cell includes at least one of an IAB node, a mobile node, or a combination thereof, and the tracking information includes location information based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0127] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the mobility history information includes: a global cell ID corresponding to a visited cell, and a physical cell ID corresponding to the visited cell.

[0128] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the visited cell includes at least one of an IAB node, a mobile node, or a combination thereof, and the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0129] In the tenth aspect, alone or in combination with one or more aspects from the first to the ninth aspects, the mobility history report configuration indicates at least one of the following: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof.

[0130] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the mobility history report configuration indicates an event-triggered report of mobility history information, and process 600 also includes: detecting the occurrence of a triggering event, wherein the wireless node sends the mobility history report at least in part based on detecting the occurrence of the triggering event.

[0131] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, detecting the occurrence of a triggering event includes determining that the wireless node has visited a certain number of cells within a time period after a previous transmission of a mobility history report, where the number of cells meets a threshold.

[0132] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, detecting the occurrence of a triggering event includes determining that the wireless node has visited a visited cell for a duration satisfying a threshold.

[0133] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, detecting the occurrence of a triggering event includes determining that a visited cell has the same global cell ID as another cell, wherein a physical cell ID of the visited cell is different from a physical cell ID of the other cell.

[0134] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, detecting the occurrence of a triggering event includes determining that a visited cell has the same physical cell ID as another cell, wherein the global cell ID of the visited cell is different from the global cell ID of the other cell.

[0135] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the wireless node includes a user equipment, a distributed unit of an IAB node, or a mobile terminal component of an IAB node.

[0136] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the visited cell is provided by a parent node of the wireless node, and the parent node includes a distributed unit of an IAB node or a mobile terminal component of an IAB node.

[0137] Although Figure 6 Example blocks of process 600 are shown, but in some aspects process 600 may include additional blocks, fewer blocks, different blocks, or different Figure 6 Those blocks shown are arranged differently. Additionally or alternatively, two or more blocks of process 600 may be performed in parallel.

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

[0139] like Figure 7 As shown in , in some aspects, process 700 may include receiving a mobility history report including mobility history information associated with a visited cell from a child node of a wireless node, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the child node enters the visited cell, an exit time corresponding to a time when the child node exits the visited cell, or a combination thereof (block 710). For example, as described above, the wireless node (e.g., using receive processor 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may receive a mobility history report including mobility history information associated with a visited cell from a child node of the wireless node. In some aspects, the mobility history information includes a mobility parameter set. In some aspects, the mobility parameter set indicates at least one of: an entry time corresponding to a time when the child node enters the visited cell, an exit time corresponding to a time when the child node exits the visited cell, or a combination thereof.

[0140] like Figure 7 As also shown in FIG. 7 , in some aspects, process 700 may include performing an action based at least in part on the mobility history information (block 720). For example, as described above, the wireless 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 the mobility history information.

[0141] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described in conjunction with one or more other processes described elsewhere herein.

[0142] Although Figure 7 Example blocks of process 700 are shown, but in some aspects process 700 may include additional blocks, fewer blocks, different blocks, or different Figure 7 Those blocks shown are arranged differently. Additionally or alternatively, two or more blocks of process 700 may be performed in parallel.

[0143] Figure 8 is a diagram illustrating an example process 800, for example, performed by a wireless node, in accordance with the present disclosure. Example process 800 is an example of a wireless node (eg, wireless node 505, base station 110, UE 120, etc.) performing operations associated with mobility history reporting in new radio.

[0144] like Figure 8 As shown, in some aspects, process 800 may include receiving a mobility history report configuration for providing mobility history information associated with a visited cell (block 810). For example, as described above, the wireless node (e.g., using receive processor 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may receive a mobility history report configuration for providing mobility history information associated with a visited cell.

[0145] like Figure 8 As also shown in FIG. 8 , in some aspects, process 800 may include sending a mobility history report including mobility history information to a parent node of the wireless node based at least in part on a mobility history report configuration, wherein the mobility history information includes tracking information associated with a visited cell (block 820). For example, as described above, the wireless node (e.g., using transmit processor 220, transmit processor 264, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may send a mobility history report including mobility history information to a parent node of the wireless node based at least in part on a mobility history report configuration. In some aspects, the mobility history information includes tracking information associated with a visited cell.

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

[0147] In a first aspect, the tracking information includes mobility state information associated with a visited cell, and the mobility state information indicates at least whether the visited cell is mobile when the wireless node visits the visited cell.

[0148] In a second aspect, alone or in combination with the first aspect, process 800 includes receiving mobility state information from a parent node providing a visited cell.

[0149] In a third aspect, alone or in combination with one or more of the first and second aspects, the tracking information includes location information associated with the wireless node when the wireless node is visiting a visited cell.

[0150] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 800 includes determining that a dwell threshold is met, wherein the dwell threshold corresponds to a duration spent by the wireless node visiting a visited cell, wherein the tracking information includes location information based at least in part on determining that the dwell threshold is met.

[0151] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the visited cell includes at least one of an IAB node, a mobile node, or a combination thereof, and the tracking information includes location information based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0152] In a sixth aspect, either alone or in combination with one or more of aspects one to five, the mobility history information includes a mobility parameter set indicating at least one of: a cell ID associated with a visited cell, an entry time corresponding to a time when a wireless node enters a visited cell, an exit time corresponding to a time when a wireless node exits a visited cell, a duration of a wireless node's visit to a visited cell, or a combination thereof.

[0153] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the mobility history information includes: a global cell ID corresponding to a visited cell, and a physical cell ID corresponding to the visited cell.

[0154] In an eighth aspect, alone or in combination with one or more of aspects one to seven, the visited cell includes at least one of an IAB node, a mobile node, or a combination thereof, and the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0155] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the mobility history report configuration indicates at least one of the following: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof.

[0156] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the mobility history report configuration indicates an event-triggered report of mobility history information, and process 800 also includes: detecting the occurrence of a triggering event, wherein the wireless node sends the mobility history report at least in part based on detecting the occurrence of the triggering event.

[0157] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, detecting the occurrence of a triggering event includes determining that the wireless node has visited a certain number of cells within a time period after a previous transmission of a mobility history report, where the number of cells meets a threshold.

[0158] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, detecting the occurrence of a triggering event includes determining that the wireless node has visited a visited cell for a duration satisfying a threshold.

[0159] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, detecting the occurrence of a triggering event includes determining that a visited cell has the same global cell ID as another cell, and a physical cell ID of the visited cell is different from a physical cell ID of the other cell.

[0160] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, detecting the occurrence of a triggering event includes determining that a visited cell has the same physical cell ID as another cell, and a global cell ID of the visited cell is different from a global cell ID of the other cell.

[0161] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the wireless node includes a user equipment, a distributed unit of an IAB node, or a mobile terminal component of an IAB node.

[0162] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the visited cell is provided by a parent node of the wireless node, and the parent node includes a distributed unit of an IAB node or a mobile terminal component of an IAB node.

[0163] Although Figure 8Example blocks of process 800 are shown, but in some aspects process 800 may include additional blocks, fewer blocks, different blocks, or different Figure 8 Those blocks shown are arranged differently. Additionally or alternatively, two or more blocks of process 800 may be performed in parallel.

[0164] Fig. 9 is a diagram illustrating an example process 900, for example, performed by a wireless node, in accordance with the present disclosure. Example process 900 is an example of a wireless node (eg, wireless node 505, base station 110, UE 120, etc.) performing operations associated with mobility history reporting in new radio.

[0165] like Fig. 9 As shown, in some aspects, process 900 may include receiving, from a child node of the wireless node, a mobility history report including mobility history information associated with a visited cell, wherein the mobility history information includes tracking information associated with the visited cell (block 910). For example, as described above, the wireless node (e.g., using receive processor 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may receive, from a child node of the wireless node, a mobility history report including mobility history information associated with a visited cell. In some aspects, the mobility history information includes tracking information associated with the visited cell.

[0166] like Fig. 9 As also shown in FIG. 9 , in some aspects, process 900 may include performing an action based at least in part on the mobility history information (block 920). For example, as described above, the wireless 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 the mobility history information.

[0167] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described in conjunction with one or more other processes described elsewhere herein.

[0168] Although Fig. 9 Example blocks of process 900 are shown, but in some aspects process 900 may include additional blocks, fewer blocks, different blocks, or different Fig. 9 Those blocks shown are arranged differently. Additionally or alternatively, two or more blocks of process 900 may be performed in parallel.

[0169] Fig.10is a diagram illustrating an example process 1000, for example, performed by a wireless node, in accordance with the present disclosure. Example process 1000 is an example of a wireless node (eg, wireless node 505, base station 110, UE 120, etc.) performing operations associated with mobility history reporting in new radio.

[0170] like Fig.10 As shown, in some aspects, process 1000 may include receiving a mobility history report configuration for providing mobility history information associated with a visited cell (block 1010). For example, as described above, the wireless node (e.g., using receive processor 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may receive a mobility history report configuration for providing mobility history information associated with a visited cell.

[0171] like Fig.10 As also shown in FIG. 1 , in some aspects, process 1000 may include sending a mobility history report including mobility history information to a parent node of the wireless node based at least in part on a mobility history report configuration, wherein the mobility history information includes: a global cell ID corresponding to a visited cell and a physical cell ID corresponding to the visited cell (block 1020). For example, as described above, the wireless node (e.g., using transmit processor 220, transmit processor 264, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may send a mobility history report including mobility history information to a parent node of the wireless node based at least in part on a mobility history report configuration. In some aspects, the mobility history information includes a global cell ID corresponding to a visited cell and a physical cell ID corresponding to the visited cell.

[0172] Process 1000 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.

[0173] In a first aspect, the visited cell includes at least one of an IAB node, a mobile node, or a combination thereof, and the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0174] In a second aspect, either alone or in combination with the first aspect, the mobility history information includes a mobility parameter set indicating at least one of: a cell ID associated with a visited cell, an entry time corresponding to a time when a wireless node enters the visited cell, an exit time corresponding to a time when the wireless node exits the visited cell, a duration of a wireless node's visit to the visited cell, or a combination thereof.

[0175] In a third aspect, alone or in combination with one or more of the first and second aspects, the mobility history information includes tracking information associated with a visited cell.

[0176] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the tracking information includes mobility state information associated with the visited cell, the mobility state information at least indicating whether the visited cell is mobile when the wireless node visits the visited cell.

[0177] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the process 1000 includes receiving mobility state information from a parent node providing a visited cell.

[0178] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the tracking information includes location information associated with the wireless node when the wireless node visits a visited cell.

[0179] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 1000 comprises determining that a dwell threshold is met, wherein the dwell threshold corresponds to a duration spent by the wireless node visiting a visited cell, wherein the tracking information comprises location information based at least in part on determining that the dwell threshold is met.

[0180] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, the visited cell includes at least one of an IAB node, a mobile node, or a combination thereof, and the tracking information includes location information based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0181] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the mobility history report configuration indicates at least one of the following: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof.

[0182] In the tenth aspect, alone or in combination with one or more of aspects one to nine, the mobility history report configuration indicates an event-triggered report of mobility history information, and process 1000 further includes: detecting the occurrence of a triggering event, wherein the wireless node sends the mobility history report based at least in part on detecting the occurrence of the triggering event.

[0183] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, detecting the occurrence of a triggering event includes determining that the wireless node has visited a certain number of cells within a time period after a previous transmission of a mobility history report, and the number of cells meets a threshold.

[0184] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, detecting the occurrence of a triggering event includes determining that the wireless node has visited a visited cell for a duration satisfying a threshold.

[0185] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, detecting the occurrence of a triggering event includes determining that a visited cell has the same global cell ID as another cell, and a physical cell ID of the visited cell is different from a physical cell ID of the other cell.

[0186] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, detecting the occurrence of a triggering event includes determining that a visited cell has the same physical cell ID as another cell, and a global cell ID of the visited cell is different from a global cell ID of the other cell.

[0187] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the wireless node includes a user equipment, a distributed unit of an IAB node, or a mobile terminal component of an IAB node.

[0188] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the visited cell is provided by a parent node of the wireless node, and the parent node includes a distributed unit of an IAB node or a mobile terminal component of an IAB node.

[0189] Although Fig.10 Example blocks of process 1000 are shown, but in some aspects process 1000 may include additional blocks, fewer blocks, different blocks, or different Fig.10 Those blocks shown are arranged differently. Additionally or alternatively, two or more blocks of process 1000 may be performed in parallel.

[0190] Fig.11 is a diagram illustrating an example process 1100, for example, performed by a wireless node, in accordance with the present disclosure. Example process 1100 is an example of a wireless node (eg, wireless node 505, base station 110, UE 120, etc.) performing operations associated with mobility history reporting in new radio.

[0191] like Fig.11As shown in FIG. 1 , in some aspects, process 1100 may include receiving a mobility history report including mobility history information associated with a visited cell from a child node of a wireless node, wherein the mobility history information includes: a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell, and performing an action based at least in part on the mobility history information (block 1110). For example, as described above, the wireless node (e.g., using receive processor 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may receive a mobility history report including mobility history information associated with a visited cell from a child node of the wireless node. In some aspects, the mobility history information includes a global cell ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell.

[0192] As shown in process 1100, in some aspects, process 1100 may include performing actions based at least in part on the mobility history information (block 1120). For example, as described above, the wireless node (e.g., transmit processor 220, transmit processor 264, using receive processor 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may receive a mobility history reporting configuration for providing mobility history information associated with a visited cell.

[0193] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described in conjunction with one or more other processes described elsewhere herein.

[0194] Although Fig.11 Example blocks of process 1100 are shown, but in some aspects process 1100 may include additional blocks, fewer blocks, different blocks, or different Fig.11 Those blocks shown are arranged differently. Additionally or alternatively, two or more blocks of process 1100 may be performed in parallel.

[0195] Fig.12 is a diagram illustrating an example process 1200, for example, performed by a wireless node, in accordance with the present disclosure. The example process 1200 is an example of a wireless node (eg, wireless node 505, base station 110, UE 120, etc.) performing operations associated with mobility history reporting in new radio.

[0196] like Fig.12As shown in FIG. 1 , in some aspects, process 1200 may include receiving a mobility history reporting configuration for providing mobility history information associated with a visited cell, wherein the mobility history reporting configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof (block 1210). For example, as described above, a wireless node (e.g., using receive processor 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may receive a mobility history reporting configuration for providing mobility history information associated with a visited cell. In some aspects, the mobility history reporting configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof.

[0197] like Fig.12 10. As also shown in FIG. 10, in some aspects, process 1200 may include sending a mobility history report including mobility history information to a parent node of the wireless node based at least in part on a mobility history report configuration (block 1220). For example, as described above, the wireless node (e.g., using transmit processor 220, transmit processor 264, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may send a mobility history report including mobility history information to a parent node of the wireless node based at least in part on a mobility history report configuration.

[0198] Process 1200 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.

[0199] In a first aspect, a mobility history report configuration indicates an event triggered report of mobility history information, and process 1200 further includes detecting an occurrence of a triggering event, wherein the wireless node sends the mobility history report based at least in part on detecting the occurrence of the triggering event.

[0200] In a second aspect, alone or in combination with the first aspect, detecting the occurrence of the triggering event includes determining that the wireless node has visited a number of cells within a time period following a previous transmission of a mobility history report, the number of cells satisfying a threshold.

[0201] In a third aspect, alone or in combination with one or more of the first and second aspects, detecting the occurrence of a triggering event includes determining that the wireless node has visited a visited cell for a duration satisfying a threshold.

[0202] In a fourth aspect, alone or in combination with one or more of the first to third aspects, detecting the occurrence of a triggering event includes determining that a visited cell has the same global cell ID as another cell, and a physical cell ID of the visited cell is different from a physical cell ID of the other cell.

[0203] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, detecting the occurrence of a triggering event includes determining that a visited cell has the same physical cell ID as another cell, and the global cell ID of the visited cell is different from the global cell ID of the other cell.

[0204] In a sixth aspect, either alone or in combination with one or more of aspects one to five, the mobility history information includes a mobility parameter set indicating at least one of: a cell ID associated with a visited cell, an entry time corresponding to a time when a wireless node enters a visited cell, an exit time corresponding to a time when a wireless node exits a visited cell, a duration of a wireless node's visit to a visited cell, or a combination thereof.

[0205] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the mobility history information includes tracking information associated with a visited cell.

[0206] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the tracking information includes mobility state information associated with the visited cell, the mobility state information at least indicating whether the visited cell is mobile when the wireless node visits the visited cell.

[0207] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the process 1200 includes receiving mobility state information from a parent node providing a visited cell.

[0208] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the tracking information includes location information associated with the wireless node when the wireless node is visiting a visited cell.

[0209] In an eleventh aspect, either alone or in combination with one or more of aspects one to ten, process 1200 comprises determining that a dwell threshold is met, wherein the dwell threshold corresponds to a duration spent by the wireless node visiting a visited cell, wherein the tracking information comprises location information based at least in part on determining that the dwell threshold is met.

[0210] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the visited cell includes at least one of an IAB node, a mobile node, or a combination thereof, and the tracking information includes location information based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0211] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the mobility history information includes: a global cell ID corresponding to a visited cell, and a physical cell ID corresponding to the visited cell.

[0212] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the visited cell includes at least one of an IAB node, a mobile node, or a combination thereof, and the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0213] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the wireless node includes a user equipment, a distributed unit of an IAB node, or a mobile terminal component of an IAB node.

[0214] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the visited cell is provided by a parent node of the wireless node, and the parent node includes a distributed unit of an IAB node or a mobile terminal component of an IAB node.

[0215] Although Fig.12 Example blocks of process 1200 are shown, but in some aspects process 1200 may include additional blocks, fewer blocks, different blocks, or different Fig.12 Those blocks shown are arranged differently. Additionally or alternatively, two or more blocks of process 1200 may be performed in parallel.

[0216] Fig.13 is a diagram illustrating an example process 1300, for example, performed by a wireless node, in accordance with the present disclosure. Example process 1300 is an example of a wireless node (eg, wireless node 505, base station 110, UE 120, etc.) performing operations associated with mobility history reporting in new radio.

[0217] like Fig.13As shown in FIG. 1 , in some aspects, process 1300 may include sending a mobility history reporting configuration for providing mobility history information associated with a visited cell to a child node of a wireless node, wherein the mobility history reporting configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof (block 1310). For example, as described above, a wireless node (e.g., using transmit processor 220, transmit processor 264, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may send a mobility history reporting configuration for providing mobility history information associated with a visited cell to a child node of a wireless node. In some aspects, the mobility history reporting configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof.

[0218] like Fig.13 13, in some aspects, process 1300 may include receiving, based at least in part on the mobility history report configuration, a mobility history report including mobility history information from a parent node of the wireless node (block 1320). For example, as described above, the wireless node (e.g., using transmit receiver 238, receive processor 258, controller / processor 240, controller / processor 280, memory 242, memory 282, etc.) may receive, based at least in part on the mobility history report configuration, a mobility history report including mobility history information from a parent node of the wireless node.

[0219] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described in conjunction with one or more other processes described elsewhere herein.

[0220] Although Fig.13 Example blocks of process 1300 are shown, but in some aspects process 1300 may include additional blocks, fewer blocks, different blocks, or different Fig.13 Those blocks shown are arranged differently. Additionally or alternatively, two or more blocks of process 1300 may be performed in parallel.

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

[0222] Aspect 1: A method of wireless communication performed by a wireless node in a wireless network, comprising: receiving a mobility history report configuration for providing mobility history information associated with a visited cell; and sending a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the wireless node enters a visited cell, an exit time corresponding to a time when the wireless node exits the visited cell, or a combination thereof.

[0223] Aspect 2: The method according to aspect 1, wherein the mobility parameter set further indicates at least one of: a cell identity (ID) associated with the visited cell, a duration for the wireless node to visit the visited cell, or a combination thereof.

[0224] Aspect 3: The method according to any one of Aspect 1 or Aspect 2, wherein the mobility history information comprises tracking information associated with a visited cell.

[0225] Aspect 4: The method according to aspect 3, wherein the tracking information includes mobility state information associated with the visited cell, wherein the mobility state information at least indicates whether the visited cell is mobile when the wireless node visits the visited cell.

[0226] Aspect 5: The method according to aspect 4 further comprises receiving mobility state information from a parent node providing a visited cell.

[0227] Aspect 6: The method according to any one of aspects 3 or 4, wherein the tracking information comprises location information associated with the wireless node when the wireless node is visiting a visited cell.

[0228] Aspect 7: The method according to aspect 6 further includes: determining that a dwell threshold is met, wherein the dwell threshold corresponds to a duration spent by the wireless node visiting the visited cell, wherein the tracking information includes location information based at least in part on determining that the dwell threshold is met.

[0229] Aspect 8: A method according to any one of Aspect 6 or Aspect 7, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the tracking information includes location information at least in part based on the visited cell including at least one of the IAB node, the mobile node, or a combination thereof.

[0230] Aspect 9: The method according to any one of aspects 1 to 8, wherein the mobility history information includes: a global cell identity (ID) corresponding to the visited cell; and a physical cell ID corresponding to the visited cell.

[0231] Aspect 10: A method according to aspect, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of the IAB node, the mobile node, or a combination thereof.

[0232] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the mobility history reporting configuration indicates at least one of the following: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof.

[0233] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the mobility history report configuration indicates an event-triggered report of mobility history information, and wherein the method further comprises: detecting the occurrence of a triggering event, wherein the wireless node sends the mobility history report at least in part based on detecting the occurrence of the triggering event.

[0234] Aspect 13: The method according to aspect 12, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited a certain number of cells within a time period after a previous transmission of the mobility history report, wherein the number of cells satisfies a threshold.

[0235] Aspect 14: The method according to any one of Aspect 12 or Aspect 13, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited the visited cell for a duration satisfying a threshold.

[0236] Aspect 15: The method according to any one of Aspects 12 to 14, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same global cell ID as another cell, wherein a physical cell ID of the visited cell is different from a physical cell ID of the other cell.

[0237] Aspect 16: The method according to any one of aspects 12 to 15, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same physical cell ID as another cell, wherein the global cell ID of the visited cell is different from the global cell ID of the other cell.

[0238] Aspect 17: The method according to any one of aspects 1 to 16, wherein the wireless node comprises a user equipment, a distributed unit of an integrated access and backhaul (IAB) node, or a mobile terminal component of an IAB node.

[0239] Aspect 18: The method according to any one of aspects 1 to 17, wherein the visited cell is provided by a parent node of the wireless node, and wherein the parent node comprises a distributed unit of an integrated access and backhaul (IAB) node or a mobile terminal component of the IAB node.

[0240] Aspect 19: A method of wireless communication performed by a wireless node, comprising: receiving a mobility history report containing mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of the following: an entry time corresponding to a time when the child node enters the visited cell, an exit time corresponding to a time when the child node exits the visited cell, or a combination thereof; and performing an action based at least in part on the mobility history information.

[0241] Aspect 20: The method according to aspect 19, wherein the mobility parameter set further indicates at least one of: a cell identity (ID) associated with the visited cell, a duration for the wireless node to visit the visited cell, or a combination thereof.

[0242] Aspect 21: The method according to any one of Aspect 19 or Aspect 20, wherein the mobility history information comprises tracking information associated with a visited cell.

[0243] Aspect 22: The method according to aspect 21, wherein the tracking information includes mobility state information associated with the visited cell, wherein the mobility state information at least indicates whether the visited cell is mobile when the wireless node visits the visited cell.

[0244] Aspect 23: The method of aspect 22, wherein the tracking information comprises location information associated with the wireless node when the wireless node is visiting a visited cell.

[0245] Aspect 24: The method of aspect 23, wherein the tracking information includes location information based at least in part on determining that a dwell threshold is satisfied, wherein the dwell threshold corresponds to a duration of time spent by the wireless node visiting a visited cell.

[0246] Aspect 25: A method according to any one of Aspect 22 or Aspect 23, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the tracking information includes location information at least in part based on the visited cell including at least one of the IAB node, the mobile node, or a combination thereof.

[0247] Aspect 26: The method according to any one of Aspects 19 to 25, wherein the mobility history information comprises: a global cell identity (ID) corresponding to the visited cell; and a physical cell ID corresponding to the visited cell.

[0248] Aspect 27: A method according to Aspect 26, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0249] Aspect 28: A method according to any one of Aspects 19 to 27, wherein the mobility history reporting configuration indicates at least one of the following: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof.

[0250] Aspect 29: The method according to any one of aspects 19 to 28, wherein the mobility history report configuration indicates an event-triggered report of the mobility history information, and wherein the method further comprises: receiving the mobility history report based at least in part on detecting the occurrence of a triggering event.

[0251] Aspect 30: The method according to aspect 29, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited a certain number of cells within a time period after a previous transmission of the mobility history report, wherein the number of cells satisfies a threshold.

[0252] Aspect 31: The method according to any one of Aspect 29 or Aspect 30, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited the visited cell for a duration satisfying a threshold.

[0253] Aspect 32: The method according to any one of Aspects 29 to 32, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same global cell ID as another cell, wherein a physical cell ID of the visited cell is different from a physical cell ID of the other cell.

[0254] Aspect 33: The method according to any one of Aspects 29 to 32, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same physical cell ID as another cell, wherein the global cell ID of the visited cell is different from the global cell ID of the other cell.

[0255] Aspect 34: The method according to any one of Aspects 19 to 33, wherein the wireless node comprises a user equipment, a distributed unit of an integrated access and backhaul (IAB) node, or a mobile terminal component of an IAB node.

[0256] Aspect 35: The method according to any one of Aspects 19 to 34, wherein the visited cell is provided by a parent node of the wireless node, and wherein the parent node comprises a distributed unit of an integrated access and backhaul (IAB) node or a mobile terminal component of the IAB node.

[0257] Aspect 36: A method of wireless communication performed by a wireless node in a wireless network, comprising: receiving a mobility history report configuration for providing mobility history information associated with a visited cell; and sending a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes tracking information associated with the visited cell.

[0258] Aspect 37: The method according to aspect 36, wherein the tracking information includes mobility state information associated with the visited cell, wherein the mobility state information at least indicates whether the visited cell is mobile when the wireless node visits the visited cell.

[0259] Aspect 38: The method according to Aspect 37 further comprises receiving mobility state information from a parent node providing the visited cell.

[0260] Aspect 39: The method according to any one of Aspect 36 or Aspect 37, wherein the tracking information comprises location information associated with the wireless node when the wireless node is visiting a visited cell.

[0261] Aspect 40: The method according to aspect 39, further comprising: determining that a dwell threshold is met, wherein the dwell threshold corresponds to a duration spent by the wireless node visiting a visited cell, wherein the tracking information includes location information based at least in part on determining that the dwell threshold is met.

[0262] Aspect 41: A method according to any one of Aspect 39 or Aspect 40, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the tracking information includes location information at least in part based on the visited cell including at least one of the IAB node, the mobile node, or a combination thereof.

[0263] Aspect 42: A method according to any one of Aspects 36 to 41, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of the following: a cell identifier (ID) associated with a visited cell, an entry time corresponding to the time when the wireless node enters the visited cell, an exit time corresponding to the time when the wireless node exits the visited cell, the duration of the wireless node's visit to the visited cell, or a combination thereof.

[0264] Aspect 43: The method according to any one of Aspects 36 to 42, wherein the mobility history information comprises: a global cell identity (ID) corresponding to the visited cell; and a physical cell ID corresponding to the visited cell.

[0265] Aspect 44: A method according to Aspect 43, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0266] Aspect 45: A method according to any one of Aspects 36 to 44, wherein the mobility history reporting configuration indicates at least one of the following: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof.

[0267] Aspect 46: A method according to any one of Aspects 36 to 45, wherein the mobility history report configuration indicates an event-triggered report of mobility history information, and wherein the method further comprises: detecting the occurrence of a triggering event, wherein the wireless node sends the mobility history report at least in part based on detecting the occurrence of the triggering event.

[0268] Aspect 47: The method according to aspect 46, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited a certain number of cells within a time period after a previous transmission of the mobility history report, wherein the number of cells satisfies a threshold.

[0269] Aspect 48: The method according to any one of Aspect 46 or Aspect 47, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited the visited cell for a duration satisfying a threshold.

[0270] Aspect 49: The method according to any one of Aspects 46 to 48, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same global cell ID as another cell, wherein a physical cell ID of the visited cell is different from a physical cell ID of the other cell.

[0271] Aspect 50: The method according to any one of Aspects 46 to 49, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same physical cell ID as another cell, wherein the global cell ID of the visited cell is different from the global cell ID of the other cell.

[0272] Aspect 51: The method according to any one of aspects 36 to 50, wherein the wireless node comprises a user equipment, a distributed unit of an integrated access and backhaul (IAB) node, or a mobile terminal component of an IAB node.

[0273] Aspect 52: The method according to any one of aspects 36 to 51, wherein the visited cell is provided by a parent node of the wireless node, and wherein the parent node comprises a distributed unit of an integrated access and backhaul (IAB) node or a mobile terminal component of the IAB node.

[0274] Aspect 53: A wireless communication method performed by a wireless node, comprising: receiving a mobility history report containing mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes tracking information associated with the visited cell; and performing an action based at least in part on the mobility history information.

[0275] Aspect 54: The method according to aspect 53, wherein the tracking information comprises mobility state information associated with the visited cell, wherein the mobility state information at least indicates whether the visited cell is mobile when the wireless node visits the visited cell.

[0276] Aspect 55: The method according to any one of Aspect 53 or Aspect 54, wherein the tracking information comprises location information associated with the wireless node when the wireless node is visiting a visited cell.

[0277] Aspect 56: The method of aspect 55, wherein the tracking information includes location information based at least in part on determining that a dwell threshold is satisfied, wherein the dwell threshold corresponds to a duration of time spent by the wireless node visiting a visited cell.

[0278] Aspect 57: A method according to any one of Aspect 55 or Aspect 56, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the tracking information includes location information at least in part based on the visited cell including at least one of the IAB node, the mobile node, or a combination thereof.

[0279] Aspect 58: A method according to any one of Aspects 53 to 57, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of the following: a cell identifier (ID) associated with a visited cell, an entry time corresponding to the time when the wireless node enters the visited cell, an exit time corresponding to the time when the wireless node exits the visited cell, the duration of the wireless node's visit to the visited cell, or a combination thereof.

[0280] Aspect 59: The method according to any one of Aspects 53 to 58, wherein the mobility history information comprises: a global cell identity (ID) corresponding to the visited cell; and a physical cell ID corresponding to the visited cell.

[0281] Aspect 60: A method according to Aspect 59, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0282] Aspect 61: A method according to any one of Aspects 53 to 60, wherein the mobility history reporting configuration indicates at least one of the following: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof.

[0283] Aspect 62: The method according to any one of aspects 53 to 61, wherein the mobility history report configuration indicates an event triggered report of the mobility history information, and wherein the method further comprises: receiving the mobility history report based at least in part on detecting the occurrence of a triggering event.

[0284] Aspect 63: The method according to aspect 62, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited a certain number of cells within a time period after a previous transmission of the mobility history report, wherein the number of cells satisfies a threshold.

[0285] Aspect 64: The method according to any one of Aspect 62 or Aspect 63, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited the visited cell for a duration satisfying a threshold.

[0286] Aspect 65: The method according to any one of Aspects 62 to 64, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same global cell ID as another cell, wherein a physical cell ID of the visited cell is different from a physical cell ID of the other cell.

[0287] Aspect 66: The method according to any one of Aspects 62 to 65, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same physical cell ID as another cell, wherein the global cell ID of the visited cell is different from the global cell ID of the other cell.

[0288] Aspect 67: A method according to any one of Aspects 53 to 66, wherein the wireless node comprises a user equipment, a distributed unit of an integrated access and backhaul (IAB) node, or a mobile terminal component of an IAB node.

[0289] Aspect 68: The method according to any one of Aspects 53 to 67, wherein the visited cell is provided by a parent node of the wireless node, and wherein the parent node comprises a distributed unit of an integrated access and backhaul (IAB) node or a mobile terminal component of the IAB node.

[0290] Aspect 69: A method of wireless communication performed by a wireless node in a wireless network, comprising: receiving a mobility history report configuration for providing mobility history information associated with a visited cell; and sending a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes: a global cell identifier (ID) corresponding to the visited cell and a physical cell ID corresponding to the visited cell.

[0291] Aspect 70: A method according to Aspect 69, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0292] Aspect 71: A method according to any one of Aspect 69 or Aspect 70, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of the following: a cell identifier (ID) associated with a visited cell, an entry time corresponding to the time when the wireless node enters the visited cell, an exit time corresponding to the time when the wireless node exits the visited cell, the duration of the wireless node's visit to the visited cell, or a combination thereof.

[0293] Aspect 72: The method according to any one of Aspects 69 to 71, wherein the mobility history information comprises tracking information associated with a visited cell.

[0294] Aspect 73: The method according to aspect 72, wherein the tracking information includes mobility state information associated with the visited cell, wherein the mobility state information at least indicates whether the visited cell is mobile when the wireless node visits the visited cell.

[0295] Aspect 74: The method according to Aspect 73 further comprises receiving mobility state information from a parent node providing the visited cell.

[0296] Aspect 75: The method according to any one of Aspects 72 to 74, wherein the tracking information comprises location information associated with the wireless node when the wireless node is visiting a visited cell.

[0297] Aspect 76: The method according to aspect 75 further includes: determining that a dwell threshold is met, wherein the dwell threshold corresponds to a duration spent by the wireless node visiting the visited cell, wherein the tracking information includes location information based at least in part on determining that the dwell threshold is met.

[0298] Aspect 77: A method according to any one of Aspect 75 or Aspect 76, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the tracking information includes location information at least in part based on the visited cell including at least one of the IAB node, the mobile node, or a combination thereof.

[0299] Aspect 78: A method according to any one of Aspects 69 to 70, wherein the mobility history reporting configuration indicates at least one of the following: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof.

[0300] Aspect 79: A method according to any one of Aspects 69 to 78, wherein the mobility history report configuration indicates an event-triggered report of mobility history information, and wherein the method further comprises: detecting the occurrence of a triggering event, wherein the wireless node sends the mobility history report at least in part based on detecting the occurrence of the triggering event.

[0301] Aspect 80: The method according to aspect 79, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited a certain number of cells within a time period after a previous transmission of the mobility history report, wherein the number of cells satisfies a threshold.

[0302] Aspect 81: The method according to any one of Aspect 79 or Aspect 80, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited the visited cell for a duration satisfying a threshold.

[0303] Aspect 82: The method according to any one of Aspects 79 to 81, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same global cell ID as another cell, wherein the physical cell ID of the visited cell is different from the physical cell ID of the other cell.

[0304] Aspect 83: The method according to any one of Aspects 79 to 82, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same physical cell ID as another cell, wherein the global cell ID of the visited cell is different from the global cell ID of the other cell.

[0305] Aspect 84: A method according to any one of Aspects 69 to 83, wherein the wireless node comprises a user equipment, a distributed unit of an integrated access and backhaul (IAB) node, or a mobile terminal component of an IAB node.

[0306] Aspect 85: The method according to any one of Aspects 69 to 84, wherein the visited cell is provided by a parent node of the wireless node, and wherein the parent node comprises a distributed unit of an integrated access and backhaul (IAB) node or a mobile terminal component of the IAB node.

[0307] Aspect 86: A wireless communication method performed by a wireless node, comprising: receiving a mobility history report containing mobility history information associated with a visited cell from a child node of the wireless node, wherein the mobility history information includes: a global cell identifier (ID) corresponding to the visited cell and a physical cell ID corresponding to the visited cell; and performing an action based at least in part on the mobility history information.

[0308] Aspect 87: A method according to Aspect 86, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0309] Aspect 88: A method according to any one of Aspect 86 or Aspect 87, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of the following: a cell identifier (ID) associated with a visited cell, an entry time corresponding to the time when the wireless node enters the visited cell, an exit time corresponding to the time when the wireless node exits the visited cell, the duration of the wireless node's visit to the visited cell, or a combination thereof.

[0310] Aspect 89: The method according to any one of Aspect 86 to Aspect 88, wherein the mobility history information comprises tracking information associated with a visited cell.

[0311] Aspect 90: The method according to aspect 89, wherein the tracking information comprises mobility state information associated with the visited cell, wherein the mobility state information indicates at least whether the visited cell is mobile when the wireless node visits the visited cell.

[0312] Aspect 91: The method of aspect 90, wherein the tracking information comprises location information associated with the wireless node when the wireless node is visiting a visited cell.

[0313] Aspect 92: The method of aspect 91, wherein the tracking information includes location information based at least in part on determining that a dwell threshold is satisfied, wherein the dwell threshold corresponds to a duration of time spent by the wireless node visiting a visited cell.

[0314] Aspect 93: A method according to any one of Aspect 91 or Aspect 92, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the tracking information includes location information at least in part based on the visited cell including at least one of the IAB node, the mobile node, or a combination thereof.

[0315] Aspect 94: A method according to any one of Aspects 86 to 93, wherein the mobility history reporting configuration indicates at least one of the following: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof.

[0316] Aspect 95: The method according to any one of aspects 86 to 94, wherein the mobility history report configuration indicates an event triggered report of the mobility history information, and wherein the method further comprises: receiving the mobility history report based at least in part on detecting the occurrence of a triggering event.

[0317] Aspect 96: The method according to aspect 95, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited a certain number of cells within a time period after a previous transmission of the mobility history report, wherein the number of cells satisfies a threshold.

[0318] Aspect 97: The method according to any one of Aspect 95 or Aspect 96, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited the visited cell for a duration satisfying a threshold.

[0319] Aspect 98: The method according to any one of Aspects 95 to 97, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same global cell ID as another cell, wherein the physical cell ID of the visited cell is different from the physical cell ID of the other cell.

[0320] Aspect 99: The method according to any one of Aspects 95 to 98, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same physical cell ID as another cell, wherein the global cell ID of the visited cell is different from the global cell ID of the other cell.

[0321] Aspect 100: The method according to any one of aspects 86 to 99, wherein the wireless node comprises a user equipment, a distributed unit of an integrated access and backhaul (IAB) node, or a mobile terminal component of an IAB node.

[0322] Aspect 101: The method according to any one of aspects 86 to 100, wherein the visited cell is provided by a parent node of the wireless node, and wherein the parent node comprises a distributed unit of an integrated access and backhaul (IAB) node or a mobile terminal component of the IAB node.

[0323] Aspect 102: A method of wireless communication performed by a wireless node in a wireless network, comprising: receiving a mobility history report configuration for providing mobility history information associated with a visited cell, wherein the mobility history report configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof; and sending a mobility history report containing the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration.

[0324] Aspect 103: A method according to aspect 102, wherein the mobility history report configuration indicates an event triggered report of the mobility history information, and wherein the method further comprises: detecting an occurrence of a triggering event, wherein the wireless node sends the mobility history report based at least in part on detecting the occurrence of the triggering event.

[0325] Aspect 104: The method according to aspect 103, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited a certain number of cells within a time period after a previous transmission of the mobility history report, wherein the number of cells satisfies a threshold.

[0326] Aspect 105: The method according to any one of Aspect 103 or Aspect 104, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited the visited cell for a duration satisfying a threshold.

[0327] Aspect 106: The method according to any one of aspects 103 to 105, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same global cell ID as another cell, wherein a physical cell ID of the visited cell is different from a physical cell ID of the other cell.

[0328] Aspect 107: The method according to any one of aspects 103 to 106, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same physical cell ID as another cell, wherein the global cell ID of the visited cell is different from the global cell ID of the other cell.

[0329] Aspect 108: A method according to any one of Aspects 102 to 107, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of the following: a cell identifier (ID) associated with a visited cell, an entry time corresponding to a time when a wireless node enters a visited cell, an exit time corresponding to a time when a wireless node exits a visited cell, a duration of a wireless node's visit to a visited cell, or a combination thereof.

[0330] Aspect 109: The method according to any one of aspects 102 to 107, wherein the mobility history information comprises tracking information associated with a visited cell.

[0331] Aspect 110: The method according to aspect 109, wherein the tracking information comprises mobility state information associated with the visited cell, wherein the mobility state information indicates at least whether the visited cell is mobile when the wireless node visits the visited cell.

[0332] Aspect 111: The method according to aspect 110, further comprising receiving mobility state information from a parent node providing a visited cell.

[0333] Aspect 112: The method according to any one of aspects 109-111, wherein the tracking information comprises location information associated with the wireless node when the wireless node is visiting a visited cell.

[0334] Aspect 113: The method according to aspect 112 further includes: determining that a dwell threshold is met, wherein the dwell threshold corresponds to a duration spent by the wireless node visiting a visited cell, wherein the tracking information includes location information based at least in part on determining that the dwell threshold is met.

[0335] Aspect 114: A method according to any one of Aspect 112 or Aspect 113, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the tracking information includes location information at least in part based on the visited cell including at least one of the IAB node, the mobile node, or a combination thereof.

[0336] Aspect 115: The method according to any one of aspects 102 to 114, wherein the mobility history information comprises: a global cell identity (ID) corresponding to the visited cell; and a physical cell ID corresponding to the visited cell.

[0337] Aspect 116: A method according to Aspect 115, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0338] Aspect 117: The method according to any one of aspects 102 to 116, wherein the wireless node comprises a user equipment, a distributed unit of an integrated access and backhaul (IAB) node, or a mobile terminal component of an IAB node.

[0339] Aspect 118: The method according to any one of aspects 102 to 117, wherein the visited cell is provided by a parent node of the wireless node, and wherein the parent node comprises a distributed unit of an integrated access and backhaul (IAB) node or a mobile terminal component of the IAB node.

[0340] Aspect 119: A method of wireless communication performed by a wireless node, comprising: sending a mobility history report configuration for providing mobility history information associated with a visited cell to a subnode of the wireless node, wherein the mobility history report configuration indicates at least one of: periodic reporting of mobility history information, semi-persistent reporting of mobility history information, event-triggered reporting of mobility history information, dynamic request reporting of mobility history information, or a combination thereof; and receiving a mobility history report containing the mobility history information from the subnode of the wireless node based at least in part on the mobility history report configuration.

[0341] Aspect 120: The method according to aspect 119, wherein the mobility history report configuration indicates an event triggered report of the mobility history information, and wherein the method further comprises: receiving the mobility history report based at least in part on detecting an occurrence of a triggering event.

[0342] Aspect 121: The method according to aspect 120, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited a certain number of cells within a time period after a previous transmission of the mobility history report, wherein the number of cells satisfies a threshold.

[0343] Aspect 122: The method according to any one of Aspect 120 or Aspect 121, wherein detecting the occurrence of the triggering event comprises determining that the wireless node has visited the visited cell for a duration satisfying a threshold.

[0344] Aspect 123: The method according to any one of aspects 120 to 122, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same global cell ID as another cell, wherein a physical cell ID of the visited cell is different from a physical cell ID of the other cell.

[0345] Aspect 124: The method according to any one of aspects 120 to 123, wherein detecting the occurrence of the triggering event comprises determining that the visited cell has the same physical cell ID as another cell, wherein the global cell ID of the visited cell is different from the global cell ID of the other cell.

[0346] Aspect 125: A method according to any one of Aspects 119 to 124, wherein the mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of the following: a cell identifier (ID) associated with a visited cell, an entry time corresponding to a time when a wireless node enters the visited cell, an exit time corresponding to a time when the wireless node exits the visited cell, a duration of a wireless node's visit to the visited cell, or a combination thereof.

[0347] Aspect 126: The method according to any one of aspects 119 to 126, wherein the mobility history information comprises tracking information associated with a visited cell.

[0348] Aspect 127: The method according to aspect 126, wherein the tracking information comprises mobility state information associated with the visited cell, wherein the mobility state information at least indicates whether the visited cell is mobile when the wireless node visits the visited cell.

[0349] Aspect 128: The method according to any of Aspect 126 or Aspect 127, wherein the tracking information comprises location information associated with the wireless node when the wireless node is visiting a visited cell.

[0350] Aspect 129: The method of aspect 128, wherein the tracking information includes location information based at least in part on determining that a dwell threshold is satisfied, wherein the dwell threshold corresponds to a duration of time spent by the wireless node visiting a visited cell.

[0351] Aspect 130: A method according to any one of Aspect 128 or Aspect 129, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the tracking information includes location information at least in part based on the visited cell including at least one of the IAB node, the mobile node, or a combination thereof.

[0352] Aspect 131: The method according to any one of Aspects 119 to 130, wherein the mobility history information comprises: a global cell identity (ID) corresponding to the visited cell; and a physical cell ID corresponding to the visited cell.

[0353] Aspect 132: A method according to Aspect 131, wherein the visited cell includes at least one of an integrated access and backhaul (IAB) node, a mobile node, or a combination thereof, and wherein the mobility history information includes a global cell ID and a physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

[0354] Aspect 133: The method according to any one of Aspects 119 to 132, wherein the wireless node comprises a user equipment, a distributed unit of an integrated access and backhaul (IAB) node, or a mobile terminal component of an IAB node.

[0355] Aspect 134: The method according to any one of aspects 119 to 133, wherein the visited cell is provided by a parent node of the wireless node, and wherein the parent node comprises a distributed unit of an integrated access and backhaul (IAB) node or a mobile terminal component of the IAB node.

[0356] Aspect 135: 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 one or more methods of aspects 1-18.

[0357] Aspect 136: 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 Aspect 1-Aspect 18.

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

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

[0360] Aspect 139: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of Aspect 1-Aspect 18.

[0361] Aspect 140: 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 one or more methods of aspects 19-35.

[0362] Aspect 141: 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 Aspect 19-Aspect 35.

[0363] Aspect 142: An apparatus for wireless communication, comprising at least one component for performing the method of one or more aspects of Aspect 19-Aspect 35.

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

[0365] Aspect 144: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more methods of aspects 19-35.

[0366] Aspect 145: 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 one or more methods of aspects 36-52.

[0367] Aspect 146: 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 Aspect 36-Aspect 52.

[0368] Aspect 147: An apparatus for wireless communication, comprising at least one component for performing the method of one or more aspects of Aspect 36-Aspect 52.

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

[0370] Aspect 149: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of Aspect 36-Aspect 52.

[0371] Aspect 150: 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 one or more methods of aspects 53-68.

[0372] Aspect 151: 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 Aspect 53-Aspect 68.

[0373] Aspect 152: An apparatus for wireless communication, comprising at least one component for performing the method of one or more aspects of Aspect 53-Aspect 68.

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

[0375] Aspect 154: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of Aspect 53-Aspect 68.

[0376] Aspect 155: 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 one or more methods of aspects 69-85.

[0377] Aspect 156: 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 Aspect 69-Aspect 85.

[0378] Aspect 157: An apparatus for wireless communication, comprising at least one component for performing the method of one or more aspects of Aspect 69-Aspect 85.

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

[0380] Aspect 159: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more methods of aspects 69-85.

[0381] Aspect 160: 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 one or more methods of aspects 86-101.

[0382] Aspect 161: 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 Aspect 86-Aspect 101.

[0383] Aspect 162: An apparatus for wireless communication, comprising at least one component for performing the method of one or more aspects of Aspect 86-Aspect 101.

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

[0385] Aspect 164: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more methods of aspects 86-101.

[0386] Aspect 165: 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 one or more methods of aspects 102-118.

[0387] Aspect 166: 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 configured to perform the method of one or more aspects of aspects 102-118.

[0388] Aspect 167: An apparatus for wireless communication, comprising at least one component for performing the method of one or more aspects of Aspects 102-118.

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

[0390] Aspect 169: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of aspects 102-118.

[0391] Aspect 170: 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 one or more methods of aspects 119-134.

[0392] Aspect 171: 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 119-134.

[0393] Aspect 172: An apparatus for wireless communication, comprising at least one component for performing the method of one or more aspects of Aspect 119-Aspect 134.

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

[0395] Aspect 174: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of aspects 119-134.

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

[0397] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other, "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, etc. As used herein, the processor is implemented in hardware and / or a combination of hardware and software. Obviously, the system and / or method described herein can be implemented in different forms of hardware and / or a combination of hardware and software. 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 can be understood that software and hardware can be designed to implement a system and / or method based at least in part on the description of this article.

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

[0399] Although specific combinations of features are listed in the claims and / or specific combinations of features are disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner that is not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below can directly rely on only one claim, the disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one" referring to the list of items refers to any combination of these items, including single members. As an example, "at least one of a, b or c" is intended to cover a, b, c, ab, ac, bc and abc, and any combination with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, ccc or any other order of a, b and c).

[0400] Unless explicitly described in this way, any element, behavior or instruction used in this article is not interpreted as critical or necessary. Moreover, as used herein, the articles "one" and "an" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more quoted items associated with the article "said", and can be used interchangeably with "said one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more projects (e.g., related items, unrelated items, or a combination of related and unrelated items, etc.), and can be used interchangeably with "one or more". If only one project is intended, the phrase "only one" or similar language is used. Moreover, as used herein, the terms "have", "have", "contain", etc. are intended to be open terms. In addition, unless otherwise clearly stated, the phrase "based on" is intended to mean "based at least in part". Moreover, as used herein, the term "or" is intended to be inclusive when used in a series, and can be used interchangeably with "and / or", unless otherwise clearly stated (e.g., if used in combination with "any" or "only one of them").

Claims

1. A wireless node for wireless communication, comprising: Memory; as well as One or more processors, coupled to the memory, configured to: receiving a mobility history reporting configuration for providing mobility history information associated with a visited cell; and sending a mobility history report including the mobility history information to a parent node of the wireless node based at least in part on the mobility history report configuration, wherein the mobility history information includes tracking information associated with the visited cell, and the tracking information includes mobility state information associated with the visited cell, wherein the mobility state information at least indicates whether the visited cell was mobile when the wireless node visited the visited cell, and wherein the mobility history information further includes at least one of a pair of cell identifiers or a mobility parameter set, the pair of cell identifiers including a global cell identifier ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell, wherein the mobility parameter set indicates at least one of: an entry time corresponding to a time when the wireless node enters the visited cell, an exit time corresponding to the time when the wireless node exits the visited cell, or Those A combination of them.

2. The wireless node according to claim 1, wherein: The mobility parameter set further indicates at least one of the following: a cell ID associated with the visited cell, duration of the wireless node's visit to the visited cell, or A combination of them.

3. The wireless node according to claim 1, wherein: The one or more processors are further configured to receive the mobility state information from a parent node providing the visited cell.

4. The wireless node according to claim 1, wherein: The tracking information includes location information associated with the wireless node while the wireless node is visiting the visited cell.

5. The wireless node according to claim 4, wherein: The one or more processors are further configured to: determining that a dwell threshold is satisfied, wherein the dwell threshold corresponds to a duration of time spent by the wireless node visiting the visited cell, Wherein the tracking information includes the location information based at least in part on determining that the dwell threshold is satisfied.

6. The wireless node according to claim 4, wherein: The visited cell includes at least one of an integrated access and backhaul IAB node, a mobile node, or a combination thereof, and The tracking information includes the location information based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

7. The wireless node according to claim 1, wherein: The mobility history information includes: a global cell ID corresponding to the visited cell; and The physical cell ID corresponding to the visited cell.

8. The wireless node according to claim 7, wherein: The visited cell includes at least one of an integrated access and backhaul IAB node, a mobile node, or a combination thereof, and The mobility history information includes the global cell ID and the physical cell ID based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

9. The wireless node according to claim 1, wherein: The mobility history reporting configuration indicates at least one of the following: periodic reporting of said mobility history information, semi-persistent reporting of the mobility history information, Event-triggered reporting of the mobility history information, Dynamic request report of the mobility history information, or A combination of them.

10. The wireless node of claim 1, wherein: The mobility history reporting configuration indicates an event triggered reporting of the mobility history information, and wherein the one or more processors are further configured to: Detect the occurrence of a trigger event, The wireless node sends the mobility history report based at least in part on detecting an occurrence of the triggering event.

11. The wireless node according to claim 10, wherein: To detect the occurrence of the triggering event, the one or more processors are configured to determine that the wireless node has visited a number of cells within a time period following a previous transmission of a mobility history report, wherein the number of cells satisfies a threshold.

12. The wireless node of claim 10, wherein: To detect the occurrence of the trigger event, the one or more processors are configured to determine that the wireless node has visited the visited cell for a duration that satisfies a threshold.

13. The wireless node of claim 10, wherein: To detect the occurrence of the triggering event, the one or more processors are configured to determine that the visited cell has the same global cell ID as another cell, wherein a physical cell ID of the visited cell is different from a physical cell ID of the another cell.

14. The wireless node of claim 10, wherein: To detect the occurrence of the triggering event, the one or more processors are configured to determine that the visited cell has the same physical cell ID as another cell, wherein a global cell ID of the visited cell is different from a global cell ID of the another cell.

15. A wireless node for wireless communication, comprising: Memory; as well as One or more processors, coupled to the memory, configured to: Receiving, from a child node of the wireless node, a mobility history report including mobility history information associated with a visited cell, wherein the mobility history information includes tracking information associated with the visited cell, and the tracking information includes mobility state information associated with the visited cell, wherein the mobility state information at least indicates whether the visited cell was mobile when the wireless node visited the visited cell, and wherein the mobility history information further includes at least one of a pair of cell identifiers or a mobility parameter set, the pair of cell identifiers including a global cell identifier ID corresponding to the visited cell and a physical cell ID corresponding to the visited cell, wherein the mobility parameter set indicates at least one of: an entry time corresponding to the time when the child node enters the visited cell, an exit time corresponding to the time when the child node exits the visited cell, or a combination thereof; and An action is performed based at least in part on the mobility history information.

16. A wireless node for wireless communication, comprising: Memory; as well as One or more processors, coupled to the memory, configured to: receiving a mobility history reporting configuration for providing mobility history information associated with a visited cell; and Based at least in part on the mobility history report configuration, a mobility history report including the mobility history information is sent to a parent node of the wireless node, wherein the mobility history information includes tracking information associated with the visited cell, wherein the tracking information includes mobility state information associated with the visited cell, and wherein the mobility state information at least indicates whether the visited cell is mobile when the wireless node visits the visited cell.

17. The wireless node of claim 16, wherein: The one or more processors are further configured to receive the mobility state information from a parent node providing the visited cell.

18. The wireless node of claim 16, wherein: The tracking information includes location information associated with the wireless node while the wireless node is visiting the visited cell.

19. The wireless node of claim 18, wherein: The one or more processors are further configured to: determining that a dwell threshold is satisfied, wherein the dwell threshold corresponds to a duration of time spent by the wireless node visiting the visited cell, Wherein the tracking information includes the location information based at least in part on determining that the dwell threshold is satisfied.

20. The wireless node of claim 18, wherein: The visited cell includes at least one of an integrated access and backhaul IAB node, a mobile node, or a combination thereof, and The tracking information includes the location information based at least in part on the visited cell including at least one of an IAB node, a mobile node, or a combination thereof.

21. The wireless node of claim 16, wherein: The mobility history information includes a mobility parameter set, wherein the mobility parameter set indicates at least one of the following: a cell identification ID associated with the visited cell, an entry time corresponding to a time when the wireless node enters the visited cell, an exit time corresponding to a time when the wireless node exits the visited cell, duration of the wireless node's visit to the visited cell, or A combination of them.

22. The wireless node of claim 16, wherein: The mobility history reporting configuration indicates an event triggered reporting of the mobility history information, and wherein the one or more processors are further configured to: Detect the occurrence of a trigger event, The wireless node sends the mobility history report based at least in part on detecting an occurrence of the triggering event.

23. The wireless node of claim 22, wherein: To detect the occurrence of the triggering event, the one or more processors are configured to determine that the wireless node has visited a number of cells within a time period following a previous transmission of a mobility history report, wherein the number of cells satisfies a threshold.

24. The wireless node of claim 22, wherein: To detect the occurrence of the trigger event, the one or more processors are configured to determine that the wireless node has visited the visited cell for a duration that satisfies a threshold.

25. The wireless node of claim 22, wherein: To detect the occurrence of the triggering event, the one or more processors are configured to determine that the visited cell has the same global cell ID as another cell, wherein a physical cell ID of the visited cell is different from a physical cell ID of the another cell.

26. The wireless node of claim 22, wherein: To detect the occurrence of the triggering event, the one or more processors are configured to determine that the visited cell has the same physical cell ID as another cell, wherein a global cell ID of the visited cell is different from a global cell ID of the another cell.

27. A wireless node for wireless communication, comprising: Memory; as well as One or more processors, coupled to the memory, configured to: receiving, from a child node of the wireless node, a mobility history report including mobility history information associated with a visited cell, wherein the mobility history information includes tracking information associated with the visited cell, wherein the tracking information includes mobility state information associated with the visited cell, and wherein the mobility state information indicates at least whether the visited cell was mobile when the wireless node was visiting the visited cell; and An action is performed based at least in part on the mobility history information.

Images