Method and device for migrating hosts

Abstract

A wireless communication method for a target integrated access backhaul (IAB) host is disclosed. The method comprises: receiving an IAB transmission migration management request message from an F1 terminal host of an IAB node, the IAB transmission migration management request message comprising at least one of the following items: a first identifier allocated by the F1 terminal host or a second identifier allocated by a target IAB host of a mobile terminal of the IAB node.

Description

[0001] This document generally pertains to wireless communication, and particularly to 5G communication.

[0002] Integrated Access and Backhaul (IAB) that supports wireless backhaul via NR (New Radio) enables flexible and very dense deployment of NR cells, and at the same time reduces the need for wired transmission infrastructure. The migration process within the hosting CU has been studied and specified in R16 IAB, where both the source parent node and the target parent node are served by the same IAB hosting CU. Additionally, inter-host CU migration has been discussed in R17 IAB, where the migrating IAB nodes are static in R17 IAB. However, inter-host migration for mobile IAB use cases as Figure 1 shown has not been discussed. As Figure 1 shown, IAB nodes can be installed in vehicles and can provide 5G coverage / capacity enhancement to in-vehicle and / or surrounding UEs (e.g., Figure 1 UE1 and UE2 in

[0003] This disclosure relates to a wireless communication method for a target Integrated Access and Backhaul (IAB) host. The method includes: receiving an IAB transmission migration management request message from an F1 terminating host of an IAB node, where the IAB transmission migration management request message includes at least one of the following: a first identifier assigned by the F1 terminating host or a second identifier assigned by a target IAB host of a mobile terminal of the IAB node.

[0004] Various embodiments may preferably implement the following features:

[0005] Preferably, the method further includes: receiving a first identifier from a source IAB host of a mobile terminal of the IAB node.

[0006] Preferably, the first identifier and the second identifier are Xn application protocol identifiers.

[0007] This disclosure also relates to a wireless communication method for use in an F1 terminating IAB host of an Integrated Access and Backhaul (IAB) node. The method includes: sending an IAB transmission migration management request message to a target IAB host of a mobile terminal of the IAB node, where the IAB transmission migration management request message includes at least one of the following: a first identifier assigned by the F1 terminating host or a second identifier assigned by the target IAB host.

[0008] Various embodiments may preferably implement the following features:

[0009] Preferably, the method further includes: receiving a second identifier from a source IAB host of a mobile terminal of the IAB node.

[0010] Preferably, the first identifier and the second identifier are Xn application protocol identifiers.

[0011] The present disclosure also relates to a wireless communication method for a source integrated access backhaul (IAB) host. The method includes: sending a conditional handover request message for an IAB node to a target IAB host, sending a configuration of a conditional handover to the target IAB host to the IAB node, receiving target information of the conditional handover to the target IAB host from the IAB node, and sending the target information to an F1 terminal host of the IAB node.

[0012] Various embodiments may preferably implement the following features:

[0013] Preferably, the configuration of the conditional handover includes at least one trigger condition configured by the source IAB host for sending the target information.

[0014] Preferably, at least one trigger condition configured by the source IAB host for sending the target information includes at least one of the following: a measurement threshold of a serving cell, a measurement threshold of a special cell, a measurement threshold of a primary cell, a measurement threshold of a primary and secondary cell, a measurement threshold of an adjacent cell, a measurement threshold of a conditional reconfiguration candidate cell, or a threshold of a measurement offset between a special and a conditional reconfiguration candidate cell.

[0015] The present disclosure also relates to a wireless communication method for an integrated access backhaul (IAB) node. The method includes: receiving a configuration of a conditional handover to a target IAB host from a source IAB host, and sending target information of the conditional handover to the target IAB host to the source IAB host or an F1 terminal host of the IAB node.

[0016] Various embodiments may preferably implement the following features:

[0017] Preferably, the configuration of the conditional handover includes at least one trigger condition configured by the source IAB host for sending the target information.

[0018] Preferably, at least one trigger condition configured by the source IAB host for sending the target information includes at least one of the following: a measurement threshold of a serving cell, a measurement threshold of a special cell, a measurement threshold of a primary cell, a measurement threshold of a primary and secondary cell, a measurement threshold of an adjacent cell, a measurement threshold of a conditional reconfiguration candidate cell, or a threshold of a measurement offset between a special and a conditional reconfiguration candidate cell.

[0019] The present disclosure also relates to a wireless communication method for a first integrated access and backhaul (IAB) host. The method includes: sending a request message associated with an IAB node to at least one second IAB host, and receiving a response message including migration capability information of at least one of the at least one second IAB host from the at least one second IAB host.

[0020] Various embodiments may preferably implement the following features:

[0021] Preferably, the wireless communication method further includes at least one of the following: determining, based on the migration capability information of the at least one second IAB host, one of the at least one second IAB hosts as a target IAB host for the migration of the IAB node.

[0022] Preferably, the request message includes at least one of the following: quality of service (QoS) information of a service associated with migration, the number of user terminals served by the DU of the IAB node, the speed of the IAB node, the location of the IAB node, a backhaul adaptation protocol (BAP) routing identifier, or a backhaul (BH) radio link control (RLC) channel identifier.

[0023] Preferably, the migration capability information includes at least one of the following: information on services that can be added to the second IAB host, the number of user terminals that can migrate to the second IAB host, a BAP routing identifier, or a BH RLC channel identifier.

[0024] The present disclosure also relates to a wireless communication method for a target integrated access and backhaul (IAB) host. The method includes: receiving an F1 establishment request message from a target logical distributed unit (DU) of an IAB node, where the F1 establishment request message includes at least one of the following: a mobile IAB indication, an identifier of a source IAB host, an identifier of the IAB node, or a DU identifier of a source logical DU of the IAB node, and sending an F1 establishment completion message to the source IAB host, where the F1 establishment completion information includes at least one of the following: an identifier of the IAB node, a DU identifier of a source logical DU of the IAB node, or an identifier of a mobile terminal of the IAB node.

[0025] Various embodiments may preferably implement the following features:

[0026] Preferably, the identifier of the IAB node includes at least one of the following: a backhaul adaptation protocol (BAP) address assigned by the source IAB host, a cell radio network temporary identifier, or an XnAP identifier.

[0027] Preferably, the identifier of the mobile terminal of the IAB node includes at least one of the following: a backhaul adaptation protocol (BAP) address assigned by the source IAB host, a cell radio network temporary identifier, or an XnAP identifier.

[0028] The present disclosure also relates to a wireless communication method for an integrated access backhaul (IAB) node. The method includes: sending an F1 establishment request message to a target IAB host, where the F1 establishment request message includes at least one of the following: a mobile IAB indication, an identifier of a source IAB host, an identifier of an IAB node, or a DU identifier of a source logical DU of the IAB node.

[0029] Various embodiments may preferably implement the following features:

[0030] Preferably, the identifier of the IAB node includes at least one of the following: a backhaul adaptation protocol (BAP) address assigned by the source IAB host, a cell radio network temporary identifier, or an XnAP identifier.

[0031] Preferably, the method further includes: receiving, from the source IAB host, an XnAP identifier assigned by the source IAB host to the IAB node.

[0032] The present disclosure also relates to a wireless communication method for an integrated access backhaul (IAB) node. The method includes: sending an F1 establishment message to a target IAB host, receiving an F1 establishment response message from the target IAB host, and sending an F1 establishment completion message to the source IAB host.

[0033] Various embodiments may preferably implement the following features:

[0034] Preferably, the F1 establishment completion message includes at least one of the following: an F1 establishment completion indication or an identifier of the target IAB host.

[0035] The present disclosure also relates to a wireless communication method for an integrated access backhaul (IAB) node. The method includes: sending an Internet protocol (IP) address request to an IAB host serving the IAB node, and receiving IP address information from the IAB host.

[0036] Various embodiments may preferably implement the following features:

[0037] Preferably, the IP address request includes at least one of the following: the number of requested IP addresses, the use of the IP address, a DU migration indication, a target logical DU indication, or a topology indication.

[0038] Preferably, the IP address information includes at least one of the following: at least one assigned IP address, the use of the IP address, a DU migration indication, a target logical DU indication, or a topology indication.

[0039] The present disclosure also relates to a wireless communication method for an F1 terminal IAB host of an integrated access backhaul (IAB) node. The method includes: sending an Internet Protocol (IP) address request for the IAB node to a target IAB provider.

[0040] Various embodiments may preferably implement the following features:

[0041] Preferably, the IP address request includes at least one of the following: the number of requested IP addresses, the IP address usage, a DU migration indication, a target logical DU indication, or a topology indication.

[0042] Preferably, the method further includes: receiving IP address information of the IAB node from the target IAB host and sending the IP address information to the IAB node.

[0043] Preferably, the IP address information includes at least one of the following: at least one assigned IP address, the IP address usage, a DU migration indication, a target logical DU indication, or a topology indication.

[0044] The present disclosure also relates to a wireless communication method for a target integrated access backhaul (IAB) host. The method includes: receiving an Internet Protocol (IP) address request for the IAB node from the IAB node or the F1 terminal IAB host of the IAB node, and sending the IP address information of the IAB node to the mobile terminal or the F1 terminal IAB host of the IAB node.

[0045] Various embodiments may preferably implement the following features:

[0046] Preferably, the IP address request includes at least one of the following: the number of requested IP addresses, the IP address usage, a DU migration indication, a target logical DU indication, or a topology indication.

[0047] Preferably, the IP address information includes at least one of the following: at least one assigned IP address, the IP address usage, a DU migration indication, a target logical DU indication, or a topology indication.

[0048] The present disclosure also relates to a wireless communication method for a source integrated access backhaul (IAB) host. The method includes: sending uplink mapping information used at the IAB node to a target IAB host.

[0049] The present disclosure also relates to a wireless communication method for a target integrated access backhaul (IAB) host. The method includes: receiving uplink mapping information used at the IAB node from the source IAB host and sending updated uplink mapping information to the IAB node.

[0050] The present disclosure also relates to a wireless communication method for an integrated access backhaul (IAB) host. The method includes: sending a sharing indication of a source logical distributed unit (DU) and a target logical DU of an IAB node to the IAB node.

[0051] Various embodiments may preferably implement the following features:

[0052] Preferably, the IAB host is a source IAB host of a mobile terminal of the IAB node, a target IAB host of a mobile terminal of the IAB node, a source IAB host of a DU of the IAB node, or a target host of a DU of the IAB node.

[0053] The present disclosure also relates to a wireless communication method for an integrated access backhaul (IAB) node. The method includes: receiving a sharing indication of a source logical distributed unit (DU) and a target logical DU of the IAB node from an IAB host.

[0054] Various embodiments may preferably implement the following features:

[0055] Preferably, the IAB host is a source IAB host of a mobile terminal of the IAB node, a target IAB host of a mobile terminal of the IAB node, a source IAB host of a DU of the IAB node, or a target host of a DU of the IAB node.

[0056] Preferably, the method further includes: sending configuration information associated with an uplink mapping configuration of the source logical DU to the target logical DU from the source logical DU.

[0057] The present disclosure also relates to a wireless communication method for an integrated access backhaul (IAB) node. The method includes: sending an Internet protocol (IP) address used by a target logical DU of the IAB node to a source IAB host.

[0058] The present disclosure also relates to a wireless communication method for a source integrated access backhaul (IAB) host. The method includes: receiving an Internet protocol (IP) address used by a target logical DU of the IAB node from a source logical distributed unit (DU) of the IAB node and sending the IP address to a target IAB host.

[0059] The present disclosure also relates to a wireless communication method for a target integrated access backhaul (IAB) host. The method includes: sending auxiliary information to an IAB host of a mobile terminal of the IAB node and receiving information for an Internet protocol (IP) header from the IAB host of the mobile terminal of the IAB node.

[0060] Various embodiments may preferably implement the following features:

[0061] Preferably, the auxiliary information includes at least one of the following: the Internet Protocol address of the IAB node, the Quality of Service (QoS) information of the service, and the identifier of the IAB node assigned by the IAB host of the mobile terminal of the IAB node.

[0062] Preferably, the information of the IP header includes at least one of the following: Differentiated Services Code Point (DSCP), flow label, or traffic information.

[0063] Preferably, the method further includes: receiving, from the target logical DU, the identifier of the IAB host of the mobile terminal of the IAB node and / or the identifier of the IAB node assigned by the IAB host of the mobile terminal of the IAB node.

[0064] The present disclosure also relates to a wireless communication method for an integrated access backhaul (IAB) host. The method includes: receiving, from a target IAB host connected to a distributed unit (DU) of an IAB node, auxiliary information for configuring a DL mapping, where the IAB host is for a mobile terminal of the IAB node, and sending information of an Internet Protocol (IP) header to the target IAB host.

[0065] Various embodiments may preferably implement the following features:

[0066] Preferably, the auxiliary information includes at least one of the following: the Internet Protocol address of the IAB node, the Quality of Service (QoS) information of the service, and the identifier of the IAB node assigned by the IAB host of the mobile terminal of the IAB node.

[0067] Preferably, the information for the IP header includes at least one of the following: Differentiated Services Code Point DSCP, flow label, or traffic information.

[0068] Preferably, the method further includes: sending the identifier of the IAB node assigned by the IAB host to the IAB node.

[0069] The present disclosure also relates to a wireless device, which includes a communication unit and a processor, and the processor is configured to execute the wireless communication method described in any one of the foregoing methods.

[0070] The present invention relates to a computer program product, which includes computer-readable program media code stored thereon, and when executed by a processor, the code causes the processor to implement the wireless communication method described in any one of the foregoing methods.

[0071] The exemplary embodiments disclosed herein are intended to provide features that will become apparent by reference to the following description and in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and not limitation, and that various modifications to the disclosed embodiments can be made by those of ordinary skill in the art upon reading this disclosure while remaining within the scope of this disclosure.

[0072] Accordingly, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based on design preferences, the specific order or hierarchy of steps of the disclosed method or process can be rearranged while remaining within the scope of the present disclosure. Thus, those of ordinary skill in the art should understand that the methods and techniques disclosed herein present various steps or acts in an exemplary order, and that the present disclosure is not limited to the specific order or hierarchy presented unless otherwise expressly stated.

[0073] The present invention is defined by the independent claims. Preferred embodiments are defined in the dependent claims. In the following description, although many features may be designated as optional, it should be recognized that all features included in the independent claims should not be construed as optional.

[0074] The above and other aspects and their implementations are described in more detail in the drawings, the description, and the claims.

[0075] Figure 1 A schematic diagram of a network is shown.

[0076] Figure 2 A schematic diagram of an integrated access and backhaul architecture according to an embodiment of the present disclosure is shown.

[0077] Figure 3 A schematic diagram of the parent / child node relationship of an IAB node according to an embodiment of the present disclosure is shown.

[0078] Figures 4A to 4C A schematic diagram of a migration in an IAB architecture according to an embodiment of the present disclosure is shown.

[0079] Figure 5 A schematic diagram of a full migration between hosts according to an embodiment of the present disclosure is shown.

[0080] Figure 6 A flowchart of a process according to an embodiment of the present disclosure is shown.

[0081] Figure 7 A flowchart of a process according to an embodiment of the present disclosure is shown.

[0082] Figure 8 Shows a flowchart of a process according to an embodiment of the present disclosure.

[0083] Figure 9 Shows a flowchart of a process according to an embodiment of the present disclosure.

[0084] Figure 10 Shows a flowchart of a process according to an embodiment of the present disclosure.

[0085] Figure 11 Shows a flowchart of a process according to an embodiment of the present disclosure.

[0086] Figure 12 Shows a flowchart of a process according to an embodiment of the present disclosure.

[0087] Figure 13 Shows a flowchart of a process according to an embodiment of the present disclosure.

[0088] Figure 14 Shows a flowchart of a process according to an embodiment of the present disclosure.

[0089] Figure 15 Shows a flowchart of a process according to an embodiment of the present disclosure.

[0090] Figure 16 Shows a flowchart of a process according to an embodiment of the present disclosure.

[0091] Figure 17 Shows a flowchart of a process according to an embodiment of the present disclosure.

[0092] Figure 18 Shows an example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure.

[0093] Figure 19 Shows an example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure.

[0094] Figure 2 Shows a schematic diagram of an integrated access backhaul (IAB) architecture according to an embodiment of the present disclosure. IAB supports wireless relay in NG-RAN (Next Generation Radio Access Network). Relay nodes called IAB nodes support access and backhaul via NR. Terminal nodes with NR backhaul on the network side are called IAB-hosts, which represent gNBs with additional functions to support IAB. Backhaul can be performed via single-hop or via multi-hop.

[0095] IAB nodes support gNB-DU functionality to terminate the NR access interface between the UE and the next-hop IAB node, and to terminate the F1 protocol for the gNB-CU functionality on the IAB host. The gNB-DU functionality on the IAB node is also referred to as IAB-DU.

[0096] In addition to gNB-DU functionality, the IAB node also supports a subset of UE functions referred to as IAB-MT (Mobile Terminal), which includes, for example, physical layer, layer 2, RRC, and NAS functions, to connect to another IAB node or the gNB-DU of the IAB host, and to connect to the gNB-CU and the core network on the IAB host.

[0097] The IAB node can use the SA mode (e.g., Figure 2 (a)) or EN-DC (e.g., Figure 2 (b)) to access the network. In EN-DC, the IAB node is also connected to the MeNB via E-UTRA, and the IAB host connects the X2-C termination as an SgNB.

[0098] Figure 3 A schematic diagram showing the parent / child node relationship of the IAB node according to an embodiment of the present disclosure is presented. In Figure 3 it, all IAB nodes connected to the IAB host via one or more hops form a directed acyclic graph (DAG) topology with the IAB host at its root. In this DAG topology, adjacent nodes on the IAB-DU interface are referred to as child nodes, and adjacent nodes on the IAB-MT interface are referred to as parent nodes. The direction towards the child nodes is further referred to as downstream, while the direction towards the parent nodes is referred to as upstream. The IAB host performs centralized resource, topology, and routing management for the IAB topology.

[0099] In one embodiment, partial migration refers to migrating the IAB-MT to a parent node under a different IAB-host-CU, while the co-located IAB-DU and one or more downstream IAB-nodes (if any) are not migrated (i.e., terminated at the initial IAB-host-CU).

[0100] In one embodiment, full migration means migrating the IAB node (i.e., the mobile IAB node in the mobile IAB scenario) and one or more downstream IAB nodes (if any) from one IAB-host-CU to another IAB-host-CU (both RRC and F1 connections).

[0101] In one embodiment, the F1-terminating IAB host refers to the IAB host that terminates the F1 (interface) for the IAB node terminal. The F1-terminating IAB host can also be named as the host of the DU (in the IAB node).

[0102] In one embodiment, there may be two logical DUs in the mobile IAB node. The two logical DUs in the mobile IAB node can be referred to as the source logical DU and the target logical DU or logical DU1 and logical DU2.

[0103] Figures 4A to 4C shows a schematic diagram of a handover in an IAB architecture according to an embodiment of the present disclosure. In Figure 4A , a partial handover is performed. The IAB-MT migrates from the host DU1 belonging to the host CU1 to the host DU2 belonging to the host CU2. Note that the IAB-DU maintains its F1 connection with the host CU1, and its UE context remains in the host CU1. In this embodiment, the F1-C / U traffic between the host CU1 and the IAB-DU is transmitted via the host DU2.

[0104] In Figure 4B , a partial handover is performed. The IAB-MT migrates from the host DU2 belonging to the host CU2 to the host DU3 belonging to the host CU3. In this embodiment, the IAB-DU maintains its F1 connection with the host CU1, and the UE context remains in the host CU1. The F1-C / U traffic between the host CU1 and the IAB-DU is transmitted via the host DU3.

[0105] In Figure 4C , a complete handover is performed. That is, the MT and DU of the IAB node are migrated to the same host. Specifically, the IAB-DU migrates from the host CU1 to the host CU3, and the UE switches from the host CU1 to the host CU3. The F1-C / U traffic between the host CU3 and the IAB-DU is transmitted via the host DU3.

[0106] Figure 5 shows a schematic diagram of a complete handover between hosts according to an embodiment of the present disclosure. In Figure 5 , the MT and its quasi-co-located DU are migrated to different IAB hosts. As Figure 5 shown, the IAB-MT migrates from the host CU2 to the host CU3, while the DU migration and UE handover processes are performed from the host CU1 to the host CU4. After the DU migration and UE handover processes, the F1 traffic between the logical DU2 and the host CU4 is transmitted via the host DU3 controlled by the host CU3. In this embodiment, the host CU1 and the host DU1 can be regarded as IAB host 1, the host CU2 and the host DU2 can be regarded as IAB host 2, and so on. IAB host 2 is the source (IAB) host of the MT of the mobile IAB node. IAB host 3 is the target IAB host of the MT of the mobile IAB node, and IAB host 1 is the source (IAB) host of the DU of the IAB node. IAB host 4 is the target host of the DU of the IAB node.

[0107] In embodiments of partial or full migration, during partial or full migration, the F1 service path needs to be transferred from the source path (i.e., via the source host DU) to the target path (i.e., via the target host DU). For example, the F1 terminal host may initiate an IAB transmission migration management request message to the target host to transfer the F1 service path. In one embodiment, the F1 terminal host UE XnAP ID and / or the non-F1 terminal host UE XnAP ID may be included in the IAB transmission migration management request message. The non-F1 terminal host UE XnAP ID in the IAB transmission migration management request message can be set / configured by Figure 6 the method / procedure shown below:

[0108] Step 601: Optionally, send the F1 terminal host XnAP ID (assigned by the F1 terminal host and used to identify the mobile IAB node) from the source host of the MT to the target host of the MT. For example, the F1 terminal host XnAP ID can be sent in the handover request message of the IAB-MT.

[0109] Step 602: Optionally, send the XnAP ID assigned by the target host of the MT (i.e., the target host XnAP ID) from the source host of the MT to the F1 terminal host.

[0110] Step 603, the F1 terminal host sends an IAB transmission migration management request message to the target host of the MT, and the message includes the F1 terminal host XnAP ID and / or the target host XnAP ID.

[0111] In Figure 6 , the target host of the MT can associate the received IAB transmission migration management request message with the corresponding IAB-MT.

[0112] In embodiments of partial or full migration, if CHO (Conditional Handover) is used for the IAB-MT, the source host of the IAB-MT may not know the target cell of the IAB-MT before sending the handover request message. The F1 terminal host of the IAB node may need to confirm the target cell information of the IAB-MT.

[0113] Figure 7 shows a flowchart of a process according to an embodiment of the present disclosure. Figure 7 The process shown includes the following steps:

[0114] Step 701: The source host of the IAB-MT sends a handover request message to the target host of the IAB-MT.

[0115] Step 702: The target host of the IAB-MT sends a handover request ACK (acknowledgment) message to the source host of the IAB-MT.

[0116] Step 703: The source host of the IAB-MT sends an RRC reconfiguration with CHO configuration to the IAB-MT. Optionally, the source host of the IAB-MT may configure new trigger conditions for the MT to send the target information of the IAB-MT. The trigger condition information configured by the IAB-MT source host includes at least one of the following: the measurement threshold of the serving cell, the measurement threshold of the SpCell / PCell / PSCell (special cell / primary cell / primary and secondary cell), the measurement threshold of adjacent cells, the measurement threshold of conditional reconfiguration candidate cells, and the threshold of the measurement offset between the SpCell and the conditional reconfiguration candidate cells. The above measurement thresholds can be configured for the measurement of RSRP (Reference Signal Receiving Power), RSRQ (Reference Signal Receiving Quality), or SINR (Signal-to-Interference-plus-Noise Ratio).

[0117] Step 704: The mobile IAB node sends the target information (e.g., via an RRC message) to the source host of the MT. The target information of the MT includes at least one of the following: the cell identifier of the target cell (e.g., PCI (Physical Cell Identifier) or NCGI (New Radio Cell Global Identifier)) or the gNB ID of the target IAB host. As an alternative or complementary solution, the mobile IAB node sends the target information to the F1 terminal host via an F1AP message (in this way, step 805 is not required).

[0118] Step 705, the source host sends the target information to the F1 terminal host according to the target information received from the mobile IAB node. The target information sent by the source host of the MT includes at least one of the cell identifier (PCI or NCGI) of the target cell, the gNB ID of the target IAB host, or the identifier of the IAB node (e.g., XnAP ID).

[0119] In the fully migrated embodiment, it may be necessary to migrate the IAB-DU and the UEs served by the IAB-DU. Figure 8 The method shown shows how the F1 terminal host (i.e., the source host of the IAB-DU) determines the target host for DU migration, i.e., the target gNB of the UEs served by the IAB-DU.

[0120] Step 801: The host of the IAB-DU (also referred to as the source host of the IAB-DU) sends a request message to another IAB host (also referred to as the second IAB host, e.g., an adjacent IAB host / candidate IAB host). The request message includes at least one of the following: the QoS information of the service to be migrated, the number of UEs served by the IAB-DU, the speed / rate of the IAB node, the location of the IAB node, the BAP routing ID, or the BH RLC channel ID.

[0121] Step 802: The second IAB host sends a response message to the host of the IAB DU. The response message includes at least one of the following: service information that can be added (such as an index or a QoS index), the number of UEs that can be migrated, a BAP routing ID, or a BHRLC channel ID.

[0122] Step 803: The host of the IAB-DU selects an IAB host as the target host of the IAB-DU based on the received response message.

[0123] In the fully migrated embodiment, the MT migration is performed after the DU migration and / or the DU and MT are migrated to different hosts. After the target logical DU completes the F1 establishment with the target host of the DU, the target host of the DU may need to send an F1 establishment completion to the source host of the DU so that the source host of the DU can initiate a UE handover process to the target host of the DU. However, the target host of the DU may not know the source host of the DU.

[0124] Figure 9 The flowchart shows a process / method for notifying the target host of the DU of the source host of the DU according to an embodiment of the present disclosure. In one embodiment, the information of the source host of the DU is sent to the target host of the DU for sending an F1 establishment completion indication.

[0125] Step 901: Optionally, the IAB host (e.g., the source host of the DU) sends the XnAP ID assigned by the IAB host for the IAB node to the IAB node (e.g., via an RRC message or an F1 message).

[0126] Step 902: The target logical DU sends an F1 establishment request message to the target host of the DU. The F1 establishment request message includes at least one of the following: a mobile IAB indication, the identity of the source host of the DU, the identity of the IAB node (e.g., the BAP address / C-RNTI / XnAP ID assigned by the source host of the DU), the DU ID of the source logical DU. In this embodiment, the source host of the DU is the host having an F1 connection with the source logical DU, that is, another logical DU in the mobile IAB node.

[0127] Step 903, the target host of the DU sends an F1 establishment completion message to the source host of the DU. The F1 establishment completion message includes at least one of the following: an F1 establishment completion indication, the identity of the IAB node, the identity of the DU, the identity of the MT (e.g., the XnAP ID / BAP address / C-RNTI assigned by the source host of the DU).

[0128] In one embodiment, for example, after receiving an F1 establishment response message from the target host of the IAB node, the IAB node (e.g., the source logical DU) sends an F1 establishment completion message / indication to the source host of the DU of the IAB node (i.e., the IAB host having an F1 connection with the source logical DU of the IAB node). This F1 establishment completion message / indication is used to indicate that the target logical DU of the IAB node has completed the F1 establishment process with the IAB host to which the target logical DU has been migrated. The F1 establishment completion message may include at least one of an F1 establishment completion indication or an identifier of the target host of the target logical DU (i.e., the IAB host having an F1 connection with the target logical DU).

[0129] In a fully migrated embodiment, there may be two logical DUs (i.e., the source logical DU and the target logical DU) in the mobile IAB node for performing DU migration. If different IP addresses are used for the two logical DUs, it may be necessary to allocate an Internet Protocol IP address to the target logical DU. The IP address can be allocated to the target logical DU via Figures 10 to 12 the method shown.

[0130] In Figure 10 , the mobile IAB-MT sends an IP address request to the IAB host of the mobile IAB-MT to request the IP address of the target logical DU (step 1001). The IP address request may include at least one of the following: the number of requested IP addresses, the IP address usage (e.g., F1-C, F1-U, all services), a DU migration indication, a target logical DU indication, or a topology indication. The IAB host of the mobile IAB-MT sends the IP address information of the target logical DU to the IAB-MT via, for example, an RRC message (step 1002). The IP address information may include at least one of the following: the allocated IP address, the IP address usage, a DU migration indication, a target logical DU indication, or a topology indication.

[0131] In Figure 11 step 1101 shown, the F1 terminal host of the IAB node sends an IP address request to the target IAB host of the IAB-MT. The IP address request may include at least one of the following: the number of requested IP addresses, the IP address usage (e.g., F1-C, F1-U, all services), a DU migration indication, a target logical DU indication, or a topology indication.

[0132] In step 1102, the IAB target host of the IAB-MT sends the IP address information of the target logical DU to the IAB-MT via, for example, an RRC message. The IP address information may include at least one of the following: the allocated IP address, the IP address usage, a DU migration indication, a target logical DU indication, or a topology indication.

[0133] In Figure 12 In it, the F1 terminal host of the IAB node sends an IP address request to the target IAB host of the IAB-MT (step 1301). The IP address request may include at least one of the following: the number of requested IP addresses, IP address usage (e.g., F1-C, F1-U, all services), DU migration indication, target logical DU indication, or topology indication.

[0134] In step 1202, the target IAB host of the IAB-MT sends the IP address information of the target logical DU to the F1 terminal host of the IAB node via the Xn interface / message. The IP address information may include at least one of the following: the assigned IP address, IP address usage, DU migration indication, target logical DU indication, or topology indication.

[0135] In step 1203, the F1 terminal host sends the IP address information to the IAB-DU node (e.g., the source logical DU) via an F1 message (i.e., via the F1 interface). The IP address information includes at least one of the following: the assigned IP address, IP address usage, DU migration indication, target logical DU indication, or topology indication.

[0136] In one embodiment, during full migration, two logical DUs in the IAB node may respectively have F1 connections with two different IAB hosts. In this embodiment, an uplink (UL) mapping may be configured for the target logical DU.

[0137] Figure 13 A schematic diagram of a method / procedure according to an embodiment of the present disclosure is shown. In Figure 13 In it, the source host of the DU (i.e., the host of the source logical DU) sends the UL mapping information used at the source logical DU to the target host of the DU (i.e., the host of the target logical DU) via, for example, a handover request message (step 1301). The UL mapping information includes at least one of the following: BAP routing ID, BH RLC channel ID, next-hop BAP address, service information (e.g., service index, QoS information of the service).

[0138] In step 1302, the target host sends the UL mapping configuration of the target logical DU to the target logical DU.

[0139] In one embodiment, during full migration, two logical DUs of the IAB node may respectively have F1 connections with two different IAB hosts. In this case, the IAB node may need to know the sharing of the two logical DUs.

[0140] Figure 14 A schematic diagram of a method / procedure according to an embodiment of the present disclosure is shown. In Figure 15Among them, the IAB host sends a sharing indication to the IAB node, for example, via an RRC or F1AP message (step 1401). In this embodiment, the IAB host can be the source host of the MT, the target host of the MT, the source host of the DU, or the target host of the DU.

[0141] In step 1402, the configuration of the source logical DU (e.g., UL mapping configuration, DU cell configuration) or information (e.g., UE context information) is passed to the target logical DU.

[0142] In a full migration embodiment, the mobile IAB-MT and its quasi-co-located DU are migrated to different hosts. In this embodiment, it may be necessary to perform an F1 establishment process between the target logical DU and the target host of the DU. The problem is how the target host of the DU obtains the IP address of the target logical DU (e.g., the IP address for F1-C or all services).

[0143] Figure 15 A flowchart of a method according to an embodiment of the present disclosure is shown. In step 1501, the source logical DU sends the IP address used by the target logical DU (e.g., for F1-C or all services, the IP address can be an internal IP address and / or an external IP address) to the source host of the DU. The source host of the DU is the IAB host having an F1 connection with the source logical DU.

[0144] In step 1502, the source host of the DU sends the IP address of the target logical DU to the target host of the DU.

[0145] In a full migration embodiment, the mobile IAB-MT and its quasi-co-located DU can be migrated to different hosts. In this embodiment, the DL service sent from the target host of the DU to the target logical DU may need to be transmitted via the host DU of the IAB-MT. In this case, it may be necessary to configure DL mapping at the host DU of the IAB-MT.

[0146] Figure 16 A flowchart of a method according to an embodiment of the present disclosure is shown. In step 1601, optionally, the IAB host (e.g., the host of the IAB-MT) sends the XnAP ID assigned by the IAB host for the IAB node to the IAB node, for example, via an RRC message or an F1 message.

[0147] In step 1602, the target logical DU sends an F1 establishment request message to the target host of the DU of the IAB node. In one embodiment, the F1 establishment request message includes the identity of the host of the IAB-MT and / or the identity of the IAB node assigned by the host of the IAB-MT (e.g., BAP address, C-RNTI, or XnAP ID).

[0148] In step 1603, the target logical DU or the target host of the DU sends an F1 establishment completion indication to the source host of the DU.

[0149] In step 1604, the source host of the DU initiates a handover procedure for one or more UEs served by the IAB node to the target host of the DU.

[0150] In step 1605, the target host of the DU sends auxiliary information to the host of the IAB-MT. In one embodiment, the auxiliary information includes at least one of the following: the IP address of the IAB node, the QoS information of the service, the identifier of the IAB node assigned by the host of the IAB-MT (e.g., BAP address, C-RNTI, or XnAP ID). Accordingly, the host of the IAB-MT can configure the DL mapping at the host DU of the IAB-MT.

[0151] In step 1606, the host of the IAB-MT sends a response message to the target host of the DU. In one embodiment, the response message includes at least one of the following: DSCP and / or flow label, service information (e.g., service index, QoS index, QoS of the service). The host of the DU can set the DSCP / flow label field of the IP header for the DL packet to be sent to the target logical DU.

[0152] Figure 17 A flowchart of a method according to an embodiment of the present disclosure is shown. In step 1701, the source host of the DU sends the identifier of the host of the IAB-MT and / or the identifier of the IAB node assigned by the host of the IAB MT to the target host of the DU. The identifier of the IAB node can be the XnAP ID or the BAP address. If the identifier of the IAB node is the BAP address, the BAP address needs to be:

[0153] - Sent from the host of the IAB-MT to the source host of the DU, or

[0154] - Sent from the target host of the IAB-MT to the source host of the IAB-MT, and then sent from the source host of the IAB-MT to the source host of the DU,

[0155] - Sent from the IAB node to the source host of the DU.

[0156] In step 1702, the target logical DU initiates an F1 establishment procedure with the target host of the DU.

[0157] In step 1703, the target logical DU or the target host of the DU sends an F1 establishment completion indication to the source host of the DU.

[0158] In step 1704, the source host of the DU initiates a handover procedure for the UE served by the IAB node to the target host of the DU.

[0159] In step 1705, the target host of the DU sends auxiliary information to the host of the IAB-MT. In one embodiment, the auxiliary information includes at least one of the following: the IP address of the IAB node, the QoS information of the service, the identifier of the IAB node assigned by the host of the IAB-MT (e.g., BAP address, C-RNTI, or XnAP ID). Thus, the host of the IAB-MT can configure the DL mapping at the host DU of the IAB-MT.

[0160] In step 1706, the host of the IAB-MT sends a response message to the target host of the DU. In one embodiment, the response message includes at least one of the following: DSCP and / or flow label, service information (e.g., service index, QoS index, QoS of the service). The host of the DU can set the DSCP / flow label field of the IP header for the DL packets to be sent to the target logical DU.

[0161] In an embodiment of partial migration, due to the movement of the mobile IAB-MT, the physical cell ID (PCI) of the cell of the mobile IAB-DU may conflict with other cells.

[0162] In one embodiment, the host of the IAB-DU can detect the PCI conflict. For example, the source host CU of the IAB-MT can send the information of the target host CU of the IAB-MT (e.g., the gNB ID of the target host of the IAB-MT) to the host CU of the IAB-DU. The host of the DU can know the gNB ID of the target host of the IAB-MT. When / if there is an Xn connection between the host CU of the DU and the target host in the IAB-MT, the host CU of the IAB-DU can obtain, for example, via the (existing) XnAP signaling (e.g., Xn SETUP / NG-RAN NODE CONFIGURATION UPDATE), one or more PCIs used in the serving cell and one or more neighboring cells of the target host CU of the IAB-MT. In this case, the host of the IAB-DU is able to detect the PCI conflict.

[0163] In response to the detection of the PCI conflict, the host of the IAB-DU sends the cell configuration information of the cell of the IAB-DU via, for example, F1 signaling (e.g., GNB-CUCONFIGURATION UPDATE message). In one embodiment, the cell configuration information includes at least one of the following: one or more PCIs, target logical DU indication, DU activation indication, two logical DU indications, or NCGI.

[0164] In one embodiment, after receiving the PCI in the cell configuration information of the mobile IAB node from the F1 terminal host, the mobile IAB node activates the second logical DU (i.e., the target logical DU) by using the received one or more PCIs.

[0165] In an embodiment for avoiding PCI conflicts, the second logical DU (i.e., the target logical DU) sends an F1 establishment request message to the host of the IAB-DU. The F1 establishment request message includes at least one of the following: the identifier of the source logical DU, the identifier of the mobile IAB node, the identifier of the mobile IAB-MT, the target logical DU indication, or the two logical DUs indication.

[0166] After the F1 connection between the second logical DU and the host of the IAB-DU is established, the host of the IAB-DU may send an RRC reconfiguration message for the UE to migrate the UE from the cell of the first logical DU (i.e., the source logical DU) to the cell of the second logical DU.

[0167] In an embodiment for avoiding PCI conflicts, the following steps may be performed:

[0168] Step 1: Optionally, the host of the IAB-DU sends the PCI of the IAB-DU cell to the target host of the IAB-MT, for example, via the Xn interface. As an alternative or complementary solution, the host of the IAB-DU sends the PCI of the IAB-DU cell to the AMF via the NG signaling. The AMF sends the received PCI of the IAB-DU cell to the target host of the IAB-MT via the NG signaling.

[0169] Step 2: The target host of the IAB-MT sends auxiliary information to the host of the IAB-DU. The auxiliary information may include at least one of the following: the PCI allocated for the cell, the one or more PCIs of the one or more serving cells, the one or more PCIs of the one or more neighboring cells, the one or more used PCIs, the one or more unused PCIs. Based on the auxiliary information, the host of the IAB-DU can thus avoid PCI conflicts.

[0170] In the present disclosure, the host may refer to the IAB host.

[0171] Figure 18Schematic diagram of a wireless terminal 180 according to an embodiment of the present disclosure. The wireless terminal 180 may be a user equipment (UE), a mobile phone, a laptop computer, a tablet computer, an e-book, or a portable computer system, and is not limited thereto. The wireless terminal 180 may include a processor 1800 such as a microprocessor or an application specific integrated circuit (ASIC), a storage unit 1810, and a communication unit 1820. The storage unit 1810 may be any data storage device that stores program code 1812 accessed and executed by the processor 1800. Embodiments of the storage unit 1810 include, but are not limited to, a subscriber identity module (SIM), a read only memory (ROM), a flash memory, a random access memory (RAM), a hard disk, and an optical data storage device. The communication unit 1820 may be a transceiver and is used to send and receive signals (e.g., messages or data packets) according to the processing result of the processor 1800. In one embodiment, the communication unit 1820 transmits and receives signals via Figure 18 at least one antenna 1822 shown.

[0172] In one embodiment, the storage unit 1810 and the program code 1812 may be omitted, and the processor 1800 may include a storage unit having the stored program code.

[0173] The processor 1800 may implement any one of the steps in the exemplary embodiments on the wireless terminal 180, for example, by executing the program code 1812.

[0174] The communication unit 1820 may be a transceiver. As an alternative or complementary solution, the communication unit 1820 may combine a transmitting unit and a receiving unit, which are configured to send signals to a wireless network node (e.g., a base station) and receive signals from a wireless network node (e.g., a base station), respectively.

[0175] Figure 19Schematic diagram of a wireless network node 190 according to an embodiment of the present disclosure. The wireless network node 190 may be a satellite, a base station (BS), a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a radio access network (RAN) node, a next-generation RAN (NG-RAN) node, a gNB, an eNB, a gNB centralized unit (gNB-CU), a gNB distributed unit (gNB-DU), a data network, a core network, or a radio network controller (RNC), and is not limited thereto. In addition, the wireless network node 190 may include (execute) at least one network function such as an access and mobility management function (AMF), a session management function (SMF), a user location function (UPF), a policy control function (PCF), an application function (AF), etc. The wireless network node 190 may include a processor 1900 such as a microprocessor or an ASIC, a storage unit 1910, and a communication unit 1920. The storage unit 1910 may be any data storage device that stores program code 1912 accessed and executed by the processor 1900. Examples of the storage unit 1910 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device. The communication unit 1920 may be a transceiver and is used to send and receive signals (e.g., messages or data packets) according to the processing result of the processor 1900. In one example, the communication unit 1920 sends and receives signals via Figure 19 at least one antenna 1922 shown.

[0176] In one embodiment, the storage unit 1910 and the program code 1912 may be omitted. The processor 1900 may include a storage unit with the stored program code.

[0177] The processor 1900 may implement any of the steps described in the exemplary embodiments on the wireless network node 190, for example, by executing the program code 1912.

[0178] The communication unit 1920 may be a transceiver. As an alternative or complementary solution, the communication unit 1920 may combine a transmitting unit and a receiving unit, which are configured to send signals to and receive signals from a wireless terminal (e.g., a user equipment or another wireless network node), respectively.

[0179] Although the various embodiments of the present disclosure have been described above, it should be understood that these embodiments are provided by way of example only and not limitation. Similarly, the various figures may depict example architectures or configurations that are provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present disclosure. However, those skilled in the art should understand that the present disclosure is not limited to the example architectures or configurations shown, but may be implemented using a variety of alternative architectures and configurations. In addition, as would be understood by those of ordinary skill in the art, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Accordingly, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.

[0180] It should also be understood that any reference herein to elements by names such as “first,” “second,” etc. generally does not limit the number or order of those elements. Instead, these names are used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, reference to first and second elements does not mean that only two elements may be used, or that the first element must precede the second element in some manner.

[0181] In addition, those of ordinary skill in the art should understand that any of a variety of different technologies and techniques may be used to represent information and signals. For example, the data, instructions, commands, information, signals, bits, and symbols that may be referred to in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0182] Those skilled in the art should also understand that any of the various illustrative logical blocks, units, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of both), firmware, various forms of programs or design code containing instructions (which may be referred to herein for convenience as “software” or “software units”), or any combination of these technologies.

