Techniques for transmitting information in integrated access and backhaul system

Abstract

Techniques for transmitting information in an integrated access and backhaul system are described. An example wireless communication method includes receiving, by a first network device, migration type information indicating a handover type associated with a handover operation of a mobile network device from the first network device to a second network device, where the first network device receives the migration type information from a third network device.

Description

Technical Field

[0001] The present disclosure relates generally to digital wireless communications. Background Art

[0002] Mobile communication technology is moving the world towards an increasingly interconnected networked society. Compared with existing wireless networks, next-generation systems and wireless communication technologies need to support a wider range of use case features and provide more complex and advanced access requirements and flexibility.

[0003] Long Term Evolution (LTE) is a wireless communication standard for mobile devices and data terminals developed by the Third Generation Partnership Project (3GPP). LTE Advanced (LTE-A) is a wireless communication standard that enhances the LTE standard. The fifth-generation wireless system, called 5G, advances the LTE and LTE-A wireless standards and is committed to supporting higher data rates, a large number of connections, ultra-low latency, high reliability, and other emerging business requirements. Summary of the invention

[0004] Techniques for transmitting information in an integrated access and backhaul system are disclosed.

[0005] A first example wireless communication method includes receiving, by a first network device, migration type information indicating a handover type associated with a handover operation of a mobile network device from the first network device to a second network device, wherein the first network device receives the migration type information from a third network device. In some embodiments, the method further includes sending a first message including the migration type information to the second network device. In some embodiments, the method further includes receiving, from the second network device, a second message including the migration type information; and in response to receiving the second message, the first network device transmits the migration type information to the mobile network device.

[0006] In some embodiments, the handover type indicates an operation sequence associated with a handover operation of a mobile network device and / or a communication device communicating with the mobile network device. In some embodiments, the migration type information includes at least one of the following: partial migration; full migration; user equipment (UE) migration priority, indicating that a handover operation is performed on the communication device before a handover operation of the mobile network device; mobile terminal (MT) migration priority, indicating that a handover operation is first performed on the MT in the mobile network device; distributed unit (DU) migration priority, indicating that a handover operation is first performed on the DU in the mobile network device; DU migration after MT migration, indicating that after a handover operation is performed on the MT in the mobile network device, a handover operation is performed on the DU in the mobile network device; UE migration after MT migration, indicating that after a handover operation is performed on the MT in the mobile network device, a handover operation is performed on the communication device; DU migration before MT migration, indicating that before a handover operation is performed on the MT in the mobile network device, a handover operation is performed on the DU in the mobile network device, and UE migration before MT migration, indicating that a handover operation is performed on the communication device before a handover operation is performed on the MT in the mobile network device.

[0007] In some embodiments, the first network device comprises a first integrated access and backhaul (IAB) donor to which the mobile network device is connected before the handover, wherein the second network device comprises a second IAB donor to which the mobile network device is connected after the handover, and / or wherein the third network device comprises a third IAB donor connected to the mobile network device. In some embodiments, the mobile network device comprises a mobile integrated access and backhaul (IAB) device.

[0008] A second example wireless communication method includes transmitting information related to the communication device by a second logical distributed unit (DU) in the mobile network device during a handover of the communication device from the first network device to the second network device, wherein the second logical DU in the mobile network device transmits information related to the UE to the second network device, wherein the communication device communicates with the mobile network device, wherein the second logical DU is configured to communicate with the second network device, wherein the information related to the communication device includes at least one of the following: a cell radio network temporary identifier (C-RNTI) allocated by the mobile network device to the communication device; a first C-RNTI allocated by the first logical DU in the mobile network device to the communication device; and a second C-RNTI allocated by the second logical DU in the mobile network device to the communication device. In some embodiments, the first network device includes a source base station and the second network device includes a target base station. In some embodiments, the mobile network device includes an integrated access and backhaul (IAB) device.

[0009] A third exemplary wireless communication method includes a first network device receiving an address associated with a mobile network device from a mobile network device; transmitting the address to a second network device. In some embodiments, the address includes a downlink (DL) transport network layer (TNL) address of an F1 service, and the F1 service is transmitted through a donor DU connected to the second network device. In some embodiments, the first network device includes a target base station to which a mobile terminal (MT) in the mobile network device is switched, and the second network device includes a source base station, and the MT in the mobile network device is switched from the source base station. In some embodiments, the mobile network device includes an integrated access and backhaul (IAB) device.

