Management of identifiers in integrated access and backhaul networks

Abstract

Various aspects of this disclosure generally relate to wireless communications. In some aspects, a central entity in an Integrated Access and Backhaul (IAB) network can: determine, at least in part, based on at least one of the following, that triggering conditions for updating transport network layer information of IAB nodes in the IAB network are met: a change in a donor distributed unit associated with an IAB node, a change in a central entity associated with an IAB node, or the establishment, release, or modification of a route including an IAB node; and provide updated transport network layer information to the IAB nodes, at least in part based on the satisfaction of the triggering conditions. Many other aspects are described.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 936,336, filed November 15, 2019, entitled “Management of IDENTIFIERS IN AN INTEGRATED ACCESS AND BACKHAUL NETWORK”; U.S. Provisional Patent Application No. 62 / 937,228, filed November 18, 2019, entitled “Management of IDENTIFIERS IN AN INTEGRATED ACCESS AND BACKHAUL NETWORK”; and U.S. Non-Provisional Patent Application No. 16 / 949,747, filed November 12, 2020, entitled “Management of IDENTIFIERS IN AN INTEGRATED ACCESS AND BACKHAUL NETWORK”, which are expressly incorporated herein by reference. Technical Field

[0003] Various aspects of this disclosure generally relate to wireless communications and techniques and apparatus for managing identifiers in integrated access and backhaul (IAB) networks. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless communication network may include several base stations (BSs) capable of supporting communication for multiple user equipments (UEs). UEs can communicate with base stations (BSs) via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the BS to the UE, while an uplink (or reverse link) refers to the communication link from the UE to the 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 aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different user equipment to communicate at the municipal, national, regional, and even global levels. New Radio (NR), also known as 5G, is a set of enhancements to the LTE mobile standard issued by the 3rd Generation Partnership Project (3GPP). NR aims to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards 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 Diffused OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies, and carrier aggregation. However, due to the continued growth in demand for mobile broadband access, there is a need for further improvements to LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0007] In some aspects, a method for wireless communication performed by a central entity in an Integrated Access and Backhaul (IAB) network may include: determining, at least in part, a triggering condition for updating transport network layer information of IAB nodes in the IAB network based on at least one of the following: a change in a donor distributed unit associated with an IAB node, a change in a central entity associated with an IAB node, or the establishment, release, or modification of a route including an IAB node; and providing the updated transport network layer information to the IAB nodes based at least in part on the satisfaction of the triggering condition.

[0008] In some aspects, a method for wireless communication performed by a central entity in an Integrated Access and Backhaul (IAB) network may include: determining triggering conditions that satisfy the identifiers of IAB nodes used to update the IAB network; and providing the updated identifiers to the IAB nodes, at least in part based on the determination that the triggering conditions are satisfied.

[0009] In some aspects, a method for wireless communication performed by a central entity in an Integrated Access and Backhaul (IAB) network may include: determining that triggering conditions are met for updating one or more cell identifiers of an IAB node in the IAB network, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node; and providing one or more updated cell identifiers to the IAB node, at least in part based on the determination that the triggering conditions are met.

[0010] In some aspects, a method of wireless communication performed by an IAB node in an Integrated Access and Backhaul (IAB) network may include: receiving updated transport network layer information based at least in part on satisfying triggering conditions for updating transport network layer information, wherein the triggering conditions are based at least in part on at least one of the following: a change in a donor distributed unit associated with the IAB node, a change in a central entity associated with the IAB node, or the establishment, release, or modification of a route including the IAB node; and performing communication using the updated transport network layer information.

[0011] In some aspects, a method for wireless communication performed by an IAB node in an Integrated Access and Backhaul (IAB) network may include: receiving an updated cell identifier of an IAB node based at least in part on triggering conditions for updating the identifier of an IAB node in the IAB network; and performing communication using the updated identifier.

[0012] In some aspects, a method for wireless communication performed by an IAB node in an Integrated Access and Backhaul (IAB) network may include: receiving one or more updated cell identifiers of the IAB node, at least in part based on the satisfaction of triggering conditions, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node; and using the one or more updated cell identifiers to perform communication.

[0013] In some aspects, a central entity of an IAB network may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: determine, at least in part, based on at least one of the following, that triggering conditions for updating transport network layer information of IAB nodes in the IAB network are met: a change in a donor distributed unit associated with an IAB node, a change in a central entity associated with an IAB node, or the establishment, release, or modification of a route including an IAB node; and provide updated transport network layer information to the IAB nodes, at least in part based on the satisfaction of the triggering conditions.

[0014] In some aspects, a central entity of an IAB network may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: determine that triggering conditions are met for updating one or more cell identifiers of IAB nodes in the IAB network, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB nodes; and provide one or more updated cell identifiers to the IAB nodes, at least in part based on the determination that the triggering conditions are met.

[0015] In some aspects, a central entity of an IAB network may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive updated transport network layer information based at least in part on satisfying triggering conditions for updating transport network layer information, wherein the triggering conditions are based at least in part on at least one of the following: a change in a donor distributed unit associated with an IAB node, a change in a central entity associated with an IAB node, or the establishment, release, or modification of a route including an IAB node; and perform communication using the updated transport network layer information.

[0016] In some aspects, a central entity of an IAB network may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive an updated identifier of an IAB node based at least in part on triggering conditions for updating the identifier of an IAB node in the IAB network; and use the updated identifier to perform communication.

[0017] In some aspects, a central entity of an IAB network may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive, at least in part, one or more updated cell identifiers of an IAB node based on the satisfaction of a triggering condition, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node; and perform communications using the one or more updated cell identifiers.

[0018] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a central entity of an IAB network, the one or more instructions may cause the one or more processors to: determine, at least in part, based on at least one of the following: a change in a donor distributed unit associated with an IAB node, a change in a central entity associated with an IAB node, or the establishment, release, or modification of a route including an IAB node; and provide the updated transport network layer information to the IAB node, at least in part based on the satisfaction of the triggering condition.

[0019] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a central entity of an IAB network, the one or more instructions may cause the one or more processors to: determine that triggering conditions for updating the identifier of an IAB node in the IAB network are met; and, based at least in part on the determination that the triggering conditions are met, provide the updated identifier to the IAB node.

[0020] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a central entity of an IAB network, the one or more instructions may cause the one or more processors to: determine that triggering conditions are met for updating one or more cell identifiers of IAB nodes of the IAB network, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB nodes; and provide the one or more updated cell identifiers to the IAB nodes, at least in part based on the determination that the triggering conditions are met.

[0021] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of an IAB node in an IAB network, the one or more instructions may cause the one or more processors to: receive updated transport network layer information based at least in part on satisfying triggering conditions for updating transport network layer information, wherein the triggering conditions are based at least in part on at least one of: a change in a donor distributed unit associated with the IAB node, a change in a central entity associated with the IAB node, or the establishment, release, or modification of a route including the IAB node; and perform communication using the updated transport network layer information.

[0022] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of an IAB node in an IAB network, the one or more instructions may cause the one or more processors to: receive an updated identifier of an IAB node based at least in part on a triggering condition for updating the identifier of an IAB node in the IAB network; and perform communication using the updated identifier.

[0023] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of an IAB node in an IAB network, the one or more instructions may cause the one or more processors to: receive one or more updated cell identifiers of the IAB node, at least in part based on the satisfaction of a triggering condition, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node; and perform communication using the one or more updated cell identifiers.

[0024] In some aspects, an apparatus for wireless communication may include: components for determining, at least in part, based on at least one of the following: a change in a donor distributed unit associated with an IAB node, a change in a central entity associated with an IAB node, or the establishment, release, or modification of a route including an IAB node; and components for providing updated transport network layer information to the IAB node, at least in part based on the satisfaction of the triggering conditions.

[0025] In some aspects, an apparatus for wireless communication may include: means for determining that triggering conditions are met for updating the identifier of an IAB node in an Integrated Access and Backhaul (IAB) network; and means for providing the updated identifier to the IAB node, at least in part, based on the determination that the triggering conditions are met.

[0026] In some aspects, an apparatus for wireless communication may include: means for determining that triggering conditions are met for updating one or more cell identifiers of an IAB node in an Integrated Access and Backhaul (IAB) network, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node; and means for providing one or more updated cell identifiers to the IAB node, at least in part based on the determination that the triggering conditions are met.

[0027] In some aspects, an apparatus for wireless communication may include: means for receiving updated transport network layer information based at least in part on satisfying triggering conditions for updating transport network layer information, wherein the triggering conditions are based at least in part on at least one of: a change in a donor distributed unit associated with an IAB node in an Integrated Access and Backhaul (IAB) network, a change in a central entity associated with an IAB node, or the establishment, release, or modification of a route including an IAB node; and means for performing communication using the updated transport network layer information.

[0028] In some aspects, an apparatus for wireless communication may include: a component for receiving an updated identifier of an IAB node in an IAB network based at least in part on a triggering condition for updating the identifier of an IAB node in an Integrated Access and Backhaul (IAB) network; and a component for performing communication using the updated identifier.

[0029] In some aspects, an apparatus for wireless communication may include: means for receiving one or more updated cell identifiers of an IAB node in an Integrated Access and Backhaul (IAB) network, at least in part based on the satisfaction of a triggering condition, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node; and means for performing communication using the one or more updated cell identifiers.

[0030] In general, the aspects include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems as fully described herein with reference to the accompanying drawings and as illustrated by the drawings.

[0031] The features and technical advantages of the examples according to this disclosure have been outlined rather broadly above to facilitate a better understanding of the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, their organization and operation, and related advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not as a limitation of the claims. Attached Figure Description

[0032] To gain a more detailed understanding of the features described above, reference can be made to various aspects for a more specific description, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of the disclosure and should therefore not be considered as limiting its scope, as the description may allow for other equivalent aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0033] Figure 1 This is a block diagram that conceptually illustrates an example of a wireless communication network according to various aspects of this disclosure.

[0034] Figure 2 This is a block diagram conceptually illustrating an example of a base station communicating with a UE in a wireless communication network according to various aspects of this disclosure.

[0035] Figure 3 This is a diagram illustrating an example of a radio access network according to various aspects of this disclosure.

[0036] Figure 4 This is a diagram illustrating an example of an integrated access and backhaul (IAB) network architecture according to various aspects of this disclosure.

[0037] Figure 5 This is a diagram illustrating another example of an IAB network architecture according to various aspects of this disclosure.

[0038] Figure 6 This is a diagram illustrating an example of triggering conditions for updating one or more identifiers of an IAB network according to various aspects of this disclosure.

[0039] Figures 7 to 10 This is a diagram illustrating an example of updating one or more identifiers of an IAB network according to various aspects of this disclosure.

[0040] Figures 11 to 13 This is a diagram illustrating an example process performed, for example, by a central entity of an IAB network, according to various aspects of this disclosure.

[0041] Figures 14 to 16 This is a diagram illustrating an example process performed, for example, by an IAB node in an IAB network, according to various aspects of this disclosure. Detailed Implementation