[0183] To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, units, circuits, and steps have been generally described above in terms of their functionality. Whether this functionality is implemented as hardware, firmware, software, or a combination of these techniques depends on the particular application and the design constraints imposed on the overall system. A person skilled in the art can implement the described functionality in various ways for each particular application, but the decision of such implementation does not result in departing from the scope of the present disclosure. According to various embodiments, a processor, device, component, circuit, structure, machine, unit, etc. can be configured to perform one or more functions described herein. The term "configured to" or "configured for" used herein for a particular operation or function refers to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed, and / or arranged to perform the particular operation or function.

[0184] In addition, those skilled in the art should understand that the various exemplary logic blocks, units, devices, components, and circuits described herein can be implemented within or performed by an integrated circuit (IC), which can include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, or any combination thereof. The logic blocks, units, and circuits can also include antennas and / or transceivers to communicate with various components within a network or device. A general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, the combination of one or more microprocessors and a DSP core, or any other suitable configuration that performs the functions described herein. If implemented in software, these functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium.

[0185] Computer-readable media include computer storage media and communication media, including any medium that can transfer a computer program or code from one place to another. Storage media can be any available media accessible by a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0186] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of these components that are used to perform the relevant functions described herein. Additionally, for purposes of discussion, the various units are described as discrete units; however, as will be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the relevant functions in accordance with embodiments of the present disclosure.

