Method and device for migrating mobile IAB node and storage medium

Abstract

The invention provides a method and device for migrating a mobile IAB node and a storage medium. The method comprises the steps of obtaining a first IAB identifier allocated to the mobile IAB node by a donor-CU of an IAB-DU of the mobile IAB node; and sending the first IAB identifier and the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the terminal IAB-MT of the mobile IAB node. According to the method and device for migrating the mobile IAB node and the storage medium provided by the invention, the donor-CU of the IAB-DU obtains the related information of the donor-CU of the IAB-MT, so that the donor-CU of the IAB-DU can initiate an IAB TMM process to the donor-CU of the IAB-MT to request the donor-CU of the IAB-MT to configure path resources required by transmission services.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device and storage medium for migrating an Integrated Access and Backhaul (IAB) node. Background Art

[0002] In the related art, discussions on mobile IAB nodes began to be conducted to increase support for mobility scenarios, for example, IAB nodes are installed on vehicles moving at high or low speeds to serve users on the vehicle. First, it is determined that continuous IAB-MT switching scenarios need to be supported, and the switching of IAB-MT between two non-F1 terminated donor-CUs is supported without changing the anchor point centralized unit (donor-CU) of the distribution unit (IAB-DU), which is also called the IAB-MT migration process. However, when the donor-CU of the IAB-DU is not changed (that is, the F1 terminated donor-CU is not changed), the F1 service always needs to be transferred from the topological domain of the IAB-MT to the donor-CU of the IAB-DU. If the activity range of the mobile IAB node is large, the donor-CU of the IAB-MT is far away from the donor-CU of the IAB-DU, which will cause service transmission delays. Therefore, it is determined that support for changing the F1 terminated donor-CU is required, also known as IAB-DU migration. In addition, considering that the functions of the donor-CU of the IAB-MT and the donor-CU of the IAB-DU are different, it also supports the situation that the IAB-MT and the IAB-DU are connected to different CUs when the mobile IAB node accesses the network.

[0003] However, in the three scenarios where the donor-CU of the IAB-DU and the donor-CU of the IAB-MT are not the same CU when the mobile IAB node accesses the network, the IAB-MT of the mobile IAB node migrates, and the IAB-DU of the mobile IAB node migrates, there is a technical problem that the donor-CU of the IAB-DU cannot initiate the IAB TMM process to the donor-CU of the IAB-MT to request the donor-CU of the IAB-MT to configure the path resources required for the transmission service. Summary of the invention

[0004] The embodiments of the present application provide a method, device and storage medium for migrating a mobile IAB node, so as to solve the technical problem in the related art that the donor-CU of the IAB-DU cannot initiate an IAB TMM process to the donor-CU of the IAB-MT to request the donor-CU of the IAB-MT to configure the path resources required for the transmission service.

[0005] In a first aspect, an embodiment of the present application provides a method for migrating a mobile IAB node, which is applied to a mobile access backhaul integrated IAB node, including:

[0006] Acquire a first IAB identifier allocated to the mobile IAB node by an anchor point centralized unit donor-CU of a distribution unit IAB-DU of the mobile IAB node;

[0007] Sending the first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the terminal IAB-MT of the mobile IAB node;

[0008] The first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are used by the donor-CU of the IAB-MT of the mobile IAB node to send the first IAB identifier and the second IAB identifier allocated to the IAB node by the donor-CU of the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0009] In some embodiments, obtaining a first IAB identifier allocated to the mobile IAB node by a donor-CU of an IAB-DU of the mobile IAB node includes:

[0010] The first IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-DU of the mobile IAB node is obtained through an F1 interface F1AP message.

[0011] In some embodiments, sending the first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the IAB-MT of the mobile IAB node includes:

[0012] The first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are sent to the donor-CU of the IAB-MT of the mobile IAB node through an RRC message.

[0013] In some embodiments, the donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

[0014] In some embodiments, the donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

[0015] In some embodiments, the first IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by a donor-CU of an IAB-DU of the mobile IAB node to an IAB-MT of the mobile IAB node.

[0016] In a second aspect, an embodiment of the present application provides a method for migrating a mobile IAB node, which is applied to a donor-CU of an IAB-MT of the mobile IAB node, including:

[0017] Acquire a first IAB identifier allocated to the mobile IAB node by a donor-CU of the IAB-DU of the mobile IAB node and a gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node sent by the mobile IAB node;

[0018] allocating a second IAB identifier to the mobile IAB node;

[0019] The first IAB identifier and the second IAB identifier are sent to the donor-CU of the IAB-DU of the mobile IAB node; the first IAB identifier and the second IAB identifier are used by the donor-CU of the IAB-DU of the mobile IAB node to initiate an IAB TMM process to the donor-CU of the IAB-MT of the mobile IAB node.

[0020] In some embodiments, the method further comprises:

[0021] Sending a new air interface cell global identity NCGI of a serving cell accessed by the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0022] In some embodiments, the method further comprises:

[0023] The tracking area identifier TAI of the serving cell accessed by the IAB-MT of the mobile IAB node is sent to the donor-CU of the IAB-DU of the mobile IAB node.

[0024] In some embodiments, the method further comprises:

[0025] Sending authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node.

[0026] In some embodiments, the donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

[0027] In some embodiments, the donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

[0028] In some embodiments, the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network are carried through an Xn interface application protocol XnAP message;

[0029] Sending the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node includes:

[0030] Taking the gNB-ID of the donor-CU of the IAB-MT of the mobile IAB node as the source radio access network RAN ​​node ID, and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node as the target RAN node ID, the XnAP message is encapsulated in a first NG interface application protocol NGAP message and sent to the access and mobility management function AMF network element, and then the AMF network element forwards the XnAP message to the donor-CU of the IAB-DU of the mobile IAB node through a second NGAP message.

[0031] In some embodiments, the second IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by a donor-CU of the IAB-MT of the mobile IAB node to the IAB-MT of the mobile IAB node.

[0032] In a third aspect, an embodiment of the present application provides a method for migrating a mobile IAB node, which is applied to a donor-CU of an IAB-DU of the mobile IAB node, including:

[0033] sending, to the mobile IAB node, a first IAB identifier allocated to the mobile IAB node;

[0034] receiving a first IAB identifier sent by a donor-CU of an IAB-MT of the mobile IAB node and a second IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-MT of the mobile IAB node;

[0035] An Xn IAB TMM process is initiated based on the first IAB identifier and the second IAB identifier to request the donor-CU of the IAB-MT of the mobile IAB node to configure path resources required for transmission services for the mobile IAB node.

[0036] In some embodiments, the method further comprises:

[0037] Receive the NCGI of the serving cell to which the IAB-MT of the mobile IAB node accesses, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0038] In some embodiments, the method further comprises:

[0039] Receive the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0040] In some embodiments, the method further comprises:

[0041] Receive the authentication status information of the mobile IAB node from the core network, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0042] In some embodiments, the donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

[0043] In some embodiments, the donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

[0044] In a fourth aspect, an embodiment of the present application provides a mobile IAB node, including a memory, a transceiver, and a processor;

[0045] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0046] Acquire a first IAB identifier allocated to the mobile IAB node by an anchor point centralized unit donor-CU of a distribution unit IAB-DU of the mobile IAB node;

[0047] Sending the first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the terminal IAB-MT of the mobile IAB node;

[0048] The first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are used by the donor-CU of the IAB-MT of the mobile IAB node to send the first IAB identifier and the second IAB identifier allocated to the IAB node by the donor-CU of the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0049] In some embodiments, obtaining a first IAB identifier allocated to the mobile IAB node by a donor-CU of an IAB-DU of the mobile IAB node includes:

[0050] The first IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-DU of the mobile IAB node is obtained through an F1 interface F1AP message.

[0051] In some embodiments, sending the first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the IAB-MT of the mobile IAB node includes:

[0052] The first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are sent to the donor-CU of the IAB-MT of the mobile IAB node through an RRC message.

[0053] In some embodiments, the donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

[0054] In some embodiments, the donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

[0055] In some embodiments, the first IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by a donor-CU of an IAB-DU of the mobile IAB node to an IAB-MT of the mobile IAB node.

[0056] In a fifth aspect, an embodiment of the present application provides a donor-CU of an IAB-MT of a mobile IAB node, including a memory, a transceiver, and a processor;

[0057] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0058] Acquire a first IAB identifier allocated to the mobile IAB node by a donor-CU of the IAB-DU of the mobile IAB node and a gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node sent by the mobile IAB node;

[0059] allocating a second IAB identifier to the mobile IAB node;

[0060] The first IAB identifier and the second IAB identifier are sent to the donor-CU of the IAB-DU of the mobile IAB node; the first IAB identifier and the second IAB identifier are used by the donor-CU of the IAB-DU of the mobile IAB node to initiate an IAB TMM process to the donor-CU of the IAB-MT of the mobile IAB node.

[0061] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0062] Sending a new air interface cell global identity NCGI of a serving cell accessed by the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0063] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0064] The tracking area identifier TAI of the serving cell accessed by the IAB-MT of the mobile IAB node is sent to the donor-CU of the IAB-DU of the mobile IAB node.

[0065] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0066] Sending authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node.

[0067] In some embodiments, the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network are carried through an Xn interface application protocol XnAP message;

[0068] Sending the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node includes:

[0069] Taking the gNB-ID of the donor-CU of the IAB-MT of the mobile IAB node as the source radio access network RAN ​​node ID, and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node as the target RAN node ID, the XnAP message is encapsulated in a first NG interface application protocol NGAP message and sent to the access and mobility management function AMF network element, and then the AMF network element forwards the XnAP message to the donor-CU of the IAB-DU of the mobile IAB node through a second NGAP message.

[0070] In some embodiments, the second IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by a donor-CU of the IAB-MT of the mobile IAB node to the IAB-MT of the mobile IAB node.

[0071] In a sixth aspect, an embodiment of the present application provides a donor-CU of an IAB-DU of a mobile IAB node, including a memory, a transceiver, and a processor;

[0072] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0073] sending, to the mobile IAB node, a first IAB identifier allocated to the mobile IAB node;

[0074] receiving a first IAB identifier sent by a donor-CU of an IAB-MT of the mobile IAB node and a second IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-MT of the mobile IAB node;

[0075] An Xn IAB TMM process is initiated based on the first IAB identifier and the second IAB identifier to request the donor-CU of the IAB-MT of the mobile IAB node to configure path resources required for transmission services for the mobile IAB node.

[0076] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0077] Receive the NCGI of the serving cell to which the IAB-MT of the mobile IAB node accesses, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0078] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0079] Receive the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0080] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0081] Receive the authentication status information of the mobile IAB node from the core network, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0082] In a seventh aspect, an embodiment of the present application provides a device for migrating a mobile IAB node, including:

