WO2023010367A1

WO2023010367A1 - Terminal device transfer method, apparatus, and system

Info

Publication number: WO2023010367A1
Application number: PCT/CN2021/110688
Authority: WO
Inventors: 路杨
Original assignee: 富士通株式会社; 路杨
Priority date: 2021-08-04
Filing date: 2021-08-04
Publication date: 2023-02-09

Abstract

Provided in the embodiments of the present application are a terminal device transfer method, apparatus, and system, wherein a first IAB node is migrated from a first host distribution unit (CU) to a second host CU, the method comprising: after receiving an F1 connection establishment command sent by the first host CU, the first IAB node makes a second distribution unit (DU) initiate establishment of an F1 connection with the second host CU, in order to transfer the terminal device from a first cell of a first DU of the first IAB node to a second cell of the second DU, wherein the first DU has established an F1 connection with the first host CU.

Description

Terminal equipment transfer method, device and system

technical field

This application relates to the field of communication.

Background technique

Future seamless cellular network deployment requires very flexible and ultra-dense NR cell deployment. Ultra-dense network is one of the goals of 5G. Deploying a new wireless (new radio, NR) network without wired backhaul is crucial for realizing 5G ultra-dense Networking is very important. Since 5G millimeter waves reduce the coverage of cells, the wireless self-backhaul system needs to be multi-hop to meet the deployment requirements. 5G's high bandwidth, massive multiple-input multiple-output MIMO and beam system make it easier for 5G to develop a wireless self-backhaul system for ultra-dense NR cells than LTE. In order to develop this multi-hop system with wireless self-backhaul, 3GPP R16 started the research and standardization of the IAB (Integrated access and backhaul) project.

Figure 1 is a schematic diagram of the IAB system. As shown in Figure 1, in the IAB system, the access and backhaul use the Uu air interface wireless transmission of NR, and the relay node supports both access and backhaul functions , the wireless transmission link of the relay node multiplexes the access link (access link) and the backhaul link (backhaul link) in the time domain, frequency domain or air domain, and the access link and the backhaul link can use the same or a different frequency band.

In the IAB network architecture as follows, a relay node refers to an IAB-node (IAB node), which supports both access and backhaul functions. The last hop access node on the network side is called IAB-donnor (IAB host), which supports gNB function and supports IAB-node access. All UE data can be sent back to IAB-Donor via IAB-node via one or more hops.

The function of IAB-node is divided into two parts, one part is gNB-DU function, called IAB-DU (IAB distribution unit), and the other part is UE function, called IAB-MT (mobile terminal). The IAB-DU implements the network-side device function, connects to the downstream child IAB-node (child IAB node), provides NR air interface access to the UE and the downstream child IAB-node, and establishes an F1 connection with the IAB donor-CU. IAB-MT implements part of the terminal equipment functions and connects to the upstream parent IAB-node (parent IAB node) or IAB-donor DU. IAB-MT includes physical layer, layer 2, RRC (Radio Resource Control, radio resource control) and NAS (Non-Access Stratum, non-access stratum) layer function, and indirectly connected to IAB donor-CU (IAB host centralized unit) and core network (Core Network, CN).

It should be noted that the above introduction to the technical background is only for the convenience of a clear and complete description of the technical solution of the present application, and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are known to those skilled in the art just because these solutions are described in the background technology section of this application.

Contents of the invention

If an IAB-node of the IAB network disconnects from the original parent IAB-node, connects to the new parent IAB-node, or, when the IAB-node remains connected to the original parent node and increases the connection to a new parent node When a connection becomes a dual connection, it will cause a change in the topology of the IAB network.

Fig. 2 is a schematic diagram of network topology changes caused by IAB-node movement. As shown in Figure 2, after IAB-node5 switches from the cell under IAB-node3 to the cell under IAB-node 4, the F1 transmission path from IAB-node5 and its downstream child node IAB-node 6 to donor-CU passes through IAB -node1 and IAB-node 2 have changed through IAB-node2 and IAB-node 4, and the network topology has changed. Or, after IAB-node5 increases the connection to IAB-node 4 and becomes a dual connection, an F1 transmission path from IAB-node5 and its downstream child node IAB-node 6 to donor-CU is added through IAB-node1 and IAB- node 2 path, the network topology changes.

R16NR has standardized the network update (topology adaptation) process when the IAB-node moves under the same donor-CU. When the IAB-node is migrated under the same donor-CU, only the migrated IAB-node needs to be switched to the new parent node, and the F1 transmission path is migrated to the new parent node, and the UE serving the migrated IAB-node does not need to switch . However, if the migrating IAB-node moves between two different donor-CUs, in addition to migrating the IAB-MT of the IAB-node needs to switch to the new donor-CU, the UE of the migrating IAB-node service may need to switch to the new donor -CU. This requires the establishment of an F1 connection between the IAB-DU of the migrated IAB-node and the new donor-CU. The migrated IAB-DU serves both the original donor-CU and the new donor-CU. There are two The logical IAB-DU is respectively connected to the original donor-CU and the new donor-CU and establishes an F1 connection. When the UE served by the migrating IAB-node switches to a new donor-CU, it is transferred from the cell of the logical IAB-DU connected to the original donor-CU to the cell of the logical IAB-DU connected to the new donor-CU.

However, the inventors found that there is currently no method for triggering the establishment of an F1 connection between the IAB node and the new donor-CU, so that it is impossible for the terminal device to communicate with the new donor in the cell of the logic IAB-DU connected to the original donor-CU. - Convenient transfer of cells of logical IAB-DUs to which CUs are connected.

In order to solve at least one of the above problems or other similar problems, embodiments of the present application provide a terminal device transfer method, device, and system.

According to the first aspect of the embodiments of the present application, there is provided an apparatus for migrating a terminal device, the apparatus is set in a first IAB node, wherein the first IAB node is migrated from the first host distribution unit (CU) to For a second host CU, the device includes: a first establishing unit, which causes a second distribution unit (DU) to initiate a connection with the second host CU after receiving the F1 connection establishment instruction sent by the first host CU Establishment of an F1 connection in order to transfer a terminal device from the first cell of the first DU of the first IAB node to the second cell of the second DU; wherein the first DU has been connected to the first parent CU There is an F1 connection established.

According to the second aspect of the embodiments of the present application, there is provided a device for migrating a terminal device, the device is set in the first host CU, and the device is applied when the first IAB node migrates from the first host CU to the second host CU When two host CUs are used, the device includes: a sixth sending unit, which sends an F1 connection establishment instruction to the first IAB node, and the F1 connection establishment instruction is used to instruct the first IAB node to communicate with the first IAB node through the second DU The second host CU establishes an F1 connection, so as to transfer the terminal device from the first cell of the first DU of the first IAB node to the second cell of the second DU; wherein, the first host CU and the The first DU of the first IAB node has established an F1 connection.

According to a third aspect of the embodiments of the present application, there is provided a terminal device transfer device, a terminal device transfer device, the device is set in the second host CU, wherein the first IAB node is migrated from the first host CU To the second host CU, the apparatus includes: a second establishment unit, which establishes an F1 connection with the second DU of the first IAB node, so as to transfer the terminal device from the first DU of the first IAB node The first cell of the second DU is transferred to the second cell of the second DU; the establishment of the F1 connection is initiated by the first IAB node after receiving the F1 connection establishment instruction sent by the first donor CU; wherein, the first The second host CU has established an F1 connection with the first DU of the first IAB node.

According to a fourth aspect of the embodiments of the present application, there is provided a network device, the network device is a first IAB node, and the network device includes the apparatus according to the first aspect of the embodiments of the present application.

According to a fifth aspect of the embodiments of the present application, there is provided a network device, the network device is a first host, and the network device includes the apparatus according to the second aspect of the embodiments of the present application.

According to a sixth aspect of the embodiments of the present application, there is provided a network device, the network device is a second host, and the network device includes the apparatus according to the third aspect of the embodiments of the present application.

According to a seventh aspect of the embodiments of the present application, there is provided a method for transferring a terminal device, wherein the first IAB node is migrated from a first host distribution unit (CU) to a second host CU, and the method includes: the first After receiving the F1 connection establishment instruction sent by the first host CU, the IAB node makes the second distribution unit (DU) initiate the establishment of the F1 connection with the second host CU, so as to transfer the terminal device from the first host CU The first cell of the first DU of an IAB node is transferred to the second cell of the second DU; wherein, the first DU has established an F1 connection with the first parent CU.

According to an eighth aspect of the embodiments of the present application, there is provided a terminal device transfer method, the method is applied when a first IAB node migrates from the first host CU to a second host CU, the method includes: The first host CU sends an F1 connection establishment instruction to the first IAB node, and the F1 connection establishment instruction is used to instruct the first IAB node to establish an F1 connection with the second host CU through the second DU, so that transferring the terminal device from the first cell of the first DU of the first IAB node to the second cell of the second DU; wherein, the first parent CU and the first DU of the first IAB node have established a relationship F1 connection.

According to a ninth aspect of the embodiments of the present application, a terminal device transfer method is provided, wherein the first IAB node is migrated from the first host CU to the second host CU, and the method includes: the second host CU and the second host CU An F1 connection is established between the second DUs of the first IAB node, so as to transfer the terminal equipment from the first cell of the first DU of the first IAB node to the second cell of the second DU; the F1 connection The establishment is initiated by the first IAB node after receiving the F1 connection establishment instruction sent by the first host CU; wherein, the second host CU has established an F1 connection with the first DU of the first IAB node .

According to a tenth aspect of the embodiments of the present application, there is provided a computer-readable program, wherein when the program is executed in the transfer device of the terminal device or the network device, the program causes the terminal device The transfer device or network device executes the terminal device transfer method described in the seventh aspect, the eighth aspect, or the ninth aspect of the embodiments of the present invention.

According to an eleventh aspect of the embodiments of the present invention, there is provided a storage medium storing a computer-readable program, wherein the computer-readable program causes a transfer device of a terminal device or a network device to execute the seventh aspect of the embodiments of the present invention Or the terminal device transfer method described in the eighth aspect or the ninth aspect.

One of the beneficial effects of the embodiment of the present application is that: the first host CU sends an F1 connection establishment instruction to the first IAB node, which is used to instruct the first IAB node to establish an F1 connection with the second host CU through the second DU, which can facilitate The terminal device is transferred from the first cell of the first DU of the first IAB node to the second cell of the second DU, thereby providing a terminal device when the first IAB node migrates from the first host CU to the second host CU An efficient mechanism for transitioning from a first host CU to a second host CU.

With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the application may be employed. It should be understood that the embodiments of the present application are not limited thereby in scope. Embodiments of the present application include many changes, modifications and equivalents within the spirit and scope of the appended notes.

Features described and/or illustrated with respect to one embodiment can be used in the same or similar manner in one or more other embodiments, in combination with, or instead of features in other embodiments .

It should be emphasized that the term "comprising/comprising" when used herein refers to the presence of a feature, integer, step or component, but does not exclude the presence or addition of one or more other features, integers, steps or components.

Description of drawings

Elements and features described in one drawing or one embodiment of an embodiment of the present application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, like numerals indicate corresponding parts in the several figures and may be used to indicate corresponding parts used in more than one embodiment.

The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation of the present application, and explain the principle of the present application together with the text description. Apparently, the drawings in the following description are only some embodiments of the present application, and those skilled in the art can obtain other drawings according to these drawings without creative efforts. In the attached picture:

Fig. 1 is a schematic diagram of the IAB system;

Figure 2 is a schematic diagram of network topology changes caused by IAB-node movement;

FIG. 3 is a schematic diagram of the IAB architecture of the SA mode;

FIG. 4 is a schematic diagram of the IAB architecture of the EN-DC mode;

Fig. 5 is a schematic diagram of a parent node (parent IAB-node) and a child node (child IAB-node);

6 is a schematic diagram of the F1-U protocol stack of the IAB system;

7 is a schematic diagram of the F1-C protocol stack of the IAB system;

Fig. 8 is a schematic diagram of a terminal device transfer method according to Embodiment 1 of the present application

Fig. 9 is another schematic diagram of the transfer method of the terminal device according to Embodiment 1 of the present application

FIG. 10 is another schematic diagram of the terminal device transfer method in Embodiment 1 of the present application according to Embodiment 1 of the present application;

FIG. 11 is another schematic diagram of the terminal device transfer method in Embodiment 1 of the present application according to Embodiment 1 of the present application;

FIG. 12 is a schematic diagram of a terminal device transfer method according to Embodiment 2 of the present application;

FIG. 13 is another schematic diagram of a terminal device transfer method according to Embodiment 2 of the present application;

FIG. 14 is another schematic diagram of the terminal device transfer method according to Embodiment 2 of the present application;

FIG. 15 is a schematic diagram of a terminal device transfer method according to Embodiment 3 of the present application;

FIG. 16 is another schematic diagram of a terminal device transfer method according to Embodiment 3 of the present application;

FIG. 17 is a schematic diagram of a terminal device transfer method according to Embodiment 4 of the present application;

FIG. 18 is a schematic diagram of a terminal device transfer method applied to scenario 1 according to Embodiment 4 of the present application;

FIG. 19 is another schematic diagram of a terminal device transfer method applied to scenario 1 according to Embodiment 4 of the present application;

FIG. 20 is a schematic diagram of a terminal device transfer method applied to scenario 2 according to Embodiment 4 of the present application;

FIG. 21 is another schematic diagram of a terminal device transfer method applied to scenario 2 according to Embodiment 4 of the present application;

FIG. 22 is a schematic diagram of a transfer device of a terminal device according to Embodiment 5 of the present application;

FIG. 23 is a schematic diagram of a transfer device of a terminal device according to Embodiment 6 of the present application;

FIG. 24 is a schematic diagram of a transfer device of a terminal device according to Embodiment 7 of the present application;

FIG. 25 is a schematic block diagram of a system configuration of a network device according to Embodiment 8 of the present application;