[0187] Furthermore, a memory or other memory and communication components may be employed in embodiments of the present disclosure. It should be understood that, for clarity, the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without detracting from the present disclosure. For example, functions illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, the reference to specific functional units is merely a reference to the appropriate means for providing the recited functionality and is not indicative of a strict logical or physical structure or organization.

[0188] For those skilled in the art, various modifications to the embodiments described in the present disclosure will be apparent, and the general principles defined herein may be applied to other embodiments without departing from the scope of the claims. Accordingly, the present disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A wireless communication method for a target integrated access backhaul (IAB) host, the method comprising: Receiving an IAB transmission migration management request message from an F1 terminal host of an IAB node, wherein the IAB transmission migration management request message includes at least one of the following: a first identifier assigned by the F1 terminal host or a second identifier assigned by a target IAB host of a mobile terminal of the IAB node.

2. The wireless communication method according to claim 1, further comprising: Receiving the first identifier from a source IAB host of the mobile terminal of the IAB node.

3. The wireless communication method according to claim 1 or 2, wherein The first identifier and the second identifier are Xn application protocol identifiers.

4. A wireless communication method for an F1 terminal IAB host of an integrated access backhaul (IAB) node, the method comprising: Sending an IAB transmission migration management request message to a target IAB host of a mobile terminal of the IAB node, wherein the IAB transmission migration management request message includes at least one of the following: a first identifier assigned by the F1 terminal host or a second identifier assigned by the target IAB host.