[0010] In another exemplary aspect, the above method is embodied in the form of processor executable code and stored in a non-transitory computer readable storage medium. When the code contained in the computer readable storage medium is executed by a processor, the processor will implement the method described in the present disclosure.

[0011] In another exemplary embodiment, an apparatus configured or operable to perform the above method is disclosed.

[0012] The above and other aspects and implementations thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 An example scenario is shown in which a mobile integrated access and backhaul (IAB) node is included on or in a train.

[0014] Figure 2A-2B An example architecture of an IAB system is shown.

[0015] Figure 3 The parent node and child node relationship of the IAB node is shown.

[0016] Figures 4A-4C An example scenario of inter-donor mobility of a mobile IAB node is shown.

[0017] Figure 5 An exemplary block diagram of a hardware platform that may be part of a network device or a communication device is shown.

[0018] Figure 6 An example of wireless communication including a base station (BS) and a user equipment (UE) based on some implementations of the disclosed technology is shown.

[0019] Figure 7 An exemplary flow chart for receiving migration type information is shown.

[0020] Figure 8An exemplary flow diagram for transmitting information associated with a communication device is shown.

[0021] Fig. 9 An exemplary flow diagram for receiving an address associated with a mobile network device is shown. DETAILED DESCRIPTION

[0022] Integrated Access and Backhaul (IAB) can support wireless backhaul via New Radio (NR), enabling flexible and very dense deployment of NR cells while reducing the need for wired transmission infrastructure. The intra-donor centralized unit (CU) migration process includes scenarios where the source and target parent nodes are served by the same IAB donor CU. In intra-donor migration (also known as handover), the IAB donor CU may not change. And, inter-donor CU migration includes scenarios where the migrated IAB node is static. In inter-donor migration, the IAB donor CU changes, at least because the IAB mobile terminal (MT) may have moved out of the coverage of the source donor CU, or the radio link quality has degraded, such that the IAB MT may need to be served by the target donor CU. In the mobile IAB use case, the IAB node can be installed in a vehicle and can provide wireless (e.g., 5G) coverage / capacity enhancement to the vehicle and / or surrounding UEs, such as Figure 1 As shown, the mobile IAB node is included on or in a train. However, in the mobile IAB use case, current technologies do not have adequate solutions to address inter-donor migration.

[0023] IAB can enable wireless relay in NG-RAN. Relay nodes, which can be called IAB nodes, can support access and backhaul via NR. The terminal node of NR backhaul on the network side can be called IAB donor, which can represent gNB with additional functions to support IAB. Backhaul can be via single hop or multi-hop. The structure of IAB is as follows Figure 2A and 2B shown. Figure 2A An IAB node is shown using a standalone (SA) mode with a Next Generation Core network (NGC). Figure 2B An IAB node using E-UTRA-NR Dual Connectivity (EN-DC) is shown.

[0024] The IAB node can support the gNB-DU function on the IAB donor to terminate the NR access interface to the UE and the next-hop IAB node, and terminate the F1 protocol to the gNB-CU function. The gNB-DU function on the IAB node can also be called IAB-DU. DU is the abbreviation of distributed unit.

[0025] In addition to the gNB-DU functionality, an IAB node can also support a subset of UE functionality called IAB-MT, which includes, for example, physical layer, layer 2, RRC, and NAS functionality to connect to a gNB-DU of another IAB node or an IAB donor, to a gNB-CU on an IAB donor, and to the core network. MT is short for mobile terminal.

[0026] IAB nodes can access the network using SA mode or EN-DC. In EN-DC, IAB nodes can also connect to the master eNB (MeNB) via E-UTRA, and the IAB donor terminates X2-C as a secondary gNB (SgNB).

[0027] Figure 3 The parent node and child node relationship of the IAB node is shown. All IAB nodes connected to the IAB donor via one or more hops can form a directed acyclic graph (DAG) topology, with the IAB donor at its root, such as Figure 3 As shown. In this DAG topology, the neighbor nodes on the IAB-DU interface can be called child nodes, and the neighbor nodes on the IAB-MT interface can be called parent nodes. The direction toward the child nodes can be further called downstream, and the direction toward the parent node can be called upstream. IABdonor performs centralized resource, topology, and routing management for the IAB topology.

[0028] The following describes the terms used in this disclosure and their corresponding example descriptions:

[0029] ●IAB donor can be a gNB that provides network access to the UE via the backhaul and access link network.

[0030] ●The IAB donor CU can be the gNB-CU of the IAB donor, terminating the F1 interface towards the IAB node and the IAB donor DU.

[0031] ●IAB donor DU can be the gNB-DU of the IAB donor, hosting the IAB BAP sublayer,

[0032] Provides wireless backhaul to IAB nodes.

[0033] The IAB-DU can have a gNB-DU function supported by the IAB node to terminate the NR access interface to the UE and the next-hop IAB node and terminate the F1 protocol to the gNB-CU function on the IAB donor.

[0034] • The IAB-MT may have an IAB node functionality that terminates the Uu interface to the parent node using the procedures and behaviors specified for the UE, unless otherwise stated. The IAB-MT functionality may correspond to the IAB-UE functionality.

[0035] ● An IAB node can be a RAN node that supports NR access links to UEs and NR backhaul links to parent and child nodes. An IAB node may not support backhaul via LTE. ● A child node can be a next-hop neighbor node for an IAB-DU and an IAB donor DU; a child node can also be an IAB node.

[0036] ●The parent node can be the next-hop neighbor node of the IAB-MT; the parent node can be an IAB node or an IAB donorDU.

[0037] ● Upstream may describe the direction towards the parent node in the IAB topology.

[0038] • Downstream may describe the direction in the IAB topology towards a child node or UE.

[0039] The example titles of the following sections are used to facilitate understanding of the disclosed subject matter and do not limit the scope of the claimed subject matter in any way. Therefore, one or more features of one example section may be combined with one or more features of another example section. In addition, for the sake of clarity, 5G terminology is used herein, but the technology disclosed herein is not limited to 5G technology and can also be used in wireless systems that implement other protocols.

[0040] I. Example Techniques for Performing Migration of Mobile IAB Nodes

[0041] Figures 4A-4C An example scenario of inter-donor mobility of a mobile IAB node is shown. Figure 4A In the example, the mobile IAB-MT migrates from donor DU1 belonging to donor CU1 to donor DU2 belonging to donor CU2. However, the mobile IAB-DU can maintain its F1 connection with donor CU1, and the UE context remains in donor CU1. Figure 4A As shown, the F1-C / U service between donor CU1 and mobile IAB-DU is transmitted via donor DU2.

[0042] exist Figure 4B In the example, the mobile IAB-MT migrates from donor DU2 belonging to donor CU2 to donor DU3 belonging to donor CU3. However, the mobile IAB-DU can maintain its F1 connection with donor CU1, and the UE context remains in donor CU1. Figure 4B As shown, the F1-C / U service between donor CU1 and mobile IAB-DU is transmitted via donor DU3.

[0043] exist Figure 4C In the example, the mobile IAB-DU migrates from donor CU1 to donor CU3. And the UE switches from donor CU1 to donor CU3. Figure 4C As shown, the F1-C / U service between donor CU3 and mobile IAB-DU is transmitted via donor DU3.

[0044] In the present disclosure, an F1-terminating donor may include a CU having an F1-C connection with a mobile IAB node, for example, a CU serving a mobile IAB-DU.

[0045] I. (a) Implementation Method 1

[0046] There are multiple migration types for inter-donor migration of mobile IAB nodes. However, the current technology does not describe a technology for determining the migration type and notifying the corresponding node of the migration type. The technology described in this part of the present disclosure at least solves these shortcomings of the current technology. In this embodiment, the source donor can be a source CU donor connected to the mobile IAB MT before the handover, and the target donor is a target CU donor to which the mobile IAB MT is connected after the handover is performed.

[0047] Step 1: Optionally, during the inter-donor migration process of the mobile IAB node (including partial migration or full migration), if the source donor of the IAB-MT and the F1 termination donor are different donors, the source donor sends MT handover information to the F1 termination donor, for example, after receiving a measurement report from the IAB-MT, or after receiving a handover request confirmation message from the target donor of the IAB-MT. The MT handover information includes at least one of the following: MT handover indication, target cell ID, candidate cell ID or candidate cell ID, MT ID assigned by the source donor, MT ID assigned by the target donor (for example, XnAP ID or BAP address).

[0048] Alternatively, the target donor of the IAB-MT sends the MT handover information to the F1 terminating donor, for example, after receiving the handover request message from the source donor.