[0042] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of the disclosure herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, an apparatus or a method may be implemented using any number of the aspects set forth herein. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods implemented using structures, functions, or structures and functions other than or different from the aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0043] Several aspects of a telecommunications system will now be described with reference to various devices and techniques. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether such an element is implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system.

[0044] It should be noted that although this document may use terms commonly associated with 3G and / or 4G wireless technologies to describe aspects, the aspects of this disclosure may be applied to communication systems based on other generations, such as 5G and later, including NR technology.

[0045] Figure 1 This diagram illustrates a wireless network 100 in which various aspects of this disclosure may be implemented. The wireless network 100 may be an LTE network or some other wireless network such as a 5G or NR network. The wireless network 100 may include several BS110s (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR BS, Node B, gNB, 5G Node B (NB), access point, Transmit / Receive Point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0046] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and allow unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and allow restricted access by UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS used for macrocells can be referred to as a macro BS. A BS used for picocells can be referred to as a pico BS. A BS used for femtocells can be referred to as a femtocell BS or a home BS. Figure 1 In the examples shown, BS 110a can be a macro BS for macro cell 102a, BS 110b can be a pico BS for pico cell 102b, and BS 110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” are used interchangeably herein.

[0047] In some respects, the cell is not necessarily stationary; the geographical area of ​​the cell can move depending on the location of the mobile BS. In some respects, BSs can interconnect and / or connect to one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections, virtual networks, and / or similar devices using any suitable transport network).

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

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

[0050] Network controller 130 can be coupled to a group of base stations (BSs) and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via a backhaul link. These BSs can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0051] UEs 120 (e.g., 120a, 120b, 120c) may be distributed across the wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or apparatus, a biometric sensor / device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), an entertainment device (e.g., a music or video device, or a satellite radio unit, etc.), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0052] Some UEs can 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, instruments, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links, for example. Some UEs can be considered as Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered as Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120, such as processor components, memory components, etc.

[0053] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0054] In some respects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary for communication with another UE). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, mesh networks, etc.). In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0055] As mentioned above, Figure 1 Provided as an example. Other examples may differ from the combination. Figure 1 The content described.

[0056] Figure 2 A block diagram of a design 200 for base station 110 and UE 120 is shown. Base station 110 and UE 120 can be Figure 1 One of the base stations and one of the UEs. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, where typically T≥1 and R≥1.

[0057] At base station 110, transmitting processor 220 can receive data for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (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. Transmitting processor 220 can also process system information (e.g., semi-static resource allocation information (SRPI), etc.) and control information (e.g., CQI requests, authorizations, upper-layer signaling, etc.) and provide overhead symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding, if applicable) on data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can (e.g., for OFDM, etc.) process its corresponding output symbol stream to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t, respectively. Position coding can be used to generate synchronization signals to convey additional information, according to various aspects described in more detail below.

[0058] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols if applicable, and provide the detected symbols. Receiver processor 258 can process (e.g., demodulate and decode) these detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The channel processor can determine the Received Reference Signal Power (RSRP), Received Signal Strength Indicator (RSSI), Received Reference Signal Quality (RSRQ), Channel Quality Indicator (CQI), etc. In some respects, one or more components of the UE 120 may be included in the housing.

[0059] On the uplink, at UE 120, the transmitting processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., control information for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmitting processor 264 can also generate reference symbols for one or more reference signals. Symbols from the transmitting processor 264 can be pre-encoded by the TX MIMO processor 266, where applicable, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM, and / or CP-OFDM, etc.), and transmitted to base station 110. At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if applicable), and further processed by receiving processor 238 to obtain decoded data and control information transmitted by UE 120. The receiving processor 238 can provide decoded data to the data sink 239 and 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 network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0060] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2Any other component in the network may perform one or more techniques associated with updating one or more identifiers in the IAB network, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component in it can execute or direct, for example Figure 11 Process 1100 Figure 12 Process 1200 Figure 13 Process 1300 Figure 14 Process 1400 Figure 15 Process 1500 Figure 16 The operation of process 1600 and / or other processes as described herein. Memory 242 and 282 may store data and program code 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 for wireless communication. For example, when executed by one or more processors of base station 110 and / or UE 120, these one or more instructions may execute or direct, for example... Figure 11 Process 1100 Figure 12 Process 1200 Figure 13 Process 1300 Figure 14 Process 1400 Figure 15 Process 1500 Figure 16 The operation of process 1600 and / or other processes as described herein. Scheduler 246 can schedule the UE for data transmission on the downlink and / or uplink.

[0061] In some aspects, BS 110 (e.g., a central entity associated with BS 110) may include: components for determining, at least in part, that a triggering condition for updating transport network layer information of an IAB node in the IAB network is satisfied based on at least one of the following: a change in a donor distributed unit associated with the IAB node, a change in a central entity associated with the IAB node, or the establishment, release, or modification of a route including the IAB node; components for providing updated transport network layer information to the IAB node, at least in part, based on the satisfaction of the triggering condition; components for providing a second central entity with the context of the IAB node's mobile terminal and an indication of the IAB node's association with a distributed unit; components for determining, at least in part, whether to update the transport network layer information based on the triggering condition; components for determining that a triggering condition for updating the identifier of an IAB node in the IAB network is satisfied; and components for providing updated transport network layer information to the IAB node, at least in part, based on the determination that the triggering condition is satisfied. Components for providing updated identifiers to IAB nodes; components for providing the context of the mobile terminal of the IAB node and an indication of the IAB node's association with a distributed unit to a second central entity; components for determining whether to update the identifier of the IAB node based at least in part on trigger conditions; components for determining that trigger conditions for updating one or more cell identifiers of the IAB node in the IAB network are met, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node; components for providing one or more updated cell identifiers to the IAB node based at least in part on the determination that the trigger conditions are met; components for providing the context of the mobile terminal of the IAB node and an indication of the IAB node's association with a distributed unit to a second central entity; and components for determining whether to update one or more cell identifiers based at least in part on trigger conditions, etc. In some aspects, these components may include combinations of... Figure 2 One or more components of the described base station 110, 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, etc.

[0062] In some aspects, base station 110 (e.g., an IAB node associated with BS 110) may include: means for receiving updated transport network layer information at least in part based on satisfying trigger conditions for updating transport network layer information; means for performing communication using the updated transport network layer information; means for receiving a request for a network address; means for providing a network address, wherein the updated transport network layer information is at least in part based on the network address; means for providing an indication to a central entity regarding the establishment, release, or modification of a route, wherein the trigger conditions are at least in part based on the indication; and means for receiving an updated identifier of an IAB node at least in part based on satisfying trigger conditions for updating the identifier of an IAB node in the IAB network. The components include: components for performing communication using updated identifiers; components for providing a central entity with an indication regarding the establishment, release, or modification of routes including IAB nodes, wherein the triggering condition is at least partially based on the indication; components for receiving one or more updated cell identifiers of an IAB node, at least partially based on the satisfaction of a triggering condition, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node; components for performing communication using one or more updated cell identifiers; and components for providing a central entity with an indication regarding the establishment, release, or modification of routes including IAB nodes, wherein the triggering condition is at least partially based on the indication. In some aspects, these components may include combinations of... Figure 2 One or more components of the described base station 110, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TXMIMO processor 230, MOD 232, antenna 234, etc.

[0063] As mentioned above, Figure 2 Provided as an example. Other examples can be combined. Figure 2 The descriptions are different.

[0064] Figure 3 This is a diagram illustrating example 300 of a radio access network according to various aspects of this disclosure.

[0065] As shown by reference numeral 305 in the attached figure, a conventional (e.g., 3G, 4G, LTE, etc.) radio access network may include multiple base stations 310 (e.g., access nodes (ANs)), each base station 310 communicating with the core network via a wired backhaul link 315 (such as a fiber optic connection). Base stations 310 may communicate with a UE 320 via an access link 325, which may be a radio link. In some aspects, Figure 3 The base station 310 shown can correspond to Figure 1 The base station 110 is shown. Similarly, Figure 3 The UE320 shown can correspond to Figure 1 The UE 120 shown.