[0083] A first acquisition module, configured to acquire a first IAB identifier allocated to the mobile IAB node by a donor-CU of a distribution unit IAB-DU of the mobile IAB node;

[0084] A first sending module, configured to send the first IAB identifier and a unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the terminal IAB-MT of the mobile IAB node;

[0085] The first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are used by the donor-CU of the IAB-MT of the mobile IAB node to send the first IAB identifier and the second IAB identifier allocated to the IAB node by the donor-CU of the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0086] In an eighth aspect, an embodiment of the present application provides a device for migrating a mobile IAB node, including:

[0087] A second acquisition module is used to acquire a first IAB identifier allocated to the mobile IAB node by a donor-CU of the IAB-DU of the mobile IAB node and a gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node sent by the mobile IAB node;

[0088] A second sending module, configured to allocate a second IAB identifier to the mobile IAB node;

[0089] The third sending module is used to send the first IAB identifier and the second IAB identifier to the donor-CU of the IAB-DU of the mobile IAB node; the first IAB identifier and the second IAB identifier are used by the donor-CU of the IAB-DU of the mobile IAB node to initiate an IAB TMM process to the donor-CU of the IAB-MT of the mobile IAB node.

[0090] In a ninth aspect, an embodiment of the present application provides a device for migrating a mobile IAB node, including:

[0091] A fourth sending module, configured to send a first IAB identifier allocated to the mobile IAB node to the mobile IAB node;

[0092] A first receiving module is configured to receive a first IAB identifier sent by a donor-CU of an IAB-MT of the mobile IAB node and a second IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-MT of the mobile IAB node;

[0093] The initiating module is configured to initiate an Xn IAB TMM process based on the first IAB identifier and the second IAB identifier to request the donor-CU of the IAB-MT of the mobile IAB node to configure path resources required for transmission services for the mobile IAB node.

[0094] In the tenth aspect, an embodiment of the present application further provides a non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a computer program, wherein the computer program is used to enable a processor to execute the method for migrating a mobile IAB node as described in the first aspect or the second aspect.

[0095] In the eleventh aspect, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, wherein the computer program is used to enable a processor to execute the method for migrating a mobile IAB node as described in the first aspect or the second aspect.

[0096] In a twelfth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program is used to enable a computer to execute the method for migrating a mobile IAB node as described in the first aspect or the second aspect.

[0097] In a thirteenth aspect, an embodiment of the present application further provides a communication device, wherein a computer program is stored in the communication device, and the computer program is used to enable the communication device to execute the method for migrating a mobile IAB node as described in the first aspect or the second aspect.

[0098] In a fourteenth aspect, an embodiment of the present application further provides a chip product, wherein a computer program is stored in the chip product, and the computer program is used to enable the chip product to execute the method for migrating a mobile IAB node as described in the first aspect or the second aspect.

[0099] The method, device and storage medium for migrating a mobile IAB node provided in the present application enable the donor-CU of the IAB-DU to obtain relevant information of the donor-CU of the IAB-MT, so that the donor-CU of the IAB-DU can initiate an IAB TMM process to the donor-CU of the IAB-MT to request the donor-CU of the IAB-MT to configure the path resources required for the transmission service, obtain the location information of the mobile IAB node and obtain the authentication information of the IAB node. BRIEF DESCRIPTION OF THE DRAWINGS

[0100] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the following is a brief introduction to the drawings required for use in the embodiments or the related technical descriptions. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0101] Figure 1 It is a schematic diagram of the IAB system;

[0102] Figure 2 This is a diagram of the IAB network architecture;

[0103] Figure 3 It is a diagram of Parent IAB-node and Child IAB-node;

[0104] Figure 4 This is a schematic diagram of the F1-U protocol stack of the IAB system;

[0105] Figure 5 This is a schematic diagram of the F1-C protocol stack of the IAB system;

[0106] Figure 6 It is a schematic diagram of the routing function of the IAB system;

[0107] Figure 7 It is a network topology diagram applicable to the IAB anchor CU;

[0108] Figure 8It is a network topology diagram applicable to the IAB anchor CU;

[0109] Fig. 9 is a schematic diagram of IAB-MT migration;

[0110] Fig.10 It is a schematic diagram of IAB-DU migration;

[0111] Fig.11 is a schematic diagram of the initial access of a mobile IAB node to the network;

[0112] Fig.12 This is one of the flowcharts of the method for migrating a mobile IAB node provided in an embodiment of the present application;

[0113] Fig.13 This is one of the flowcharts of the donor-CU of the IAB-DU acquiring the relevant information of the donor-CU of the IAB-MT provided in the embodiment of the present application;

[0114] Fig.14 This is the second flow chart of the donor-CU of the IAB-DU acquiring the relevant information of the donor-CU of the IAB-MT provided in the embodiment of the present application;

[0115] Fig.15 This is the third flow chart of the donor-CU of the IAB-DU acquiring the relevant information of the donor-CU of the IAB-MT provided in the embodiment of the present application;

[0116] Fig.16 It is a schematic diagram of NGAP forwarding class 1XnAP message provided in an embodiment of the present application;

[0117] Fig.17 It is one of the schematic diagrams of the NGAP message provided in the embodiment of the present application;

[0118] Fig.18 It is a schematic diagram of NGAP forwarding class 2XnAP message provided in an embodiment of the present application;

[0119] Fig.19 This is the second schematic diagram of the NGAP message provided in the embodiment of the present application;

[0120] Fig. 20 This is a second flow chart of the method for migrating a mobile IAB node provided in an embodiment of the present application;

[0121] Fig.21 This is a third flow chart of the method for migrating a mobile IAB node provided in an embodiment of the present application;

[0122] Fig. 22It is a structural diagram of a mobile IAB node provided in an embodiment of the present application;

[0123] Fig.23 It is a structural diagram of a donor-CU of an IAB-MT of a mobile IAB node provided in an embodiment of the present application;

[0124] Fig.24 It is a structural diagram of a donor-CU of an IAB-DU of a mobile IAB node provided in an embodiment of the present application;

[0125] Fig.25 This is one of the structural diagrams of a device for migrating a mobile IAB node provided in an embodiment of the present application;

[0126] Fig.26 This is a second structural diagram of a device for migrating a mobile IAB node provided in an embodiment of the present application;

[0127] Fig. 27 This is the third structural diagram of a device for migrating a mobile IAB node provided in an embodiment of the present application. DETAILED DESCRIPTION

[0128] The future seamless cellular network deployment requires very flexible and ultra-dense New Radio (NR) cell deployment. Ultra-dense networks are one of the goals of the 5th generation mobile communication (5G). Deploying an NR network without wired backhaul is very important for realizing 5G's ultra-dense network. Since 5G millimeter waves reduce the cell coverage, the wireless self-backhaul system also needs to be multi-hop to meet deployment requirements. 5G's high bandwidth, large-scale multiple input multiple output (MIMO) and beam system make it easier for 5G to develop ultra-dense NR cell wireless self-backhaul systems than Long Term Evolution (LTE). In order to develop this multi-hop system with wireless self-backhaul, 3GPP started the research and standardization of the IAB (Integrated access and backhaul for NR) project in R16. Figure 1 This is a schematic diagram of the IAB system. Figure 1 As shown, access and backhaul adopt NR's Uu air interface wireless transmission, and the relay node supports both access and backhaul functions. The relay node multiplexes the access link (access) and the backhaul link (backhaul) in the time domain, frequency domain or spatial domain. The access and backhaul links can use the same or different frequency bands.

[0129] Figure 2This is a schematic diagram of the IAB network architecture, where: Figure 2 The a in the figure is the IAB architecture of SA mode. Figure 2 b in the figure is the IAB architecture in EN-DC mode. The relay node refers to IAB-node, which supports both access and backhaul functions. The last hop access node on the network side is called IAB-donor, which supports gNB functions and IAB-node access. All UE data can be backhauled to IAB-donor via IAB-node through one or more hops.

[0130] Figure 3 This is a diagram of the Parent IAB-node and Child IAB-node, such as Figure 3 As shown, the functions of IAB-node are divided into two parts, one is the gNB-DU function, called IAB-DU, and the other is the UE function, called IAB-MT. IAB-DU implements the network side equipment function, serves one or more cells and connects to the downstream child IAB-node, provides NR air interface access to UE and downstream child IAB-node, and establishes an F1 connection with IAB donor-CU. IAB-MT implements some terminal equipment functions, connects to the upstream parent IAB-node or IAB-donor DU. IAB-MT includes physical layer, layer 2, RRC and NAS layer functions, and is also indirectly connected to IAB donor-CU and core network. IAB-node can access the network through SA mode or EN-DC mode.

[0131] Figure 4 This is a schematic diagram of the IAB system F1-U protocol stack. Figure 5 This is a schematic diagram of the IAB system F1-C protocol stack, such as Figure 4 and Figure 5 As shown, F1-U and F1-C are built on the transport layer (IP) between IAB-DU and IAB-donor-CU, and go through two hops of wireless backhaul and one hop of wired backhaul. On the backhaul link, the transport (IP) layer is carried on the backhaul adaptation protocol (BAP) sublayer. The BAP entity in the IAB-node implements the routing function of the IAB system, and the routing table is provided by the IAB-donor CU. The BAP PDU is transmitted in the RLC channel of the backhaul link. Multiple RLC channels of the backhaul link can be configured by the IAB-donor to carry services of different priorities and QoS. The BAP entity maps the BAP PDU to different backhaul RLC channels.

[0132] Figure 6 This is a schematic diagram of the routing function of the IAB system. Figure 6As shown in the figure, the routing function of the IAB system is implemented by the BAP layer. Each IAB-node node stores a routing table (BH routing configuration) and an RLC channel mapping table (BH RLC Channel Mapping Configuration). The BAP entity performs routing based on the routing table, RLC channel mapping table and the Routing ID in the BAP layer data packet header. The Routing ID contains the destination BAP address and the path identifier.

[0133] The routing table contains the mapping relationship between the Routing ID and the next node address. The RLC channel mapping table contains the mapping relationship between the previous hop address, the ingress RLC channel ID, and the next hop address and the egress RLC channel ID. For each data packet, the next hop address can be found from the routing table through the Routing ID in the packet header. The previous hop address and the ingress RLC channel ID are both known. In this way, after the next hop address is determined, the egress RLC channel ID can be found through the RLC channel mapping table based on the previous hop address + ingress RLC channel ID + next hop address.