FIG. 26 is a schematic block diagram of the system configuration of the network device according to Embodiment 9 of the present application;

FIG. 27 is a schematic block diagram of a system configuration of a network device according to Embodiment 10 of the present application;

Fig. 28 is a schematic diagram of a communication system according to Embodiment 11 of the present application.

Detailed ways

The foregoing and other features of the present application will become apparent from the following description, taken with reference to the accompanying drawings. In the specification and drawings, specific embodiments of the present application are specifically disclosed, which indicate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments, on the contrary, the present application The application includes all amendments, variations and equivalents falling within the scope of the appended notes.

In this embodiment of the application, the terms "first", "second", etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or time order of these elements, and these elements should not be referred to by these terms restricted. The term "and/or" includes any and all combinations of one or more of the associated listed items. The terms "comprising", "including", "having" and the like refer to the presence of stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.

In the embodiments of the present application, the singular forms "a", "the" and the like include plural forms, which should be broadly understood as "one" or "a class" and not limited to the meaning of "one"; in addition, the term "all The above should be understood to include both the singular and the plural, unless the context clearly dictates otherwise. In addition, the term "based on" should be understood as "at least in part based on..." and the term "based on" should be understood as "at least in part based on...", unless the context clearly indicates otherwise.

In this embodiment of the application, the term "communication network" or "wireless communication network" may refer to a network conforming to any of the following communication standards, such as Long Term Evolution (LTE, Long Term Evolution), Enhanced Long Term Evolution (LTE-A, LTE- Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access), etc.

Moreover, the communication between devices in the communication system can be carried out according to any stage of communication protocol, for example, it can include but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR, New Radio), etc., and/or other communication protocols that are currently known or will be developed in the future.

In this embodiment of the present application, the term "network device" refers to, for example, a device in a communication system that connects a user equipment to a communication network and provides services for the user equipment. Network devices may include but are not limited to the following devices: "node" and/or "donor" under the IAB architecture, base station (BS, Base Station), access point (AP, Access Point), sending and receiving Point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) etc.

Among them, the base station may include but not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include Remote Radio Head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low-power node (such as femto, pico, etc.). And the term "base station" may include some or all of their functions, each base station may provide communication coverage for a particular geographic area. The term "cell" can refer to a base station and/or its coverage area depending on the context in which the term is used.

In the embodiment of the present application, the term "User Equipment" (UE, User Equipment) refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be called "Terminal Equipment" (TE, Terminal Equipment). A terminal device may be fixed or mobile, and may also be called a mobile station (MS, Mobile Station), a terminal, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, etc. For example, a terminal device served by an IAB node or an IAB host under the IAB architecture.

Among them, the terminal equipment may include but not limited to the following equipment: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication equipment, handheld equipment, machine-type communication equipment, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.

For another example, in scenarios such as the Internet of Things (IoT, Internet of Things), the terminal device can also be a machine or device for monitoring or measurement, such as but not limited to: a machine type communication (MTC, Machine Type Communication) terminal, Vehicle communication terminal, device to device (D2D, Device to Device) terminal, machine to machine (M2M, Machine to Machine) terminal, etc.

In the IAB system, the IAB-node can access the network through an independent networking (SA, Standalone) mode or a non-independent networking (EN-DC, E-UTRA-NRDualConnectivity) mode. FIG. 3 is a schematic diagram of an IAB architecture in SA mode. Fig. 3 is a schematic diagram of the IAB architecture of the EN-DC mode. As shown in Figure 4, in the dual connectivity mode, the IAB node is connected to a MeNB through E-UTRA, and the IAB host serves as the SgNB to terminate X2-C.

Fig. 5 is a schematic diagram of an IAB node (IAB-node), a parent node (parent IAB-node) and a child node (child IAB-node). As shown in FIG. 4 , the IAB-DU of the IAB node is connected to the IAB-MT of the child node as the network side, and the IAB-MT of the IAB node is connected to the IAB-DU of the parent node as the terminal side. .

Fig. 6 is a schematic diagram of the F1 user plane (F1-U) protocol stack between the IAB-DU and the IAB-Donor CU. Figure 7 is a schematic diagram of the F1 control plane (F1-C) protocol stack between the IAB-DU and the IAB-Donor CU.

As shown in Figure 6 and Figure 7, F1-U and F1-C are established on the transmission (IP) layer between IAB-DU and IAB-Donor-CU, and in Figure 6 and Figure 7, after two hops of wireless transmission and one-hop wired return. On the backhaul link, the transport (IP) layer is carried on the Backhaul Adaptive Protocol (BAP) sublayer, and the BAP entity in the IAB-node implements the routing function of the IAB system, and the IAB-Donor CU provides the routing table. BAP PDU (Protocol Data Unit) is transmitted in the RLC (Radio Link Control) channel of the backhaul link. Multiple RLC channels of the backhaul link can be configured by IAB-Donor to carry different priorities and QoS (Quality of Service) ) business, the BAP entity maps the BAP PDU to different backhaul RLC channels.

Example 1

Embodiment 1 of the present application provides a transfer method of a terminal device, which is described from the side of the first IAB node.

This method is applied to the situation where the first IAB node migrates from the first host distribution unit (CU) to the second host CU. FIG. 8 is a schematic diagram of a terminal device transfer method according to Embodiment 1 of the present application. As shown in FIG. 8, the method includes:

Step 801: After receiving the F1 connection establishment instruction sent by the first host CU, the first IAB node makes the second distribution unit (DU) initiate the establishment of the F1 connection with the second host CU, so as to transfer the terminal device from The first cell of the first DU of the first IAB node is transferred to the second cell of the second DU;

Wherein, the first DU has established an F1 connection with the first host CU.

In this way, the terminal device can be conveniently transferred from the first cell of the first DU of the first IAB node to the second cell of the second DU, thus providing a method for the first IAB node to migrate from the first host CU to the second host When the CU is an effective mechanism, the terminal device is also transferred from the first host CU to the second host CU.

For example, as shown in Figure 8, the method also includes:

Step 802: the first IAB node receives the F1 connection establishment instruction sent by the first host CU.

In the embodiment of this application, the first IAB node is the IAB node for migration, the first host is the original host of the first IAB node, that is, the source host of the migration, and the second host is the new host of the first IAB node, that is, the migration target host.

Correspondingly, the first host CU is the CU of the first host, that is, the CU of the original host, and the second host CU is the CU of the second host, that is, the CU of the new host.

In this embodiment of the present application, the F1 connection establishment instruction is sent by the first owner CU to the first IAB node through an RRC reconfiguration message or an F1AP message.

For example, in step 802, the first IAB node receives the F1 connection establishment instruction sent by the first donor CU through an RRC reconfiguration message or an F1AP message.

In step 802, after receiving the F1 connection establishment instruction sent by the first host CU, the first IAB node makes the second distribution unit (DU) initiate the establishment of the F1 connection with the second host CU; thus, the method Can also include:

Step 803: the second DU of the first IAB node establishes an F1 connection with the second host CU.

FIG. 9 is another schematic diagram of the terminal device transfer method according to Embodiment 1 of the present application. As shown in FIG. 9, the method includes:

Step 901: the first IAB node receives the F1 connection establishment instruction sent by the first host CU;

Step 902: the second DU of the first IAB node initiates the establishment of the F1 connection with the second host CU;

Step 903: the second DU of the first IAB node establishes an F1 connection with the second host CU.

In this embodiment of the application, after step 903, the method may further include:

Step 904: the first IAB node sends at least one of the second PCI, the second downlink frequency point and the second NCGI of the second cell to the first host CU;

Because there may be more than one cell in the first DU and the second DU, after step 903, the method may further include:

Step 905: the first IAB node sends the correspondence between the NCGI of the first cell and the second NCGI of the second cell to the first donor CU.

In this way, the first host CU is informed that the first IAB node has established an F1 connection with the second host CU, and requests the second host CU to transfer the terminal equipment accessed to the first cell to the second cell.

In this embodiment of the application, PCI is a physical cell ID (Physical Cell ID). NCGI is NR Cell Global Identity, which is the unique identifier of a cell in the world.

Fig. 10 is another schematic diagram of the terminal device transfer method in Embodiment 1 of the present application according to Embodiment 1 of the present application. As shown in Fig. 10 , the method includes:

Step 1001: the first IAB node receives the F1 connection establishment instruction sent by the first host CU;

Step 1002: the second DU of the first IAB node initiates the establishment of the F1 connection with the second host CU;

Different from the steps in Figure 9, as shown in Figure 10, the method may also include:

Step 1003: When the second DU establishes an F1 connection with the second host CU, the first IAB node sends the first PCI, the first downlink frequency point, and the first NCGI of the first cell through an F1 establishment request message. at least one of , and send it to the second host CU.

In this way, after the second DU of the first IAB node establishes an F1 connection with the second host CU, the second host CU can send the information of the second cell to the first host CU, so that the first host CU can learn about the first IAB The node has established an F1 connection with the second donor CU, and requests the second donor CU to transfer the terminal equipment connected to the first cell to the second cell.

Because there may be more than one first cell and second cell in the first DU and the second DU, in this embodiment of the application, the F1 Setup Request message may also include: the first NCGI of the first cell and the first NCGI of the second cell Second NCGI correspondence.

In this embodiment of the present application, the first IAB node may share the same air interface resources for the first cell of the first DU and the second cell of the second DU.

In this way, when the terminal device is transferred from the first cell of the first DU connected to the first parent CU to the second cell of the second DU connected to the second parent CU, the first IAB node does not need to be a cell of two DUs Two sets of different air interface resources are prepared at the same time, which improves the utilization efficiency of air interface resources.

However, in this embodiment of the application, it is also possible that when the first IAB node migrates from the first host CU to the second host CU, the first cell of the first DU and the second cell of the second DU use different air interface resources. This embodiment of the application does not limit this.

In this embodiment, if the first cell of the first DU and the second cell of the second DU share the same air interface resources, the air interface resources can only send signals related to one cell, and the air interface resources need to be transmitted from the first cell The related signal is switched to transmit the signal related to the second cell.

In the embodiment of the present application, as shown in FIG. 9, if the first cell of the first DU and the second cell of the second DU share the same air interface resource, the method may further include:

Step 906: the first IAB node receives an air interface resource conversion instruction from the first host CU;

Step 907: The first IAB node switches air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell.

In this embodiment of the present application, as shown in FIG. 9 , before step 906, the first donor CU needs to know whether the first cell and the second cell use the same air interface resources. The method can also include:

Step 908: The first IAB node sends an air interface resource sharing indication to the second donor CU, where the air interface resource sharing indication is used to indicate that the first cell of the first DU and the second cell of the second DU share the same air interface resources.

In this embodiment, if the first cell of the first DU and the second cell of the second DU share the same air interface resources, the first PCI and the first downlink frequency of the first cell are the same as those of the second cell. The second PCI and the second downlink frequency points may be the same or different, but since the two cells belong to different host CUs, the NCGIs of the two cells must be different.

In this embodiment, the above steps enable the first host CU to know the second PCI and the second downlink frequency of the second cell, so as to determine whether the PCI and the downlink frequency of the first cell and the second cell are the same. If the PCI and downlink frequencies of the first cell and the second cell are the same, when the air interface resources are switched from sending signals related to the first cell to sending signals related to the second cell, the air interface resources can continue to serve the original connection to the first cell. For the terminal equipment in the cell, even if the public configurations of the two cells are different (including NCGI), the terminal equipment originally connected to the first cell will not experience radio link failure. In this case, it may not be possible to use a dedicated RRC message (such as an RRC reconfiguration message for handover) to configure the public cell configuration of the second cell to the terminal device. After connecting to the second cell, the terminal device needs to read the first System information of the second cell to obtain the public cell configuration of the second cell.

For example, as shown in FIG. 9, before step 907, the method may further include:

Step 909: The first IAB node receives a system information change request from the first host CU, and sends a system information change instruction to the terminal device, so as to trigger the terminal device to receive system information related to the second cell. In this embodiment of the present application, the system information change request may be included in the air interface resource switching instruction, that is, step 906 and step 909 may be performed in combination. However, the system information change request and the air interface resource switching instruction may also be sent separately, that is, step 906 and step 909 are executed separately.

In this embodiment, if the PCIs of the first cell and the second cell are different or the downlink frequencies are different, when the air interface resources are switched from sending signals related to the first cell to sending signals related to the second cell, the air interface resources cannot continue to serve The terminal equipment originally connected to the first cell, and the terminal equipment originally connected to the first cell may experience radio link failure. In this case, the RRC reconfiguration message for handover may be used to trigger the terminal device to transfer from the first cell to the second cell, and the RRC reconfiguration message may be used to configure the public cell configuration of the second cell to the terminal device.

Step 910: The first IAB node receives a downlink F1AP message sent by the first host CU through the first DU, where the downlink F1AP message includes an RRC reconfiguration message for the terminal device;

Step 911: the first IAB node sends the RRC reconfiguration message to the terminal device;

Wherein, the RRC reconfiguration message is used to transfer the terminal equipment from the first cell to the second cell; since the first cell and the second cell belong to different owner CUs, the terminal equipment must update the A master key, the RRC reconfiguration message at least includes master key update information (MasterKeyUpdate) and synchronization reconfiguration information (ReconfigurationWithSync) for the terminal device to synchronize to the second cell.

In addition, the synchronous reconfiguration information may include the PCI of the second cell and the public configuration information of the second cell. For example, if the PCIs of the first cell and the second cell are different or the downlink frequencies are different, the synchronous reconfiguration information includes the PCI of the second cell and the public configuration information of the second cell.

In this embodiment of the application, if the PCI of the first cell and the second cell are different or the downlink frequencies are different, the above RRC reconfiguration message must be sent to the terminal device before the air interface resources are switched to send the signal of the second cell, otherwise the original connection Terminal equipment to the first cell will not be able to receive. Therefore, the air interface resource switching indication may be carried in the last downlink F1AP message sent by the first host CU in step 909 .