5. The wireless communication method according to claim 4, further comprising: Receiving the second identifier from a source IAB host of the mobile terminal of the IAB node.

6. The wireless communication method according to claim 4 or 5, wherein, The first identifier and the second identifier are Xn application protocol identifiers.

7. A wireless communication method for a source integrated access backhaul (IAB) host, the method comprising: Sending a conditional handover request message of an IAB node to a target IAB host, Sending a configuration of a conditional handover to the target IAB host to the IAB node, Receiving target information of the conditional handover to the target IAB host from the IAB node, and Sending the target information to an F1 terminal host of the IAB node.

8. The wireless communication method according to claim 7, wherein, The configuration of the conditional handover includes at least one trigger condition configured by the source IAB host for sending the target information.

9. The wireless communication method according to claim 8, wherein, The at least one trigger condition configured by the source IAB host for sending the target information includes at least one of the following: A measurement threshold of a serving cell, A measurement threshold of a special cell A measurement threshold of a primary cell A measurement threshold of a primary and secondary cell, A measurement threshold of an adjacent cell, A measurement threshold of a conditional reconfiguration candidate cell, or A threshold of a measurement offset between a special and a conditional reconfiguration candidate cell.

10. A wireless communication method for an integrated access backhaul (IAB) node, the method comprising: Receiving a configuration of a conditional handover to a target IAB host from a source IAB host, and Sending target information of the conditional handover to the target IAB host to a source IAB host or an F1 terminal host of the IAB node.