[0134] IAB-donor DU stores the routing table (BH routing configuration) and the downlink RLC channel mapping table (Downlink Traffic to BH RLC Channel Mapping Configuration). IAB-donor DU performs routing based on the routing table, RLC channel mapping table and the Routing ID in the BAP layer data packet header. The routing table contains the mapping relationship between the Routing ID and the next node address. The downlink RLC channel mapping table contains the mapping relationship between the target IP address, DSCP and next hop address and the egress RLC channel ID. For each downlink data packet arriving at IAB-donor DU, the next hop address can be found from the routing table based on the Routing ID in the packet header. In this way, after the next hop address is determined, the egress RLC channel ID can be found from the downlink RLC channel mapping table based on the IP address and DSCP of the data packet.

[0135] Figure 7 This is a network topology diagram applicable to the IAB anchor CU, such as Figure 7As shown, 3GPP R16 studies the workflow when the IAB node initially accesses the network, and the process of switching between parent nodes of different donor-CDU services of the IAB-MT under the initial donor-CU, and standardizes the process of service transmission path migration caused by network topology changes (topology adaptation) when the IAB-MT switches between different parent nodes under the same donor-CU. R16 only supports the scenario where the RRC connection and F1 connection of the IAB node always terminate at the initial donor-CU.

[0136] Figure 8 This is a schematic diagram of the network topology between IAB anchor CUs, such as Figure 8 As shown, the process of IAB-MT switching from the initial donor-CU to another donor-CU was studied in R17. R17 supports the scenario where the RRC connection of the IAB node is switched between the initial donor-CU and another donor-CU (non-F1 termination donor-CU) when the F1 connection of the IAB node is terminated at the initial donor-CU, and standardizes the process of migrating the service transmission path between the topological domains of the two CUs due to changes in the network topology when the IAB-MT switches between the initial CU and another CU.

[0137] NRR18 started the discussion on mobile IAB nodes and added support for mobility scenarios, for example, loading IAB nodes on high-speed or low-speed moving vehicles to serve users on the vehicle. First, R18 determined the need to support continuous IAB-MT switching scenarios and support the switching of IAB-MT between two non-F1 terminated donor-CUs without changing the donor-CU of IAB-DU, also known as the IAB-MT migration process. However, when the donor-CU of IAB-DU is not changed (that is, the F1 terminated donor-CU is not changed), the F1 service always needs to be transferred from the topological domain of IAB-MT to the donor-CU of IAB-DU. If the activity range of the mobile IAB node is large, the donor-CU of IAB-MT is far away from the donor-CU of IAB-DU, which will cause service transmission delay. Therefore, R18 determined the need to support the change of F1 terminated donor-CU, also known as IAB-DU migration. In addition, considering that the functions of the donor-CU of IAB-MT and the donor-CU of IAB-DU are different, R18 also supports the situation where the IAB-MT and IAB-DU access different CUs when the mobile IAB node accesses the network.

[0138] Fig. 9 is a schematic diagram of IAB-MT migration, such as Fig. 9As shown, when IAB-MT migrates, IAB-MT switches from the source donor-CU (also called source RRC or non-F1 terminated donor-CU) to the target donor-CU (also called target RRC or non-F1AP terminated donor-CU). Therefore, the transmission path of the service needs to be switched from the source donor-CU topology domain of the IAB-MT migration to the topology domain of the target donor-CU of the IAB-MT migration. The donor-CU of the IAB-DU needs to obtain the relevant information of the target donor-CU of the IAB-MT migration, so that the donor-CU of the IAB-DU sends an IAB TMM request message to the target donor-CU of the IAB-MT migration, so that the target donor-CU of the IAB-MT migration configures the path resources required for the transmission of the service.

[0139] Fig.10 is a schematic diagram of IAB-DU migration, such as Fig.10 As shown, when the IAB-DU migrates, the donor-CU of the IAB-DU changes from the source donor-CU (also called the source F1 terminated donor-CU) to the target donor-CU (also called the target F1 terminated donor-CU). When executing this process, the IAB node needs to implement two logical DU functions. The target logical DU of the IAB node establishes an F1 connection with the target donor-CU. At this time, the original F1 connection is still retained between the source logical DU of the IAB node and the source donor-CU. Through the two logical DUs and the corresponding F1 connections, the UE served by the IAB node can be switched from the source donor-CU to the target donor-CU. Subsequently, the source logical DU of the IAB node releases the F1 connection with the source donor-CU. When migrating the IAB-DU, the target donor-CU needs to request the transmission of services in the donor-CU topology domain of the IAB-MT. Therefore, the target donor-CU needs to obtain the relevant information of the donor-CU of the IAB-MT so that the target donor-CU of the IAB-DU migration can send an IAB TMM request message to the donor-CU of the IAB-MT so that the donor-CU of the IAB-MT can configure the path resources required for the transmission service.

[0140] Fig.11 is a schematic diagram of the initial access of a mobile IAB node to the network, such as Fig.11As shown, similar to the IAB-DU migration process, when the mobile IAB node initially accesses the network, if the donor-CU of the IAB-DU (also called the F1 terminated donor-CU) and the donor-CU of the IAB-MT (also called the RRC or non-F1AP terminated donor-CU) are not the same CU, the donor-CU of the IAB-DU needs to request to transmit the service in the topological domain of the donor-CU of the IAB-MT. Therefore, the donor-CU of the IAB-DU needs to obtain the relevant information of the donor-CU of the IAB-MT, so that the donor-CU of the IAB-DU sends an IAB TMM request message to the donor-CU of the IAB-MT so that the donor-CU of the IAB-MT configures the path resources required for the transmission of the service.

[0141] In the mobile IAB scenario, in order to assist the core network in locating the UE served by the mobile IAB node, in addition to the UE's location information (NCGI and TAC of the cell the UE accesses), the donor-CU of the IAB-DU needs to send the location information of the mobile IAB node serving the UE (including the NCGI and TAI of the cell the IAB-MT accesses) to the AMF. However, in the current case of IAB-MT migration, IAB-DU migration, and when the IAB-MT and IAB-DU initially access different donor-CUs of the mobile IAB node, the donor-CU of the IAB-DU cannot obtain the location information of the mobile IAB node.

[0142] For the IAB node, the AMF can indicate the authentication result of the IAB node to the donor-CU of the IAB-MT when the IAB node initially accesses the network or switches. The AMF can send the IAB node authentication status information (authentication success or failure) to the donor-CU of the IAB-MT through the initial context establishment request (INITIAL CONTEXT SETUP REQUEST), UE context modification request (UE CONTEXT MODIFICATION REQUEST) or handover request (HANDOVER REQUEST). For the mobile IAB node, depending on the location of the mobile, the authentication status of the mobile IAB node in the core network will change according to the cell accessed by the IAB-MT. The AMF can also send the authentication status information (authentication success or authentication failure) for the mobile IAB node to the donor-CU of the IAB-MT through the UE CONTEXT MODIFICATION REQUEST or HANDOVER REQUEST. When the authentication of an IAB node or a mobile IAB node fails, the IAB node or the mobile IAB node needs to stop serving the UE. However, the authentication information is currently sent by the AMF to the donor-CU of the IAB-MT. The donor-CU of the IAB-DU cannot obtain the authentication information of the IAB node, so it is impossible to stop serving the UE when the authentication fails.

[0143] Based on the above technical problems, the embodiments of the present application propose a method, device and storage medium for migrating a mobile IAB node, so that the donor-CU of the IAB-DU obtains relevant information of the donor-CU of the IAB-MT, so that the donor-CU of the IAB-DU can initiate an IAB TMM process to the donor-CU of the IAB-MT to request the donor-CU of the IAB-MT to configure the path resources required for the transmission service, obtain the location information of the mobile IAB node and obtain the authentication information of the IAB node.

[0144] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0145] Fig.12 This is one of the flow charts of the method for migrating a mobile IAB node provided in an embodiment of the present application, such as Fig.12As shown, the embodiment of the present application provides a method for migrating a mobile IAB node, and the execution subject may be a mobile IAB node. The method includes:

[0146] Step 1201: Obtain a first IAB identifier allocated to the mobile IAB node by a donor-CU of a distribution unit IAB-DU of the mobile IAB node.

[0147] Specifically, in the embodiment of the present application, the donor-CU of the IAB-DU of the mobile IAB node first sends the first IAB identifier allocated to the mobile IAB node to the mobile IAB node.

[0148] The mobile IAB node obtains a first IAB identifier allocated to the mobile IAB node by a donor-CU of an IAB-DU of the mobile IAB node.

[0149] Step 1202: Send the first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the terminal IAB-MT of the mobile IAB node; the first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are used by the donor-CU of the IAB-MT of the mobile IAB node to send the first IAB identifier and the second IAB identifier allocated to the IAB node by the donor-CU of the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0150] Specifically, in an embodiment of the present application, the mobile IAB node sends the first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the IAB-MT of the mobile IAB node; the first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are used by the donor-CU of the IAB-MT of the mobile IAB node to send the first IAB identifier and the second IAB identifier allocated to the IAB node by the donor-CU of the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0151] The donor-CU of the IAB-MT of the mobile IAB node obtains the first IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-DU of the mobile IAB node and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node sent by the mobile IAB node.

[0152] The donor-CU of the IAB-MT of the mobile IAB node allocates a second IAB identity to the mobile IAB node.

[0153] The donor-CU of the IAB-MT of the mobile IAB node sends the first IAB identifier and the second IAB identifier to the donor-CU of the IAB-DU of the mobile IAB node.

[0154] The donor-CU of the IAB-DU of the mobile IAB node receives the first IAB identifier sent by the donor-CU of the IAB-MT of the mobile IAB node and the second IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-MT of the mobile IAB node.

[0155] The donor-CU of the IAB-DU of the mobile IAB node initiates the Xn IABBTMM process based on the first IAB identity and the second IAB identity to request the donor-CU of the IAB-MT of the mobile IAB node to configure the path resources required for the transmission service for the mobile IAB node.

[0156] In some embodiments, the mobile IAB node obtains the first IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-DU of the mobile IAB node through an F1 interface F1AP message.

[0157] In some embodiments, the mobile IAB node sends the first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the IAB-MT of the mobile IAB node through an RRC message.

[0158] In some embodiments, the donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

[0159] In some embodiments, the donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

[0160] In some embodiments, the first IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by a donor-CU of an IAB-DU of the mobile IAB node to an IAB-MT of the mobile IAB node.

[0161] In some embodiments, the method further comprises:

[0162] The donor-CU of the IAB-MT of the mobile IAB node sends the new air interface cell global identity NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0163] The donor-CU of the IAB-DU of the mobile IAB node receives the NCGI of the serving cell to which the IAB-MT of the mobile IAB node accesses, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0164] In the embodiment of the present application, the donor-CU of the IAB-MT sends the location information of the mobile IAB node (the NCGI of the cell to which the IAB-MT is connected) to the donor-CU of the IAB-DU through an XnAP message, so that the donor-CU of the IAB-DU can send the location information of the IAB node as the additional location information of the UE to the core network. This solves the problem of how to enable the donor-CU of the IAB-DU to obtain the location information of the mobile IAB node in different scenarios.