For example, in step 911, when the first IAB node successfully sends the RRC reconfiguration message contained in the downlink F1AP to the terminal device, step 907 is performed, that is, the first IAB node broadcasts the air interface resource from the broadcast to the terminal device. Signals related to the first cell are converted to broadcast signals related to the second cell.

In this embodiment of the application, if the PCIs of the first cell and the second cell are different or the downlink frequencies are different, since the RRC reconfiguration messages of all terminal devices that need to be handed over to the second cell must be sent before the air interface resource switching, it may When some terminal devices receive the RRC reconfiguration message, the air interface resources have not been converted, so some terminal devices may not be able to detect the second PCI immediately when receiving the RRC reconfiguration message. In this way, the handover timer T304 expires, causing these terminals to initiate RRC re-establishment. In order to avoid the RRC re-establishment caused by the timeout of T304, the time length of T304 can be increased, so that the terminal equipment can be handed over to the second cell successfully. Or configure conditional handover (CHO, conditional handover) for the terminal device. When receiving the conditional handover configuration, the terminal device does not immediately trigger the handover (execute RRC reconfiguration, such as starting T304), but when the signal L3filter measurement result of the second cell satisfies The transfer to the second cell is triggered (starting T304) only when the configured conditions are met. In this way, the conditional handover can be triggered only after the air interface resources are transferred to the second cell, and the terminal device can start T304, so that the terminal device is successfully handed over to the second cell.

For example, when the PCIs of the first cell and the second cell are different or the downlink frequencies are different, the RRC reconfiguration message of the terminal device may be an RRC reconfiguration message for conditional handover (CHO); the RRC reconfiguration message also includes A condition for the terminal device to switch to the second cell.

In this embodiment of the application, if the PCI of the first cell and the second cell are different or the downlink frequencies are different, when the air interface resource of the first IAB node is switched from sending the signal of the first cell to the signal of the second cell, the first The IAB node no longer uses the F1 connection with the first host CU. For all connected terminal devices and all initial access terminal devices, the first IAB node uses the second DU and passes through the connection with the second host CU. F1 connection.

Therefore, as shown in FIG. 9, after step 907, the method may further include:

Step 912: the first IAB node sends the RRC reconfiguration complete message received from the terminal device to the second owner CU through the second DU.

In this embodiment of the present application, if the PCI of the first cell and the second cell are different or the downlink frequencies are different, the first IAB node converts the air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell. After the cell-related signal, the first IAB node does not need to allocate a new C-RNTI for the terminal equipment transferred to the second cell. The C-RNTI of the terminal device in the second cell is the same as the C-RNTI of the terminal device in the first cell. In addition, the UE context of the terminal device under the second DU can be completely inherited from the context of the terminal device under the first DU, including the unique identifier gNB-DU UE F1AP ID of the UE in the first IAB node.

In the embodiment of the present application, as shown in FIG. 9, after step 907, the method may further include:

Step 913: The first IAB node initiates the release of the F1 connection between the first DU and the first host CU.

In the method shown in FIG. 10 , steps similar to steps 906 to 913 may also be performed. The embodiment of the present application uses the method shown in FIG. 9 as an example for description, and the description will not be repeated here.

In addition, in the method shown in FIG. 9, through

steps

906 and 907, the first IAB node switches the air interface resources from broadcasting signals related to the first cell according to the air interface resource switching instruction received from the first host CU. To broadcast a signal related to the second cell.

However, alternatively, after the second DU of the first IAB node establishes an F1 connection with the second host CU, the first IAB node may also switch the air interface resources spontaneously.

For example, when the first PCI and the first downlink frequency of the first cell are the same as the second PCI and the second downlink frequency of the second cell, that is, the PCI remains unchanged, the first IAB node can spontaneously perform air interface resource conversion.

Fig. 11 is another schematic diagram of the terminal device transfer method in Embodiment 1 of the present application according to Embodiment 1 of the present application. As shown in Fig. 11 , the method includes:

Step 1101: the first IAB node receives the F1 connection establishment instruction sent by the first owner CU;

Step 1102: the second DU of the first IAB node initiates the establishment of the F1 connection with the second host CU;

Step 1103: the second DU of the first IAB node establishes an F1 connection with the second host CU;

Step 1104: the first IAB node switches air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell.

In the embodiment of the present application, as shown in FIG. 11, after step 1104, the method may further include:

Step 1105: the first IAB node initiates the release of the F1 connection between the first DU and the first host CU.

It can be seen from the above-mentioned embodiment that the terminal device can be conveniently transferred from the first cell of the first DU of the first IAB node to the second cell of the second DU, thereby providing a method of migrating the first IAB node from the first host CU An effective mechanism for the terminal device to also transfer from the first host CU to the second host CU when reaching the second host CU.

Example 2

Embodiment 2 of the present application provides a transfer method of a terminal device, which is described from the side of the first host CU. It corresponds to the method of Example 1, and the same parts will not be described repeatedly.

This method is applied to the situation where the first IAB node migrates from the first CU to the second host CU. FIG. 12 is a schematic diagram of a terminal device transfer method according to Embodiment 2 of the present application. As shown in FIG. 12, the method includes:

Step 1201: the first host CU sends an F1 connection establishment indication to the first IAB node, and the F1 connection establishment indication is used to instruct the first IAB node to establish an F1 connection with the second host CU through a second DU, so as to The terminal device is transferred from the first cell of the first DU of the first IAB node to the second cell of the second DU;

Wherein, the first host CU has established an F1 connection with the first DU of the first IAB node.

In this way, the terminal device can be conveniently transferred from the first cell of the first DU of the first IAB node to the second cell of the second DU, thus providing a method for the first IAB node to migrate from the first host CU to the second host An effective mechanism for a terminal device to also transfer from a first host CU to a second host CU when a CU is used.

In this embodiment of the present application, the first host CU may send the F1 connection establishment instruction to the first IAB node through an RRC reconfiguration message or an F1AP message.

In the embodiment of the present application, as shown in FIG. 12, before step 1201, the method may further include:

Step 1202: The first host CU receives an indication from the second host CU of accepting the request for establishing an F1 connection with the first IAB node.

For example, the first host CU receives an indication from the second host CU of accepting the request to establish an F1 connection with the first IAB node through an Xn handover response message directed to the first IAB node.

Step 1203: the first host CU receives the TNL address configured for the first IAB node by the second host CU for the first IAB node to establish an F1 connection with the second host CU;

For example, the TNL address is included in the Xn Handover Response message for the first IAB node.

That is to say, step 1202 and step 1203 can be performed in combination.

In this embodiment of the application, before step 1202, the method may further include:

Step 1204: the first host CU requests the second host CU to establish an F1 connection with the first IAB node.

For example, the first host CU requests the second host CU to establish an F1 connection with the first IAB node through an Xn handover request message directed to the first IAB node.

In this embodiment of the present application, in step 1201, the first host CU may send the F1 connection indication to the first IAB node through a downlink F1AP message, wherein the downlink F1AP message includes information for the first IAB node and the first IAB node. The TNL address for the second host CU to establish the F1 connection, for example, the TNL address obtained from the second host CU in step 1203 for the first IAB node to establish the F1 connection with the second host CU.

In this embodiment of the present application, the TNL address used to establish the F1 connection between the first IAB node and the second host CU may also be included in the RRC reconfiguration message for the first IAB node carried by the Xn handover response message In; for example, in step 1201, the first host CU forwards the RRC reconfiguration message for the first IAB node to the first IAB node, where the RRC reconfiguration message is used to indicate the first IAB node An F1 connection is established with the second host CU.

In the embodiment of the present application, after the first IAB node establishes an F1 connection with the second host CU through the second DU, as shown in FIG. 12 , the method further includes:

Step 1205: the first donor CU sends an Xn handover request message for the terminal device to the second donor CU, wherein the Xn handover response message includes the first NCGI of the first cell.

That is to say, since the first donor CU has not obtained the second NCGI of the second cell, the Xn handover response message contains the first NCGI of the first cell. In this case, the second donor CU can pass the first NCGI The corresponding relationship between the NCGI and the second NCGI, it is learned that the target cell to which the terminal equipment transfers is the second cell.

In this embodiment of the application, after the first host CU sends the RRC reconfiguration message of the terminal device, or after the terminal device successfully completes the RRC reconfiguration, that is, after successfully transferring to the second host CU, there is no need to use the first host CU. F1 connection between the IAB node and the first host CU. As shown in Figure 12, the method also includes:

Step 1206: When the first host CU finishes sending the last downlink F1AP message containing the RRC reconfiguration message of the terminal device, or when the first host CU receives the last message sent by the second host CU for the terminal device When receiving the UE context release instruction message of the device, the first host CU initiates the release of the F1 connection with the first DU of the first IAB node.

FIG. 13 is another schematic diagram of the terminal device transfer method according to Embodiment 2 of the present application. As shown in FIG. 13, the method includes:

Step 1301: The first host CU receives an indication from the second host CU of accepting the request to establish an F1 connection with the first IAB node;

Step 1302: the first host CU receives the TNL address configured by the second host CU for the first IAB node for the first IAB node to establish an F1 connection with the second host CU;

Step 1303: the first host CU sends an F1 connection establishment instruction to the first IAB node, and the F1 connection establishment instruction is used to instruct the first IAB node to establish an F1 connection with the second host CU through the second DU, so as to The terminal device is transferred from the first cell of the first DU of the first IAB node to the second cell of the second DU;

In the embodiment of the present application, after the first IAB node establishes an F1 connection with the second host CU through the second DU, as shown in FIG. 13 , the method may further include:

Step 1304: the first host CU receives at least one of the second PCI, the second downlink frequency point and the second NCGI of the second cell from the first IAB node;

Step 1305: The first donor CU receives the correspondence between the first NCGI of the first cell and the second NCGI of the second cell from the first IAB node.

In this way, the first host CU can learn that the first IAB node has established an F1 connection with the second host CU, thereby triggering a transfer process for the terminal device.

In the embodiment of the present application, as shown in FIG. 13, after step 1305, the method may further include:

Step 1306: the first donor CU sends an Xn handover request message for the terminal device to the second donor CU, where the Xn handover request message includes the second NCGI of the second cell.

That is to say, since the first CU has obtained the second NCGI, the Xn switching request message contains the second NCGI.

FIG. 14 is another schematic diagram of the terminal device transfer method according to Embodiment 2 of the present application. As shown in FIG. 14, the method includes:

Step 1401: The first host CU receives an indication from the second host CU of accepting the request to establish an F1 connection with the first IAB node;

Step 1402: the first host CU receives the TNL address configured for the first IAB node by the second host CU for the first IAB node to establish an F1 connection with the second host CU;

Step 1403: the first host CU sends an F1 connection establishment indication to the first IAB node, and the F1 connection establishment indication is used to instruct the first IAB node to establish an F1 connection with the second host CU through the second DU, so as to The terminal device is transferred from the first cell of the first DU of the first IAB node to the second cell of the second DU;

After the first IAB node establishes an F1 connection with the second host CU through the second DU, as shown in FIG. 14 , the method may further include:

Step 1404: The first host CU receives at least one of the second PCI, the second downlink frequency point and the second NCGI of the second cell from the second host CU;

Step 1405: The first donor CU receives the correspondence between the first NCGI of the first cell and the second NCGI of the second cell from the second donor CU.

In step 1405, the first host CU may receive at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell from the second host CU through a node configuration update message (Node Configure Update) .

In the embodiment of the present application, as shown in FIG. 14, after step 1405, the method may further include:

Step 1406: the first donor CU sends an Xn handover request message for the terminal device to the second donor CU, wherein the Xn handover response message includes the second NCGI of the second cell.

That is to say, since the first CU has obtained the second NCGI of the second cell, the Xn handover response message contains the second NCGI.

In the embodiment of this application, as shown in Figure 14, the method may further include:

Step 1407: When the first host CU finishes sending the last downlink F1AP message containing the RRC reconfiguration message for switching the terminal device, or when the first host CU receives the last When there is a UE context release indication message of the terminal device, the first host CU initiates the release of the F1 connection with the first DU of the first IAB node.

In this embodiment of the present application, the method shown in FIG. 12 to FIG. 14 may further include: the first host CU sending at least one of the first PCI, the first downlink frequency point, and the first NCGI of the first cell to the The second host CU.

For example, the first owner CU sends the first PCI, the first downlink frequency point, and the first At least one of the NCGIs is sent to the second host CU.

In this embodiment of the present application, the first cell of the first DU and the second cell of the second DU may share the same air interface resources.

In this way, when the terminal device can transfer from the first cell of the first DU connected to the first parent CU to the second cell of the second DU connected to the second parent CU, the first IAB node does not need to be two DUs The cell prepares two different sets of air interface resources at the same time, which improves the efficiency of air interface resources.

The method in FIGS. 12 to 14 may further include: the first host CU receiving an air interface resource sharing indication sent by the first IAB node, where the air interface resource sharing indication is used to indicate that the first cell and the second cell share the same air interface resources.

In this embodiment of the present application, when the first host CU receives the air interface resource sharing instruction, the method may further include: the first host CU sends an air interface resource conversion instruction to the first IAB node, wherein the air interface resource conversion The indication is used to instruct the first IAB node to switch the air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell.

In this embodiment of the present application, before the first host CU sends an air interface resource conversion indication to the first IAB node, the method in FIG. 12 to FIG. 14 may further include:

The first host CU sends a system information change request to the first IAB node, so as to trigger the first IAB node to send a system information change instruction to the terminal device.

For example, if the first PCI and the first downlink frequency of the first cell are the same as the first PCI and the first downlink frequency of the first cell, the first host CU sends the system information change to the first IAB node ask.

In this embodiment of the present application, before the first host CU sends an air interface resource conversion instruction to the first IAB node, the method may further include:

The first host CU sends a downlink F1AP message to the first IAB node through the first DU, where the downlink F1AP message includes an RRC reconfiguration message for the terminal device;

Wherein, the RRC reconfiguration message is used to transfer the terminal equipment from the first cell to the second cell; the RRC reconfiguration message at least includes master key update information and information for the terminal equipment to synchronize to the second cell Synchronous reconfiguration information (ReconfigurationWithSync).

Wherein, the RRC reconfiguration message is an RRC reconfiguration message for conditional handover (CHO). For example, if the PCIs of the first cell and the second cell are different or the downlink frequencies are different, the RRC reconfiguration message is an RRC reconfiguration message for conditional handover (CHO); the RRC reconfiguration message also includes the terminal equipment switched to The condition of the second cell.

Wherein, the air interface resource conversion indication is carried in the last downlink F1AP message sent by the first host CU. For example, if the PCIs of the first cell and the second cell are different or the downlink frequencies are different, the air interface resource switching indication is carried in the last downlink F1AP message sent by the first donor CU.

Example 3

Embodiment 3 of the present application provides a transfer method of a terminal device, which is described from the side of the second host CU. It corresponds to the methods of Example 1 and Example 2, and the same parts will not be described repeatedly.

This method is applied to the situation where the first IAB node migrates from the first CU to the second host CU. FIG. 15 is a schematic diagram of a terminal device transfer method according to Embodiment 3 of the present application. As shown in FIG. 15, the method includes:

Step 1501: An F1 connection is established between the second parent CU and the second DU of the first IAB node, so as to transfer the terminal device from the first cell of the first DU of the first IAB node to the second DU of the second DU. The second cell: the establishment of the F1 connection is initiated by the first IAB node after receiving the F1 connection establishment instruction sent by the first owner CU;

Wherein, the second host CU has established an F1 connection with the first DU of the first IAB node.

In the embodiment of this application, as shown in Figure 15, before step 1501, the method further includes:

Step 1502: the second host CU receives the request sent by the first host CU to establish an F1 connection between the second host CU and the first IAB node.

For example, the second host CU receives a request sent by the first host CU to establish an F1 connection between the second host CU and the first IAB node through an Xn switching request message directed to the first IAB node.

In the embodiment of the present application, as shown in FIG. 15, after step 1502, the method further includes:

Step 1503: the second host CU sends to the first host CU an indication of accepting the request for establishing an F1 connection with the first IAB node.

For example, the second host CU sends to the first host CU an indication of accepting the request for establishing an F1 connection with the first IAB node through an Xn handover response message directed at the first IAB node.

Step 1504: the second host CU sends to the first host CU the TNL address configured for the first IAB node for establishing an F1 connection between the first IAB node and the second host CU.

For example, the TNL address is included in the Xn handover response message for the first IAB node, or the TNL address for the first IAB node to establish an F1 connection with the second host CU is included in the Xn handover response message carried In the RRC reconfiguration message for the first IAB node.

For example, step 1503 and step 1504 may be performed in combination.

In this way, by sending to the first host CU an indication of accepting the request to establish an F1 connection with the first IAB node and the TNL configured for the first IAB node for establishing an F1 connection between the first IAB node and the second host CU The address enables the first host to send an F connection establishment instruction to the first IAB node, so that the first IAB node establishes an F1 connection with the second host CU.

In the embodiment of this application, as shown in Figure 15, after step 1501, the method further includes:

Step 1505: The second donor CU receives an Xn handover request message for the terminal device from the first host CU, wherein the Xn handover response message includes the second NCGI of the second cell or the first NCGI of the first cell.

For example, when the first donor CU knows the second NCGI of the first IAB node, the Xn handover response message includes the second NCGI of the second cell, otherwise, the Xn handover response message includes the first NCGI of the first cell .

FIG. 16 is another schematic diagram of the terminal device transfer method according to Embodiment 3 of the present application. As shown in FIG. 16, the method includes:

Step 1601: The second host CU receives a request from the first host CU to establish an F1 connection between the second host CU and the first IAB node;

Step 1602: the second host CU sends to the first host CU an indication of accepting the request to establish an F1 connection with the first IAB node;

Step 1603: the second host CU sends to the first host CU the TNL address configured for the first IAB node for establishing an F1 connection between the first IAB node and the second host CU;

Step 1604: An F1 connection is established between the second parent CU and the second DU of the first IAB node, so as to transfer the terminal device from the first cell of the first DU of the first IAB node to the second DU of the second DU. The second cell: the establishment of the F1 connection is initiated by the first IAB node after receiving the F1 connection establishment instruction sent by the first owner CU;

In the embodiment of the present application, as shown in FIG. 16, after step 1604, the method further includes:

Step 1605: the second host CU sends at least one of the second PCI, the second downlink frequency point and the second NCGI of the second cell to the first host CU;

Step 1606: the second donor CU sends the correspondence between the NCGI of the first cell and the NCGI of the second cell to the first donor CU.

Step 1607: The second donor CU receives an Xn handover request message for the terminal device from the first donor CU, where the Xn handover request message includes the second NCGI of the second cell.

In step 1605, for example, the second host CU sends at least the second PCI, the second downlink frequency point, and the second NCGI of the second cell to the first host CU through a node configuration update message (Node Configure Update). one.

In the embodiment of the present application, in the method shown in Figure 15 and Figure 16, the method may further include:

The second donor CU receives at least one of the first PCI, the first downlink frequency point and the first NCGI of the first cell from the first donor CU.

For example, the second host CU receives the first PCI of the first cell, the first At least one of the downlink frequency point and the first NCGI.

In this embodiment of the present application, when establishing an F1 connection between the second host CU and the second DU of the first IAB node, the second host CU receives the first IAB node sent by the first IAB node through an F1 establishment request message. At least one of the first PCI, the first downlink frequency point, and the first NCGI of a cell.

For example, the F1 establishment request message further includes: a correspondence between the first NCGI of the first cell and the second NCGI of the second cell.

In this way, the second host CU can obtain the first NCGI of the first cell of the first IAB node through the first host CU or the first IAB node. In the case of NCGI, the first host CU may know that the target cell for transfer of the terminal device is the second cell of the first IAB node.

In this embodiment of the present application, the first cell and the second cell may share the same air interface resource. If the PCIs of the first cell and the second cell are different or the downlink frequencies are different, after the first IAB node converts the air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, the first The IAB node does not need to allocate a new C-RNTI for the terminal equipment transferred to the second cell. The C-RNTI of the terminal device in the second cell is the same as the C-RNTI of the terminal device in the first cell. In addition, the UE context of the terminal device under the second DU can be completely inherited from the context of the terminal device under the first DU, including the unique identifier gNB-DU UE F1AP ID of the terminal device in the first IAB node.

Therefore, when the second benefactor CU receives the Xn handover request for the terminal device from the first benefactor CU, if the second benefactor CU has obtained the first PCI and downlink Frequency, the second host CU may determine that the PCI or downlink frequency of the first cell is different from that of the second cell, so as not to request the second DU of the IAB node to establish the context of the terminal device.

For example, the method further includes: the second donor CU determines that the PCI or downlink frequency of the first cell is different from that of the second cell, and the second donor CU does not send the second DU for the terminal device to the second DU of the IAB node. UE context establishment request.

It can be seen from the above-mentioned embodiment that the terminal device can be conveniently transferred from the first cell of the first DU of the first IAB node to the second cell of the second DU, thereby providing a method for migrating the first IAB node from the first host CU An effective mechanism for the terminal device to also transfer from the first host CU to the second host CU when reaching the second host CU.

Example 4

Embodiment 4 of the present application provides a transfer method of a terminal device, which is described from the side of the first IAB node, the side of the first host CU, the side of the second host CU, and the side of the terminal device. It corresponds to the methods of Example 1, Example 2 and Example 3, and the same parts will not be described repeatedly.

This method is applied to the situation where the first IAB node migrates from the first CU to the second host CU. FIG. 17 is a schematic diagram of a terminal device transfer method according to Embodiment 4 of the present application. As shown in FIG. 17, the method includes:

Step 1701: the first host CU sends a request to the second host CU to establish an F1 connection between the second host CU and the first IAB node;

Step 1702: the second host CU sends to the first host CU an indication of accepting the request to establish an F1 connection with the first IAB node;

Step 1703: the second host CU sends to the first host CU the TNL address configured for the first IAB node for establishing an F1 connection between the first IAB node and the second host CU;

Step 1704: the first host CU sends an F1 connection establishment instruction to the first IAB node;

Step 1705: the second DU of the first IAB node initiates the establishment of the F1 connection with the second host CU;

Step 1706: the second DU of the first IAB node establishes an F1 connection with the second host CU.

The following describes specific application scenarios.

Scenario 1. The first cell of the first DU of the first IAB node and the second cell of the second DU share the same set of air interface resources, and use different PCIs or different downlink frequencies (ARFCN-DL):

FIG. 18 is a schematic diagram of a terminal device transfer method applied to scenario 1 according to Embodiment 4 of the present application. As shown in FIG. 18 , the method includes:

IAB-MT switching of IAB-DU and migration of F1 connection, wherein, the MT of the first IAB node is switched to the second host CU, and the transmission path of the DU of the first IAB node and the F1 connection of the first host CU is migrated to the second host CU. host side;

The second DU of the first IAB node establishes an F1 connection with the second host CU;

The first IAB node sends the second PCI, the second downlink frequency point, the second NCGI and the first PCI, the first downlink frequency point, and the first NCGI to the first host CU through the F1 Setup Information message;

The first host CU sends an Xn handover request message for the terminal device to the second host CU, indicating that the target cell of the terminal device is the second NCGI, and also includes the second PCI, the second downlink frequency point, the first PCI, the second downlink frequency point and the second NCGI;

The second host CU determines that the PCI or downlink frequency of the first IAB node has changed through the Xn switching request, and does not send a UE context establishment request to the first IAB node;

The second host CU sends an Xn handover response message to the first host CU, which carries the RRC reconfiguration message generated by the second host CU, and the RRC reconfiguration message includes the second PCI, the second NCGI-related key information (MasterKeyUpdate) and T304 . If conditional handover is configured for the terminal device, the RRC reconfiguration message also includes the conditions that the measurement results of the second cell need to meet when triggering the transfer to the second cell;

The first host CU forwards the RRC reconfiguration message to the first IAB node through the DL F1AP;

The first host CU determines that the PCI or downlink frequency of the first IAB node has changed through the F1 establishment information message, and when the first host CU sends the RRC reconfiguration message of all terminal devices, it sends an air interface resource switch to the first IAB node Instructing, triggering the first IAB node to start sending the air interface signal of the second cell, and in addition, enabling the context of the terminal device under the F1 connection of the second parent CU to inherit the UE context of the terminal device under the F1 connection of the first parent CU;

The terminal device performs RRC reconfiguration, and initiates random access to the first IAB node; or, when the L3filter measurement result of the signal of the second PCI cell meets the conditions required to trigger the transfer to the second PCI cell, the terminal device performs RRC reconfiguration , initiate random access to the first IAB node, and send an RRC reconfiguration complete message;

The first IAB node forwards the RRC reconfiguration complete message through the F1 connection (UL F1AP) with the second host CU;

After receiving the air interface resource switching instruction, the first IAB node initiates the release of the F1 connection with the first host CU.

FIG. 19 is another schematic diagram of a terminal device transfer method applied to scenario 1 according to Embodiment 4 of the present application. As shown in FIG. 19 , the method includes:

The IAB-MT switching of IAB-DU and the migration of F1 connection, wherein, the MT of the first IAB node is switched to the second host CU, and the transmission path of the DU of the first IAB node and the F1 connection of the first host CU is migrated to the second host CU. Second host side;

The second DU of the first IAB node establishes an F1 connection with the second host CU, wherein the F1 Setup Req st message sent by the first IAB node includes the second PCI, the second downlink frequency, the second NCGI, the first PCI, the second Downlink frequency, No. 1 NCGI;

The second host CU sends a node configuration update message to the first host CU, which carries the second PCI, the second downlink frequency point, the second NCGI and the first PCI, the first downlink frequency point, and the first NCGI.

The first host CU sends an Xn handover request message for the terminal device to the second host CU, indicating that the target cell of the terminal device is the second NCGI, and also includes the second PCI, the second downlink frequency point, the first PCI, the first downlink Frequency point, the first NCGI.

The second host CU determines that the PCI or downlink frequency of the first IAB node changes through the Xn switching request, and does not send a terminal device context establishment request to the first IAB node.

The second host CU sends an Xn handover response message to the first host CU, which carries the RRC reconfiguration message generated by the second host CU, and the RRC reconfiguration message includes the second PCI, the second NCGI-related key information (MasterKeyUpdate) and T304 . If conditional handover is configured for the terminal device, the RRC reconfiguration message also includes a condition that the measurement result of the second PCI cell needs to meet when the transfer to the second PCI cell is triggered.

The first host CU forwards the RRC reconfiguration message to the first IAB node through the F1 connection.

The first host CU determines that the PCI and downlink frequency of the first IAB node have changed through the F1 establishment information message. When the first host CU sends the RRC reconfiguration message of all terminal devices, it sends an air interface resource switch to the first IAB node. The instruction triggers the first IAB node to start sending the air interface signal of the second cell, and also makes the F1 connection between the first IAB node and the second host CU inherit the terminal device context of the terminal device under the F1 connection of the first host CU.

The first IAB node forwards the RRC reconfiguration complete message through the F1 connection (UL F1AP) with the second owner CU.

Scenario 2: The first cell of the first DU of the first IAB node and the second cell of the second DU share the same set of air interface resources, and use the same PCI or the same downlink frequency point (ARFCN-DL):

FIG. 20 is a schematic diagram of a terminal device transfer method applied to scenario 2 according to Embodiment 4 of the present application. As shown in FIG. 20 , the method includes:

The first IAB node sends the second PCI, the second downlink frequency point, the second NCGI and the first PCI, the first downlink frequency point, and the first NCGI to the first host CU through the F1 establishment information message;

The first host CU determines that the PCI and downlink frequency of the first IAB node have not changed, and sends a system information change request to the first IAB node;

The first IAB node sends a system information change instruction to the terminal device, triggering the terminal device to receive the changed system information; or, sending a dedicated RRC reconfiguration message to configure updated system information to the terminal device whose active BWP does not include a public search space;

The first host CU sends an Xn handover request message for the terminal device to the second host CU, indicating that the target cell of the terminal device is the second NCGI, and also includes the second PCI, the second downlink frequency point, the first PCI, the first downlink Frequency point, the first NCGI. In this embodiment of the present application, the above two steps are not limited, that is, the order in which the first IAB node sends a system information change instruction to the terminal device and the first host CU sends a switching request for the terminal device to the second host CU;

The second host CU determines that the PCI and downlink frequency of the first IAB node have not changed through the Xn switching request, and sends a terminal device context establishment request to the first IAB node;

The first IAB node allocates a new C-RNTI and a new gNB-DU terminal device F1AP ID for the terminal device, and binds the terminal device with the F1 signaling connection between the second host CU and the first IAB node. The first IAB node sends a terminal device context establishment response to the second host CU, carrying the new C-RNTI and the new gNB-DU terminal device F1AP ID;

The second host CU sends an Xn handover response message to the first host CU, which carries the RRC reconfiguration message generated by the second host CU, and the RRC reconfiguration message includes the key information (MasterKeyUpdate) related to the second NCGI and the new C-RNTI;

The first host CU forwards the RRC reconfiguration message to the first IAB node through the F1 connection;

The terminal device uses the new C-RNTI and new key to send an RRC reconfiguration complete message to the first IAB node. The first IAB node determines the new gNB-DU terminal device F1AP ID through the new C-RNTI and communicates with the F1AP ID of the second host CU. The connection forwards the RRC reconfiguration complete message;

The second host CU sends a terminal device context release request to the original Donor;

When receiving context release requests from all terminal devices, or after sending RRC reconfiguration messages from all terminal devices, the first host CU initiates the release of the F1 connection with the first IAB node.

FIG. 21 is another schematic diagram of the terminal device transfer method applied to scenario 2 according to Embodiment 4 of the present application. As shown in FIG. 21 , the method includes:

The second DU of the first IAB node establishes an F1 connection with the second host CU, wherein the F1 Setup Reqst message sent by the first IAB node includes the second PCI, the second downlink frequency point, the second NCGI and the first PCI, the first Downlink frequency point, the first NCGI;

The second host CU sends a node configuration update message to the first host CU, which carries the second PCI, the second downlink frequency point, the second NCGI and the first PCI, the first downlink frequency point, and the first NCGI;

The first IAB node sends a system information change instruction to the terminal device, triggering the terminal device to receive the changed system information; or, sending a dedicated RRC reconfiguration message to configure updated system information to the terminal device whose active BWP does not include a common search space;

The first donor CU determines the target cell of the terminal device through the indication of the node configuration update message, and sends an Xn handover request message for the terminal device to the second donor CU, indicating that the target cell of the terminal device is the second NCGI. In this embodiment of the present application, the above two steps are not limited, that is, the order in which the first IAB node sends a system information change instruction to the terminal device and the first host CU sends a switching request for the terminal device to the second host CU;

The second host CU determines that the PCI and downlink frequency of the first IAB node have not changed through the Xn switching request message, and sends a terminal device context establishment request to the first IAB node;

Example 5

An embodiment of the present application provides an apparatus for migrating a terminal device. The apparatus is set in a first IAB node, wherein the first IAB node is migrated from a first host distribution unit (CU) to a second host CU. The device corresponds to the method described in Example 1, and the same content will not be described repeatedly.

FIG. 22 is a schematic diagram of a transfer device of a terminal device according to Embodiment 5 of the present application. As shown in Figure 22, the device 2200 includes:

The first establishment unit 2201, after receiving the F1 connection establishment instruction sent by the first host CU, enables the second distribution unit (DU) to initiate the establishment of the F1 connection with the second host CU, so as to transfer the terminal device from the The first cell of the first DU of the first IAB node is transferred to the second cell of the second DU;

Wherein, the first DU has established an F1 connection with the first host CU.

In the embodiment of this application,

The F1 connection establishment instruction is sent by the first owner CU to the first IAB node through an RRC reconfiguration message or an F1AP message.

For example, the device also includes:

The first sending unit, after the second DU establishes an F1 connection with the second donor CU, sends at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell to the second CU A host CU.

For example, the device also includes:

The second sending unit, after the second DU establishes an F1 connection with the second parent CU, the first IAB node sends the correspondence between the NCGI of the first cell and the second NCGI of the second cell to the first Host CU.

For example, the device also includes:

The third sending unit, when the second DU establishes an F1 connection with the second host CU, sends at least one of the first PCI, the first downlink frequency point, and the first NCGI of the first cell through an F1 establishment request message One, sent to the second host CU.

In this embodiment of the application, the F1 establishment request message also includes:

The corresponding relationship between the first NCGI of the first cell and the second NCGI of the second cell.

In this embodiment of the present application, the first IAB node shares the same air interface resources for the first cell of the first DU and the second cell of the second DU.

For example, the device also includes:

a first receiving unit, which receives an air interface resource conversion instruction from the first host CU;

A first conversion unit, which converts air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell.

For example, the device also includes:

a second receiving unit, which receives a system information change request from the first host CU before the air interface resource of the first IAB node switches from broadcasting a signal related to the first cell to broadcasting a signal related to the second cell, And send a system information change indication to the terminal device, so as to trigger the terminal device to receive the system information related to the second cell.

For example, the device also includes:

A third receiving unit, before the first conversion unit converts air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, receiving the transmission of the first host CU through the first DU A downlink F1AP message, wherein the downlink F1AP message includes an RRC reconfiguration message for the terminal device;

a fourth sending unit, which sends the RRC reconfiguration message to the terminal device;

For example, the RRC reconfiguration message is an RRC reconfiguration message for conditional handover (CHO); the RRC reconfiguration message also includes the conditions for the terminal equipment to transfer to the second cell.

For example, the air interface resource switching indication is carried in the last downlink F1AP message sent by the first host CU.

For example, when the first IAB node successfully sends the RRC reconfiguration message contained in the downlink F1AP to the terminal device, the first conversion unit converts the air interface resource from broadcasting a signal related to the first cell to broadcasting a signal related to the Signals related to the second cell.

For example, the device also includes:

The fifth sending unit, after the first IAB node converts the air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, sends the RRC reconfiguration complete message received from the terminal device to It is sent to the second host CU through the second DU.

For example, after the first conversion unit converts the air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, the C-RNTI of the terminal device in the second cell is related to the terminal The C-RNTIs of the devices in the first cell are the same.

In the embodiment of this application, the device also includes:

The second conversion unit, after the second DU of the first IAB node establishes an F1 connection with the second host CU, converts the air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell Signal.

For example, the device also includes:

A first initiating unit, after the first IAB node converts air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, and initiates a communication between the first DU and the first host CU The release of the F1 connection between.

Example 6

An embodiment of the present application provides an apparatus for migrating a terminal device. The apparatus is set in a first host, where a first IAB node is migrated from a distribution unit (CU) of the first host to a second host CU. This device corresponds to the method described in Example 2, and the same content will not be described repeatedly.

FIG. 23 is a schematic diagram of a transfer apparatus of a terminal device according to Embodiment 6 of the present application. As shown in Figure 23, the device 2300 includes:

A sixth sending unit 2301, which sends an F1 connection establishment instruction to the first IAB node, where the F1 connection establishment instruction is used to instruct the first IAB node to establish an F1 connection with the second host CU through the second DU, so as to connect the terminal The device is transferred from the first cell of the first DU of the first IAB node to the second cell of the second DU;

For example, the first donor CU sends the F1 connection establishment instruction to the first IAB node through an RRC reconfiguration message or an F1AP message.

For example, the device also includes:

A first request unit, which requests the second host CU to establish an F1 connection with the first IAB node before the first host CU sends an F1 connection establishment instruction to the first IAB node.

For example, the device also includes:

A fourth receiving unit, configured to receive the indication sent by the second owner CU to accept the request for establishing an F1 connection with the first IAB node.

For example, the fourth receiving unit receives the indication of accepting the F1 connection establishment request with the first IAB node sent by the second host CU through the Xn handover response message directed at the first IAB node.

For example, the device also includes:

The fifth receiving unit, before the first host CU sends an F1 connection establishment instruction to the first IAB node, the first host CU receives the first IAB configured by the second host CU for the first IAB node The TNL address of the node establishing the F1 connection with the second host CU; wherein the TNL address is included in the Xn handover response message for the first IAB node.

For example, the sixth sending unit sends the F1 connection indication to the first IAB node through a downlink F1AP message, wherein the downlink F1AP message includes a TNL address for the first IAB node to establish an F1 connection with the second host CU.

For example, the TNL address used to establish the F1 connection between the first IAB node and the second host CU is included in the RRC reconfiguration message for the first IAB node carried by the Xn handover response message;

The first host CU forwards the RRC reconfiguration message for the first IAB node to the first IAB node, where the RRC reconfiguration message is used to instruct the first IAB node to establish an F1 connection with the second host CU .

For example, the device also includes:

The seventh sending unit, after the first IAB node establishes an F1 connection with the second host CU through the second DU, sends an Xn handover request message for the terminal device to the second host CU, wherein the Xn handover request message The first NCGI including the first cell.

For example, the device also includes:

The second initiating unit, when the first host CU sends the last downlink F1AP message containing the RRC reconfiguration message used to transfer the terminal device, or when the first host CU receives the second host CU When the last UE context release indication message for the terminal device is sent, the release of the F1 connection with the first DU of the first IAB node is initiated.

For example, the device also includes:

The sixth receiving unit, after the first IAB node establishes an F1 connection with the second host CU through the second DU, receives the second PCI of the second cell, the second downlink frequency, and the second PCI from the first IAB node. At least one of the two NCGI.

For example, the device also includes:

a seventh receiving unit, which receives the first NCGI of the first cell and the second NCGI correspondence.

For example, the device also includes:

The eighth receiving unit, after the first IAB node establishes an F1 connection with the second host CU through the second DU, receives the second PCI of the second cell, the second downlink frequency point, and the second host CU from the second host CU. At least one of the two NCGI.

For example, the eighth receiving unit receives at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell from the second donor CU through a node configuration update message (Node Configure Update).

For example, the device also includes:

A ninth receiving unit, which receives the correspondence between the NCGI of the first cell and the NCGI of the second cell from the second donor CU after the first IAB node establishes an F1 connection with the second donor CU through the second DU .

For example, the device also includes:

An eighth sending unit, after the first donor CU receives at least one of the second PCI of the second cell, the second downlink frequency point, and the second NCGI from the second donor CU, send to the second donor CU An Xn handover request message for the terminal device, wherein the Xn handover request message includes the second NCGI of the second cell.

For example, the device also includes:

The third initiating unit, when the first host CU sends the last downlink F1AP message containing the RRC reconfiguration message used to transfer the terminal device, or when the first host CU receives the second host CU When the last UE context release indication message for the terminal device is sent, the release of the F1 connection with the first DU of the first IAB node is initiated.

For example, the device also includes:

A ninth sending unit, configured to send at least one of the first PCI, the first downlink frequency point, and the first NCGI of the first cell to the second donor CU.

For example, the ninth sending unit transmits the first PCI of the first cell, the first downlink frequency point and the first At least one of the NCGIs is sent to the second host CU.

For example, the device also includes:

A tenth receiving unit, configured to receive an air interface resource sharing indication sent by the first IAB node, where the air interface resource sharing indication is used to indicate that the first cell and the second cell share the same air interface resource.

For example, the device also includes:

A tenth sending unit, which sends an air interface resource switching instruction to the first IAB node, where the air interface resource switching instruction is used to instruct the first IAB node to switch the air interface resource from broadcasting signals related to the first cell to Signals related to the second cell are broadcast.

For example, the device also includes:

An eleventh sending unit, before the first host CU sends an air interface resource conversion instruction to the first IAB node, the first host CU sends a system information change request to the first IAB node, so as to trigger the first IAB node Send a system information change instruction to the terminal device.

For example, the device also includes:

A twelfth sending unit, which sends a downlink F1AP message to the first IAB node through the first DU before the first owner CU sends an air interface resource conversion instruction to the first IAB node, wherein the downlink F1AP message includes a message for the first IAB node The RRC reconfiguration message of the terminal device;

Wherein, the RRC reconfiguration message is used to transfer the terminal equipment from the first cell to the second cell; the RRC reconfiguration message at least includes master key update information and is used for the terminal equipment to synchronize to the second cell. Cell synchronization reconfiguration information (ReconfigurationWithSync).

For example, the air interface resource conversion indication is carried in the last downlink F1AP message sent by the first host CU.

Example 7

An embodiment of the present application provides an apparatus for migrating a terminal device. The apparatus is set in a second host, wherein a first IAB node is migrated from a distribution unit (CU) of the first host to a second host CU. This device corresponds to the method described in Example 3, and the same content will not be described repeatedly.

FIG. 24 is a schematic diagram of a transfer device of a terminal device according to Embodiment 7 of the present application. As shown in Figure 24, the device 2400 includes:

The second establishing unit 2401, which establishes an F1 connection with the second DU of the first IAB node, so as to transfer the terminal device from the first cell of the first DU of the first IAB node to the second DU of the second DU The second cell: the establishment of the F1 connection is initiated by the first IAB node after receiving the F1 connection establishment instruction sent by the first owner CU;

For example, the device also includes:

The eleventh receiving unit, before establishing the F1 connection between the second host CU and the second DU of the first IAB node, receives the second host CU sent by the first host CU to establish an F1 connection with the first IAB node connection request.