11. The wireless communication method according to claim 10, wherein, The configuration of the conditional handover includes at least one trigger condition configured by the source IAB host for sending the target information.

12. The wireless communication method according to claim 11, wherein, The at least one trigger condition configured by the source IAB host for sending the target information includes at least one of the following: A measurement threshold of a serving cell, A measurement threshold of a special cell A measurement threshold of a primary cell Measurement thresholds for the primary and secondary cells Measurement thresholds for neighboring cells Measurement thresholds for conditionally reconfigurable candidate cells, or Thresholds for measurement offsets between special and conditionally reconfigurable candidate cells.

13. A wireless communication method for a first integrated access and backhaul (IAB) host, the method comprising: Sending a request message associated with the IAB node to at least one second IAB host, and Receiving a response message from the at least one second IAB host, the response message including mobility capability information of the at least one second IAB host.

14. The wireless communication method according to claim 13, wherein, The request message includes at least one of the following: Quality of service (QoS) information of services associated with the IAB node, The number of user terminals served by the DU of the IAB node, The speed of the IAB node, The location of the IAB node, A backhaul adaptation protocol (BAP) routing identifier, or A backhaul (BH) radio link control (RLC) channel identifier.

15. The wireless communication method according to claim 13 or 14, wherein, The mobility capability information includes at least one of the following: Information on services that can be added to the second IAB host, The number of user terminals that can be migrated to the second IAB host, A BAP routing identifier, or A BH RLC channel identifier.