[0165] In some embodiments, the method further comprises:

[0166] The donor-CU of the IAB-MT of the mobile IAB node sends the tracking area identifier TAI of the serving cell accessed by the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0167] The donor-CU of the IAB-DU of the mobile IAB node receives the TAI of the serving cell to which the IAB-MT of the mobile IAB node accesses, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0168] In the embodiment of the present application, the donor-CU of the IAB-MT sends the location information of the mobile IAB node (TAI of the cell to which the IAB-MT is connected) to the donor-CU of the IAB-DU through an XnAP message, so that the donor-CU of the IAB-DU can send the location information of the IAB node as additional location information of the UE to the core network. This solves the problem of how to enable the donor-CU of the IAB-DU to obtain the location information of the mobile IAB node in different scenarios.

[0169] In some embodiments, the method further comprises:

[0170] The donor-CU of the IAB-MT of the mobile IAB node sends the authentication status information of the core network to the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0171] The donor-CU of the IAB-DU of the mobile IAB node receives the authentication status information of the mobile IAB node from the core network, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0172] In the embodiment of the present application, the donor-CU of the IAB-MT sends the authentication status information of the mobile IAB node to the donor-CU of the IAB-DU through an XnAP message, so that the donor-CU of the IAB-DU can make the IAB node stop serving the UE when the IAB node authentication fails. This solves the problem of how to make the donor-CU of the IAB-DU know the authentication information of the mobile IAB node by the core network in different scenarios.

[0173] For example, Fig.13 This is one of the flowcharts of the donor-CU of the IAB-DU obtaining the relevant information of the donor-CU of the IAB-MT provided in the embodiment of the present application, such as Fig.13 As shown, when the mobile IAB node initially accesses the network, if the donor-CU of the IAB-DU and the donor-CU of the IAB-MT are not the same CU, the specific steps for the donor-CU of the IAB-DU to obtain the relevant information of the donor-CU of the IAB-MT are as follows:

[0174] Step 1: When the IAB-MT of the mobile IAB node establishes an RRC connection with the donor-CU of the IAB-MT, the CU configures the default BAP configuration and IP address for the mobile IAB node to transmit F1-C / non-F1 services through an RRC reconfiguration message. The IAB-DU of the mobile IAB node establishes an F1 connection with the donor-CU according to the parameters of the donor-CU of the IAB-DU pre-configured by OAM (such as gNB-ID or IP address). During this process, the unique identifier F1APUE ID assigned by the donor-CU of the IAB-DU to the IAB-DU can be obtained. The donor-CU of the IAB-MT is configured to transmit the backhaul RLC channel and route for transmitting the F1-C / non-F1 services of the mobile IAB node in the CU topology domain. In this step, the donor-CU sends the XnAPUE ID allocated for the IAB-MT to the IAB-DU through the F1AP message (for example, through the F1 SETUP RESPONSE message), and the IAB-DU can request the donor-CU to send the XnAP UE ID allocated for the IAB-MT through the F1AP message (for example, through the F1 SETUP REQUEST request message).

[0175] Step 2: The IAB-MT of the mobile IAB node reports the gNB-ID of the donor-CU of the IAB-DU and the unique identifier assigned by the donor-CU of the IAB-DU to the mobile IAB node to the donor-CU of the IAB-MT through an RRC message (e.g., a UEAssistanceInformation message), which may be the XnAP UEID assigned to the IAB-MT obtained in Step 1. Optionally, in this step, the donor-CU of the IAB-MT may configure in advance through an RRC message (e.g., an RRCReconfiguration message) whether the IAB-MT reports the gNB-ID of the donor-CU of the IAB-DU and the unique identifier XnAP UE ID assigned by the donor-CU of the IAB-DU to the mobile IAB node. The purpose of this step is to facilitate the donor-CU of the IAB-MT in Step 3 to send an XnAP message for the mobile IAB node to the donor-CU of the IAB-DU.

[0176] Step 3: After receiving the gNB-ID of the donor-CU of the IAB-DU and the unique identifier XnAP UE ID assigned by the donor-CU of the IAB-DU to the mobile IAB node, the donor-CU of the IAB-MT sends a new XnAP message to the donor-CU of the IAB-DU through the Xn interface, which carries the unique identifier XnAP UE ID assigned by the donor-CU of the IAB-DU to the mobile IAB node, the unique identifier XnAP UE ID assigned by the donor-CU of the IAB-MT to the IAB-MT, the NCGI of the cell to which the IAB-MT accesses, and the authentication status information of the core network for the IAB-MT.

[0177] Optionally, if there is no Xn interface between the donor-CU of the IAB-MT and the donor-CU of the IAB-DU, the XnAP also needs to carry the TAI of the cell to which the IAB-MT accesses. The reason is that if there is no Xn interface between the donor-CU of the IAB-MT and the donor-CU of the IAB-DU, the donor-CU of the IAB-DU does not have the TAI information about the service cell of the donor-CU of the IAB-MT.

[0178] Optionally, if there is no Xn interface between the donor-CU of IAB-MT and the donor-CU of IAB-DU, the new XnAP message needs to be forwarded through the NG interface. That is, the donor-CU of IAB-MT encapsulates the XnAP message in an NGAP message (with the gNB-ID of the donor-CU of IAB-MT as the source and the gNB-ID of the donor-CU of IAB-DU as the target RAN node ID) and sends it to AMF, and then AMF forwards the XnAP message to the donor-CU of IAB-DU through another NGAP message.

[0179] Step 4: The donor-CU of IAB-DU receives the new XnAP message, obtains the gNB-ID of the donor-CU of IAB-MT for the mobile IAB node, the unique identifier XnAP UE ID assigned to IAB-MT, the NCGI and TAI of the cell to which IAB-MT accesses, and the authentication status information of IAB-MT by the core network. Afterwards, when the mobile IAB node serves the UE, the donor-CU of IAB-DU can use the unique identifier XnAP UE ID assigned to IAB-MT by the donor-CU of IAB-MT to initiate the Xn IABTMM process to request the donor-CU of IAB-MT to configure the path resources required for the service to be transmitted in the topological domain of the CU.

[0180] Optionally, if there is no Xn interface between the donor-CU of the IAB-MT and the donor-CU of the IAB-DU, the donor-CU of the IAB-DU encapsulates the Xn IAB TMM Request message in an NGAP message (using the gNB-ID of the donor-CU of the IAB-DU as the source RAN node ID and the gNB-ID of the donor-CU of the IAB-MT as the target RAN node ID) and sends it to the AMF, and the AMF forwards the Xn IAB TMM Request message to the donor-CU of the IAB-MT through another NGAP message; the CU of the IAB-MT encapsulates the Xn IAB TMM Response message in an NGAP message (using the gNB-ID of the donor-CU of the IAB-MT as the source RAN node ID and the gNB-ID of the donor-CU of the IAB-DU as the target RAN node ID) and sends it to the AMF, and the AMF forwards the XnAP message to the peer CU through another NGAP message.

[0181] When the donor-CU of the IAB-DU needs to send the UE location information to the core network, the location information (NCGI and TAI) of the cell to which the IAB-MT is connected is also reported to the core network.

[0182] If the donor-CU of the IAB-DU receives information that the core network fails to authenticate the IAB-MT, the IAB-DU stops serving the UE. For example, an F1AP message (such as a GNB-CU CONFIGURATION UPDATE message) may be sent to the IAB-DU to activate the serving cell of the IAB-DU.

[0183] For another example, Fig.14 This is a second flow chart of the donor-CU of the IAB-DU obtaining relevant information of the donor-CU of the IAB-MT provided in the embodiment of the present application, such as Fig.14 As shown, when performing IAB-MT migration of a mobile IAB node, the specific steps for the donor-CU of the IAB-DU of the mobile IAB node to obtain the relevant information of the target CU of the IAB-MT migration are as follows:

[0184] Step 1: During the process of establishing an F1 connection between the IAB-DU and the donor-CU of the IAB-DU, the IAB-DU can obtain the unique identifier (F1AP UE ID) allocated to the IAB-DU by the donor-CU of the IAB-DU. In this step, the donor-CU of the IAB-DU sends the unique identifier XnAP UE ID allocated for the IAB-MT to the IAB-DU through an F1AP message (for example, through an F1 SETUP REQUEST message or a GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message), and the IAB-DU can request the CU to send the XnAP UE ID allocated for the IAB-MT through the F1AP message (for example, through an F1 SETUP REQUEST request message or a GNB-DU CONFIGURATION UPDATE message).

[0185] Step 2: When the IAB-MT of the mobile IAB node switches to the target CU of the IAB-MT migration, including the core network (NG switching) or the source CU of the IAB-MT migration (Xn switching), the authentication status information for the IAB-MT can be sent to the target CU, and the target CU can configure the default BAP configuration and IP address for transmitting F1-C / non-F1 services for the mobile IAB node through the switching command.

[0186] After IAB-MT switches to the target CU of IAB-MT migration, the gNB-ID of the donor-CU of IAB-DU and the unique identifier assigned by the donor-CU of IAB-DU to the mobile IAB node are reported to the target CU of IAB-MT through RRC messages (such as UEAssistanceInformation messages), and the unique identifier can be the XnAP UE ID assigned to IAB-MT obtained in Step 1. Optionally, in this step, the target CU of IAB-MT migration can configure IAB-MT in advance through RRC messages (such as switching commands) whether to report the gNB-ID of the donor-CU of IAB-DU and the unique identifier XnAP UE ID assigned by the donor-CU of IAB-DU to the mobile IAB node. The purpose of this step is to facilitate the target CU of IAB-MT migration in Step 3 to send XnAP messages for the mobile IAB node to the donor-CU of IAB-DU.

[0187] Step 3: After the target CU of IAB-MT migration receives the gNB-ID of the donor-CU of IAB-DU and the unique identifier XnAP UE ID assigned by the donor-CU of IAB-DU to the mobile IAB node, it sends a new XnAP message to the donor-CU of IAB-DU through the Xn interface, which carries the unique identifier XnAP UE ID assigned by the donor-CU of IAB-DU to the mobile IAB node, the unique identifier XnAP UE ID assigned by the donor-CU of IAB-MT to the IAB-MT, the NCGI of the cell to which the IAB-MT accesses, and the authentication status information of the core network for the IAB-MT.

[0188] Optionally, if there is no Xn interface between the target CU of IAB-MT migration and the donor-CU of IAB-DU, the XnAP also needs to carry the TAI of the cell accessed by IAB-MT. The reason is that if there is no Xn interface between the target CU of IAB-MT migration and the donor-CU of IAB-DU, the donor-CU of IAB-DU does not have the TAI information of the service cell of the target CU of IAB-MT migration.