For example, the device also includes:

A thirteenth sending unit, configured to send an indication of accepting the request for establishing an F1 connection with the first IAB node to the first host CU.

For example, the thirteenth sending unit sends an indication of accepting the request for establishing an F1 connection with the first IAB node to the first host CU through an Xn handover response message directed at the first IAB node.

For example, the device also includes:

A fourteenth sending unit, before establishing an F1 connection between the second host CU and the second DU of the first IAB node, sends to the first host CU the configuration for the first IAB node for the first The TNL address of the F1 connection established between the IAB node and the second host CU.

For example, the TNL address used to establish the F1 connection between the first IAB node and the second host CU is included in the Xn handover response message for the first IAB node or in the Xn handover response message carried by the Xn handover response message for the second host CU. In an RRC reconfiguration message of an IAB node.

For example, the device also includes:

A twelfth receiving unit, after establishing an F1 connection between the second host CU and the second DU of the first IAB node, receives an Xn request response message for the terminal device from the first host CU, wherein the Xn The handover request message includes the first NCGI of the first cell or includes the second NCGI of the second cell.

For example, the device also includes:

A fifteenth sending unit, after establishing an F1 connection between the second host CU and the second DU of the first IAB node, sends the second PCI and the second downlink frequency of the second cell to the first host CU point and at least one of the second NCGI.

For example, the fifteenth sending unit sends at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell to the first donor CU through a node configuration update message (Node Configure Update).

For example, the device also includes:

A sixteenth sending unit, after an F1 connection is established between the second donor CU and the second DU of the first IAB node, send the NCGI of the first cell and the NCGI of the second cell to the first donor CU corresponding relationship.

For example, the device also includes:

A thirteenth receiving unit, after the second host CU sends at least one of the second PCI of the second cell, the second downlink frequency point, and the second NCGI to the first host CU, from the first host CU An Xn handover request message for the terminal device is received, where the Xn handover request message includes the second NCGI of the second cell.

For example, the device also includes:

A fourteenth receiving unit, configured to receive at least one of the first PCI, the first downlink frequency point, and the first NCGI of the first cell from the first donor CU.

For example, the fourteenth receiving unit receives the first PCI of the first cell, the first PCI, the second Downlink frequency point and at least one of the first NCGI.

For example, when an F1 connection is established between the second donor CU and the second DU of the first IAB node, the second donor CU receives the first connection information of the first cell sent by the first IAB node through the F1 establishment request message. At least one of the PCI, the first downlink frequency point, and the first NCGI.

For example, the F1 establishment request message also includes:

For example, the first cell and the second cell share the same air interface resource.

For example, the device also includes:

The first determining unit is configured to determine that the PCI or downlink frequency of the first cell is different from that of the second cell when the second donor CU receives an Xn handover request for the terminal device from the first donor CU, and the second donor CU The CU does not send a UE context establishment request for the terminal device to the second DU of the IAB node.

Example 8

An embodiment of the present application provides a network device, where the network device includes the device for transferring a terminal device as described in Embodiment 5.

FIG. 25 is a schematic block diagram of a system configuration of a network device according to Embodiment 8 of the present application. As shown in FIG. 25 , a network device 2500 may include: a processor (processor) 2510 and a memory 2520 ; the memory 2520 is coupled to the processor 2510 . The memory 2520 can store various data; in addition, it also stores an information processing program 2530, and executes the program 2530 under the control of the processor 2510 to receive various information sent by the terminal equipment and send various information to the terminal equipment .

In one embodiment, the function of the transferring means of the terminal device may be integrated into the processor 2510 .

The processor 2510 may be configured to: after the first IAB node receives the F1 connection establishment instruction sent by the first host CU, make the second distribution unit (DU) initiate the establishment of the F1 connection with the second host CU , so as to transfer the terminal device from the first cell of the first DU of the first IAB node to the second cell of the second DU;

Wherein, the first DU has established an F1 connection with the first host CU.

In another embodiment, the transfer device of the terminal device can be configured separately from the processor 2510, for example, the device for generating the preemptive cache status report can be configured as a chip connected to the processor 2510, and the terminal device can be implemented through the control of the processor 2510. function of the transfer device.

In addition, as shown in FIG. 25 , the network device 2500 may further include: a transceiver 2540 and an antenna 2550 ; wherein, the functions of the above components are similar to those of the prior art, and will not be repeated here. It should be noted that the network device 2500 does not necessarily include all the components shown in FIG. 25 ; in addition, the network device 2500 may also include components not shown in FIG. 25 , and reference may be made to the prior art.

Example 9

An embodiment of the present application provides a network device, where the network device includes the device for transferring a terminal device as described in Embodiment 6.

FIG. 26 is a schematic block diagram of the system configuration of the network device according to Embodiment 9 of the present application. As shown in FIG. 26 , a network device 2600 may include: a processor (processor) 2610 and a memory 2620 ; the memory 2620 is coupled to the processor 2610 . The memory 2620 can store various data; in addition, it also stores an information processing program 2630, and executes the program 2630 under the control of the processor 2610 to receive various information sent by the terminal equipment and send various information to the terminal equipment .

In one embodiment, the function of the transferring means of the terminal device may be integrated into the processor 2610 .

The processor 2610 may be configured to: the first host CU sends an F1 connection establishment indication to the first IAB node, and the F1 connection establishment indication is used to instruct the first IAB node to establish an F1 connection with the second host CU through the second DU. connecting to facilitate transfer of a terminal device from a first cell of a first DU of the first IAB node to a second cell of a second DU;

In another embodiment, the transfer device of the terminal device can be configured separately from the processor 2610, for example, the device for generating the preemption cache status report can be configured as a chip connected to the processor 2610, and the terminal device can be implemented through the control of the processor 2610. function of the transfer device.

In addition, as shown in FIG. 26 , the network device 2600 may further include: a transceiver 2640 and an antenna 2650 ; wherein, the functions of the above components are similar to those of the prior art, and will not be repeated here. It should be noted that the network device 2600 does not necessarily include all the components shown in FIG. 26 ; in addition, the network device 2600 may also include components not shown in FIG. 26 , and reference may be made to the prior art.

Example 10

An embodiment of the present application provides a network device, where the network device includes the device for transferring a terminal device as described in Embodiment 7.

FIG. 27 is a schematic block diagram of the system configuration of the network device according to Embodiment 10 of the present application. As shown in FIG. 27 , a network device 2700 may include: a processor (processor) 2710 and a memory 2720 ; the memory 2720 is coupled to the processor 2710 . The memory 2720 can store various data; in addition, it also stores an information processing program 2730, and executes the program 2730 under the control of the processor 2710 to receive various information sent by the terminal equipment and send various information to the terminal equipment .

In one embodiment, the function of the transferring means of the terminal device may be integrated into the processor 2710 .

An F1 connection is established between the second parent CU and the second DU of the first IAB node, so as to transfer the terminal device from the first cell of the first DU of the first IAB node to the second cell of the second DU ; The establishment of the F1 connection is initiated by the first IAB node after receiving the F1 connection establishment instruction sent by the first owner CU;

In another embodiment, the transfer device of the terminal device can be configured separately from the processor 2710. For example, the device for generating the preemptive cache status report can be configured as a chip connected to the processor 2710, and the terminal device can be implemented through the control of the processor 2710. function of the transfer device.

In addition, as shown in FIG. 27 , the network device 2700 may further include: a transceiver 2740 and an antenna 2750 ; wherein, the functions of the above components are similar to those of the prior art, and will not be repeated here. It should be noted that the network device 2700 does not necessarily include all the components shown in FIG. 27 ; in addition, the network device 2700 may also include components not shown in FIG. 27 , and reference may be made to the prior art.

Example 11

An embodiment of the present invention provides a communication system, where the communication system includes the network device described in Embodiment 8, the network device described in Embodiment 9, at least one of the network devices described in Embodiment 10, and a terminal device.

Fig. 28 is a schematic diagram of a communication system according to Embodiment 11 of the present application. As shown in FIG. 28 , a communication system 2800 includes: a first IAB node 2801 , a child IAB node 2802 of the first IAB node, a terminal device 2803 served by the first IAB node, a first host 3804 and a second host 2805 .

For example, the first IAB node 2801 may be the network device described in Embodiment 8, and/or the first host 2804 may be the network device described in Embodiment 9, and the second host 2805 may be the network device described in Embodiment 10 equipment.

When the first IAB node 2801 migrates from the first host CU to the second host CU, the terminal device 2803 also migrates from the first host CU to the second host CU.

The above devices and methods of the present invention can be implemented by hardware, or by combining hardware and software. The present invention relates to such a computer-readable program that, when the program is executed by a logic component, enables the logic component to realize the above-mentioned device or constituent component, or enables the logic component to realize the above-mentioned various methods or steps. Logic components such as field programmable logic components, microprocessors, processors used in computers, and the like. The present invention also relates to a storage medium for storing the above program, such as hard disk, magnetic disk, optical disk, DVD, flash memory and the like.

The method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of both. For example, one or more of the functional block diagrams shown in FIG. 22 and/or one or more combinations of the functional block diagrams may correspond to each software module or each hardware module of the computer program flow. These software modules may respectively correspond to the steps shown in FIG. 8 . These hardware modules, for example, can be realized by solidifying these software modules by using a Field Programmable Gate Array (FPGA).

A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art. A storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium, or it can be an integral part of the processor. The processor and storage medium can be located in the ASIC. The software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) adopts a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module can be stored in the MEGA-SIM card or large-capacity flash memory device.

One or more of the functional blocks and/or one or more combinations of the functional blocks described in FIG. 22 can be implemented as a general-purpose processor, a digital signal processor ( DSP), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof. One or more of the functional blocks and/or one or more combinations of the functional blocks described in FIG. A processor, one or more microprocessors in communication with a DSP, or any other such configuration.

The present application has been described above in conjunction with specific implementation manners, but those skilled in the art should be clear that these descriptions are exemplary rather than limiting the protection scope of the present application. Those skilled in the art can make various variations and modifications to this application according to the spirit and principles of this application, and these variations and modifications are also within the scope of this application.

Regarding the above-mentioned implementation mode disclosed in this embodiment, the following additional notes are also disclosed:

Note 1.

1. An apparatus for transferring a terminal device, the apparatus is set in a first IAB node, wherein the first IAB node is migrated from a first host distribution unit (CU) to a second host CU, and the apparatus includes:

The first establishment unit, after receiving the F1 connection establishment instruction sent by the first host CU, makes the second distribution unit (DU) initiate the establishment of the F1 connection with the second host CU, so as to connect the terminal device transferring from a first cell of a first DU of the first IAB node to a second cell of a second DU;

Wherein, the first DU has established an F1 connection with the first host CU.

2. The device according to appendix 1, wherein,

3. The device according to Supplement 2, wherein the device further comprises:

A first sending unit, configured to send at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell after the second DU establishes an F1 connection with the second donor CU to the first host CU.

4. The device according to Note 3, wherein the device further comprises:

The second sending unit, after the second DU establishes an F1 connection with the second donor CU, the first IAB node sends the correspondence between the NCGI of the first cell and the second NCGI of the second cell to the first host CU.

5. The device according to Supplement 2, wherein the device further comprises:

The third sending unit, when the second DU establishes an F1 connection with the second host CU, sends the first PCI, the first downlink frequency point, and the first NCGI of the first cell through an F1 establishment request message At least one of them is sent to the second host CU.

6. The device according to supplementary note 5, wherein the F1 establishment request message further includes:

A correspondence relationship between the first NCGI of the first cell and the second NCGI of the second cell.

7. The device according to any one of Supplements 2 to 6, wherein the first IAB node shares the same air interface for the first cell of the first DU and the second cell of the second DU resource.

8. The device according to supplementary note 7, wherein the device further comprises:

a first receiving unit, configured to receive an air interface resource conversion instruction from the first host CU;

9. The device according to supplementary note 8, wherein the device further comprises:

A second receiving unit, which receives a system from the first host CU before the air interface resources of the first IAB node are switched from broadcasting signals related to the first cell to broadcasting signals related to the second cell an information change request, and send a system information change indication to the terminal device, so as to trigger the terminal device to receive system information related to the second cell.

10. The device according to supplementary note 8, wherein the device further comprises:

A third receiving unit, before the first conversion unit converts the air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, receiving the first DU through the first DU A downlink F1AP message sent by the first owner CU, wherein the downlink F1AP message includes an RRC reconfiguration message for the terminal device;

Wherein, the RRC reconfiguration message is used to transfer the terminal device from the first cell to the second cell; the RRC reconfiguration message at least includes master key update information and information for the terminal device Synchronize to the synchronization reconfiguration information (ReconfigurationWithSync) of the second cell.

11. The device according to appendix 10, wherein,

The RRC reconfiguration message is an RRC reconfiguration message for conditional handover (CHO); the RRC reconfiguration message also includes conditions for the terminal device to transfer to the second cell.

12. The device according to appendix 8, wherein,

The air interface resource conversion indication is carried in the last downlink F1AP message sent by the first host CU.

13. The device according to supplementary note 12, wherein,

When the first IAB node successfully sends the RRC reconfiguration message contained in the downlink F1AP to the terminal device, the first conversion unit converts the air interface resources from broadcasting signals related to the first cell to A signal related to the second cell is broadcast.

14. The device according to supplementary note 10 or 11, wherein the device further comprises:

A fifth sending unit, after the first IAB node converts air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, the RRC received from the terminal device The reconfiguration complete message is sent to the second host CU through the second DU.

15. The device according to supplementary note 10 or 11, wherein after the first conversion unit converts air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, The C-RNTI of the terminal device in the second cell is the same as the C-RNTI of the terminal device in the first cell.

16. The device according to supplementary note 7, wherein the device further comprises:

The second converting unit, after the second DU of the first IAB node establishes an F1 connection with the second host CU, converts air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell Signals related to the second cell.

17. The device according to any one of Supplements 7 to 16, wherein the device further comprises:

The first initiating unit, after the first IAB node converts air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, initiates the communication between the first DU and the Release of the F1 connection between the first host CU.

18. An apparatus for transferring a terminal device, the apparatus is set in a first host CU, and the apparatus is applied when a first IAB node migrates from the first host CU to a second host CU, the apparatus includes :

A sixth sending unit, which sends an F1 connection establishment instruction to the first IAB node, where the F1 connection establishment instruction is used to instruct the first IAB node to establish an F1 connection with the second host CU through a second DU, so that for transferring a terminal device from a first cell of a first DU of said first IAB node to a second cell of a second DU;

19. The device according to appendix 18, wherein,

The first owner CU sends the F1 connection establishment instruction to the first IAB node through an RRC reconfiguration message or an F1AP message.

20. The device according to Supplement 19, wherein the device further comprises:

21. The device according to supplementary note 20, wherein the device further comprises:

22. The device according to supplementary note 21, wherein,

The fourth receiving unit receives the indication of accepting the F1 connection establishment request with the first IAB node sent by the second host CU through the Xn handover response message directed at the first IAB node.

23. The device according to supplementary note 18, wherein the device further comprises:

The fifth receiving unit, before the first host CU sends an F1 connection establishment instruction to the first IAB node, the first host CU receives the user configured by the second host CU for the first IAB node A TNL address for establishing an F1 connection between the first IAB node and the second host CU; wherein, the TNL address is included in an Xn handover response message for the first IAB node.

24. The device according to supplementary note 23, wherein,

The sixth sending unit sends the F1 connection indication to the first IAB node through a downlink F1AP message, wherein the downlink F1AP message includes information for the first IAB node to establish an F1 connection with the second host CU TNL address.

25. The device according to supplementary note 23, wherein,

The TNL address used to establish the F1 connection between the first IAB node and the second host CU is included in the RRC reconfiguration message for the first IAB node carried by the Xn handover response message;

The first host CU forwards the RRC reconfiguration message for the first IAB node to the first IAB node, where the RRC reconfiguration message is used to indicate that the first IAB node and the The second host CU establishes an F1 connection.

26. The device according to any one of Supplements 23 to 25, wherein the device further comprises:

The seventh sending unit, after the first IAB node establishes an F1 connection with the second host CU through the second DU, sends an Xn switching request message for the terminal device to the second host CU, wherein the The Xn handover request message includes the first NCGI of the first cell.

27. The device according to supplementary note 26, wherein the device further comprises:

The second initiating unit, when the first host CU sends the last downlink F1AP message containing the RRC reconfiguration message used to transfer the terminal device, or when the first host CU receives the first host CU Initiating the release of the F1 connection with the first DU of the first IAB node when the UE context release instruction message for the last terminal device is sent by the second owner CU.

28. The device according to any one of Supplements 23 to 25, wherein the device further comprises:

The sixth receiving unit, after the first IAB node establishes an F1 connection with the second host CU through the second DU, receives the second PCI of the second cell, the second downlink Frequency point and at least one of the second NCGI.

29. The device according to supplementary note 28, wherein the device further comprises:

a seventh receiving unit, which receives the first NCGI of the first cell and the first The corresponding relationship of the second NCGI of the second cell.

30. The device according to any one of Supplements 23 to 25, wherein the device further comprises:

The eighth receiving unit, after the first IAB node establishes an F1 connection with the second host CU through the second DU, receives the second PCI of the second cell, the second downlink Frequency point and at least one of the second NCGI.

31. The device according to appendix 30, wherein,

The eighth receiving unit receives at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell from the second donor CU through a node configuration update message (Node Configure Update).

32. The device according to supplementary note 30 or 31, wherein the device further comprises:

A ninth receiving unit, which receives the NCGI of the first cell and the second cell from the second host CU after the first IAB node establishes an F1 connection with the second host CU through the second DU The NCGI correspondence.

33. The device according to any one of Supplements 28 to 32, wherein the device further comprises:

An eighth sending unit, after the first donor CU receives at least one of the second PCI of the second cell, the second downlink frequency point, and the second NCGI from the second donor CU, send to the first donor CU The second-owner CU sends an Xn handover request message for the terminal device, where the Xn handover request message includes the second NCGI of the second cell.

34. The device according to supplementary note 33, wherein the device further comprises:

The third initiating unit, when the first host CU sends the last downlink F1AP message containing the RRC reconfiguration message used to transfer the terminal device, or when the first host CU receives the first host CU Initiating the release of the F1 connection with the first DU of the first IAB node when the UE context release instruction message for the last terminal device is sent by the second owner CU.

35. The device according to any one of Supplements 23 to 34, wherein the device further comprises:

36. The device according to supplementary note 35, wherein,

The ninth sending unit transmits the first PCI of the first cell, the first downlink frequency point, and the At least one of the first NCGIs is sent to the second host CU.

37. The device according to any one of Supplements 23 to 36, wherein the device further comprises:

38. The device according to supplementary note 37, wherein the device further comprises:

A tenth sending unit, which sends an air interface resource switching instruction to the first IAB node, where the air interface resource switching instruction is used to instruct the first IAB node to switch air interface resources from broadcasting signals related to the first cell Converting to broadcasting signals related to the second cell.

39. The device according to supplementary note 38, wherein the device further comprises:

An eleventh sending unit, before the first host CU sends an air interface resource conversion instruction to the first IAB node, the first host CU sends a system information change request to the first IAB node, so as to trigger the The first IAB node sends a system information change instruction to the terminal device.

40. The device according to supplementary note 38, wherein the device further comprises:

A twelfth sending unit, which sends a downlink F1AP message to the first IAB node through the first DU before the first host CU sends an air interface resource conversion instruction to the first IAB node, wherein the downlink The F1AP message includes an RRC reconfiguration message for the terminal device;

Wherein, the RRC reconfiguration message is used to transfer the terminal device from the first cell to the second cell; the RRC reconfiguration message at least includes master key update information and information for the terminal The device synchronizes to the synchronization reconfiguration information (ReconfigurationWithSync) of the second cell.

41. The device according to appendix 40, wherein,

42. The device according to appendix 40, wherein,

43. An apparatus for transferring a terminal device, the apparatus is set in a second host CU, wherein the first IAB node is migrated from the first host CU to the second host CU, the apparatus includes:

A second establishment unit, which establishes an F1 connection with the second DU of the first IAB node, so as to transfer the terminal device from the first cell of the first DU of the first IAB node to the second DU. The second cell: the establishment of the F1 connection is initiated by the first IAB node after receiving the F1 connection establishment instruction sent by the first owner CU;

44. The device according to supplementary note 43, wherein the device further comprises:

The eleventh receiving unit is configured to receive the second host CU and the first host CU sent by the first host CU before the F1 connection is established between the second host CU and the second DU of the first IAB node. IAB node request to establish F1 connection.

45. The device according to supplementary note 44, wherein the device further comprises:

46. The device according to appendix 45, wherein,

The thirteenth sending unit sends an indication of accepting the request for establishing an F1 connection with the first IAB node to the first host CU through an Xn handover response message directed to the first IAB node.

47. The device according to supplementary note 43, wherein the device further comprises:

A fourteenth sending unit, before establishing an F1 connection between the second host CU and the second DU of the first IAB node, send the user configured for the first IAB node to the first host CU A TNL address for establishing an F1 connection between the first IAB node and the second host CU.

48. The device according to supplementary note 43, wherein the TNL address used for establishing the F1 connection between the first IAB node and the second host CU is included in the Xn handover response message for the first IAB node or included in the RRC reconfiguration message for the first IAB node carried in the Xn handover response message.

49. The device according to supplementary note 47 or 48, wherein the device further comprises:

A twelfth receiving unit, after the F1 connection is established between the second host CU and the second DU of the first IAB node, receives an Xn request response message for the terminal device from the first host CU, wherein , the Xn handover request message includes the first NCGI of the first cell or includes the second NCGI of the second cell.

50. The device according to supplementary note 47 or 48, wherein the device further comprises:

A fifteenth sending unit, after the F1 connection is established between the second donor CU and the second DU of the first IAB node, send the second PCI, the second PCI of the second cell to the first donor CU, At least one of the second downlink frequency point and the second NCGI.

51. The device according to appendix 50, wherein,

The fifteenth sending unit sends at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell to the first donor CU through a node configuration update message (Node Configure Update).

52. The device according to supplementary note 50 or 51, wherein the device further comprises:

A sixteenth sending unit, after establishing an F1 connection between the second donor CU and the second DU of the first IAB node, send the NCGI of the first cell and the The corresponding relationship of the NCGI of the second cell.

53. The device according to any one of Supplements 50 to 52, wherein the device further comprises:

A thirteenth receiving unit, after the second donor CU sends at least one of the second PCI of the second cell, the second downlink frequency, and the second NCGI to the first donor CU, from the The first donor CU receives an Xn handover request message for the terminal device, where the Xn handover request message includes the second NCGI of the second cell.

54. The device according to any one of Supplements 47-53, wherein the device further comprises:

55. The device according to appendix 54, wherein,

The fourteenth receiving unit receives from the first donor CU the first At least one of the PCI, the first downlink frequency point, and the first NCGI.

56. The device according to any one of Supplements 43 to 48, wherein when an F1 connection is established between the second host CU and the second DU of the first IAB node, the second host The CU receives at least one of the first PCI, the first downlink frequency point, and the first NCGI of the first cell sent by the first IAB node through the F1 establishment request message.

57. The device according to supplementary note 56, wherein the F1 establishment request message further includes:

58. The device according to any one of Supplements 45 to 57, wherein the first cell and the second cell share the same air interface resources.

59. The device according to supplementary note 58, wherein the device further comprises:

A first determining unit, configured to determine that the PCI or downlink frequency of the first cell is different from that of the second cell when the second donor CU receives an Xn handover request for the terminal device from the first donor CU, The second host CU does not send a UE context establishment request for the terminal device to the second DU of the IAB node.

60. A network device, the network device is a first IAB node, and the network device includes the apparatus according to any one of Supplements 1-17.

61. A network device, the network device is the first host, and the network device includes the device according to any one of Supplements 18-42.

62. A network device, the network device is the second host, and the network device includes the apparatus according to any one of Supplements 43-59.

63. A communication system, comprising at least one of the network device described in Supplement 60, the network device described in Supplement 61, and the network device described in Supplement 62, and a terminal device.

Note II.

1. A method for transferring a terminal device, wherein the first IAB node migrates from a first host distribution unit (CU) to a second host CU, the method comprising:

After the first IAB node receives the F1 connection establishment instruction sent by the first host CU, the second distribution unit (DU) initiates the establishment of the F1 connection with the second host CU, so that the terminal device transferring from a first cell of a first DU of the first IAB node to a second cell of a second DU;

Wherein, the first DU has established an F1 connection with the first host CU.

2. The method according to appendix 1, wherein,

3. The method according to appendix 2, wherein,

After the second DU establishes an F1 connection with the second host CU, the method further includes:

The first IAB node sends at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell to the first donor CU.

4. The method according to appendix 3, wherein,

The first IAB node sends the correspondence between the NCGI of the first cell and the second NCGI of the second cell to the first donor CU.

5. The method according to appendix 2, wherein,

When the second DU establishes an F1 connection with the second host CU, the first IAB node transmits the first PCI, the first downlink frequency point, and the first NCGI of the first cell through the F1 establishment request message At least one of them is sent to the second host CU.

6. The method according to supplementary note 5, wherein the F1 establishment request message further includes:

7. The method according to any one of Supplements 2 to 6, wherein the first IAB node shares the same air interface for the first cell of the first DU and the second cell of the second DU resource.

8. The method according to Supplement 7, wherein the method further includes:

The first IAB node receives an air interface resource conversion instruction from the first host CU;

The first IAB node switches air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell.

9. The method according to appendix 8, wherein,

Before the air interface resources of the first IAB node are switched from broadcasting signals related to the first cell to broadcasting signals related to the second cell, the method further includes:

The first IAB node receives a system information change request from the first donor CU, and sends a system information change instruction to the terminal device, so as to trigger the terminal device to receive system information related to the second cell.

10. The method according to appendix 8, wherein,

Before the first IAB node switches air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, the method further includes:

The first IAB node receives a downlink F1AP message sent by the first host CU through the first DU, where the downlink F1AP message includes an RRC reconfiguration message for the terminal device;

The first IAB node sends the RRC reconfiguration message to the terminal device;

11. The method according to appendix 10, wherein,

12. The method according to appendix 8, wherein,

13. The method according to appendix 12, wherein,

When the first IAB node successfully sends the RRC reconfiguration message contained in the downlink F1AP to the terminal device, the first IAB node converts air interface resources from broadcasting signals related to the first cell to A signal related to the second cell is broadcast.

14. The method according to appendix 10 or 11, wherein,

After the first IAB node switches air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, the method further includes:

The first IAB node sends the RRC reconfiguration complete message received from the terminal device to the second donor CU through the second DU.

15. The method according to supplementary note 10 or 11, wherein after the first IAB node switches the air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, The C-RNTI of the terminal device in the second cell is the same as the C-RNTI of the terminal device in the first cell.

16. The method according to appendix 7, wherein,

After the second DU of the first IAB node establishes an F1 connection with the second host CU, the method further includes:

17. The method according to any one of Supplements 7 to 16, wherein,

The first IAB node initiates the release of the F1 connection between the first DU and the first host CU.

18. A transfer method of a terminal device, the method is applied when a first IAB node migrates from the first host CU to a second host CU, the method comprising:

The first host CU sends an F1 connection establishment indication to the first IAB node, and the F1 connection establishment indication is used to instruct the first IAB node to establish an F1 connection with the second host CU through a second DU, so that for transferring a terminal device from a first cell of a first DU of said first IAB node to a second cell of a second DU;