[0049] Alternatively, the IAB node sends the MT handover information to the F1 terminating donor, for example, after receiving the RRCreconfiguration message from the source donor.

[0050] Step 2: Optionally, if the source donor and the F1 terminating donor of the IAB-MT are different donors, the F1 terminating donor may determine (e.g., based on whether there is an Xn interface or IP connection between the F1 terminating donor and the target donor) the migration type. The F1 terminating donor may then send migration type information to the source donor or the target donor. The F1 terminating donor may be connected to the mobile IAB DU. The migration type information may indicate whether a UE handover and / or a handover sequence involving a UE, a mobile IAB node, a DU in a mobile IAB node, and / or an MT in a mobile IAB node is to be performed. The migration type information includes at least one of the following: partial migration; full migration; UE migration priority; MT migration priority; DU migration priority; DU migration is performed after MT migration; UE migration is performed after MT migration; DU migration is performed before MT migration; UE migration is performed before MT migration. Indications associated with "UE migration priority" or "MT migration priority" or "DU migration priority" may indicate that the handover is first performed by the UE or MT or DU, respectively. Indications associated with “Perform DU migration after MT migration”, “Perform UE migration after MT migration”, “Perform DU migration before MT migration”, and “Perform UE migration before MT migration” respectively indicate that the switch is first performed by the MT and then by the DU, the switch is first performed by the MT and then by the UE, the switch is first performed by the DU and then by the MT, and the switch is first performed by the UE and then by the MT.

[0051] In some embodiments, if the F1 terminating donor determines that there is an Xn and F1 connection between the F1 terminating donor and the target donor, the F1 terminating donor determines that a partial migration can be performed, and the F1 terminating donor can indicate the partial migration in the migration type information. In an example implementation, the partial migration can include performing a migration of the IAB-MT to a parent node under a different IABdonor CU, while the donor CU serving the co-located IAB-DU and the served UE remain unchanged. In some embodiments, if the F1 terminating donor determines that there is no Xn interface between the F1 terminating donor and the target donor, the F1 terminating donor determines that a full migration needs to be performed instead of a partial migration, and the F1 terminating donor can indicate the full migration in the migration type information. In an example implementation, the full migration can include migrating the IAB-MT, the co-located IAB-DU, and the served UE (e.g., RRC and F1 connections) to the target IAB donor CU. In some embodiments, if the F1 terminating donor determines that there is no IP connection between the F1 terminating donor and the target donor, the F1 terminating donor determines that DU migration needs to be performed before MT migration, and the F1 terminating donor can indicate "perform DU migration after MT migration" in the migration type information.

[0052] Step 3: The source donor of IAB-MT sends migration type information to the target donor of IAB-MT, for example, after receiving the migration type information from the F1 terminating donor. The source donor may send the migration type information to the target donor via an XnAP message (eg, a handover request message).

[0053] Step 4: The target donor includes the migration type information in the RRCreconfiguration message and includes the RRCreconfiguration message in the XnAP message. Then the target donor sends the XnAP message including the migration type information to the source donor.

[0054] Step 5: The source donor sends an RRCreconfiguration message containing migration type information to the IAB-MT.

[0055] I. (b) Implementation Method 2

[0056] Technical issue: In a normal UE handover process, UE context establishment and release procedures are used at the target and source DUs, respectively, to establish the UE context at the target DU and release the UE context at the source DU. In a mobile IAB scenario, the source DU and target DU of the UE handover process are two logical DUs co-located in the same mobile IAB node. Therefore, it is not effective to use the UE context establishment and release procedures during the UE handover process. A potential solution is that the UE context can be shared between the two logical DUs in the mobile IAB node. In this way, UE context modification can be used to update the UE context at the mobile IAB node, instead of the UE context establishment / release procedures at the source / target logical DUs, respectively. The technical issue is how to transmit the UE information used in the target logical DU (e.g., a logical DU having an F1 connection with a target donor) to the target donor if the UE context establishment procedure is not used during the UE handover process.

[0057] In the example scenario given below, the mobile IAB node switches from a source DU to a target DU, wherein before the switch, the UE is connected to the source logical DU in the mobile IAB node, and after the switch, the UE is connected to the target logical DU in the mobile IAB node.