[0189] Optionally, if there is no Xn interface between the target CU of IAB-MT migration and the donor-CU of IAB-DU, the new XnAP message needs to be forwarded through the NG interface. That is, the XnAP message is encapsulated in an NGAP message (the gNB-ID of the target CU of IAB-MT migration is used as the source RAN node ID, and the gNB-ID of the donor-CU of IAB-DU is used as the target RAN node ID) and sent to AMF, and then the AMF forwards the XnAP message to the donor-CU of IAB-DU through another NGAP message.

[0190] Step 4: The donor-CU of IAB-DU receives the new XnAP message, obtains the gNB-ID of the IAB-MT target CU for the mobile IAB node, the unique identifier XnAP UE ID assigned to IAB-MT, the NCGI and TAI of the cell to which IAB-MT accesses, and the authentication status information of IAB-MT by the core network. Afterwards, the donor-CU of IAB-DU uses the unique identifier XnAP UE ID assigned to IAB-MT by the IAB-MT target CU to initiate the Xn IAB TMM process to request the target CU of IAB-MT migration to configure the path resources required for the F1-U service to be transmitted in the topological domain of the CU.

[0191] Optionally, if there is no Xn interface between the target CU of IAB-MT migration and the donor-CU of IAB-DU, the donor-CU of IAB-DU encapsulates the Xn IAB TMM Request message in an NGAP message (taking the gNB-ID of the donor-CU of IAB-DU as the source RAN node ID and the gNB-ID of the target CU of IAB-MT migration as the target RAN node ID) and sends it to AMF, and then AMF forwards the Xn IAB TMM Request message to the donor-CU of IAB-MT through another NGAP message; the target CU of IAB-MT encapsulates the Xn IAB TMM Response message in an NGAP message (taking the gNB-ID of the target CU of IAB-MT as the source RAN node ID and the gNB-ID of the donor-CU of IAB-DU as the target RAN node ID) and sends it to AMF, and then AMF forwards the XnAP message to the opposite CU through another NGAP message.

[0192] When the donor-CU of the IAB-DU needs to send the UE location information to the core network, the location information of the cell to which the IAB-MT is connected is also reported to the core network. If the donor-CU of the IAB-DU learns through the new XnAP message that the core network has failed to authenticate the IAB-MT, the IAB-DU stops serving the UE. For example, an F1AP message (such as a GNB-CU CONFIGURATION UPDATE message) may be sent to the IAB-DU to activate the serving cell of the IAB-DU.

[0193] For another example, Fig.15 This is a third flow chart of the donor-CU of the IAB-DU obtaining relevant information of the donor-CU of the IAB-MT provided in the embodiment of the present application, such as Fig.15 As shown, when the IAB-DU of the mobile IAB node is migrated, the specific steps for the target CU of the IAB-DU migration to obtain the relevant information of the donor-CU of the IAB-MT of the mobile IAB node are as follows:

[0194] Step 1: When IAB-DU migration is triggered, the mobile IAB node establishes an F1 connection between the target logical DU and the target CU according to the OAM pre-configuration or the parameters of the target CU of the IAB-DU migration indicated by the source CU of the IAB-DU migration (e.g., gNB-ID or IP address). In this process, the unique identifier F1AP UE ID assigned to the IAB node by the target CU of the IAB-DU migration can be obtained. In this step, the target CU of the IAB-DU migration sends the XnAPUE ID assigned to the IAB-MT to the target logical DU through the F1AP message (e.g., through the F1 SETUP RESPONSE message), and the IAB-DU can request the target CU to send the XnAP UE ID assigned to the IAB-MT through the F1AP message (e.g., through the F1 SETUP REQUEST request message).

[0195] Step 2: The IAB-MT of the mobile IAB node reports the gNB-ID of the target CU of the IAB-DU migration and the unique identifier assigned to the mobile IAB node by the target CU of the IAB-DU migration to the donor-CU of the IAB-MT through an RRC message (e.g., UEAssistanceInformation message), which may be the XnAPUE ID assigned to the IAB-MT obtained in Step 1. Optionally, in this step, the donor-CU of the IAB-MT may configure the IAB-MT in advance through an RRC message (e.g., RRCReconfiguration message) whether to report the gNB-ID of the donor-CU of the IAB-DU and the unique identifier XnAP UE ID assigned to the mobile IAB node by the donor-CU of the IAB-DU. The purpose of this step is to facilitate the donor-CU of the IAB-MT in Step 3 to send an XnAP message for the mobile IAB node to the target CU of the IAB-DU migration.

[0196] Step 3: After the donor-CU of IAB-MT receives the gNB-ID of the target CU for IAB-DU migration and the unique identifier XnAP UE ID assigned by the donor-CU of IAB-DU to the mobile IAB node, it sends a new XnAP message to the target CU for IAB-DU migration through the Xn interface, which carries the unique identifier XnAP UE ID assigned by the target CU for IAB-DU migration to the mobile IAB node, the unique identifier XnAP UE ID assigned by the donor-CU of IAB-MT to the IAB-MT, the NCGI of the cell to which the IAB-MT accesses, and the authentication status information of the core network for the IAB-MT.

[0197] Optionally, if there is no Xn interface between the donor-CU of the IAB-MT and the target CU of the IAB-DU migration, the XnAP also needs to carry the TAI of the cell to which the IAB-MT accesses. The reason is that if there is no Xn interface between the donor-CU of the IAB-MT and the target CU of the IAB-DU migration, the target CU of the IAB-DU migration does not have the TAI information of the service cell of the donor-CU of the IAB-MT.

[0198] Optionally, if there is no Xn interface between the donor-CU of IAB-MT and the target CU of IAB-DU migration, the new XnAP message needs to be forwarded through the NG interface. That is, the donor-CU of IAB-MT encapsulates the XnAP message in an NGAP message (the gNB-ID of the donor-CU of IAB-MT is used as the source RAN node ID, and the gNB-ID of the target CU of IAB-DU is used as the target RAN node ID) and sends it to AMF, and then the AMF forwards the XnAP message to the target CU of IAB-DU migration through another NGAP message.

[0199] Step 4: The target CU of IAB-DU migration receives the new XnAP message, obtains the gNB-ID of the donor-CU of IAB-MT for the mobile IAB node, the unique identifier XnAP UE ID assigned to IAB-MT, the NCGI and TAI of the cell to which IAB-MT accesses, and the authentication status information of IAB-MT by the core network. Afterwards, when switching the mobile IAB node to serve the UE, the target CU of IAB-DU migration can use the unique identifier XnAP UE ID assigned to IAB-MT by the donor-CU of IAB-MT to initiate the XnIAB TMM process to request the donor-CU of IAB-MT to configure the path resources required for the UE service to be transmitted in the topological domain of the CU.

[0200] Optionally, if there is no Xn interface between the donor-CU of IAB-MT and the target CU of IAB-DU migration, the target CU of IAB-DU migration encapsulates the Xn IAB TMM Request message in an NGAP message (taking the gNB-ID of the target CU of IAB-DU migration as the source RAN node ID and the gNB-ID of the donor-CU of IAB-MT as the target RAN node ID) and sends it to AMF, and then AMF forwards the Xn IAB TMM Request message to the donor-CU of IAB-MT through another NGAP message; the CU of IAB-MT encapsulates the Xn IAB TMM Response message in an NGAP message (taking the gNB-ID of the donor-CU of IAB-MT as the source RAN node ID and the gNB-ID of the target CU of IAB-DU as the target RAN node ID) and sends it to AMF, and then AMF forwards the XnAP message to the opposite CU through another NGAP message.

[0201] When the target CU of IAB-DU migration needs to send UE location information to the core network, the location information of the cell accessed by IAB-MT is also reported to the core network.

[0202] If the target CU of IAB-DU migration receives the core network's IAB-MT authentication failure information, the IAB-DU stops serving the UE. For example, an F1AP message (such as a GNB-CU CONFIGURATION UPDATE message) can be sent to the target logical DU to activate the serving cell of the target logical DU.

[0203] In some embodiments, when there is no Xn interface between the donor-CU of the IAB-DU or the target donor-CU of the IAB-DU migration and the donor-CU of the IAB-MT, the specific manner of transmitting the IAB-related XnAP message is as follows:

[0204] The NG-RAN node sending the message encapsulates the XnAP message in an NGAP message (with the gNB-ID of the NG-RAN node as the source RAN node ID and the gNB-ID of the opposite NG-RAN node as the target RAN node ID) and sends it to the AMF, which then forwards the XnAP message to the opposite CU via another NGAP message (containing at least the source RAN node ID).

[0205] Specifically, in an embodiment of the present application, the first IAB identifier and the second IAB identifier, the NCGI of the service cell accessed by the IAB-MT of the mobile IAB node, the TAI of the service cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network are carried through the Xn interface application protocol XnAP message.

[0206] The donor-CU of the IAB-MT of the mobile IAB node uses the gNB-ID of the donor-CU of the IAB-MT of the mobile IAB node as the source radio access network RAN ​​node ID, and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node as the target RAN node ID, encapsulates the XnAP message in the first NG interface application protocol NGAP message and sends it to the access and mobility management function AMF network element, and then the AMF network element forwards the XnAP message to the donor-CU of the IAB-DU of the mobile IAB node through the second NGAP message.

[0207] For example, Fig.16 Schematic diagram of NGAP forwarding class 1XnAP message provided by an embodiment of the present application, such as Fig.16 As shown, the messages transmitted between the donor-CU of IAB-DU or the donor-CU of IAB-DU have nothing to do with the core network. Therefore, when there is no Xn interface between the donor-CU of IAB-DU or the target CU of IAB-DU migration and the donor-CU of IAB-MT, the IAB-related XnAP messages can be transparently forwarded through NGAP, including all IAB-related class 1 and class 2 XnAP process messages. When forwarding XnAP messages, the core network treats the XnAP messages as transparent message units and does not parse them.

[0208] In order to indicate the destination NG-RAN node and the source NG-RAN node of the XnAP message, the NGAP message forwarding the XnAP message needs to carry the gNB-ID of the destination NG-RAN node and the gNB-ID of the source NG-RAN node.

[0209] Fig.17 is one of the schematic diagrams of the NGAP message provided in the embodiment of the present application, such as Fig.17As shown, for the class1XnAP process, the NG-RAN node that sends the initial message encapsulates the XnAP message in the first NGAP message (using the gNB-ID of the node as the source RAN node ID and the gNB-ID of the opposite node as the target RAN node ID) and sends it to the AMF, and then the AMF forwards the XnAP message to the CU of the destination ID through the second NGAP message (including the source RAN node ID in the first NGAP message); the NG-RAN node that sends the response message encapsulates the XnAP message in the third NGAP message (using the gNB-ID of the node as the source RAN node ID and the opposite node as the target RAN node ID) and sends it to the AMF, and then the AMF forwards the XnAP message to the NG-RAN node that sends the initial message through the fourth NGAP message (including the source RAN node ID in the third NGAP message).