19. The method according to appendix 18, wherein,

20. The method according to supplementary note 19, wherein, before the first host CU sends an F1 connection establishment instruction to the first IAB node, the method further includes:

The first host CU requests the second host CU to establish an F1 connection with the first IAB node.

21. The method according to supplementary note 20, wherein the method further includes:

The first host CU receives an indication from the second host CU of accepting the request for establishing an F1 connection with the first IAB node.

22. The method according to appendix 21, wherein,

The first host CU receives an indication from the second host CU of accepting the request for establishing an F1 connection with the first IAB node through an Xn handover response message directed to the first IAB node.

23. The method according to supplementary note 18, wherein, before the first host CU sends an F1 connection establishment instruction to the first IAB node, the method further includes:

The first host CU receives the TNL address configured by the second host CU for the first IAB node for the first IAB node to establish an F1 connection with the second host CU; wherein, the TNL address Included in the Xn Handover Response message for the first IAB node.

24. The method according to appendix 23, wherein,

The first host CU sends the F1 connection indication to the first IAB node through a downlink F1AP message, wherein the downlink F1AP message includes information for the first IAB node to establish an F1 connection with the second host CU TNL address.

25. The method according to appendix 23, wherein,

26. The method according to any one of Supplements 23 to 25, wherein,

After the first IAB node establishes an F1 connection with the second host CU through the second DU, the method further includes:

The first donor CU sends an Xn handover request message for the terminal device to the second donor CU, where the Xn handover request message includes the first NCGI of the first cell.

27. The method according to supplementary note 26, wherein the method further includes:

When the first host CU finishes sending the last downlink F1AP message containing the RRC reconfiguration message used to transfer the terminal device, or when the first host CU receives the message sent by the second host CU for When the last UE context release indication message of the terminal device is issued, the first host CU initiates the release of the F1 connection with the first DU of the first IAB node.

28. The method according to any one of Supplements 23 to 25, wherein after the first IAB node establishes an F1 connection with the second host CU through the second DU, the method further includes:

The first donor CU receives at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell from the first IAB node.

29. The method according to supplementary note 28, wherein after the first IAB node establishes an F1 connection with the second host CU through the second DU, the method further includes:

The first donor CU receives the correspondence between the first NCGI of the first cell and the second NCGI of the second cell from the first IAB node.

30. The method according to any one of Supplements 23 to 25, wherein after the first IAB node establishes an F1 connection with the second host CU through the second DU, the method further includes:

The first donor CU receives at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell from the second donor CU.

31. The method according to appendix 30, wherein,

The first donor CU receives at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell from the second donor CU through a node configuration update message (Node Configure Update).

32. The method according to supplementary note 30 or 31, wherein after the first IAB node establishes an F1 connection with the second host CU through the second DU, the method further includes:

The first donor CU receives the correspondence between the NCGI of the first cell and the NCGI of the second cell from the second donor CU.

33. The method according to any one of Supplements 28 to 32, wherein,

After the first donor CU receives at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell from the second donor CU, the method further includes:

The first donor CU sends an Xn handover request message for the terminal device to the second donor CU, where the Xn handover request message includes the second NCGI of the second cell.

34. The method according to supplementary note 33, wherein the method further includes:

35. The method according to any one of Supplements 23 to 34, wherein the method further comprises:

The first donor CU sends at least one of the first PCI of the first cell, the first downlink frequency point, and the first NCGI to the second donor CU.

36. The method according to appendix 35, wherein,

The first owner CU transfers the first PCI, the first downlink frequency point, and the At least one of the first NCGIs is sent to the second host CU.

37. The method according to any one of Supplements 23 to 36, wherein the method further comprises:

The first donor CU receives an air interface resource sharing indication sent by the first IAB node, where the air interface resource sharing indication is used to indicate that the first cell and the second cell share the same air interface resource.

38. The method according to supplementary note 37, wherein the method further includes:

The first host CU sends an air interface resource conversion instruction to the first IAB node, where the air interface resource conversion instruction is used to instruct the first IAB node to switch the air interface resource from broadcasting a signal related to the first cell Converting to broadcasting signals related to the second cell.

39. The method according to appendix 38, wherein,

Before the first host CU sends an air interface resource conversion instruction to the first IAB node, the method further includes:

40. The method according to appendix 38, wherein,

41. The method according to appendix 40, wherein,

42. The method according to appendix 40, wherein,

43. A terminal device transfer method, wherein the first IAB node is migrated from the first host CU to the second host CU, the method comprising:

An F1 connection is established between the second owner CU and the second DU of the first IAB node, so as to transfer the terminal device from the first cell of the first DU of the first IAB node to the second DU. The second cell: the establishment of the F1 connection is initiated by the first IAB node after receiving the F1 connection establishment instruction sent by the first owner CU;

44. The method according to supplementary note 43, wherein, before establishing the F1 connection between the second host CU and the second DU of the first IAB node, the method further includes:

The second host CU receives a request sent by the first host CU to establish an F1 connection between the second host CU and the first IAB node.

45. The method according to supplementary note 44, wherein the method further includes:

The second host CU sends to the first host CU an indication of accepting the request for establishing an F1 connection with the first IAB node.

46. The method according to appendix 45, wherein,

The second host CU sends an indication of accepting the request for establishing an F1 connection with the first IAB node to the first host CU through an Xn handover response message directed at the first IAB node.

47. The method according to supplementary note 43, wherein, before establishing the F1 connection between the second host CU and the second DU of the first IAB node, the method further includes:

The second host CU sends to the first host CU the TNL address configured for the first IAB node for establishing an F1 connection between the first IAB node and the second host CU.

48. The method according to supplementary note 43, wherein the TNL address used to establish the F1 connection between the first IAB node and the second host CU is included in the Xn handover response message for the first IAB node or included in the RRC reconfiguration message for the first IAB node carried in the Xn handover response message.

49. The method according to Supplementary note 47 or 48, wherein after establishing the F1 connection between the second host CU and the second DU of the first IAB node, the method further includes:

The second donor CU receives an Xn handover request message for the terminal device from the first donor CU, wherein the Xn handover request message includes the first NCGI of the first cell or includes the first NCGI of the second cell. Two NCGI.

50. The method according to Supplementary Note 47 or 48, wherein after the F1 connection is established between the second host CU and the second DU of the first IAB node, the method further includes:

The second donor CU sends at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell to the first donor CU.

51. The method according to appendix 50, wherein,

The second donor CU sends at least one of the second PCI, the second downlink frequency point, and the second NCGI of the second cell to the first donor CU through a node configuration update message (Node Configure Update).

52. The method according to Supplementary note 50 or 51, wherein after the F1 connection is established between the second host CU and the second DU of the first IAB node, the method further includes:

The second donor CU sends the correspondence between the NCGI of the first cell and the NCGI of the second cell to the first donor CU.

53. The method according to any one of Supplements 50 to 52, wherein,

After the second donor CU sends at least one of the second PCI of the second cell, the second downlink frequency point, and the second NCGI to the first donor CU, the method further includes:

The second donor CU receives an Xn handover request message for the terminal device from the first donor CU, where the Xn handover request message includes the second NCGI of the second cell.

54. The method according to any one of supplementary notes 47-53, wherein the method further comprises:

The second donor CU receives at least one of the first PCI, the first downlink frequency point, and the first NCGI of the first cell from the first donor CU.

55. The method according to appendix 54, wherein,

The second donor CU receives the first PCI of the first cell from the first donor CU through an Xn handover request message directed at the first IAB node or through an Xn handover request message directed at the terminal device , at least one of the first downlink frequency point and the first NCGI.

56. The method according to any one of Supplements 43 to 48, wherein when an F1 connection is established between the second host CU and the second DU of the first IAB node, the second host The CU receives at least one of the first PCI, the first downlink frequency point, and the first NCGI of the first cell sent by the first IAB node through the F1 establishment request message.

57. The method according to supplementary note 56, wherein the F1 establishment request message further includes:

58. The method according to any one of Supplements 45 to 57, wherein the first cell and the second cell share the same air interface resource.

59. The method according to supplementary note 58, wherein when the second host CU receives an Xn handover request for the terminal device from the first host CU, the method further includes:

The second host CU determines that the PCI or downlink frequency of the first cell is different from that of the second cell, and the second host CU does not send the UE aimed at the terminal device to the second DU of the IAB node Context establishment request.

Claims

An apparatus for transferring a terminal device, the apparatus is set in a first IAB node, wherein the first IAB node is migrated from a first host distribution unit (CU) to a second host CU, and the apparatus includes:

The first establishment unit, after receiving the F1 connection establishment instruction sent by the first host CU, makes the second distribution unit (DU) initiate the establishment of the F1 connection with the second host CU, so as to connect the terminal device transferring from a first cell of a first DU of the first IAB node to a second cell of a second DU;

Wherein, the first DU has established an F1 connection with the first host CU.
The device according to claim 1, wherein,

The F1 connection establishment instruction is sent by the first owner CU to the first IAB node through an RRC reconfiguration message or an F1AP message.
The device according to claim 2, wherein the device further comprises:

The third sending unit, when the second DU establishes an F1 connection with the second host CU, sends the first PCI, the first downlink frequency point, and the first NCGI of the first cell through an F1 establishment request message At least one of them is sent to the second host CU.
The apparatus according to claim 2, wherein the first IAB node shares the same air interface resources for the first cell of the first DU and the second cell of the second DU.
The device according to claim 4, wherein the device further comprises:

a first receiving unit, configured to receive an air interface resource conversion instruction from the first host CU;

A first conversion unit, which converts air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell.
The device according to claim 5, wherein the device further comprises:

A second receiving unit, which receives a system from the first host CU before the air interface resources of the first IAB node are switched from broadcasting signals related to the first cell to broadcasting signals related to the second cell an information change request, and send a system information change indication to the terminal device, so as to trigger the terminal device to receive system information related to the second cell.
The device according to claim 5, wherein the device further comprises:

A third receiving unit, before the first conversion unit converts the air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, receiving the first DU through the first DU A downlink F1AP message sent by the first owner CU, wherein the downlink F1AP message includes an RRC reconfiguration message for the terminal device;

A fourth sending unit, which sends the RRC reconfiguration message to the terminal device;

Wherein, the RRC reconfiguration message is used to transfer the terminal device from the first cell to the second cell; the RRC reconfiguration message at least includes master key update information and information for the terminal device Synchronize to the synchronization reconfiguration information (ReconfigurationWithSync) of the second cell.
The apparatus according to claim 7, wherein,

The RRC reconfiguration message is an RRC reconfiguration message for conditional handover (CHO); the RRC reconfiguration message also includes conditions for the terminal device to transfer to the second cell.
The apparatus according to claim 5, wherein,

The air interface resource conversion indication is carried in the last downlink F1AP message sent by the first host CU.
The device according to claim 7, wherein the device further comprises:

A fifth sending unit, after the first IAB node converts air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, the RRC received from the terminal device The reconfiguration complete message is sent to the second host CU through the second DU.
The apparatus according to claim 7, wherein after the first conversion unit converts air interface resources from broadcasting signals related to the first cell to broadcasting signals related to the second cell, the terminal device The C-RNTI in the second cell is the same as the C-RNTI of the terminal device in the first cell.
An apparatus for transferring a terminal device, the apparatus is set in a first host CU, and the apparatus is applied when a first IAB node migrates from the first host CU to a second host CU, the apparatus includes:

A sixth sending unit, which sends an F1 connection establishment instruction to the first IAB node, where the F1 connection establishment instruction is used to instruct the first IAB node to establish an F1 connection with the second host CU through a second DU, so that for transferring a terminal device from a first cell of a first DU of said first IAB node to a second cell of a second DU;

Wherein, the first host CU has established an F1 connection with the first DU of the first IAB node.
The apparatus of claim 12, wherein,

The first owner CU sends the F1 connection establishment instruction to the first IAB node through an RRC reconfiguration message or an F1AP message.
The apparatus according to claim 13, wherein said apparatus further comprises:

A first request unit, which requests the second host CU to establish an F1 connection with the first IAB node before the first host CU sends an F1 connection establishment instruction to the first IAB node.
The apparatus according to claim 12, wherein said apparatus further comprises:

The fifth receiving unit, before the first host CU sends an F1 connection establishment instruction to the first IAB node, the first host CU receives the user configured by the second host CU for the first IAB node A TNL address for establishing an F1 connection between the first IAB node and the second host CU; wherein, the TNL address is included in an Xn handover response message for the first IAB node.
The apparatus of claim 15, wherein,

The TNL address used to establish the F1 connection between the first IAB node and the second host CU is included in the RRC reconfiguration message for the first IAB node carried by the Xn handover response message;

The first host CU forwards the RRC reconfiguration message for the first IAB node to the first IAB node, where the RRC reconfiguration message is used to indicate that the first IAB node is related to the The second host CU establishes an F1 connection.
The device according to claim 15, wherein the device further comprises:

The second initiating unit, when the first host CU sends the last downlink F1AP message containing the RRC reconfiguration message used to transfer the terminal device, or when the first host CU receives the first host CU Initiating the release of the F1 connection with the first DU of the first IAB node when the UE context release indication message for the last terminal device is sent by the second owner CU.
The device according to claim 15, wherein the device further comprises:

The eighth receiving unit, after the first IAB node establishes an F1 connection with the second host CU through the second DU, receives the second PCI of the second cell, the second downlink Frequency point and at least one of the second NCGI.
The device according to claim 15, wherein the device further comprises:

A ninth sending unit, configured to send at least one of the first PCI, the first downlink frequency point, and the first NCGI of the first cell to the second donor CU.
The device according to claim 15, wherein the device further comprises:

A tenth receiving unit, configured to receive an air interface resource sharing indication sent by the first IAB node, where the air interface resource sharing indication is used to indicate that the first cell and the second cell share the same air interface resource.