[0058] Example scenario: For example, UE information is sent from the target logical DU in the mobile IAB node to the target donor (e.g., target donor CU) via an F1AP UE context modification response or an IAB UP configuration update response message. The UE information includes at least one of the following: a cell radio network temporary identifier (C-RNTI) allocated by the mobile IAB node to the UE, an old C-RNTI allocated by the source logical DU to the UE, and a new C-RNTI allocated by the target logical DU to the UE. The C-RNTI allocated by the mobile IAB node may not change and may be used to identify the UE in the source logical DU and the target logical DU. The old C-RNTI is used to identify the UE in the source logical DU, and the new C-RNTI is used to identify the UE through the target logical DU.

[0059] I. (c) Implementation Method 3

[0060] Technical problem: If DU migration is performed in the IAB node before MT migration, the target logical DU in the IAB node needs to establish an F1 connection with the target donor before MT migration. Therefore, the F1 traffic between the target donor and the mobile IAB node needs to be transmitted via the source path (e.g., through the source parent DU and the source donor DU). The problem is how to transmit the F1 traffic between the target CU and the mobile IAB node via the source path.

[0061] In the example scenario given below, migration of a mobile IAB node from a source donor CU to a target donor CU is facilitated, wherein the migration of DUs in the IAB node is performed before the migration of MTs in the same IAB node.

[0062] Example scenario:

[0063] Step 1: The F1 terminal donor or source donor of the IAB-MT sends the DSCP / flow label for the downlink F1 service to the target donor of the IAB-MT. The target donor can set the DSCP / flow label of the F1 service according to the DSCP / flow label information received from the F1 terminal donor or source donor.

[0064] Step 2: The target donor obtains the new DL TNL address used by the mobile IAB node via F1AP, for example, F1 Setup, DU Configuration Update or IAB UP Configuration Update Response message.

[0065] Step 3: The target donor sends the new DL TNL address of the F1 service to the source donor via an XnAP message to the source donor. The source donor can use the new DL TNL address to perform DL mapping configuration at the source donor DU.

[0066] Alternatively, the target donor sends the new DL TNL address of the F1 service to the F1 terminating donor via an XnAP message. Then the F1 terminating donor sends the new DL TNL address to the source donor via an XnAP message.

[0067] Figure 5 An exemplary block diagram of a hardware platform 500 is shown, which may be part of a network device (e.g., a base station) or a communication device (e.g., a user equipment (UE)). The hardware platform 500 includes at least one processor 510 and a memory 505 having instructions stored thereon. The instructions executed by the processor 510 configure the hardware platform 500 to perform Figures 1 to 4C and Figures 6 to 9 The operations described in the embodiments described in the present disclosure and in the various embodiments described in the present disclosure. Transmitter 515 transmits or sends information or data to another device. For example, a network device transmitter can send a message to a user device. Receiver 520 receives information or data transmitted or sent by another device. For example, a user device can receive a message from a network device.

[0068] The implementation described above will be applicable to wireless communications. Figure 6An example of a wireless communication system (e.g., a 5G or NR cellular network) including a base station 620 and one or more user equipments (UEs) 611, 612, and 613 is shown. In some embodiments, the UE uses a communication link to the network (sometimes referred to as an uplink direction, as shown by dashed arrows 631, 632, 633) to access the BS (e.g., the network), which enables subsequent communication from the BS to the UE (e.g., shown in the direction from the network to the UE, sometimes referred to as a downlink direction, as shown by arrows 641, 642, 643). In some embodiments, the BS sends information to the UE (sometimes referred to as a downlink direction, as shown by arrows 641, 642, 643), which enables subsequent communication from the UE to the BS (e.g., shown in the direction from the UE to the BS, sometimes referred to as an uplink direction, as shown by dashed arrows 631, 632, 633). The UE can be, for example, a smartphone, a tablet, a mobile computer, a machine-to-machine (M2M) device, an Internet of Things (IoT) device, etc.

[0069] Figure 7 An exemplary flow chart for receiving migration type information is shown. Operation 702 includes a first network device receiving migration type information indicating a handover type associated with a handover operation of a mobile network device from the first network device to a second network device, wherein the first network device receives the migration type information from a third network device. In some embodiments, the method further includes sending a first message including the migration type information to the second network device. In some embodiments, the method further includes receiving a second message including the migration type information from the second network device; in response to receiving the second message, the first network device transmits the migration type information to the mobile network device.