16. A wireless communication method for a target integrated access and backhaul (IAB) host, the method comprising: Receiving an F1 establishment request message from a target logical distributed unit (DU) of an IAB node, wherein the F1 establishment request message includes at least one of the following: a mobile IAB indication, an identifier of a source IAB host, an identifier of the IAB node, or a DU identifier of a source logical DU of the IAB node, and Sending an F1 establishment completion message to the source IAB host, the F1 establishment completion message includes at least one of the following: an identifier of the IAB node, the DU identifier of the source logical DU of the IAB node, or an identifier of a mobile terminal of the IAB node.

17. The wireless communication method according to claim 16, wherein, The identifier of the IAB node includes at least one of the following: a backhaul adaptation protocol (BAP) address assigned by the source IAB host, a cell radio network temporary identifier, or an XnAP identifier.

18. The wireless communication method according to claim 16 or 17, wherein, The identifier of the mobile terminal of the IAB node includes at least one of the following: a backhaul adaptation protocol (BAP) address assigned by the source IAB host, a cell radio network temporary identifier, or an XnAP identifier.

19. A wireless communication method for an integrated access and backhaul (IAB) node, the method comprising: Sending an F1 establishment request message to a target IAB host, wherein the F1 establishment request message includes at least one of the following: a mobile IAB indication, an identifier of a source IAB host, an identifier of the IAB node, or a DU identifier of a source logical DU of the IAB node.