[0210] The Class1 IAB process and IAB XnAP messages that need to be forwarded by NGAP are shown in Table 1:

[0211] Table 1

[0212]

[0213]

[0214] For another example, Fig.18 is a schematic diagram of NGAP forwarding class 2XnAP message provided in an embodiment of the present application, Fig.19 This is the second schematic diagram of the NGAP message provided in the embodiment of the present application, such as Fig.18 and 19 As shown, for the class 2XnAP process, the NG-RAN node that sends the initial message encapsulates the XnAP message in the fifth NGAP message (using the gNB-ID of the node as the source RAN node ID and the gNB-ID of the opposite node as the target RAN node ID) and sends it to the AMF, and then the AMF forwards the XnAP message to the opposite CU through the sixth NGAP message (including the source RAN node ID in the fifth NGAP message).

[0215] The Class2 IAB process and IAB XnAP messages that need to be forwarded by NGAP are shown in Table 2:

[0216] Table 2

[0217] Elementary Procedure Initiating Message F1-C Traffic Transfer F1-C TRAFFIC TRANSFER

[0218] In the embodiment of the present application, the NG-RAN node that sends the message encapsulates the XnAP message in an NGAP message (with the gNB-ID of the NG-RAN node as the source RAN node ID and the gNB-ID of the opposite NG-RAN node as the target RAN node ID) and sends it to the AMF, and then the AMF forwards the XnAP message to the opposite CU through another NGAP message (containing at least the source RAN node ID). In this way, the AMF can determine the destination node of the XnAP message through the target RAN node ID in the NGAP message sent by the NG-RAN node, so that the XnAP message can be forwarded to the destination node; the destination NG-RAN node can determine the source NG-RAN node that sent the XnAP message through the source RAN node ID in the NGAP message sent by the AMF. In this way, when there is no Xn interface between the donor-CU of the IAB-DU and the donor-CU of the IAB-MT, the problem of how to transmit IAB-related XnAP messages is solved.

[0219] In some embodiments, the second IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by a donor-CU of the IAB-MT of the mobile IAB node to the IAB-MT of the mobile IAB node.

[0220] Fig. 20 FIG. 2 is a flow chart of a method for migrating a mobile IAB node provided in an embodiment of the present application. Fig. 20 As shown, an embodiment of the present application provides a method for migrating a mobile IAB node, and the execution subject may be a donor-CU of an IAB-MT of the mobile IAB node, etc.

[0221] The method includes:

[0222] Step 2001: Acquire a first IAB identifier allocated to the mobile IAB node by a donor-CU of the IAB-DU of the mobile IAB node and a gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node sent by the mobile IAB node;

[0223] Step 2002: Allocate a second IAB identifier to the mobile IAB node;

[0224] Step 2003: Send the first IAB identifier and the second IAB identifier to the donor-CU of the IAB-DU of the mobile IAB node; the first IAB identifier and the second IAB identifier are used by the donor-CU of the IAB-DU of the mobile IAB node to initiate an IAB TMM process to the donor-CU of the IAB-MT of the mobile IAB node.

[0225] In some embodiments, the method further comprises:

[0226] Sending a new air interface cell global identity NCGI of a serving cell accessed by the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0227] In some embodiments, the method further comprises:

[0228] The tracking area identifier TAI of the serving cell accessed by the IAB-MT of the mobile IAB node is sent to the donor-CU of the IAB-DU of the mobile IAB node.

[0229] In some embodiments, the method further comprises:

[0230] Sending authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node.

[0231] In some embodiments, the donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

[0232] In some embodiments, the donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

[0233] In some embodiments, the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network are carried through an Xn interface application protocol XnAP message;

[0234] Sending the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node includes:

[0235] Taking the gNB-ID of the donor-CU of the IAB-MT of the mobile IAB node as the source radio access network RAN ​​node ID, and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node as the target RAN node ID, the XnAP message is encapsulated in a first NG interface application protocol NGAP message and sent to the access and mobility management function AMF network element, and then the AMF network element forwards the XnAP message to the donor-CU of the IAB-DU of the mobile IAB node through a second NGAP message.

[0236] In some embodiments, the second IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by a donor-CU of the IAB-MT of the mobile IAB node to the IAB-MT of the mobile IAB node.

[0237] Specifically, the method for migrating a mobile IAB node provided in an embodiment of the present application can refer to the method embodiment for migrating a mobile IAB node in which the execution subject is a mobile IAB node, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the above-mentioned corresponding method embodiments will not be described in detail here.

[0238] Fig.21 FIG. 3 is a flow chart of a method for migrating a mobile IAB node provided in an embodiment of the present application. Fig.21 As shown, an embodiment of the present application provides a method for migrating a mobile IAB node, and the execution subject may be a donor-CU of an IAB-DU of the mobile IAB node, etc.

[0239] The method includes:

[0240] Step 2101: Send a first IAB identifier allocated to the mobile IAB node to the mobile IAB node;

[0241] Step 2102: Receive a first IAB identifier sent by a donor-CU of the IAB-MT of the mobile IAB node and a second IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-MT of the mobile IAB node;

[0242] Step 2103: Initiate an Xn IAB TMM process based on the first IAB identifier and the second IAB identifier to request the donor-CU of the IAB-MT of the mobile IAB node to configure path resources required for transmission services for the mobile IAB node.

[0243] In some embodiments, the method further comprises:

[0244] Receive the NCGI of the serving cell to which the IAB-MT of the mobile IAB node accesses, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0245] In some embodiments, the method further comprises:

[0246] Receive the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0247] In some embodiments, the method further comprises:

[0248] Receive the authentication status information of the mobile IAB node from the core network, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0249] In some embodiments, the donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

[0250] In some embodiments, the donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

[0251] Specifically, the method for migrating a mobile IAB node provided in an embodiment of the present application can refer to the method embodiment for migrating a mobile IAB node in which the execution subject is a mobile IAB node, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the above-mentioned corresponding method embodiments will not be described in detail here.

[0252] Fig. 22 is a structural diagram of a mobile IAB node provided in an embodiment of the present application, such as Fig. 22 As shown, the mobile IAB node includes a memory 2220, a transceiver 2200, and a processor 2210, wherein:

[0253] The memory 2220 is used to store computer programs; the transceiver 2200 is used to send and receive data under the control of the processor 2210; the processor 2210 is used to read the computer program in the memory 2220 and perform the following operations:

[0254] Acquire a first IAB identifier allocated to the mobile IAB node by an anchor point centralized unit donor-CU of a distribution unit IAB-DU of the mobile IAB node;

[0255] Sending the first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the terminal IAB-MT of the mobile IAB node;

[0256] The first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are used by the donor-CU of the IAB-MT of the mobile IAB node to send the first IAB identifier and the second IAB identifier allocated to the IAB node by the donor-CU of the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0257] Among them, Fig. 22 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 2210 and various circuits of memory represented by memory 2220 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 2200 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and other transmission media. For different user devices, the user interface 2230 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0258] The processor 2210 is responsible for managing the bus architecture and general processing, and the memory 2220 can store data used by the processor 2210 when performing operations.

[0259] In some embodiments, the processor 2210 can be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD), and the processor can also adopt a multi-core architecture.

[0260] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0261] In some embodiments, obtaining a first IAB identifier allocated to the mobile IAB node by a donor-CU of an IAB-DU of the mobile IAB node includes:

[0262] The first IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-DU of the mobile IAB node is obtained through an F1 interface F1AP message.

[0263] In some embodiments, sending the first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the IAB-MT of the mobile IAB node includes:

[0264] The first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are sent to the donor-CU of the IAB-MT of the mobile IAB node through an RRC message.

[0265] In some embodiments, the donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

[0266] In some embodiments, the donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

[0267] In some embodiments, the first IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by a donor-CU of an IAB-DU of the mobile IAB node to an IAB-MT of the mobile IAB node.

[0268] It should be noted here that the above-mentioned mobile IAB node provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is the mobile IAB node, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0269] Fig.23 is a schematic diagram of the structure of a donor-CU of an IAB-MT of a mobile IAB node provided in an embodiment of the present application, such as Fig.23As shown, the donor-CU of the IAB-MT of the mobile IAB node includes a memory 2320, a transceiver 2300, and a processor 2310, wherein:

[0270] The memory 2320 is used to store computer programs; the transceiver 2300 is used to send and receive data under the control of the processor 2310; the processor 2310 is used to read the computer program in the memory 2320 and perform the following operations:

[0271] Acquire a first IAB identifier allocated to the mobile IAB node by a donor-CU of the IAB-DU of the mobile IAB node and a gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node sent by the mobile IAB node;

[0272] allocating a second IAB identifier to the mobile IAB node;

[0273] The first IAB identifier and the second IAB identifier are sent to the donor-CU of the IAB-DU of the mobile IAB node; the first IAB identifier and the second IAB identifier are used by the donor-CU of the IAB-DU of the mobile IAB node to initiate an IAB TMM process to the donor-CU of the IAB-MT of the mobile IAB node.

[0274] Among them, Fig.23 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 2310 and various circuits of memory represented by memory 2320 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 2300 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 2310 is responsible for managing the bus architecture and general processing, and the memory 2320 may store data used by the processor 2310 when performing operations.

[0275] The processor 2310 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0276] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0277] Sending a new air interface cell global identity NCGI of a serving cell accessed by the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0278] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0279] The tracking area identifier TAI of the serving cell accessed by the IAB-MT of the mobile IAB node is sent to the donor-CU of the IAB-DU of the mobile IAB node.

[0280] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0281] Sending authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node.

[0282] In some embodiments, the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network are carried through an Xn interface application protocol XnAP message;

[0283] Sending the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node includes:

[0284] Taking the gNB-ID of the donor-CU of the IAB-MT of the mobile IAB node as the source radio access network RAN ​​node ID, and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node as the target RAN node ID, the XnAP message is encapsulated in a first NG interface application protocol NGAP message and sent to the access and mobility management function AMF network element, and then the AMF network element forwards the XnAP message to the donor-CU of the IAB-DU of the mobile IAB node through a second NGAP message.

[0285] In some embodiments, the second IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by a donor-CU of the IAB-MT of the mobile IAB node to the IAB-MT of the mobile IAB node.

[0286] Specifically, the donor-CU of the IAB-MT of the above-mentioned mobile IAB node provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is the donor-CU of the IAB-MT of the mobile IAB node, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0287] Fig.24 is a schematic diagram of the structure of a donor-CU of an IAB-DU of a mobile IAB node provided in an embodiment of the present application, such as Fig.24 As shown, the donor-CU of the IAB-DU of the mobile IAB node includes a memory 2420, a transceiver 2400, and a processor 2410, wherein:

[0288] The memory 2420 is used to store computer programs; the transceiver 2400 is used to send and receive data under the control of the processor 2410; the processor 2410 is used to read the computer program in the memory 2420 and perform the following operations:

[0289] sending, to the mobile IAB node, a first IAB identifier allocated to the mobile IAB node;

[0290] receiving a first IAB identifier sent by a donor-CU of an IAB-MT of the mobile IAB node and a second IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-MT of the mobile IAB node;

[0291] An Xn IAB TMM process is initiated based on the first IAB identifier and the second IAB identifier to request the donor-CU of the IAB-MT of the mobile IAB node to configure path resources required for transmission services for the mobile IAB node.

[0292] Among them, Fig.24 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 2410 and various circuits of memory represented by memory 2420 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 2400 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 2410 is responsible for managing the bus architecture and general processing, and the memory 2420 may store data used by the processor 2410 when performing operations.

[0293] The processor 2410 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0294] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0295] Receive the NCGI of the serving cell to which the IAB-MT of the mobile IAB node accesses, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0296] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0297] Receive the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0298] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0299] Receive the authentication status information of the mobile IAB node from the core network, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0300] Specifically, the donor-CU of the IAB-DU of the above-mentioned mobile IAB node provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is the donor-CU of the IAB-DU of the mobile IAB node, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0301] Fig.25 is one of the structural diagrams of a device for migrating a mobile IAB node provided in an embodiment of the present application, such as Fig.25 As shown, the embodiment of the present application provides a device for migrating a mobile IAB node, including a first acquisition module 2501 and a first sending module 2502, wherein:

[0302] The first acquisition module 2501 is used to acquire a first IAB identifier allocated to the mobile IAB node by a donor-CU of a distribution unit IAB-DU of the mobile IAB node;

[0303] The first sending module 2502 is used to send the first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the terminal IAB-MT of the mobile IAB node;

[0304] The first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are used by the donor-CU of the IAB-MT of the mobile IAB node to send the first IAB identifier and the second IAB identifier allocated to the IAB node by the donor-CU of the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0305] In some embodiments, obtaining a first IAB identifier allocated to the mobile IAB node by a donor-CU of an IAB-DU of the mobile IAB node includes:

[0306] The first IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-DU of the mobile IAB node is obtained through an F1 interface F1AP message.

[0307] In some embodiments, sending the first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the IAB-MT of the mobile IAB node includes:

[0308] The first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are sent to the donor-CU of the IAB-MT of the mobile IAB node through an RRC message.

[0309] In some embodiments, the donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

[0310] In some embodiments, the donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

[0311] In some embodiments, the first IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by a donor-CU of an IAB-DU of the mobile IAB node to an IAB-MT of the mobile IAB node.

[0312] Specifically, the above-mentioned device for migrating a mobile IAB node provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiment in which the execution subject is a mobile IAB node, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0313] Fig.26 This is a second structural diagram of a device for migrating a mobile IAB node provided in an embodiment of the present application, such as Fig.26 As shown, the embodiment of the present application provides a device for migrating a mobile IAB node, including a second acquisition module 2601, a second sending module 2602 and a third sending module 2603, wherein:

[0314] The second acquisition module 2601 is used to obtain the first IAB identifier assigned to the mobile IAB node by the donor-CU of the IAB-DU of the mobile IAB node and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node sent by the mobile IAB node; the second sending module 2602 is used to allocate a second IAB identifier to the mobile IAB node; the third sending module 2603 is used to send the first IAB identifier and the second IAB identifier to the donor-CU of the IAB-DU of the mobile IAB node; the first IAB identifier and the second IAB identifier are used by the donor-CU of the IAB-DU of the mobile IAB node to initiate an IAB TMM process to the donor-CU of the IAB-MT of the mobile IAB node.

[0315] In some embodiments, the apparatus further comprises:

[0316] The fifth sending module is configured to send the new air interface cell global identifier NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0317] In some embodiments, the apparatus further comprises:

[0318] The sixth sending module is configured to send the tracking area identifier TAI of the serving cell accessed by the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

[0319] In some embodiments, the apparatus further comprises:

[0320] The seventh sending module is configured to send the authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node.

[0321] In some embodiments, the donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

[0322] In some embodiments, the donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

[0323] In some embodiments, the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network are carried through an Xn interface application protocol XnAP message;

[0324] Sending the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node includes:

[0325] Taking the gNB-ID of the donor-CU of the IAB-MT of the mobile IAB node as the source radio access network RAN ​​node ID, and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node as the target RAN node ID, the XnAP message is encapsulated in a first NG interface application protocol NGAP message and sent to the access and mobility management function AMF network element, and then the AMF network element forwards the XnAP message to the donor-CU of the IAB-DU of the mobile IAB node through a second NGAP message.

[0326] In some embodiments, the second IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by a donor-CU of the IAB-MT of the mobile IAB node to the IAB-MT of the mobile IAB node.

[0327] Specifically, the above-mentioned device for migrating a mobile IAB node provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment of the donor-CU of the IAB-MT whose execution subject is the mobile IAB node, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0328] Fig. 27 FIG. 3 is a structural diagram of a device for migrating a mobile IAB node provided in an embodiment of the present application. Fig. 27 As shown, the embodiment of the present application provides a device for migrating a mobile IAB node, including a fourth sending module 2701, a first receiving module 2702 and an initiating module 2703, wherein:

[0329] The fourth sending module 2701 is used to send the first IAB identifier allocated to the mobile IAB node to the mobile IAB node; the first receiving module 2702 is used to receive the first IAB identifier sent by the donor-CU of the IAB-MT of the mobile IAB node and the second IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-MT of the mobile IAB node; the initiating module 2703 is used to initiate the Xn IAB TMM process based on the first IAB identifier and the second IAB identifier to request the donor-CU of the IAB-MT of the mobile IAB node to configure the path resources required for the transmission service for the mobile IAB node.

[0330] In some embodiments, the apparatus further comprises:

[0331] The second receiving module is configured to receive the NCGI of the serving cell to which the IAB-MT of the mobile IAB node accesses, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0332] In some embodiments, the apparatus further comprises:

[0333] The third receiving module is configured to receive the TAI of the serving cell to which the IAB-MT of the mobile IAB node accesses, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0334] In some embodiments, the apparatus further comprises:

[0335] The fourth receiving module is configured to receive authentication status information of the mobile IAB node from the core network, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

[0336] In some embodiments, the donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

[0337] In some embodiments, the donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

[0338] Specifically, the above-mentioned device for migrating a mobile IAB node provided in an embodiment of the present application can implement all the method steps implemented by the method embodiment of the donor-CU of the IAB-DU whose execution subject is the mobile IAB node, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0339] It should be noted that the division of units / modules in the above embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, the functional units in the various embodiments of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated units may be implemented in the form of hardware or in the form of software functional units.

[0340] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0341] In some embodiments, a non-transitory readable storage medium is further provided, wherein the non-transitory readable storage medium stores a computer program, wherein the computer program is used to enable a processor to execute the method for migrating a mobile IAB node provided in the above method embodiments.

[0342] Specifically, the above-mentioned non-transitory readable storage medium provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects that are the same as the method embodiments in this embodiment will not be described in detail here.

[0343] It should be noted that the non-transitory readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0344] In some embodiments, a processor-readable storage medium is further provided, wherein the processor-readable storage medium stores a computer program, wherein the computer program is used to enable a processor to execute the method for migrating a mobile IAB node provided in the above-mentioned method embodiments.

[0345] Specifically, the processor-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects that are the same as those in the method embodiments will not be described in detail herein.

[0346] In some embodiments, a computer-readable storage medium is further provided, wherein the computer-readable storage medium stores a computer program, wherein the computer program is used to enable a computer to execute the method for migrating a mobile IAB node provided in the above method embodiments.

[0347] Specifically, the above-mentioned computer-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0348] In some embodiments, a communication device is further provided, wherein a computer program is stored in the communication device, and the computer program is used to enable the communication device to execute the method for migrating a mobile IAB node provided in the above-mentioned method embodiments.

[0349] Specifically, the above-mentioned communication device provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects that are the same as the method embodiments in this embodiment will not be described in detail here.

[0350] In some embodiments, a chip product is further provided. A computer program is stored in the chip product. The computer program is used to enable the chip product to execute the method for migrating a mobile IAB node provided in the above method embodiments.

[0351] Specifically, the above-mentioned chip product provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0352] It should also be noted that the terms "first", "second", etc. in the embodiments of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more.

[0353] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0354] "Determine B based on A" in the embodiments of the present application means that the factor A should be considered when determining B. It is not limited to "B can be determined based on A alone", but should also include: "Determine B based on A and C", "Determine B based on A, C and E", "Determine C based on A, and further determine B based on C", etc. In addition, it can also include taking A as a condition for determining B, for example, "When A meets the first condition, use the first method to determine B"; for another example, "When A meets the second condition, determine B", etc.; for another example, "When A meets the third condition, determine B based on the first parameter", etc. Of course, it can also be a condition that takes A as a factor for determining B, for example, "When A meets the first condition, use the first method to determine C, and further determine B based on C", etc.

[0355] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0356] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0357] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0358] The network device involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0359] Network devices and terminal devices can each use one or more antennas for multi-input multi-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoding transmission or beamforming transmission, etc.

[0360] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0361] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0362] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0363] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0364] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for migrating a mobile IAB node, characterized in that: Applied to IAB nodes for integrated mobile access and backhaul, including: Acquire a first IAB identifier allocated to the mobile IAB node by an anchor point centralized unit donor-CU of a distribution unit IAB-DU of the mobile IAB node; Sending the first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the terminal IAB-MT of the mobile IAB node; The first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are used by the donor-CU of the IAB-MT of the mobile IAB node to send the first IAB identifier and the second IAB identifier allocated to the IAB node by the donor-CU of the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

2. The method for migrating a mobile IAB node according to claim 1, characterized in that: Acquiring a first IAB identifier allocated to the mobile IAB node by a donor-CU of an IAB-DU of the mobile IAB node includes: The first IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-DU of the mobile IAB node is obtained through an F1 interface F1AP message.

3. The method for migrating a mobile IAB node according to claim 1, characterized in that: Sending the first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the IAB-MT of the mobile IAB node includes: The first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are sent to the donor-CU of the IAB-MT of the mobile IAB node through an RRC message.

4. The method for migrating a mobile IAB node according to any one of claims 1 to 3, characterized in that: The donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

5. The method for migrating a mobile IAB node according to any one of claims 1 to 3, characterized in that: The donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