[0070] In some embodiments, the handover type indicates an operation sequence associated with a handover operation of a mobile network device and / or a communication device communicating with the mobile network device. In some embodiments, the migration type information includes at least one of the following: partial migration; full migration; user equipment (UE) migration priority, indicating that a handover operation is performed on the communication device before a handover operation of the mobile network device; mobile terminal (MT) migration priority, indicating that a handover operation is first performed on the MT in the mobile network device; distributed unit (DU) migration priority, indicating that a handover operation is first performed on the DU in the mobile network device; DU migration after MT migration, indicating that after a handover operation is performed on the MT in the mobile network device, a handover operation is performed on the DU in the mobile network device; UE migration after MT migration, indicating that after a handover operation is performed on the MT in the mobile network device, a handover operation is performed on the communication device; DU migration before MT migration, indicating that before a handover operation is performed on the MT in the mobile network device, a handover operation is performed on the DU in the mobile network device, and UE migration before MT migration, indicating that a handover operation is performed on the communication device before a handover operation is performed on the MT in the mobile network device.

[0071] In some embodiments, the first network device comprises a first integrated access and backhaul (IAB) donor to which the mobile network device is connected before the handover, wherein the second network device comprises a second IAB donor to which the mobile network device is connected after the handover, and / or wherein the third network device comprises a third IAB donor connected to the mobile network device. In some embodiments, the mobile network device comprises a mobile integrated access and backhaul (IAB) device.

[0072] Figure 8 An exemplary flow chart for sending information related to a communication device is shown. Operation 802 includes a second logical distributed unit (DU) in a mobile network device transmitting information related to a communication device during a handover of the communication device from a first network device to a second network device, wherein the second logical DU in the mobile network device transmits information related to a UE to the second network device, wherein the communication device communicates with the mobile network device, wherein the second logical DU is configured to communicate with the second network device, wherein the information related to the communication device includes at least one of the following: a cell radio network temporary identifier (C-RNTI) allocated by the mobile network device to the communication device; a first C-RNTI allocated by the first logical DU in the mobile network device to the communication device; and a second C-RNTI allocated by the second logical DU in the mobile network device to the communication device. In some embodiments, the first network device includes a source base station and the second network device includes a target base station. In some embodiments, the mobile network device includes an integrated access and backhaul (IAB) device.

[0073] Fig. 9 An exemplary flow chart for receiving an address associated with a mobile network device is shown. Operation 902 includes a first network device receiving an address associated with a mobile network device from a mobile network device. Operation 904 includes transmitting the address to a second network device. In some embodiments, the address includes a downlink (DL) transport network layer (TNL) address of an F1 service, and the F1 service is transmitted through a donor DU connected to the second network device. In some embodiments, the first network device includes a target base station to which a mobile terminal (MT) in the mobile network device is switched, and the second network device includes a source base station, and the MT in the mobile network device is switched from the source base station. In some embodiments, the mobile network device includes an integrated access and backhaul (IAB) device.

[0074] In this document, the term "exemplary" is used to mean "an example of," and does not imply an ideal or preferred embodiment unless otherwise stated.

[0075] Some embodiments described herein are described in the general context of methods or processes, which can be implemented in one embodiment by a computer program product contained in a computer-readable medium, including computer executable instructions executed by a computer in a network environment, such as program code. Computer-readable media may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), compact disk (CD), digital versatile disk (DVD), etc. Therefore, computer-readable media may include non-transitory storage media. Typically, program modules may include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. Computer or processor executable instructions, related data structures, and program modules represent examples of program codes for executing the method steps disclosed herein. A specific sequence of such executable instructions or related data structures represents an example of corresponding actions for implementing the functions described in such steps or processes.

[0076] Some disclosed embodiments can be implemented as devices or modules using hardware circuits, software or a combination thereof. For example, a hardware circuit implementation may include discrete analog and / or digital components that are, for example, integrated as a part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application specific integrated circuits (ASICs) and / or field programmable gate arrays (FPGAs) devices. Some implementations may additionally or alternatively include a digital signal processor (DSP), which is a dedicated microprocessor with an optimized architecture for the operational requirements of digital signal processing associated with the functions disclosed in the present application. Similarly, various components or subcomponents within each module may be implemented with software, hardware or firmware. The connection between the modules and / or the components within the modules may be provided using any connection method and medium known in the art, including but not limited to communicating via the Internet, wired or wireless networks using appropriate protocols.