20. The wireless communication method according to claim 19, wherein, The identifier of the IAB node includes at least one of the following: a backhaul adaptation protocol (BAP) address assigned by the source IAB host, a cell radio network network temporary identifier, or an XnAP identifier.

21. The wireless communication method according to claim 19 or 20, further comprising: Receive, from the source IAB host, the XnAP identifier allocated by the source IAB host for the IAB node.

22. A wireless communication method for an integrated access backhaul (IAB) node, the method comprising: Send an F1 setup message to a target IAB host, Receive an F1 setup response message from the target IAB host, and Send an F1 setup completion message to the source IAB host.

23. The wireless communication method according to claim 22, wherein, The F1 setup completion message includes at least one of the following: an F1 setup completion indication or an identifier of the target IAB host.

24. A wireless communication method for an integrated access backhaul (IAB) node, the method comprising: Send an Internet Protocol (IP) address request to an IAB host serving the IAB node, and Receive IP address information from the IAB host.

25. The wireless communication method according to claim 24, wherein, The IP address request includes at least one of the following: the number of requested IP addresses, IP address usage, DU migration indication, target logical DU indication, or topology indication.

26. The wireless communication method according to claim 24 or 25, wherein The IP address information includes at least one of the following: at least one allocated IP address, IP address usage, DU migration indication, target logical DU indication, or topology indication.

27. A wireless communication method for an F1 terminating IAB host of an integrated access backhaul (IAB) node, the method comprising: Send an Internet Protocol (IP) address request for the IAB node to a target IAB host.

28. The wireless communication method according to claim 27, wherein, The IP address request includes at least one of the following: the number of requested IP addresses, IP address usage, DU migration indication, target logical DU indication, or topology indication.

29. The wireless communication method according to claim 27 or 28, further comprising: Receive the IP address information of the IAB node from the target IAB host, and Send the IP address information to the IAB node.

30. The wireless communication method according to claim 29, wherein, The IP address information includes at least one of the following: at least one allocated IP address, IP address usage, DU migration indication, target logical DU indication, or topology indication.

31. A wireless communication method for a target integrated access backhaul (IAB) host, the method comprising: Receive an Internet Protocol (IP) address request for the IAB node from the IAB node or the F1 terminating IAB host of the IAB node, and Send the IP address information of the IAB node to the mobile terminal or the F1 terminating IAB host of the IAB node.

32. The wireless communication method according to claim 31, wherein, The IP address request includes at least one of the following: the number of requested IP addresses, IP address usage, DU migration indication, target logical DU indication, or topology indication.

33. The wireless communication method according to claim 31 or 32, wherein, The IP address information includes at least one of the following: at least one allocated IP address, IP address usage, DU migration indication, target logical DU indication, or topology indication.

34. A wireless communication method for a source integrated access backhaul (IAB) host, the method comprising: Send uplink mapping information used at the IAB node to a target IAB host.

35. A wireless communication method for a target integrated access backhaul (IAB) host, the method comprising: Receive uplink mapping information used at an IAB node from a source IAB host, and Send updated uplink mapping information to the IAB node.

36. A wireless communication method for an integrated access backhaul (IAB) host, the method comprising: Send a sharing indication of a source logical distributed unit (DU) and a target logical DU of the IAB node to the IAB node.

37. The wireless communication method according to claim 36, wherein, The IAB host is a source IAB host of a mobile terminal of the IAB node, a target IAB host of the mobile terminal of the IAB node, a source IAB host of a DU of the IAB node, or a target host of the DU of the IAB node.

38. A wireless communication method for an integrated access backhaul (IAB) node, the method comprising: Receive a sharing indication of a source logical distributed unit (DU) and a target logical DU of the IAB node from an IAB host.

39. The wireless communication method according to claim 38, wherein, The IAB host is a source IAB host of a mobile terminal of the IAB node, a target IAB host of the mobile terminal of the IAB node, a source IAB host of a DU of the IAB node, or a target host of the DU of the IAB node.

40. The wireless communication method according to claim 38 or 39, further comprising: Send configuration information associated with the uplink mapping configuration of the source logical DU from the source logical DU to the target logical DU.

41. A wireless communication method for an integrated access backhaul (IAB) node, the method comprising: Send an Internet Protocol (IP) address used by a target logical DU of the IAB node to a source IAB host.

42. A wireless communication method for a source integrated access backhaul (IAB) host, the method comprising: Receive an Internet Protocol (IP) address used by a target logical DU of the IAB node from a source logical distributed unit (DU) of the IAB node, and Send the IP address to a target IAB host.

43. A wireless communication method for a target integrated access backhaul (IAB) host, the method comprising: Send auxiliary information to an IAB host of a mobile terminal of the IAB node, Receive information of an Internet Protocol (IP) header from the IAB host of the mobile terminal of the IAB node.