6. The method for migrating a mobile IAB node according to any one of claims 1 to 3, characterized in that: The first IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by the donor-CU of the IAB-DU of the mobile IAB node to the IAB-MT of the mobile IAB node.

7. A method for migrating a mobile IAB node, characterized in that: The donor-CU of the IAB-MT applied to the mobile IAB node includes: Acquire a first IAB identifier allocated to the mobile IAB node by a donor-CU of the IAB-DU of the mobile IAB node and a gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node sent by the mobile IAB node; Allocating a second IAB identifier to the mobile IAB node; The first IAB identifier and the second IAB identifier are sent to the donor-CU of the IAB-DU of the mobile IAB node; the first IAB identifier and the second IAB identifier are used by the donor-CU of the IAB-DU of the mobile IAB node to initiate an IAB TMM process to the donor-CU of the IAB-MT of the mobile IAB node.

8. The method for migrating a mobile IAB node according to claim 7, characterized in that: The method further comprises: The new air interface cell global identity NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node is sent to the donor-CU of the IAB-DU of the mobile IAB node.

9. The method for migrating a mobile IAB node according to claim 7, characterized in that: The method further comprises: The tracking area identifier TAI of the serving cell accessed by the IAB-MT of the mobile IAB node is sent to the donor-CU of the IAB-DU of the mobile IAB node.

10. The method for migrating a mobile IAB node according to claim 7, characterized in that: The method further comprises: Sending authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node.

11. The method for migrating a mobile IAB node according to any one of claims 7 to 10, characterized in that: The donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

12. The method for migrating a mobile IAB node according to any one of claims 7 to 10, characterized in that: The donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

13. The method for migrating a mobile IAB node according to any one of claims 7 to 10, characterized in that: The first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network are carried through an Xn interface application protocol XnAP message; Sending the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node includes: Taking the gNB-ID of the donor-CU of the IAB-MT of the mobile IAB node as the source radio access network RAN ​​node ID, and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node as the target RAN node ID, the XnAP message is encapsulated in a first NG interface application protocol NGAP message and sent to the access and mobility management function AMF network element, and then the AMF network element forwards the XnAP message to the donor-CU of the IAB-DU of the mobile IAB node through a second NGAP message.

14. The method for migrating a mobile IAB node according to claim 7, characterized in that: The second IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by the donor-CU of the IAB-MT of the mobile IAB node to the IAB-MT of the mobile IAB node.

15. A method for migrating a mobile IAB node, characterized in that: The donor-CU of the IAB-DU applied to the mobile IAB node includes: sending, to the mobile IAB node, a first IAB identifier allocated to the mobile IAB node; receiving a first IAB identifier sent by a donor-CU of an IAB-MT of the mobile IAB node and a second IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-MT of the mobile IAB node; An Xn IAB TMM process is initiated based on the first IAB identifier and the second IAB identifier to request the donor-CU of the IAB-MT of the mobile IAB node to configure path resources required for transmission services for the mobile IAB node.

16. The method for migrating a mobile IAB node according to claim 15, characterized in that: The method further comprises: Receive the NCGI of the serving cell to which the IAB-MT of the mobile IAB node accesses, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

17. The method for migrating a mobile IAB node according to claim 15, characterized in that: The method further comprises: Receive the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

18. The method for migrating a mobile IAB node according to claim 15, characterized in that: The method further comprises: Receive the authentication status information of the mobile IAB node from the core network, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

19. The method for migrating a mobile IAB node according to any one of claims 15 to 18, characterized in that: The donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

20. The method for migrating a mobile IAB node according to any one of claims 15 to 18, characterized in that: The donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

21. A mobile IAB node, characterized in that: Including memory, transceiver, processor; A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Acquire a first IAB identifier allocated to the mobile IAB node by an anchor point centralized unit donor-CU of a distribution unit IAB-DU of the mobile IAB node; Sending the first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the terminal IAB-MT of the mobile IAB node; The first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are used by the donor-CU of the IAB-MT of the mobile IAB node to send the first IAB identifier and the second IAB identifier allocated to the IAB node by the donor-CU of the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

22. The mobile IAB node according to claim 21, characterized in that: Acquiring a first IAB identifier allocated to the mobile IAB node by a donor-CU of an IAB-DU of the mobile IAB node includes: The first IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-DU of the mobile IAB node is obtained through an F1 interface F1AP message.

23. The mobile IAB node according to claim 21, characterized in that: Sending the first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the IAB-MT of the mobile IAB node includes: The first IAB identifier and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are sent to the donor-CU of the IAB-MT of the mobile IAB node through an RRC message.

24. The mobile IAB node according to any one of claims 21 to 23, characterized in that: The donor-CU of the IAB-DU of the mobile IAB node is a target donor-CU for migration of the IAB-DU of the mobile IAB node.

25. The mobile IAB node according to any one of claims 21 to 23, characterized in that: The donor-CU of the IAB-MT of the mobile IAB node is a target donor-CU for migration of the IAB-MT of the mobile IAB node.

26. The mobile IAB node according to any one of claims 21 to 23, characterized in that: The first IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by the donor-CU of the IAB-DU of the mobile IAB node to the IAB-MT of the mobile IAB node.

27. A donor-CU of an IAB-MT of a mobile IAB node, characterized in that: Including memory, transceiver, processor; A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Acquire a first IAB identifier allocated to the mobile IAB node by a donor-CU of the IAB-DU of the mobile IAB node and a gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node sent by the mobile IAB node; Allocating a second IAB identifier to the mobile IAB node; The first IAB identifier and the second IAB identifier are sent to the donor-CU of the IAB-DU of the mobile IAB node; the first IAB identifier and the second IAB identifier are used by the donor-CU of the IAB-DU of the mobile IAB node to initiate an IAB TMM process to the donor-CU of the IAB-MT of the mobile IAB node.

28. The donor-CU of the IAB-MT of the mobile IAB node according to claim 27, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: The new air interface cell global identity NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node is sent to the donor-CU of the IAB-DU of the mobile IAB node.

29. The donor-CU of the IAB-MT of the mobile IAB node according to claim 27, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: The tracking area identifier TAI of the serving cell accessed by the IAB-MT of the mobile IAB node is sent to the donor-CU of the IAB-DU of the mobile IAB node.

30. The donor-CU of the IAB-MT of the mobile IAB node according to claim 27, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: Sending authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node.

31. The donor-CU of the IAB-MT of the mobile IAB node according to any one of claims 27 to 30, characterized in that: The first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network are carried through an Xn interface application protocol XnAP message; Sending the first IAB identifier and the second IAB identifier, the NCGI of the serving cell accessed by the IAB-MT of the mobile IAB node, the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, or the authentication status information of the mobile IAB node by the core network to the donor-CU of the IAB-DU of the mobile IAB node includes: Taking the gNB-ID of the donor-CU of the IAB-MT of the mobile IAB node as the source radio access network RAN ​​node ID, and the gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node as the target RAN node ID, the XnAP message is encapsulated in a first NG interface application protocol NGAP message and sent to the access and mobility management function AMF network element, and then the AMF network element forwards the XnAP message to the donor-CU of the IAB-DU of the mobile IAB node through a second NGAP message.

32. The donor-CU of the IAB-MT of the mobile IAB node according to claim 27, characterized in that: The second IAB identifier is an Xn interface application protocol terminal identifier XnAP UE ID allocated by the donor-CU of the IAB-MT of the mobile IAB node to the IAB-MT of the mobile IAB node.

33. A donor-CU of an IAB-DU of a mobile IAB node, characterized in that: Including memory, transceiver, processor; A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: sending, to the mobile IAB node, a first IAB identifier allocated to the mobile IAB node; receiving a first IAB identifier sent by a donor-CU of an IAB-MT of the mobile IAB node and a second IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-MT of the mobile IAB node; An Xn IAB TMM process is initiated based on the first IAB identifier and the second IAB identifier to request the donor-CU of the IAB-MT of the mobile IAB node to configure path resources required for transmission services for the mobile IAB node.

34. The donor-CU of the IAB-DU of the mobile IAB node according to claim 33, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: Receive the NCGI of the serving cell to which the IAB-MT of the mobile IAB node accesses, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

35. The donor-CU of the IAB-DU of the mobile IAB node according to claim 33, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: Receive the TAI of the serving cell accessed by the IAB-MT of the mobile IAB node, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

36. The donor-CU of the IAB-DU of the mobile IAB node according to claim 33, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: Receive the authentication status information of the mobile IAB node from the core network, which is sent by the donor-CU of the IAB-MT of the mobile IAB node.

37. A device for migrating a mobile IAB node, characterized in that: include: A first acquisition module, configured to acquire a first IAB identifier allocated to the mobile IAB node by a donor-CU of a distribution unit IAB-DU of the mobile IAB node; A first sending module, configured to send the first IAB identifier and a unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node to the donor-CU of the terminal IAB-MT of the mobile IAB node; The first IAB identifier and the unique identifier gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node are used by the donor-CU of the IAB-MT of the mobile IAB node to send the first IAB identifier and the second IAB identifier allocated to the IAB node by the donor-CU of the IAB-MT of the mobile IAB node to the donor-CU of the IAB-DU of the mobile IAB node.

38. A device for migrating a mobile IAB node, characterized in that: include: A second acquisition module is used to acquire a first IAB identifier allocated to the mobile IAB node by a donor-CU of the IAB-DU of the mobile IAB node and a gNB-ID of the donor-CU of the IAB-DU of the mobile IAB node sent by the mobile IAB node; A second sending module, configured to allocate a second IAB identifier to the mobile IAB node; The third sending module is used to send the first IAB identifier and the second IAB identifier to the donor-CU of the IAB-DU of the mobile IAB node; the first IAB identifier and the second IAB identifier are used by the donor-CU of the IAB-DU of the mobile IAB node to initiate an IAB TMM process to the donor-CU of the IAB-MT of the mobile IAB node.

39. A device for migrating a mobile IAB node, characterized in that: include: A fourth sending module, configured to send a first IAB identifier allocated to the mobile IAB node to the mobile IAB node; A first receiving module is configured to receive a first IAB identifier sent by a donor-CU of an IAB-MT of the mobile IAB node and a second IAB identifier allocated to the mobile IAB node by the donor-CU of the IAB-MT of the mobile IAB node; The initiating module is configured to initiate an Xn IAB TMM process based on the first IAB identifier and the second IAB identifier to request the donor-CU of the IAB-MT of the mobile IAB node to configure path resources required for transmission services for the mobile IAB node.

40. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method for migrating a mobile IAB node according to any one of claims 1 to 6.

41. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method for migrating a mobile IAB node according to any one of claims 7 to 14.

42. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method for migrating a mobile IAB node according to any one of claims 15 to 20.

Images