[0077] Although this document contains many details, these details should not be interpreted as limitations on the scope of the claimed invention or the scope that may be claimed, but rather as descriptions of specific features of specific embodiments. Certain features described in this document in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although the features may be described above as acting in certain combinations, or even initially claimed, in some cases, one or more features in the claimed combination may be removed from the combination, and the claimed combination may be for a sub-combination or a variant of a sub-combination. Similarly, although the drawings describe operations in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in sequence, or that all the operations shown be performed to achieve the desired result.

[0078] Only a few implementations and examples are described, and other implementations, enhancements, and variations may be made based on what is described and illustrated in this disclosure.

Claims

1. A wireless communication method, comprising: A first network device receives migration type information indicating a handover type associated with a handover operation of a mobile network device from the first network device to a second network device, The first network device receives the migration type information from the third network device.

2. The method according to claim 1, further comprising: A first message including the migration type information is sent to the second network device.

3. The method according to claim 1, further comprising: receiving a second message including the migration type information from the second network device; In response to receiving the second message, the first network device transmits the migration type information to the mobile network device.

4. The method according to claim 1, wherein: The handover type indicates an operation sequence associated with the handover operation of the mobile network device and / or a communication device communicating with the mobile network device.

5. The method according to any one of claims 1 to 4, wherein: The migration type information includes at least one of the following: Partial migration, Full migration, User equipment UE migration priority, indicating that the switching operation is performed on the communication device before the switching operation of the mobile network device, The mobile terminal MT migration priority indicates that the switching operation is first performed on the MT in the mobile network device, Distributed unit DU migration priority indicates that the switching operation is first performed on the DU in the mobile network device, DU migration is performed after MT migration, indicating that after the switching operation is performed on the MT in the mobile network device, the switching operation is performed on the DU in the mobile network device, UE migration is performed after MT migration, indicating that the switching operation is performed on the communication device after the switching operation is performed on the MT in the mobile network device, and DU migration is performed before MT migration, indicating that the switching operation is performed on the DU in the mobile network device before the switching operation is performed on the MT in the mobile network device, The UE migration is performed before the MT migration, indicating that the handover operation is performed on the communication device before the handover operation is performed on the MT in the mobile network device.

6. The method according to any one of claims 1 to 5, in, The first network device comprises a first integrated access and backhaul IAB host to which the mobile network device is connected before the handover, wherein the second network device comprises a second IAB host to which the mobile network device is connected after the switching, or The third network device includes a third IAB host connected to the mobile network device.

7. The method according to any one of claims 1 to 6, wherein: The mobile network equipment includes mobile integrated access and backhaul IAB equipment.

8. A wireless communication method, comprising: During the switching of the communication device from the first network device to the second network device, the second logical distributed unit DU in the mobile network device transmits information related to the communication device, The second logical DU in the mobile network device transmits the information related to the UE to the second network device, wherein the communication device communicates with the mobile network device, The second logical DU is configured to communicate with the second network device, The information related to the communication device includes at least one of the following: a cell radio network temporary identifier C-RNTI allocated by the mobile network device to the communication device, The first logical DU in the mobile network device is a first C-RNTI allocated to the communication device, The second logical DU in the mobile network device is a second C-RNTI allocated to the communication device.

9. The method according to claim 8, wherein: The first network device includes a source base station, and the second network device includes a target base station.

10. The method according to any one of claims 8 to 9, wherein: The mobile network equipment includes an integrated access and backhaul IAB device.

11. A wireless communication method, comprising: The first network device receives, from a mobile network device, an address associated with the mobile network device; The address is transmitted to the second network device.

12. The method according to claim 11, wherein: The address comprises a downlink DL transport network layer TNL address for F1 traffic passing through a host DU connected to the second network device.

13. The method according to claim 11, in, The first network device includes a target base station to which the mobile terminal MT in the mobile network device switches. The second network device includes a source base station, and the MT in the mobile network device is switched from the source base station.

14. The method according to any one of claims 11 to 13, wherein: The mobile network equipment includes an integrated access and backhaul IAB device.

15. An apparatus for wireless communication, comprising a processor configured to implement the method according to one or more of claims 1 to 14.

16. A non-transitory computer-readable program storage medium having codes stored thereon, which, when executed by a processor, cause the processor to implement the method according to one or more of claims 1 to 14.

Images