44. The wireless communication method according to claim 43, wherein, The auxiliary information includes at least one of the following: an Internet Protocol address of the IAB node, quality of service (QoS) information of the service, an identifier of the IAB node assigned by the IAB host of the mobile terminal of the IAB node.

45. The wireless communication method according to claim 43 or 44, wherein, The information of the IP header includes at least one of the following: differentiated services code point (DSCP), flow label, or service information.

46. The wireless communication method according to any one of claims 43 to 45, further comprising: Receive an identifier of the IAB host of the mobile terminal of the IAB node and / or an identifier of the IAB node assigned by the IAB host of the mobile terminal of the IAB node from the target logical DU.

47. A wireless communication method for an integrated access backhaul (IAB) host, the method comprising: Receiving, from a target IAB host connected to a distributed unit (DU) of an IAB node, auxiliary information for configuring a DL mapping, wherein the IAB host is for a mobile terminal of the IAB node; Sending information of an Internet Protocol (IP) header to the target IAB host.

48. The wireless communication method according to claim 47, wherein, The auxiliary information includes at least one of the following: the Internet Protocol address of the IAB node, the quality of service (QoS) information of the service, and the identifier of the IAB node assigned by the IAB host of the mobile terminal of the IAB node.

49. The wireless communication method according to claim 47 or 48, wherein, The information for the IP header includes at least one of the following: differentiated services code point (DSCP), flow label, or traffic information.

50. The wireless communication method according to any one of claims 47 to 49, further comprising: Sending the identifier of the IAB node assigned by the IAB host to the IAB node.

51. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Receive, via the communication unit, an IAB transmission migration management request message from an F1 terminal host of the IAB node, Among them, The IAB transmission migration management request message includes at least one of the following: a first identifier assigned by the F1 terminal host or a second identifier assigned by a target IAB host of a mobile terminal of the IAB node.

52. The wireless device according to claim 51, wherein, The processor is further configured to execute the wireless communication method according to claim 2 or 3.

53. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Send, via the communication unit, an IAB transmission migration management request message to a target IAB host of a mobile terminal of the IAB node, Among them, The IAB transmission migration management request message includes at least one of the following: a first identifier assigned by the F1 terminal host or a second identifier assigned by the target IAB host.

54. The wireless device according to claim 53, wherein, The processor is further configured to execute the wireless communication method according to claim 5 or 6.

55. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Send, via the communication unit, a conditional handover request message of the IAB node to a target IAB host; Send, via the communication unit, a configuration of the conditional handover to the target IAB host to the IAB node; Receive, via the communication unit, target information of the conditional handover to the target IAB host from the IAB node; and Send, via the communication unit, the target information to an F1 terminal host of the IAB node.

56. The wireless device according to claim 55, wherein, The processor is further configured to execute the wireless communication method according to claim 8 or 9.

57. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Receive, via the communication unit, a configuration of a conditional handover from a source IAB host to a target IAB host; and Send the target information of the conditional handover to the target IAB host to the source IAB host or the F1 terminal host of the IAB node via the communication unit.

58. The wireless device according to claim 57, wherein, The processor is further configured to execute the wireless communication method according to claim 11 or 12.

59. A wireless device, the wireless device includes a communication unit and a processor, and the processor is configured to: Send a request message associated with the IAB node to at least one second IAB host via the communication unit, and Receive a response message from the at least one second IAB host via the communication unit, the response message including the mobility capability information of the at least one second IAB host.

60. The wireless device according to claim 59, wherein, The processor is further configured to execute the wireless communication method according to claim 14 or 15.

61. A wireless device, the wireless device includes a communication unit and a processor, and the processor is configured to: Receiving an F1 establishment request message from a target logical distributed unit (DU) of an IAB node via the communication unit, where The F1 establishment request message includes at least one of the following: a mobile IAB indication, an identifier of the source IAB host, an identifier of the IAB node, or a DU identifier of the source logical DU of the IAB node, and Send an F1 establishment completion message to the source IAB host via the communication unit, the F1 establishment completion message including at least one of the following: an identifier of the IAB node, a DU identifier of the source logical DU of the IAB node, or an identifier of a mobile terminal of the IAB node.

62. The wireless device according to claim 61, wherein, The processor is further configured to execute the wireless communication method according to claim 17 or 18.

63. A wireless device, the wireless device includes a communication unit and a processor, and the processor is configured to: Send an F1 establishment request message to the target IAB host via the communication unit, where The F1 establishment request message includes at least one of the following: a mobile IAB indication, an identifier of the source IAB host, an identifier of the IAB node, or a DU identifier of the source logical DU of the IAB node.

64. The wireless device according to claim 63, wherein, The processor is further configured to execute the wireless communication method according to claim 20 or 21.

65. A wireless device, the wireless device includes a communication unit and a processor, and the processor is configured to: Send an F1 establishment message to the target IAB host via the communication unit, Receive an F1 establishment response message from the target IAB host via the communication unit, and Send an F1 establishment completion message to the source IAB host via the communication unit.

66. The wireless device according to claim 65, wherein, The processor is further configured to execute the wireless communication method according to claim 23.

67. A wireless device, the wireless device includes a communication unit and a processor, and the processor is configured to: Send an Internet Protocol (IP) address request to the IAB host serving the IAB node via the communication unit, and Receive IP address information from the IAB host via the communication unit.

68. The wireless device according to claim 67, wherein, The processor is further configured to execute the wireless communication method according to claim 25 or 26.

69. A wireless device, the wireless device includes a communication unit and a processor, and the processor is configured to: Send an Internet Protocol (IP) address request for the IAB node to the target IAB host via the communication unit.

70. The wireless device according to claim 69, wherein, The processor is further configured to execute the wireless communication method according to any one of claims 28 to 30.

71. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Receive, via the communication unit, an Internet Protocol (IP) address request for the IAB node from an IAB node or an F1 terminal IAB host of the IAB node, and Send, via the communication unit, the IP address information of the IAB node to the mobile terminal of the IAB node or the F1 terminal IAB host.

72. The wireless device according to claim 71, wherein, The processor is further configured to execute the wireless communication method according to any one of claims 32 or 33.

73. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Send, via the communication unit, uplink mapping information used at an IAB node to a target IAB host.

74. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Receive, via the communication unit, uplink mapping information used at an IAB node from a source IAB host, and Send, via the communication unit, the updated uplink mapping information to the IAB node.

75. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Send, via the communication unit, uplink mapping information used at an IAB node to a target IAB host.

76. The wireless device according to claim 75, wherein, The processor is further configured to execute the wireless communication method according to claim 37.

77. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Receive, via the communication unit, a sharing indication of a source logical distributed unit (DU) and a target logical DU of the IAB node from an IAB host.

78. The wireless device according to claim 77, wherein, The processor is further configured to execute the wireless communication method according to any one of claims 39 or 40.

79. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Send, via the communication unit, an Internet Protocol (IP) address used by a target logical DU of the IAB node to a source IAB host.

80. The wireless device according to claim 79, wherein, The processor is further configured to execute the wireless communication method according to claim 42.

81. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Send, via the communication unit, auxiliary information to an IAB host of a mobile terminal of an IAB node, Receive, via the communication unit, information of an Internet Protocol (IP) header from the IAB host of the mobile terminal of the IAB node.

82. The wireless device according to claim 81, wherein, The processor is further configured to execute the wireless communication method according to any one of claims 44 to 46.

83. A wireless device, the wireless device comprising a communication unit and a processor, the processor being configured to: Receiving, via the communication unit, auxiliary information for configuring a DL mapping from a target IAB host connected to a distributed unit (DU) of an IAB node, wherein, The IAB host is for the mobile terminal of the IAB node, Send, via the communication unit, information of an Internet Protocol (IP) header to the target IAB host.

84. The wireless device according to claim 84, wherein, The processor is also configured to execute the wireless communication method according to any one of claims 48 to 50.

85. A computer program product comprising computer-readable program media code stored thereon, which, when executed by a processor, causes the processor to implement the wireless communication method according to any one of claims 1 to 50.

Images