[0066] As indicated by reference numeral 330 in the attached figure, the radio access network may include a radio 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 the core network via a wired backhaul link 340 (such as a fiber optic 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, IAB nodes (or IAB-nodes). Non-anchor base stations 345 may communicate directly or indirectly (e.g., via one or more non-anchor base stations 345) with the anchor base station 335 via one or more backhaul links 350 to form a backhaul path to the core network for carrying backhaul services. The backhaul link 350 may be a radio 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 radio link for carrying access services. In some aspects, Figure 3 The anchor base station 335 and / or non-anchor base station 345 shown can correspond to Figure 1 The base station 110 is shown. Similarly, Figure 3 The UE 355 shown can correspond to Figure 1 The UE 120 shown.

[0067] As indicated by reference numeral 365 in the attached figure, in some aspects, radio access networks, including IAB networks, can use millimeter-wave technology and / or directional communication (e.g., beamforming, precoding, etc.) 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 radio backhaul link 370 between base stations can use millimeter waves to carry information and / or can use beamforming, precoding, etc., to be directed to a target base station. Similarly, a radio access link 375 between a UE and a base station can use millimeter waves and / or can be directed to a target radio node (e.g., between a UE and / or a base station). This reduces inter-link interference.

[0068] Figure 3 The configuration of the base station and UE in the example is shown, and other examples are possible. For example, Figure 3 The one or more base stations shown can be replaced by one or more UEs communicating via a UE-to-UE access network (e.g., peer-to-peer network, device-to-device network, etc.). In this case, the anchor node can refer to a UE that communicates directly with a base station (e.g., an anchor base station or a non-anchor base station).

[0069] As mentioned above, Figure 3Provided as an example. Other examples can be combined. Figure 3 The descriptions are different.

[0070] Figure 4 This is a diagram illustrating an example 400 of an integrated access and backhaul (IAB) network architecture according to various aspects of this disclosure.

[0071] like Figure 4 As shown, the IAB network may include anchor node 405 or an IAB donor (shown as IAB-donor) connected to the core network via a wired connection (shown as wired). For example, the Ng interface of anchor node 405 may terminate at the core network. Additionally or alternatively, anchor node 405 may be connected to one or more devices of the core network that provide core access and mobility management functions (e.g., Access Management Function (AMF)). In some aspects, anchor node 405 may include base station 110, such as an anchor base station, as described above. Figure 3 Described.

[0072] like Figure 4 As further illustrated, the IAB network may include a non-anchor node 410 or an IAB node (shown as an IAB-node). The non-anchor node 410 may provide integrated access and backhaul functionality and may include a Mobile Terminal (MT) function 415 (sometimes referred to as a UE function (UEF)) and a Distributed Unit (DU) function 420 (sometimes referred to as an Access Node (ANF)). The MT function 415 may be controlled and / or scheduled by another non-anchor node 410 and / or an anchor node 405. The DU function 420 may control and / or schedule other non-anchor nodes 410 and / or UE 625 (e.g., it may correspond to UE 120). In some aspects, the anchor node 405 may include only the DU function 420 and not the MT function 415. That is, the anchor node 405 may control and schedule communication with the non-anchor node 410 and / or UE 425. Additionally or alternatively, the UE 425 may include only the MT function 415 and not the DU function 420. That is, the communication of UE 425 can be controlled and / or scheduled by anchor node 405 and / or non-anchor node 410.

[0073] When the first node controls and / or schedules communication for the second node (e.g., when the first node provides DU functionality for the second node's MT function), the first node can be referred to as the parent node of the second node, and the second node can be referred to as the child node of the first node. Therefore, the parent node's DU functionality 420 can control and / or schedule communication for the parent node's child node. The parent node can be an anchor node 405 or a non-anchor node 410, and the child node can be a non-anchor node 410 or a UE 425. Communication of the child node's MT functionality 415 can be controlled and / or scheduled by the child node's parent node.

[0074] like Figure 4 As further illustrated, the link between UE 425 (e.g., having only MT function 415 and not DU function 420) and anchor node 405, or between UE 425 and non-anchor node 410, can be referred to as access link 430. Access link 430 can be a radio access link that provides radio access to the core network to UE 425 via anchor node 405 and optionally via one or more non-anchor nodes 410.

[0075] like Figure 4 As further illustrated, the link between anchor node 405 and non-anchor node 410, or between two non-anchor nodes 410, can be referred to as backhaul link 435. Backhaul link 435 can be a wireless backhaul link that provides radio access to the core network to non-anchor nodes 410 via anchor node 405 and optionally via one or more other non-anchor nodes 410. In some aspects, backhaul link 435 can be a primary backhaul link (shown as backhaul link 435) or a secondary backhaul link 440 (e.g., a backup backhaul link). In some aspects, secondary backhaul link 440 can be used if the primary backhaul link fails, becomes congested, becomes overloaded, etc.

[0076] As mentioned above, Figure 4 Provided as an example. Other examples can be combined. Figure 4 The descriptions are different.

[0077] Figure 5 This is a diagram illustrating an example 500 of an IAB network architecture according to various aspects of this disclosure.

[0078] like Figure 5 As shown, the IAB network may include an IAB donor 505 (shown as an IAB-donor) connected to the core network via a wired connection (shown as a wired backhaul). For example, the Ng interface of the IAB donor 505 may terminate at the core network. Additionally or alternatively, the IAB donor 505 may connect to one or more devices in the core network that provide core access and mobility management functions (e.g., AMF). In some aspects, the IAB donor 505 may include a base station 110, such as an anchor base station, as described above. Figure 3As described, the IAB donor 505 may include a central unit (CU) that can perform Access Node Controller (ANC) functions, AMF functions, etc. The CU can configure the distributed units (DUs) of the IAB donor 505 and / or can configure one or more IAB nodes 510 (e.g., the MTs and / or DUs of IAB nodes 510) connected to the core network via the IAB donor 505. Therefore, the CU of the IAB donor 505 can control and / or configure the entire IAB network connected to the core network via the IAB donor 505, for example, by using control messages and / or configuration messages (e.g., Radio Resource Control (RRC) configuration messages, etc.).

[0079] like Figure 5 As further illustrated, the IAB network may include IAB nodes 510 (shown as IAB-Node 1 and IAB-Node 2) connected to the core network via IAB donor 505. As shown, IAB node 510 may include Mobile Terminal (MT) functions (sometimes referred to as UE functions (UEF)) and may include DU functions (sometimes referred to as Access Node Functions (ANF)). The MT function of IAB node 510 (e.g., a child node) may be controlled and / or scheduled by another IAB node 510 (e.g., the parent node of the child node) and / or by IAB donor 505. The DU function of IAB node 510 (e.g., the parent node) may control and / or schedule other IAB nodes 510 (e.g., the child node of the parent node) and / or UE 120. Therefore, DU may be referred to as a scheduling node or scheduling component, while MT may be referred to as a scheduled node or scheduled component. In some aspects, IAB donor 505 may include DU functions but not MT functions. In other words, the IAB donor 505 can configure, control, and / or schedule the communication of the IAB node 510 and / or the UE 120. In some aspects, the UE 120 may include only the MT function and not the DU function. That is, the communication of the UE 120 can be controlled and / or scheduled by the IAB donor 505 and / or the IAB node 510 (e.g., the parent node of the UE 120).

[0080] When the first node controls and / or schedules communication for the second node (e.g., when the first node provides DU functionality for the second node's MT function), the first node can be referred to as the parent node of the second node, and the second node can be referred to as the child node of the first node. The child node of the second node can be referred to as the grandchild node of the first node. Therefore, the parent node's DU functionality can control and / or schedule communication for the parent node's child nodes. The parent node can be IAB donor 505 or IAB node 510, while the child node can be IAB node 510 or UE 120. Communication for the child node's MT function can be controlled and / or scheduled by the child node's parent node.

[0081] Figure 5 Access link 515 is also shown between UE 120 (e.g., having only MT functionality and not DU functionality) and IAB donor 505 or between UE 120 and IAB node 510. Access link 515 may be a radio access link that provides radio access to the core network to UE 120 via IAB donor 505 and optionally via one or more IAB nodes 510. Figure 5 The network shown can be called a multi-hop network because some UEs 120 achieve radio access to the core network via two or more devices (e.g., IAB donor 505 and one or more IAB nodes 510).

[0082] like Figure 5 As further illustrated, the link between IAB donor 505 and IAB node 510, or between two IAB nodes 510, can be referred to as a backhaul link 520. The backhaul link 520 can be a wireless backhaul link that provides radio access to the core network to IAB node 510 via IAB donor 505 and optionally via one or more IAB nodes 510. In some aspects, the backhaul link 520 can be a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link). In some aspects, a secondary backhaul link can be used if the primary backhaul link fails, becomes congested, becomes overloaded, etc. As used herein, a node or wireless node can refer to IAB donor 505 or IAB node 510.

[0083] A control interface connection, such as an F1 connection (F1-C), can be established between the IAB donor CU and each of the IAB donor DUs and IAB node DUs associated with the IAB donor CU. An F1 application protocol (AP) or flow control transport protocol (SCTP) connection can be used to exchange control plane (CP) messages between the IAB donor CU, IAB node DU, and / or IAB donor DU. Each IAB donor DU and IAB node DU within the base station can be configured with a gNB-DU identifier. The gNB-DU identifier can be used during the F1-AP procedure. The IAB donor DU and IAB node DU can provide the gNB-DU identifier to the IAB donor CU during the F1 establishment procedure. The gNB-DU identifier can uniquely identify the IAB donor DU or IAB node DU at the IAB donor CU. Furthermore, the CU can include a CU-control plane (CU-CP) and a CU-user plane (CU-UP) capable of handling control plane functions and user plane functions, respectively.

[0084] As mentioned above, Figure 5 Provided as an example. Other examples can be combined. Figure 5 The descriptions are different.

[0085] In some cases, the topology of an IAB network can change. As one example, the routing of an IAB node can switch from one parent node to another. As another example, the routing of an IAB node can switch from a first parent node associated with a first IAB donor and CU to a second parent node associated with a second IAB donor and CU. In these cases, the various identifiers associated with the IAB node may become outdated. For example, transport layer identifiers (e.g., Internet Protocol (IP) addresses), IAB node identifiers, cell identifiers, etc., may become outdated when the topology associated with the IAB node changes.

[0086] Updating one or more identifiers associated with an IAB node can be advantageous. However, certain techniques used to update or assign these identifiers (e.g., pre-configuration or configuration during IAB node integration) can lead to latency and service interruptions. This is particularly problematic in IAB networks where the topology can change frequently (e.g., due to changes in channel conditions, changes in IAB node identifiers, changes in IAB node locations, etc.).

[0087] Some of the techniques and apparatuses described herein provide dynamic configuration of updated identifiers (e.g., transport network layer information, IAB node DU identifiers, and / or cell identifiers) for IAB nodes, at least in part, based on various changes in the IAB network. For example, this dynamic configuration can be performed at least in part based on triggering conditions, such as redirecting existing interface associations or tunnels to new routes, establishing new interface associations or tunnels, integrating IAB nodes, radio link failures, handovers, topology adaptations, etc. Furthermore, some of the techniques and apparatuses described herein provide implementations of updated identifiers performed by IAB nodes (e.g., IAB node DUs). This reduces latency and service interruptions associated with identifier updates due to topology changes in the IAB network, thereby increasing throughput and saving computational resources.

[0088] Figure 6Figures 605 and 610 illustrate examples of triggering conditions for updating one or more identifiers of an IAB network according to various aspects of this disclosure. Example 605 is an example of an intra-CU change of an IAB donor DU. In example 605, as shown by reference numeral 615, the parent node of IAB node 5 can change from IAB node 3 to IAB node 4. The connection to IAB node 4 is indicated by reference numeral 620. As further shown, IAB nodes 3 and 4 are associated with different IAB donor DUs and the same CU (shown as the same CU-control plane (CP) and the same CU-user plane (UP)). In this case, the CU can update the Transport Network Layer (TNL) information to redirect the F1-U tunnel and F1-AP interface to a new route corresponding to IAB donor DU 2. Therefore, an intra-CU change of an IAB donor DU can be a triggering condition for the techniques described herein.

[0089] Example 610 is an example of an intra-CU change for an IAB donor DU. In Example 610, as shown by reference numeral 625, the parent node of IAB node 3 can change from IAB node 1 to IAB node 2. As further shown, IAB nodes 1 and 2 are associated with different IAB donor CUs. In this case, the transport network layer addresses of the DUs of IAB node 3 and IAB node 5 can be updated to establish F1-AP associations and F1-U tunnels for updated routes through IAB node 2. Furthermore, the gNB-DU IDs of the DUs of IAB node 3 and IAB node 5 may need to be unique at IAB donor CU 2, and therefore may or may not be updated. Further still, the NR Cell Global Identifier (NCGI) of the cell served by the DUs of IAB node 3 and IAB node 5 can be configured with a cell identifier corresponding to IAB donor CU 2. Therefore, an intra-CU change for an IAB donor DU can be a triggering condition for the techniques described herein.

[0090] Figures 7 to 10 The figures are examples 700, 800, 900, and 1000 illustrating one or more identifiers of an updated IAB network according to various aspects of this disclosure.

[0091] Figure 7 Example 700 shown is an example of updating Transport Network Layer (TNL) information based at least in part on determining that triggering conditions are met. As shown, Example 700 includes a central entity (e.g., CU, etc.), IAB nodes, and child nodes. IAB nodes and child nodes include corresponding MTs (represented by smaller circles) and DUs (represented by larger circles). In some aspects, IAB nodes may be associated with a parent node, such as another IAB node upstream of an IAB node between an IAB donor and an IAB node.

[0092] In some aspects, the triggering condition may involve a change in the donor DU associated with the IAB node (e.g., in Example 605, such as due to a radio link failure on the link to the donor DU). In other aspects, the triggering condition may involve a change in the donor CU associated with the IAB node, as in Example 610.

[0093] In some respects, triggering conditions may involve the establishment, release, or modification of routes involving IAB nodes. As a first example, triggering conditions may involve the integration of IAB nodes. As a second example, triggering conditions may involve radio link failures (RLFs) on the following links: links to the parent DU (e.g., IAB node DU or IAB donor DU) of an IAB node or an upstream IAB node, links to the primary cell group of an IAB node or an upstream IAB node, or links to the secondary cell group of an IAB node or an upstream IAB node. As a third example, triggering conditions may involve handover to an IAB node or a node upstream of that IAB node, addition of a secondary node (e.g., a secondary node associated with a dual-connectivity configuration or non-standalone (NSA) mode), handover between primary nodes (e.g., with or without a secondary node change), secondary node change, primary / secondary node role switching (e.g., a primary node associated with a dual-connectivity configuration or NSA mode), modification of a primary or secondary node (e.g., a mobile bearer used for load balancing), etc. As a fourth example, the triggering condition can involve topology adaptation, which in turn involves the addition, release, or modification of IP routes or Backhaul Adaptation Protocol (BAP) routes. The addition of new routes can be for topology redundancy, for signaling transmission, for data transmission, or a combination thereof.

[0094] As shown by reference numeral 710 in the attached figure, an IAB node can provide instructions to a central entity. These instructions can be provided by the MT (Mean Transmission Unit) or DU (Distribution Unit) of the IAB node. Various examples of these instructions are provided below.

[0095] In some respects, the indication can involve the RRC connection establishment process. For example, when an IAB node is integrated into an IAB network, the MT of the IAB node can initiate an RRC connection establishment process, during which the IAB node indicates to the central entity that the IAB node has a co-located DU.

[0096] In some respects, the indication may involve RLF. For example, after an RLF occurs on a parent link, the MT of an IAB node may initiate an RRC connection re-establishment procedure, during which the MT indicates to the central entity that the MT has a co-located DU. The MT of an IAB node may also indicate that the IAB node DU was previously activated. In some respects, the MT of an IAB node may provide a list of previously served and / or active cells at the co-located DU. In some respects, the MT of an IAB node may provide context for the serving child nodes (e.g., UEs and / or child IAB nodes) of the previously activated IAB node DU. In this case, in some respects, the central entity that initiated the RRC connection re-establishment procedure may request context about the IAB node (e.g., the MT and / or DU) and the serving subtree below the IAB node from the previous central entity of the IAB node or the IAB node's Access Management Function (AMF) (if such an entity can be identified).

[0097] In some respects, after initiating the establishment of an F1-C association with the IAB donor central entity, the IAB node DU can indicate to the central entity that the IAB node DU was previously activated. In this case, the IAB node DU can provide a list of services and active cells associated with the IAB node DU.

[0098] As shown by reference numeral 720, the central entity can determine whether a triggering condition is met. For example, the central entity can determine whether to update TNL information. In Example 700, the central entity determines the meeting of the triggering condition (e.g., to update TNL information) based at least in part on an indication received from the IAB node. In some aspects, the central entity can determine the meeting of the triggering condition independently of an indication or even without receiving an indication. As further shown, the central entity can update the TNL information of the IAB node. For example, as shown by reference numeral 730, the central entity can provide the updated TNL information of the IAB node to the IAB node and / or one or more other nodes associated with the IAB node. For example, the central entity can provide the updated TNL information in an RRC message, an F1-AP message, etc.

[0099] TNL information can identify IP addresses (e.g., IPv4 or IPv6 addresses), multiple IP addresses, or aggregations of IP addresses (e.g., IP prefixes). In some respects, TNL information can be the same for signaling services (e.g., F1-C services) and data transmission (e.g., F1-U services). In some respects, TNL information for signaling services can differ from TNL information for data transmission. For example, TNL information associated with the F1 Control Plane (F1-C) interface, F1 Application Protocol (F1-AP), and SCTP can differ from TNL information for the F1 User Plane (F1-U) and General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Plane (GTP-U) tunnels. In some respects, TNL information can be the same for non-UE-related services (e.g., non-F1 services) and UE-related services. In some respects, TNL information for non-UE-related services can differ from TNL information for UE-related services.

[0100] In some respects, updated TNL information can be based at least in part on the association with the IAB donor DU on a newly established or redirected route between the IAB node's DU and the central entity (e.g., CU-CP or CU-UP). As an example, the IAB donor DU can be associated with an IP prefix. The IP address of the IAB node DU can be derived from that IP prefix. The central entity can request one or more IP addresses from the IAB donor DU and can provide configuration messages to the IAB node's DU based at least in part on one or more IP addresses provided by the IAB donor DU. Similarly, if an F1-AP association or F1-U tunnel is to be rejected or redirected from the IAB donor DU, the central entity can send a configuration message to the IAB node instructing the release of one or more IP addresses. The central entity can instruct the IAB donor DU to release IP addresses.

[0101] As shown by reference numeral 740 in the attached figure, an IAB node can use updated TNL information to perform communication (e.g., via the IP layer). For example, an IAB node can indicate updated TNL information in sent packets after the corresponding TNL association becomes operational. Here, communication with the IAB donor DU is performed, but communication with any IAB node, UE, or IAB donor can also be performed.

[0102] Figure 8 Example 800 shown is an example of a central entity updating the identifier of a DU (e.g., gNB-DU ID) based at least in part on determining that triggering conditions are met. In some aspects, triggering conditions may include a combination of the above. Figure 7One or more of the described triggering conditions. Additionally or alternatively, the triggering conditions may involve establishing an F1-C association to another IAB donor CU. For example, when a central entity wants to establish an F1-C association between an IAB node and another central entity, the central entity may determine that the triggering conditions are met and may update the identifier of the IAB node, the cell identifier associated with the IAB node, etc. accordingly.

[0103] like Figure 8 As shown by reference numeral 810 in the attached figure, the IAB node can provide instructions to the central entity. Combined with... Figure 7 Reference numeral 710 describes an example of the indication in more detail. As shown by reference numeral 820, the central entity can be determined to meet the triggering condition. Combined with... Figure 7 Reference numeral 720 describes in more detail the determination of whether the triggering condition is met. As shown by reference numeral 830, the central entity can provide the IAB node with an updated identifier for the DU. For example, the central entity can use RRC messages, F1-AP messages, etc., to provide the updated identifier. As shown by reference numeral 840, the IAB node can use the updated identifier to perform communication. For example, the IAB node can perform control plane communication including the updated identifier (e.g., with another IAB node's DU, with the central entity, with another central entity, etc.).

[0104] Figure 9 Example 900 shown is an example of a central entity updating one or more cell identifiers (e.g., a portion or the entire NCGI) based at least in part on determining that triggering conditions are met. As indicated by reference numeral 910, the IAB node can provide indications associated with the triggering conditions used to update one or more cell identifiers. Combined Figure 7 and Figure 8 Examples of triggering conditions are described in more detail. As indicated by reference numeral 920 in the accompanying drawings, a central entity can determine that a triggering condition is met (e.g., at least in part based on an indication or independently of an indication), such as in combination with... Figure 7 and Figure 8 A more detailed description follows. Therefore, the central entity can determine one or more updated cell identifiers and can provide these updated cell identifiers to the IAB nodes, as shown by reference numeral 930 in the attached figure.

[0105] Cell identifiers can include information that identifies the cell. For example, a cell identifier can include an NR Cell Global Identifier (NCGI). An NCGI can include a Public Land Mobile Network (PLMN) identifier and an NR Cell Identifier (NCI). An NCI can include a gNB identifier and a local cell identifier. A gNB identifier can be unique within a gNB (e.g., BS 110) and can be common to all cells served by the gNB. Therefore, a gNB identifier can be common to all IAB donor DUs and IAB node DUs served by the gNB's IAB donor CU-CP.

[0106] In some respects, one or more cell identifiers may indicate an association with an IAB donor CU or base station. For example, if a gNB identifier or an NCI including a gNB identifier is included in one or more cell identifiers, then the one or more cell identifiers may indicate an association with an IAB donor CU or base station. If the one or more cell identifiers do not include a gNB identifier or do not include an NCI including a gNB identifier (e.g., if the one or more cell identifiers do not share an identifier with cells on other DUs associated with the same central entity or base station), then the one or more cell identifiers may not indicate an association with an IAB donor CU or base station.

[0107] As shown by reference numeral 940 in the attached figure, an IAB node can perform broadcasting using one or more updated cell identifiers. For example, a base station associated with an IAB node can send a System Information Block (SIB) identifying at least a portion of one or more updated cell identifiers, such as SIB1. In some aspects, the IAB node's DU can include one or more updated cell identifiers in an F1-AP message sent to a central entity. In some aspects, if the IAB node receives an updated NCI, gNB identifier, or local cell identifier for a cell, the IAB node's DU can update the cell's NCGI and include the updated NCGI in the System Information Block or F1-AP message.

[0108] Figure 10Example 1000 illustrates an example where a source central entity provides one or more identifiers to a target central entity as part of a switchover of one or more IAB nodes from the source central entity to the target central entity. For example, in Example 1000, as shown by reference numeral 1010, in some aspects, one or more IAB nodes (shown as IAB nodes and child nodes) can be switched from the source central entity to the target central entity. These operations can also be performed when the target central entity is associated with a secondary node (SN) added for one or more IAB nodes. In these cases, as shown by reference numeral 1020, information associated with one or more IAB nodes can be transferred from the source central entity to the target central entity. For example, after a switchover of an IAB node MT or the addition of an SN, the source central entity can transfer the context of the IAB node MT and can indicate to the target central entity that the MT has a co-located DU (e.g., using TNL information and / or the DU identifier of the co-located DU). In some aspects, the source central entity can indicate that the IAB node DU was previously activated. In some aspects, the source central entity may provide a list of previously served and / or active cells at the IAB node DU (e.g., using the corresponding cell identifiers of the previously served and / or active cells). In some aspects, the source central entity may provide a list of one or more serving IAB nodes and / or UEs (e.g., in a subtree below the IAB node) within the IAB node. Figure 10 The child nodes shown Figure 10 The target central entity may provide context for one or more IAB nodes and / or UEs (not shown in the diagram). In some aspects, the target central entity may request context about IAB nodes (e.g., the MT of an IAB node, the DU of an IAB node, etc.) and / or one or more IAB nodes and / or UEs in a subtree. For example, the target central entity may request context from the source central entity, AMF, etc.

[0109] Figure 11 This is a diagram illustrating an example process 1100 performed, for example, by a central entity, according to various aspects of this disclosure. Example process 1100 is a central entity (e.g., the CU of anchor node 405, the CU of IAB donor 505, CU-CP, CU-UP, etc.). Figures 7 to 10 Examples of operations performed by central entities (such as central entities) that are associated with the management of identifiers in the IAB network.

[0110] like Figure 11As shown, in some aspects, process 1100 may include determining triggering conditions that satisfy the requirements for updating transport network layer information of IAB nodes in the IAB network (block 1110). For example, a central entity (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receiver processor 238, controller / processor 240, etc.) may determine that triggering conditions satisfy the requirements for updating transport network layer information of IAB nodes in the IAB network. The central entity may perform this determination based at least in part on at least one of the following: a change in the donor distributed unit associated with the IAB node, a change in the central entity associated with the IAB node, or the establishment, release, or modification of a route including the IAB node, as described above.

[0111] like Figure 11 As further shown, in some aspects, process 1100 may include providing updated transport network layer information to the IAB node, at least in part based on the satisfaction of triggering conditions (box 1120). For example, a central entity (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.) may provide updated transport network layer information to the IAB node, at least in part based on the satisfaction of triggering conditions, as described above.

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

[0113] In the first aspect, the updated transport network layer information includes at least one of one or more Internet Protocol (IP) addresses or IP prefixes.

[0114] In the second aspect, either alone or in combination with the first aspect, the updated transport network layer information differs for signaling services and for data transmission.

[0115] In the third aspect, whether alone or in combination with one or more of the first and second aspects, the updated transport network layer information is the same for signaling services and data transmission.

[0116] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the updated transport network layer information differs for non-user equipment (UE) related services from that for UE related services.

[0117] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the updated transport network layer information is different for non-user equipment (UE) related services and UE related services.

[0118] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the change of the donor distributed unit associated with the IAB node is associated with redirecting the existing control interface association or tunnel from the route associated with the first donor distributed unit to the route associated with the second donor distributed unit.

[0119] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the first donor distributed unit and the second donor distributed unit are associated with the same central entity.

[0120] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the first donor distributed unit and the second donor distributed unit are associated with different control entities.

[0121] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the updated transport network layer information is associated with the donor distributed unit.

[0122] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the establishment, release or modification of routes for IAB nodes is based at least in part on the integration of another IAB node, other than the IAB node, into the route.

[0123] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the establishment, release or modification of routes for IAB nodes is based at least in part on integrating IAB nodes into routes.

[0124] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the establishment, release or modification of routes of an IAB node is based at least in part on a radio link failure on a link associated with one of the following: the distributed cell of the parent node of the IAB node or an upstream node, the primary cell group of the IAB node or an upstream IAB node, or the secondary cell group of the IAB node or an upstream IAB node.

[0125] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the establishment, release or modification of routes for IAB nodes is based at least in part on at least one of the following: switching of upstream nodes of the IAB node, addition of secondary nodes, switching between primary nodes, change of secondary nodes, role switching or modification of primary or secondary nodes.

[0126] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the establishment, release or modification of routes for IAB nodes is based at least in part on topology adaptation of routes.

[0127] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, it is determined that the triggering condition is satisfied based at least in part on receiving an instruction from a mobile terminal of an IAB node or a different IAB node associated with the central entity.

[0128] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, it is determined that the satisfaction of the triggering condition is based at least in part on receiving an instruction from a distributed unit of an IAB node or a different IAB node associated with a central entity.

[0129] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the central entity is a first central entity, and the method further includes providing the second central entity with the context of the mobile terminal of the IAB node and an indication of the association between the IAB node and the distributed unit when the establishment, release or modification of the route including the IAB node is at least partially based on the handover to the second central entity or the addition of a secondary node.

[0130] In the eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, the context of the mobile terminal of the IAB node and the indication of the IAB node being associated with the distributed unit are provided at least in part based on receiving a request from the second central entity for the context and the indication of the IAB node being associated with the distributed unit.

[0131] In the nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, the central entity is a first central entity, which includes the establishment, release or modification of routes for IAB nodes based at least in part on a handover to a second central entity or the addition of a secondary node, and wherein the second central entity receives from the core network the context of the mobile terminal of the IAB node and instructions associated with the IAB node and the distributed unit.

[0132] In the twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, process 1100 includes determining, at least in part, whether to update transport network layer information based on triggering conditions.

[0133] In aspect 21, either alone or in combination with one or more of aspects 1 to 20, updated transport network layer information is provided using radio resource control messages or control interface messages.

[0134] In the twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, the method includes sending a request for a network address; and receiving a network address, wherein updated transport network layer information is based at least in part on the network address.

[0135] In the twenty-third aspect, alone or in combination with one or more of the first to twenty-two aspects, the method includes sending a configuration message indicating the release of one or more network addresses.

[0136] In the twenty-fourth aspect, alone or in combination with one or more of the first to twenty-third aspects, the network address includes at least one of IPv4 address, IPv6 address, or IPv6 prefix.

[0137] In the twenty-fifth aspect, either alone or in combination with one or more of the first to twenty-fourth aspects, the information indicating the network address indicates the use of the network address, and wherein updated transport network layer information is at least partially based on this use. This use may indicate whether the network address is used for signaling services, data transmission, or non-UE-related services.

[0138] In the twenty-sixth aspect, either alone or in combination with one or more of the first to twenty-fifth aspects, the information indicating the network address does not indicate the use of the network address, and wherein, based at least in part on the information indicating the network address not indicating the use, the updated transport network layer information can be used for all services (e.g., signaling services, data transmission, and non-UE-related services).

[0139] In the twenty-seventh aspect, either alone or in combination with one or more of the first to twenty-sixth aspects, the change of the donor distributed unit is associated with the radio link failure of the mobile terminal.

[0140] although Figure 11 An example box for process 1100 is shown, but in some respects, it differs from... Figure 11 Compared to the boxes depicted, process 1100 may include additional boxes, fewer boxes, different boxes, or boxes with different arrangements. Additionally or alternatively, two or more boxes in process 1100 may be executed in parallel.

[0141] Figure 12 This is a diagram illustrating an example process 1200 performed, for example, by a central entity, according to various aspects of this disclosure. Example process 1200 is the CU, CU-CP, CU-UP, etc. of a central entity (e.g., CU anchor node 405, IAB donor 505). Figures 7 to 10 Examples of operations performed by central entities (such as central entities) that are associated with the management of identifiers in the IAB network.

[0142] like Figure 12As shown, in some aspects, process 1200 may include determining triggering conditions that satisfy the identifiers of IAB nodes used to update the IAB network (box 1210). For example, a central entity (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receiver processor 238, controller / processor 240, etc.) may determine the triggering conditions that satisfy the identifiers of IAB nodes used to update the IAB network, as described above.

[0143] like Figure 12 As further shown, in some aspects, process 1200 may include providing an updated identifier to the IAB node, at least in part, based on the determination that a triggering condition is met (box 1220). For example, a central entity (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.) may provide an updated identifier to the IAB node, at least in part, based on the determination that a triggering condition is met, as described above.

[0144] Process 1200 may include additional aspects, such as any single aspect or any combination thereof described below and / or in conjunction with one or more other process descriptions elsewhere described herein.

[0145] In the first aspect, determining whether the triggering conditions are met is based at least in part on the establishment, release, or modification of routes including IAB nodes.

[0146] In the second aspect, either alone or in combination with the first aspect, the identifier of an IAB node includes a distributed unit identifier for controlling the interface process.

[0147] In the third aspect, either alone or in combination with one or more of the first and second aspects, the triggering condition is associated with establishing a control plane association between the IAB node and the target central entity.

[0148] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, it is determined that the triggering condition is satisfied based at least in part on receiving an instruction from a mobile terminal of an IAB node or a different IAB node associated with the central entity.

[0149] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, it is determined that the triggering condition is satisfied based at least in part on receiving an instruction from a distributed unit of a different IAB node associated with a central entity.

[0150] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the central entity is a first central entity, and when the triggering condition is at least in part based on a switch to a second central entity or the addition of a secondary node, the method further includes: providing the second central entity with the context of the mobile terminal of the IAB node and an indication of the association between the IAB node and the distributed unit.

[0151] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1200 includes determining, at least in part, whether to update the identifier of the IAB node based on triggering conditions.

[0152] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the updated identifier is provided using radio resource control messages or control interface messages.

[0153] although Figure 12 An example box for process 1200 is shown, but in some respects, it differs from... Figure 12 Compared to the boxes depicted, process 1200 may include additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 1200 may be executed in parallel.

[0154] Figure 13 This is a diagram illustrating an example process 1300 performed, for example, by a central entity, according to various aspects of this disclosure. Example process 1300 is the CU, CU-CP, CU-UP, etc. of a central entity (e.g., CU anchor node 405, IAB donor 505). Figures 7 to 10 Examples of operations performed by central entities (such as central entities) that are associated with the management of identifiers in the IAB network.

[0155] like Figure 13 As shown, in some aspects, process 1300 may include determining triggering conditions that satisfy one or more cell identifiers of an IAB node for updating the IAB network, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node (box 1310). For example, a central entity (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, etc.) may determine triggering conditions that satisfy one or more cell identifiers of an IAB node for updating the IAB network, as described above. In some aspects, the one or more updated cell identifiers correspond to one or more cells served by the IAB node. As used herein, a cell served by an IAB node may refer to a cell to which the IAB node provides backhaul to the IAB donor and / or core network.

[0156] like Figure 13As further shown, in some aspects, process 1300 may include providing one or more updated cell identifiers to the IAB node, at least in part based on determining that a triggering condition is met (box 1320). For example, a central entity (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.) may provide one or more updated cell identifiers to the IAB node, at least in part based on determining that a triggering condition is met, as described above.

[0157] Process 1300 may include additional aspects, such as any single aspect or any combination thereof described below and / or in conjunction with one or more other process descriptions elsewhere described herein.

[0158] In the first aspect, determining whether the triggering conditions are met is based at least in part on the establishment, release, or modification of routes including IAB nodes.

[0159] In the second aspect, either alone or in combination with the first aspect, one or more cell identifiers include at least one of a new radio cell global identifier, a public land mobile network identifier, a base station identifier, a local cell identifier, or a new radio cell identifier.

[0160] In the third aspect, either alone or in combination with one or more of the first and second aspects, the triggering condition is associated with establishing a control plane association between the IAB node and the target central entity.

[0161] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, it is determined that the triggering condition is satisfied based at least in part on receiving an instruction from a mobile terminal of an IAB node or a different IAB node associated with the central entity.

[0162] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, it is determined that the triggering condition is satisfied based at least in part on receiving an instruction from a distributed unit of a different IAB node associated with a central entity.

[0163] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the central entity is a first central entity, and when the triggering condition is at least in part based on a switch to a second central entity or the addition of a secondary node, the method further includes: providing the second central entity with the context of the mobile terminal of the IAB node and an indication of the association between the IAB node and the distributed unit.

[0164] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1300 includes determining, at least in part, whether to update one or more cell identifiers based on triggering conditions.

[0165] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, one or more updated cell identifiers are provided using radio resource control messages or control interface messages.

[0166] although Figure 13 An example box for process 1300 is shown, but in some respects, it differs from... Figure 13 Compared to the boxes depicted, process 1300 may include additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 1300 may be executed in parallel.

[0167] Figure 14 This is a diagram illustrating an example process 1400 performed, for example, by an IAB node, according to various aspects of this disclosure. Example process 1400 is performed by an IAB node (e.g., BS 110, non-anchor base station 345, non-anchor node 410, DU function 420, MT function 415, IAB node 510, etc.). Figures 7 to 10 The IAB node shown Figures 7 to 10 Examples shown include child nodes (e.g.) performing operations associated with the management of identifiers in the IAB network.

[0168] like Figure 14 As shown, in some aspects, process 1400 may include receiving updated transport network layer information (block 1410) based at least in part on satisfying triggering conditions for updating transport network layer information. For example, an IAB node (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receiver processor 238, controller / processor 240) may receive updated transport network layer information based at least in part on satisfying triggering conditions for updating transport network layer information, as described above. In some aspects, the triggering conditions are based at least in part on at least one of the following: a change in the donor distributed unit associated with the IAB node, a change in the central entity associated with the IAB node, or the establishment, release, or modification of a route including the IAB node.

[0169] like Figure 14 As further shown, in some aspects, process 1400 may include performing communication using updated transport network layer information (block 1420). For example, IAB nodes (e.g., using controller / processor 240, transmit processor 220, TXMIMO processor 230, MOD 232, antenna 234, etc.) may use updated transport network layer information to perform communication, as described above.

[0170] Process 1400 may include additional aspects, such as any single aspect or any combination thereof described below and / or in conjunction with one or more other process descriptions elsewhere described herein.

[0171] In a first aspect, process 1400 includes: receiving a request for a network address; and providing a network address, wherein updated transport network layer information is based at least in part on the network address.

[0172] In a second aspect, either alone or in combination with the first aspect, process 1400 includes: receiving a configuration message indicating the release of one or more network addresses; and releasing one or more network addresses at least in part based on the configuration message.

[0173] In the third aspect, either alone or in combination with one or more of the first to second aspects, the network address includes at least one of IPv4 addresses, IPv6 addresses, or IPv6 prefixes.

[0174] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the information indicating the network address indicates the use of the network address, and the updated transport network layer information is at least partially based on that use.

[0175] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the information indicating the network address does not indicate the use of the network address, and wherein, at least in part based on the information indicating the network address, the use is not indicated, and updated transport network layer information can be used for all services.

[0176] In the sixth aspect, either alone or in combination with one or more of the first to fifth and sixth aspects, changes in the donor distributed unit are associated with radio link failures of the mobile terminal.

[0177] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1400 includes providing a central entity with instructions regarding the establishment, release, or modification of routes, wherein triggering conditions are at least partially based on the instructions.

[0178] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the IAB node includes a mobile terminal.

[0179] In the ninth aspect, either alone or in combination with one or more of the first through eighth aspects, the IAB node includes distributed units.

[0180] In the tenth aspect, either alone or in combination with one or more aspects from the first to the ninth aspect, the IAB node is an IAB donor.

[0181] although Figure 14An example box for process 1400 is shown, but in some respects, it differs from... Figure 14 Compared to the boxes depicted, process 1400 may include additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 1400 may be executed in parallel.

[0182] Figure 15 This is a diagram illustrating an example process 1500 performed, for example, by an IAB node according to various aspects of this disclosure. Example process 1500 is an IAB node (e.g., BS 110, non-anchor base station 345, non-anchor node 410, DU function 420, MT function 415, IAB node 510, ...). Figures 7 to 10 The IAB node shown Figures 7 to 10 Examples shown include child nodes (e.g.) performing operations associated with the management of identifiers in the IAB network.

[0183] like Figure 15 As shown, in some aspects, process 1500 may include receiving an updated identifier of an IAB node (box 1510) based at least in part on a triggering condition for updating the identifier of an IAB node in the IAB network. For example, an IAB node (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receiver processor 238, controller / processor 240) may receive an updated identifier of an IAB node based at least in part on a triggering condition for updating the identifier of an IAB node in the IAB network, as described above.

[0184] like Figure 15 As further shown, in some aspects, process 1500 may include performing communication using an updated identifier (box 1520). For example, IAB nodes (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.) may use the updated identifier to perform communication, as described above.

[0185] Process 1400 may include additional aspects, such as any single aspect or any combination thereof described below and / or in conjunction with one or more other process descriptions elsewhere described herein.

[0186] In the first aspect, the identifier of an IAB node includes a distributed unit identifier used to control the interface process.

[0187] In a second aspect, either alone or in combination with the first aspect, process 1500 includes providing a central entity with instructions regarding the establishment, release, or modification of routes including IAB nodes, wherein triggering conditions are based at least in part on the instructions.

[0188] In the third aspect, either alone or in combination with one or more of the first to second aspects, the IAB node includes a mobile terminal.

[0189] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, an IAB node includes distributed units.

[0190] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the IAB node is an IAB donor.

[0191] although Figure 15 An example box for process 1500 is shown, but in some respects, it differs from... Figure 15 Compared to the boxes depicted, process 1500 may include additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in the process 1500 may be executed in parallel.

[0192] Figure 16 This is a diagram illustrating an example process 1600 performed, for example, by an IAB node according to various aspects of this disclosure. Example process 1600 is an IAB node (e.g., BS 110, non-anchor base station 345, non-anchor node 410, DU function 420, MT function 415, IAB node 510, ...). Figures 7 to 10 The IAB node shown Figures 7 to 10 Examples shown include child nodes (e.g.) performing operations associated with the management of identifiers in the IAB network.

[0193] like Figure 16 As shown, in some aspects, process 1600 may include receiving one or more updated cell identifiers from an IAB node, at least in part based on the satisfaction of a triggering condition, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node (box 1610). For example, an IAB node (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240) may receive one or more updated cell identifiers from an IAB node, at least in part based on the satisfaction of a triggering condition, as described above. In some aspects, the one or more updated cell identifiers correspond to one or more cells served by the IAB node.

[0194] like Figure 16As further shown, in some aspects, process 1600 may include performing communication using one or more updated cell identifiers (box 1620). For example, an IAB node (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.) may use one or more updated cell identifiers to perform communication, as described above.

[0195] Process 1600 may include additional aspects, such as any single aspect or any combination thereof described below and / or in conjunction with one or more other process descriptions elsewhere described herein.

[0196] In a first aspect, process 1600 includes providing a central entity with instructions regarding the establishment, release, or modification of routes including IAB nodes, wherein triggering conditions are based at least in part on the instructions.

[0197] In the second aspect, either alone or in combination with the first aspect, the communication includes: one or more System Information Blocks (SIBs) broadcasting one or more updated cell identifiers, or one or more control interface messages including one or more updated cell identifiers.

[0198] In the third aspect, either alone or in combination with one or more of the first to second aspects, the IAB node includes a mobile terminal.

[0199] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, an IAB node includes distributed units.

[0200] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the IAB node is an IAB donor.

[0201] although Figure 16 An example box for process 1600 is shown, but in some respects, it differs from... Figure 16 Compared to the boxes depicted, process 1600 may include additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 1600 may be executed in parallel.

[0202] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or can be derived from practice in the subject matter.

[0203] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented as hardware, firmware, and / or a combination of hardware and software.

[0204] As used in this article, depending on the context, satisfying the threshold can mean that the value is greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0205] Clearly, the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or combinations 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, this document does not refer to specific software code to describe the operation and behavior of the systems and / or methods—it should be understood that software and hardware can be designed to implement the systems and / or methods, at least in part, based on the descriptions herein.

[0206] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of aspects. In fact, many of these features can be combined in ways not specifically stated in the claims and / or disclosed in the specification. While each dependent claim listed below may be directly subordinate to a claim, the disclosure of aspects includes combinations of each dependent claim with every other claim in the claim set. The phrase “at least one” in the list of items refers to any combination of these items, including single members. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0207] None of the elements, actions, or instructions used herein should be construed as critical or essential unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with “one or more.” Where only one item is anticipated, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “has,” “have,” “having,” and / or similar terms are intended to be open-ended terms. Additionally, the phrase “based on” is intended to mean “at least partially based on” unless explicitly stated otherwise.

Claims

1. A central entity in an integrated access and backhaul (IAB) network, comprising: Memory; as well as One or more processors are operatively coupled to the memory, wherein the one or more processors are configured to: The triggering conditions for updating the transport network layer information of the IAB node in the IAB network are determined based at least in part on a change in the first donor distributed unit associated with the IAB node or the second donor distributed unit in the IAB network. as well as At least in part based on the fulfillment of the triggering condition, updated transport network layer information is provided to the IAB node, the updated transport network layer information identifying Internet Protocol (IP) addresses for non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for the non-UE related services and the UE related services.

2. The central entity according to claim 1, wherein, The IP address includes IP version 4 address or IP version 6 address.

3. The central entity according to claim 1, wherein, The updated transport network layer information differs between signaling services and data transmission.

4. The central entity according to claim 1, wherein, The updated transport network layer information is the same for both signaling services and data transmission.

5. The central entity according to claim 1, wherein, The updated transport network layer information differs between services related to non-user equipment (UE) and services related to UE.

6. The central entity according to claim 1, wherein, The updated transport network layer information is the same for non-user equipment (UE) related services and for UE related services.

7. The central entity according to claim 1, wherein, The change to the first donor distributed unit is associated with redirecting existing control interface associations or tunnels from routes associated with the first donor distributed unit to routes associated with the second donor distributed unit.

8. The central entity according to claim 7, wherein, The first donor distributed unit and the second donor distributed unit are associated with the same central entity.

9. The central entity according to claim 7, wherein, The first donor distributed unit and the second donor distributed unit are associated with different central entities.

10. The central entity according to claim 1, wherein, The updated transport network layer information is associated with the second donor distributed unit.

11. The central entity according to claim 1, wherein, The determination of the triggering condition for updating the transport network layer information of the IAB node in the IAB network is also based at least in part on the establishment, release or modification of a route including the IAB node, and the establishment, release or modification of a route including the IAB node is based at least in part on integrating another IAB node other than the IAB node into the route.

12. The central entity according to claim 1, wherein, The establishment, release, or modification of routes including the IAB nodes is based at least in part on integrating the IAB nodes into the routes.

13. The central entity according to claim 1, wherein, The establishment, release, or modification of routes, including those of the IAB nodes, is based at least in part on a radio link failure associated with one of the following: The distributed unit of the parent node of the IAB node or the upstream IAB node. The primary cell group of the IAB node or the upstream IAB node, or The auxiliary cell group of the IAB node or the upstream IAB node.

14. The central entity according to claim 1, wherein, The establishment, release, or modification of routes, including those of the IAB nodes, is based at least in part on at least one of the following: The switching of upstream nodes of the IAB node, Adding auxiliary nodes Master node switching Auxiliary node change, Role switching, or Modify the primary or secondary node.

15. The central entity according to claim 1, wherein, The establishment, release, or modification of routes, including those of the IAB nodes, is at least in part based on topology adaptation of the routes.

16. The central entity according to claim 1, wherein, The one or more processors are configured to determine that the trigger condition is met, at least in part, based on receiving an instruction from a mobile terminal of the IAB node or a different IAB node associated with the central entity.

17. The central entity according to claim 1, wherein, The one or more processors are configured, upon determining that the trigger condition is met, to determine that the trigger condition is met based at least in part on receiving an instruction from a distributed unit of the IAB node or a different IAB node associated with the central entity.

18. The central entity according to claim 1, wherein, The central entity is a first central entity, and the one or more processors are configured to: when the establishment, release, or modification of routes including the IAB node is at least partially based on a switch to a second central entity or the addition of a secondary node. The second central entity is provided with the context of the mobile terminal of the IAB node and an indication of the association between the IAB node and the distributed unit.

19. The central entity according to claim 18, wherein, The one or more processors are configured to provide the context of the mobile terminal of the IAB node and the indication of the IAB node being associated with the distributed unit, at least in part based on a request received from the second central entity for the context and the indication of the IAB node being associated with the distributed unit.

20. The central entity according to claim 1, wherein, The central entity is a first central entity, wherein the establishment, release, or modification of routes for the IAB node is at least partially based on a handover to a second central entity or the addition of a secondary node, and wherein the second central entity is configured to receive from the core network the context of the mobile terminal of the IAB node and an indication of the IAB node being associated with a distributed unit.

21. The central entity according to claim 1, wherein, The one or more processors are configured to: Whether to update the transport network layer information is determined at least in part based on the triggering conditions.

22. The central entity according to claim 1, wherein, Updated transport network layer information is provided using radio resource control messages or configuration messages.

23. The central entity according to claim 1, wherein, The one or more processors are configured to: Send a request for a network address; and The network address is received, wherein the updated transport network layer information is based at least in part on the network address.

24. The central entity according to claim 23, wherein, The one or more processors are configured to: Send a configuration message indicating that one or more network addresses are to be released.

25. The central entity according to claim 23, wherein, The network address includes at least one of IP version 4 address, IP version 6 address, or IP version 6 prefix.

26. The central entity according to claim 23, wherein, The information indicating the network address indicates the use of the network address, and wherein the updated transport network layer information is at least partially based on the use.

27. The central entity according to claim 23, wherein, The information indicating the network address does not indicate the use of the network address, and wherein, at least in part based on the information indicating the network address not indicating the use, updated transport network layer information can be used for all services.

28. The central entity according to claim 1, wherein, The change in the donor distributed unit is associated with a radio link failure in the mobile terminal.

29. An IAB node in an integrated access and backhaul IAB network, comprising: Memory; as well as One or more processors are operatively coupled to the memory, wherein the one or more processors are configured to: The system receives updated transport network layer information, which identifies the Internet Protocol (IP) addresses used for both non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for both UE related services and UE related services. The updated transport network layer information is at least partially based on the satisfaction of triggering conditions for updating the transport network layer information. The triggering condition is at least partially based on a change in a first donor distributed unit associated with the IAB node or a second donor distributed unit in the IAB network; and Communication is performed using the updated transport network layer information.

30. The IAB node according to claim 29, wherein, The one or more processors are configured to: Receive requests for network addresses; and The network address is provided, wherein the updated transport network layer information is based at least in part on the network address.

31. The IAB node according to claim 30, wherein, The one or more processors are configured to: Receive a configuration message instructing the release of one or more network addresses, and The one or more network addresses are released, at least in part, based on the configuration message.

32. The IAB node according to claim 30, wherein, The network address includes at least one of IP version 4 address, IP version 6 address, or IP version 6 prefix.

33. The IAB node according to claim 30, wherein, The information indicating the network address indicates the use of the network address, and wherein the updated transport network layer information is at least partially based on the use.

34. The IAB node according to claim 30, wherein, The information indicating the network address does not indicate the use of the network address, and wherein, at least in part based on the information indicating the network address not indicating the use, updated transport network layer information can be used for all services.

35. The IAB node according to claim 29, wherein, The change of the first donor distributed unit or the second donor distributed unit is associated with a radio link failure of the mobile terminal.

36. The IAB node according to claim 29, wherein, The one or more processors are configured to: Provide instructions to a central entity regarding the establishment, release, or modification of routes, wherein the triggering conditions are based at least in part on the instructions.

37. The IAB node according to claim 29, wherein, The IAB node includes a mobile terminal.

38. The IAB node according to claim 29, wherein, The IAB node includes distributed units.

39. The IAB node according to claim 29, wherein, The IAB node is an IAB donor.

40. A method for wireless communication performed by a central entity in an Integrated Access and Backhaul (IAB) network, comprising: The triggering conditions for updating the transport network layer information of the IAB node in the IAB network are determined based at least in part on a change in the first donor distributed unit associated with the IAB node or the second donor distributed unit in the IAB network. as well as At least in part based on the fulfillment of the triggering condition, updated transport network layer information is provided to the IAB node, the updated transport network layer information identifying Internet Protocol (IP) addresses for non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for the non-UE related services and the UE related services.

41. The method according to claim 40, wherein, The IP address includes IP version 4 address or IP version 6 address.

42. The method according to claim 40, wherein, The updated transport network layer information differs between signaling services and data transmission.

43. The method according to claim 40, wherein, The updated transport network layer information is the same for both signaling services and data transmission.

44. The method of claim 40, wherein, The updated transport network layer information differs between services related to non-user equipment (UE) and services related to UE.

45. The method according to claim 40, wherein, The updated transport network layer information is the same for non-user equipment (UE) related services and for UE related services.

46. ​​The method of claim 40, wherein, The change to the first donor distributed unit is associated with redirecting existing control interface associations or tunnels from routes associated with the first donor distributed unit to routes associated with the second donor distributed unit.

47. The method according to claim 46, wherein, The first donor distributed unit and the second donor distributed unit are associated with the same central entity.

48. The method according to claim 46, wherein, The first donor distributed unit and the second donor distributed unit are associated with different central entities.

49. The method according to claim 40, wherein, The updated transport network layer information is associated with the second donor distributed unit.

50. The method of claim 40, wherein, The determination of the triggering condition for updating the transport network layer information of the IAB node in the IAB network is also based at least in part on the establishment, release or modification of a route including the IAB node, and the establishment, release or modification of a route including the IAB node is based at least in part on integrating another IAB node other than the IAB node into the route.

51. The method according to claim 40, wherein, The establishment, release, or modification of routes including the IAB nodes is based at least in part on integrating the IAB nodes into the routes.

52. The method according to claim 40, wherein, The establishment, release, or modification of routes, including those of the IAB nodes, is based at least in part on a radio link failure associated with one of the following: The distributed unit of the parent node of the IAB node or the upstream IAB node. The primary cell group of the IAB node or the upstream IAB node, or The auxiliary cell group of the IAB node or the upstream IAB node.

53. The method according to claim 40, wherein, The establishment, release, or modification of routes, including those of the IAB nodes, is based at least in part on at least one of the following: The switching of upstream nodes of the IAB node, Adding auxiliary nodes Master node switching Auxiliary node change, Role switching, or Modify the primary or secondary node.

54. The method according to claim 40, wherein, The establishment, release, or modification of routes, including those of the IAB nodes, is at least in part based on topology adaptation of the routes.

55. The method according to claim 40, wherein, The determination that the triggering condition is met is based at least in part on receiving an instruction from a mobile terminal of the IAB node or a different IAB node associated with the central entity.

56. The method of claim 40, wherein, The determination that the triggering condition is met is based at least in part on receiving an instruction from the IAB node or a distributed unit of a different IAB node associated with the central entity.

57. The method of claim 40, wherein, The central entity is a first central entity, and the method includes the following when the establishment, release, or modification of routes including the IAB node is at least partially based on a switch to a second central entity or the addition of a secondary node: The second central entity is provided with the context of the mobile terminal of the IAB node and an indication of the association between the IAB node and the distributed unit.

58. The method according to claim 57, wherein, The provision of the context of the mobile terminal of the IAB node and the indication of the association between the IAB node and the distributed unit are based at least in part on receiving a request from the second central entity for the context and the indication of the association between the IAB node and the distributed unit.

59. The method according to claim 40, wherein, The central entity is a first central entity, wherein the establishment, release, or modification of routes for the IAB node is at least partially based on a handover to a second central entity or the addition of a secondary node, and wherein the second central entity receives from the core network the context of the mobile terminal of the IAB node and an indication that the IAB node is associated with a distributed unit.

60. The method of claim 40, further comprising: Whether to update the transport network layer information is determined at least in part based on the triggering conditions.

61. The method according to claim 40, wherein, Updated transport network layer information is provided using radio resource control messages or configuration messages.

62. The method of claim 40, further comprising: Send a request for a network address; as well as The network address is received, wherein the updated transport network layer information is based at least in part on the network address.

63. The method of claim 62, further comprising: Send a configuration message indicating that one or more network addresses are to be released.

64. The method according to claim 62, wherein, The network address includes at least one of IP version 4 address, IP version 6 address, or IP version 6 prefix.

65. The method according to claim 62, wherein, The information indicating the network address indicates the use of the network address, and wherein the updated transport network layer information is at least partially based on the use.

66. The method according to claim 62, wherein, The information indicating the network address does not indicate the use of the network address, and wherein, based at least in part on the fact that the information indicating the network address does not indicate the use, the updated transport network layer information can be used for all services.

67. The method of claim 40, wherein, The change in the donor distributed unit is associated with a radio link failure in the mobile terminal.

68. A method for wireless communication performed by an IAB node in an Integrated Access and Backhaul (IAB) network, comprising: The system receives updated transport network layer information, which identifies the Internet Protocol (IP) addresses used for both non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for both UE related services and UE related services. The updated transport network layer information is at least partially based on the satisfaction of triggering conditions for updating the transport network layer information. The triggering condition is at least partially based on a change in a first donor distributed unit associated with the IAB node or a second donor distributed unit in the IAB network; and Communication is performed using the updated transport network layer information.

69. The method of claim 68, further comprising: Receive requests for network addresses; as well as The network address is provided, wherein the updated transport network layer information is based at least in part on the network address.

70. The method of claim 69, further comprising: Receive a configuration message indicating that one or more network addresses should be released; as well as The one or more network addresses are released, at least in part, based on the configuration message.

71. The method according to claim 69, wherein, The network address includes at least one of IP version 4 address, IP version 6 address, or IP version 6 prefix.

72. The method according to claim 69, wherein, The information indicating the network address indicates the use of the network address, and wherein the updated transport network layer information is at least partially based on the use.

73. The method according to claim 69, wherein, The information indicating the network address does not indicate the use of the network address, and wherein, based at least in part on the fact that the information indicating the network address does not indicate the use, updated transport network layer information can be used for all services.

74. The method according to claim 68, wherein, The change of the first donor distributed unit or the second donor distributed unit is associated with a radio link failure of the mobile terminal.

75. The method of claim 68, further comprising: Provide instructions to a central entity regarding the establishment, release, or modification of routes, wherein the triggering conditions are based at least in part on the instructions.

76. The method according to claim 68, wherein, The IAB node includes a mobile terminal.

77. The method according to claim 68, wherein, The IAB node includes distributed units.

78. The method according to claim 68, wherein, The IAB node is an IAB donor.

79. A method for wireless communication performed by a central entity in an Integrated Access and Backhaul (IAB) network, comprising: Determine if the triggering conditions for updating the identifiers of IAB nodes in the IAB network are met. as well as At least in part based on determining that the triggering condition is met, the IAB node is provided with an updated identifier and updated transport network layer information, wherein the updated transport network layer information identifies the Internet Protocol (IP) address for both the non-user equipment (UE) related service and the UE related service, and wherein the IP address is the same for both the non-UE related service and the UE related service.

80. The method according to claim 79, wherein, The determination that the triggering condition is met is based at least in part on the establishment, release, or modification of routes including the IAB node.

81. The method according to claim 79, wherein, The identifier of the IAB node includes a distributed unit identifier used to control the interface process.

82. The method according to claim 79, wherein, The triggering condition is associated with establishing a control plane association between the IAB node and the target central entity.

83. The method according to claim 79, wherein, The determination that the triggering condition is met is based at least in part on receiving an instruction from a mobile terminal of the IAB node or a different IAB node associated with the central entity.

84. The method according to claim 79, wherein, The determination that the triggering condition is met is based at least in part on receiving an instruction from the IAB node or a distributed unit of a different IAB node associated with the central entity.

85. The method according to claim 79, wherein, The central entity is a first central entity, and the method further includes, when the triggering condition is at least partially based on a switch to a second central entity or the addition of a secondary node: The second central entity is provided with the context of the mobile terminal of the IAB node and an indication of the association between the IAB node and the distributed unit.

86. The method of claim 79, further comprising: Whether to update the identifier of the IAB node is determined at least in part based on the triggering condition.

87. The method according to claim 79, wherein, The updated identifier is provided using radio resource control messages or control interface messages.

88. A method for wireless communication performed by a central entity in an Integrated Access and Backhaul (IAB) network, comprising: Determine whether triggering conditions are met for updating one or more cell identifiers of an IAB node in the IAB network, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node; and Based at least in part on determining that the triggering condition is met, the IAB node is provided with one or more updated cell identifiers and updated transport network layer information, wherein the updated transport network layer information identifies Internet Protocol (IP) addresses for non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for the non-UE related services and the UE related services.

89. The method according to claim 88, wherein, The determination that the triggering condition is met is based at least in part on the establishment, release, or modification of routes including the IAB node.

90. The method according to claim 89, wherein, The central entity is a first central entity, wherein the establishment, release, or modification of routes for the IAB node is at least partially based on a handover to a second central entity or the addition of a secondary node, and wherein the second central entity receives from the core network the context of the mobile terminal of the IAB node and an indication that the IAB node is associated with a distributed unit.

91. The method according to claim 88, wherein, The one or more cell identifiers include at least one of the following: a new radio cell global identifier, a public land mobile network identifier, a base station identifier, a local cell identifier, or a new radio cell identifier.

92. The method according to claim 88, wherein, The triggering condition is associated with establishing a control plane association between the IAB node and the target central entity.

93. The method according to claim 88, wherein, The determination that the triggering condition is met is based at least in part on receiving an instruction from a mobile terminal of the IAB node or a different IAB node associated with the central entity.

94. The method according to claim 88, wherein, The determination that the triggering condition is met is based at least in part on receiving an instruction from the IAB node or a distributed unit of a different IAB node associated with the central entity.

95. The method according to claim 88, wherein, The central entity is a first central entity, and the method further includes, when the triggering condition is at least partially based on a switch to a second central entity or the addition of a secondary node: The second central entity is provided with the context of the mobile terminal of the IAB node and an indication of the association between the IAB node and the distributed unit.

96. The method according to claim 95, wherein, The provision of the context of the mobile terminal of the IAB node and the indication of the association between the IAB node and the distributed unit are based at least in part on receiving a request from the second central entity for the context and the indication of the association between the IAB node and the distributed unit.

97. The method of claim 88, further comprising: Whether to update the one or more cell identifiers is determined at least in part based on the triggering conditions.

98. The method according to claim 88, wherein, The one or more updated cell identifiers are provided using radio resource control messages or control interface messages.

99. A method for wireless communication performed by an IAB node in an Integrated Access and Backhaul (IAB) network, comprising: At least in part, based on a triggering condition for updating the identifier of the IAB node in the IAB network, the updated identifier and updated transport network layer information of the IAB node are received, wherein the updated transport network layer information identifies Internet Protocol (IP) addresses for non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for the non-UE related services and the UE related services; and Communication is performed using the updated identifier and the updated transport network layer information.

100. The method according to claim 99, wherein, The identifier of the IAB node includes a distributed unit identifier for controlling the interface process.

101. The method of claim 99, further comprising: The central entity is provided with instructions regarding the establishment, release, or modification of routes including the IAB node, wherein the triggering conditions are based at least in part on the instructions.

102. The method according to claim 99, wherein, The IAB node includes a mobile terminal.

103. The method according to claim 99, wherein, The IAB node includes distributed units.

104. The method according to claim 99, wherein, The IAB node includes an IAB donor.

105. A method for wireless communication performed by an IAB node in an Integrated Access and Backhaul (IAB) network, comprising: At least in part based on satisfying a triggering condition, the IAB node receives one or more updated cell identifiers and updated transport network layer information, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node, and wherein the updated transport network layer information identifies Internet Protocol (IP) addresses used for non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for both the UE related services and the UE related services; and Communication is performed using the one or more updated cell identifiers and the updated transport network layer information.

106. The method of claim 105, further comprising: The central entity is provided with instructions regarding the establishment, release, or modification of routes including the IAB node, wherein the triggering conditions are based at least in part on the instructions.

107. The method according to claim 105, wherein, The communication includes: one or more System Information Blocks (SIBs) broadcasting the one or more updated cell identifiers, or one or more control interface messages including the one or more updated cell identifiers.

108. The method according to claim 105, wherein, The IAB node includes a mobile terminal.

109. The method according to claim 105, wherein, The IAB node includes distributed units.

110. The method of claim 105, wherein, The IAB node is an IAB donor.

111. A central entity in an integrated access and backhaul (IAB) network, comprising: Memory; as well as One or more processors are operatively coupled to the memory, wherein the one or more processors are configured to: Determine if the triggering conditions for updating the identifiers of IAB nodes in the IAB network are met. as well as At least in part based on determining that the triggering condition is met, the IAB node is provided with an updated identifier and updated transport network layer information, wherein the updated transport network layer information identifies the Internet Protocol (IP) address for both the non-user equipment (UE) related service and the UE related service, and wherein the IP address is the same for both the non-UE related service and the UE related service.

112. A central entity in an integrated access and backhaul (IAB) network, comprising: Memory; as well as One or more processors are operatively coupled to the memory, wherein the one or more processors are configured to: Determine if triggering conditions are met for updating one or more cell identifiers of an IAB node in the IAB network, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node; as well as Based at least in part on determining that the triggering condition is met, the IAB node is provided with one or more updated cell identifiers and updated transport network layer information, wherein the updated transport network layer information identifies Internet Protocol (IP) addresses for non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for the non-UE related services and the UE related services.

113. An IAB node in an integrated access and backhaul IAB network, comprising: Memory; as well as One or more processors are operatively coupled to the memory, wherein the one or more processors are configured to: At least in part, based on a triggering condition for updating the identifier of the IAB node in the IAB network, the updated identifier and updated transport network layer information of the IAB node are received, wherein the updated transport network layer information identifies Internet Protocol (IP) addresses for non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for the non-UE related services and the UE related services; and Communication is performed using the updated identifier and the updated transport network layer information.

114. An IAB node in an integrated access and backhaul IAB network, comprising: Memory; as well as One or more processors are operatively coupled to the memory, wherein the one or more processors are configured to: At least in part based on satisfying a triggering condition, the IAB node receives one or more updated cell identifiers and updated transport network layer information, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node, and wherein the updated transport network layer information identifies Internet Protocol (IP) addresses used for non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for both the UE related services and the UE related services; and Communication is performed using the one or more updated cell identifiers and the updated transport network layer information.

115. An apparatus for wireless communication, comprising: A component for determining, at least in part, based on a change in a first donor distributed unit associated with an IAB node or a second donor distributed unit in the IAB network, a trigger condition that satisfies the updating of transport network layer information of IAB nodes in the integrated access and backhaul IAB network. as well as A component for providing updated transport network layer information to the IAB node based at least in part on the fulfillment of the triggering condition, the updated transport network layer information identifying Internet Protocol (IP) addresses for non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for the non-UE related services and the UE related services.

116. An apparatus for wireless communication, comprising: A component used to determine the triggering conditions that are met for updating the identifiers of IAB nodes in the integrated access and backhaul IAB networks. as well as A component for providing the IAB node with an updated identifier and updated transport network layer information, at least in part based on determining that the triggering condition is met, wherein the updated transport network layer information identifies the Internet Protocol (IP) address for both non-user equipment (UE) related services and UE related services, wherein the IP address is the same for both UE related services and UE related services.

117. An apparatus for wireless communication, comprising: Components for determining whether triggering conditions are met for updating one or more cell identifiers of an IAB node in an integrated access and backhaul IAB network, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node; and Components for providing one or more updated cell identifiers and updated transport network layer information to the IAB node, at least in part based on determining that the triggering condition is met, wherein the updated transport network layer information identifies Internet Protocol (IP) addresses for non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for the non-UE related services and the UE related services.

118. An apparatus for wireless communication, comprising: A component for receiving updated transport network layer information, at least in part, based on satisfying triggering conditions for updating transport network layer information, wherein the updated transport network layer information identifies Internet Protocol (IP) addresses for non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for both the non-UE related services and the UE related services. The updated transport network layer information is at least partially based on the satisfaction of triggering conditions for updating the transport network layer information. The triggering condition is at least partially based on a change in a first donor distributed unit associated with the IAB node or a second donor distributed unit in the IAB network; and A component used to perform communication using updated transport network layer information.

119. An apparatus for wireless communication, comprising: A component for receiving an updated identifier and an updated transport network layer information identifier of an IAB node in an IAB network, at least in part based on a triggering condition for updating the identifier of an IAB node in an integrated access and backhaul IAB network, wherein the updated transport network layer information identifier is for Internet Protocol (IP) addresses of non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for the non-UE related services and the UE related services. as well as A component for performing communication using an updated identifier and the updated transport network layer information identifier.

120. An apparatus for wireless communication, comprising: Components for receiving, at least in part, one or more updated cell identifiers and updated transport network layer information identifiers of an IAB node in an Integrated Access and Backhaul (IAB) network based on a triggering condition, wherein the one or more updated cell identifiers correspond to one or more cells served by the IAB node, and wherein the updated transport network layer information identifiers are for Internet Protocol (IP) addresses of non-user equipment (UE) related services and UE related services, wherein the IP addresses are the same for both the UE related services and the UE related services; and A component for performing communication using the one or more updated cell identifiers and the updated transport network layer information identifiers.

Images