CN115119269A

CN115119269A - Switching method and device of self-return network and network side equipment

Info

Publication number: CN115119269A
Application number: CN202110286829.2A
Authority: CN
Inventors: 刘进华
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2021-03-17
Filing date: 2021-03-17
Publication date: 2022-09-27
Anticipated expiration: 2041-03-17
Also published as: CN115119269B; WO2022194074A1

Abstract

The application discloses a switching method and device of a self-return network and network side equipment, and belongs to the field of wireless communication. The switching method of the self-return network in the embodiment of the application comprises the following steps: under the condition of triggering switching, an original CU node sends a second network switching request at least comprising context information of a first network node to a target CU node, wherein the context information is the context information of the first network node during switching triggering, and the first network switching request is sent to the target CU node by the original CU node before switching triggering relative to at least part of information of change of the context information of the first network node in the first network switching request; receiving a second network switching response sent by the target CU node, wherein the second network switching response at least comprises second reconfiguration information; configuring switching of the first network node from the original CU node to the target CU node based on the first reconfiguration information and the second reconfiguration information.

Description

Switching method and device of self-return network and network side equipment

Technical Field

The present application belongs to the field of wireless communication technologies, and in particular, to a method and an apparatus for switching a self-backhaul network, and a network side device.

Background

In a New Radio (NR) system, an Integrated Access Backhaul (IAB) may provide extended coverage for an NR cell and may also provide capacity enhancement for the NR cell, where an Access node that supports wireless Access of a User Equipment (UE) and wirelessly backhauls data is referred to as an IAB node (IABN). Data are transmitted between the UE and the access node through a wireless access link (access link), and data are transmitted between the access nodes through a wireless backhaul link.

In the Mobile IAB System (Mobile IAB System), the supporting Centralized Unit (CU) node of the IAB network is located in the host (donor) IAB node, called IAB-donor-CU, and all nodes directly connected to the donor IAB node or connected to the donor IAB node through the downstream IAB node of the donor IAB node are controlled by the IAB-donor-CU. That is, one IAB node and its downstream nodes (IAB/UE) are controlled by the IAB-node-CU of the IAB node, i.e., context information of the mobile IAB network is in the IAB-node-CU.

In this case, taking a high-speed moving scenario as an example, if the IAB node is deployed on a high-speed train, the mobile user and the mobile IAB node move along with each other, and the IAB-donor-CU node is fixed, once the high-speed train crosses a CU node coverage area boundary to reach another CU node coverage area, the mobile IAB node and its downstream nodes (e.g., IAB nodes/UE nodes) deployed on the train need to be handed over from the original IAB-donor-CU node to the target IAB-donor-CU node, and at the same time, context information of the mobile IAB node and its downstream nodes also need to be sent from the original IAB-donor-CU node to the target IAB-donor-CU node, so that the target IAB-donor-CU node can generate a reconfiguration message based on the context information of the mobile IAB node and its downstream nodes, and the signaling is sent to the mobile IAB node and the downstream nodes thereof through the original IAB-donor-CU node, which means that a large amount of signaling needs to be transmitted, thus causing the occurrence of signaling storm and the increase of switching delay.

Disclosure of Invention

The embodiment of the application provides a switching method and device for a self-return network and network side equipment, which can solve the problems of signaling storm and large switching delay which may occur during switching of an IAB network.

In a first aspect, a handover method for a self-backhaul network is provided, where the handover method is performed by an original CU node, and the method includes: under the condition of triggering handover, sending a second network handover request to a target CU node, wherein the second network handover request at least comprises context information of a first network node, the context information is the context information of the first network node when the handover is triggered, and at least part of information which is changed relative to the context information of the first network node and is included in the first network handover request is sent to the target CU node by the original CU node before the handover is triggered, and the first network node is any network node in an IAB network to be switched; receiving a second network switching response sent by the target CU node, wherein the second network switching response at least comprises second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network switching request; and configuring the switching of the first network node from the original CU node to a target CU node based on first reconfiguration information and the second reconfiguration information, wherein the first reconfiguration information is generated by the target CU node according to the first network switching request before the switching is triggered.

In a second aspect, a handover method for a self-backhaul network is provided, which is performed by a target CU node, and includes: receiving a second network switching request sent by an original CU node when switching is triggered, wherein the second network switching request at least comprises context information of a first network node, the context information is the context information of the first network node when switching is triggered, and at least part of information which is changed relative to the context information of the first network node and is included in the first network switching request is sent to a target CU node by the original CU node before switching is triggered, and the first network node is any network node in an IAB network to be switched; and sending a second network switching response to the original CU node, wherein the second network switching response comprises second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network switching request.

In a third aspect, a switching apparatus for a self-backhauled network is provided, the apparatus comprising: a first sending module, configured to send a second network handover request to a target CU node when handover is triggered, where the second network handover request includes at least context information of a first network node, where the context information is context information of the first network node when handover is triggered, and at least part of information that changes with respect to the context information of the first network node included in the first network handover request, the first network handover request is sent to the target CU node by an original CU node before handover is triggered, and the first network node is any network node in an IAB network to be handed over;

a first receiving module, configured to receive a second network handover response sent by the target CU node, where the second network handover response at least includes second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network handover request; a configuration module, configured to configure switching of the first network node from the original CU node to a target CU node based on first reconfiguration information and the second reconfiguration information, where the first reconfiguration information is generated by the target CU node according to the first network switching request before triggering switching.

In a fourth aspect, a switching apparatus for a self-backhauled network is provided, the apparatus comprising: a first sending module, configured to send a second network handover request to a target CU node when handover is triggered, where the second network handover request includes at least context information of a first network node, where the context information is context information of the first network node when handover is triggered, and at least part of information that changes with respect to the context information of the first network node included in the first network handover request, the first network handover request is sent to the target CU node by an original CU node before handover is triggered, and the first network node is any network node in an IAB network to be handed over; a first receiving module, configured to receive a second network handover response sent by the target CU node, where the second network handover response at least includes second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network handover request; a configuration module, configured to configure switching of the first network node from the original CU node to a target CU node based on first reconfiguration information and the second reconfiguration information, where the first reconfiguration information is generated by the target CU node according to the first network switching request before triggering switching.

In a fifth aspect, a network side device is provided, which comprises a processor, a memory and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method according to the first or second aspect.

In a sixth aspect, a network-side device is provided, which includes a processor and a communication interface, where the processor and the communication interface are configured to implement the steps of the method according to the first aspect or the second aspect.

In a seventh aspect, there is provided a readable storage medium on which a program or instructions is stored, which program or instructions, when executed by a processor, performs the steps of the method according to the first aspect, or performs the steps of the method according to the second aspect.

In an eighth aspect, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a network-side device program or instruction, implement the method according to the first aspect, or implement the method according to the second aspect.

In a ninth aspect, there is provided a computer program product comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the method of the first or second aspect.

In the embodiment of the application, the original CU node acquires the first reconfiguration information through the first network handover request before handover triggering, so that under the handover triggering condition, only the reconfiguration information corresponding to the changed information in the context information needs to be acquired through the second network handover request, and therefore, the amount of signaling to be transmitted after the handover triggering is triggered can be greatly reduced, so that a signaling storm is avoided, meanwhile, the handover delay caused by the need of acquiring the reconfiguration information can be shortened, and the network handover performance is ensured.

Drawings

Fig. 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment of the present application.

Fig. 2a is a schematic structural diagram of a mobile IAB system according to an exemplary embodiment of the present application.

Fig. 2b is a schematic structural diagram of an IAB network to be switched according to an exemplary embodiment of the present application.

Fig. 3 is a flowchart illustrating a handover method 300 for a self-backhauled network according to an exemplary embodiment of the present application.

Fig. 4 is a flowchart illustrating a handover method 400 for a self-backhauled network according to an exemplary embodiment of the present application.

Fig. 5 is an interaction flow diagram of a handover method 500 for a self-backhauled network according to an exemplary embodiment of the present application.

Fig. 6 is a flowchart illustrating a handover method 600 for a self-backhauled network according to an exemplary embodiment of the present application.

Fig. 7 is a block diagram illustrating a switching device 700 of a self-backhaul network according to an exemplary embodiment of the present application.

Fig. 8 is a block diagram illustrating a switching device 800 of a self-backhaul network according to an exemplary embodiment of the present application.

Fig. 9 is a schematic block structure diagram of a network-side device according to an exemplary embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described clearly below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in other sequences than those illustrated or otherwise described herein, and that the terms "first" and "second" are generally used herein in a generic sense to distinguish one element from another, and not necessarily from another element, such as a first element which may be one or more than one. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a new air interface NR system for purposes of example, and using NR terminology in much of the description below, the techniques may also be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.

Fig. 1 shows a diagram of the results of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be referred to as a terminal Device or a user terminal, the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palm top Computer, a netbook, an ultra-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, and the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but a specific type of the Base Station is not limited.

In this embodiment of the present application, the UE may include, but is not limited to, a Mobile Station (MS), a Mobile Terminal (Mobile Terminal), a Mobile phone (Mobile phone), a handset (handset), a portable device (portable equipment), a vehicle (vehicle), and the like, and the UE may communicate with one or more core networks through a Radio Access Network (RAN), for example, the UE may provide a Radio Access service through an IAB Network node. Alternatively, the UE may be a mobile telephone (or so-called "cellular" telephone), a computer with wireless communication capabilities, or the like, and the terminal device may also be a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device.

On this basis, please refer to fig. 2a in combination, where fig. 2a is a structure diagram of a CU-DU of the mobile IAB system according to an embodiment of the present application. Specifically, in a self-feedback link, the DUs in the most upstream IAB network node in the IAB network (e.g., IAB network 1 in fig. 2 a) are all connected to a CU network, and the CU network can configure the DUs through the F1-AP protocol and configure the MT through the Radio Resource Control (RRC) protocol. A self-backhauling link also includes a home (Donor) IAB network node (alternatively referred to as an IAB Donor) that does not have MT functionality, but has a wireline transport network directly connected to it.

In this case, taking the IAB network 1 shown in fig. 2a (i.e. the IAB network to be switched) as an example, the IAB network 1 may include a plurality of IAB network nodes (e.g. IAB1, IAB2, IAB3 … … shown in fig. 2 b) connected in a cascade manner, and UEs (e.g. UE1, UE2 … … shown in fig. 2 b) providing network access services through the respective IAB network nodes, where the IAB1 is an upstream-most IAB network node in the IAB network 1, the IAB1 is a parent IAB network node of the downstream network node IAB2 adjacent thereto, the IAB2 is a parent IAB network node … … of the downstream network node IAB3 adjacent thereto, in other words, the IAB2 is a child IAB network node of the upstream IAB1 adjacent thereto, and the IAB3 is a child IAB network node 2 adjacent thereto. In addition, one IAB network node may provide network access services for one or more UEs.

The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings through some embodiments and application scenarios thereof.

As shown in fig. 3, which is a flowchart illustrating a switching method 300 for a self-backhaul network according to an exemplary embodiment of the present application, the method 300 may be executed by an original CU node, and specifically may be executed by software and/or hardware installed in the original CU node. The method 300 includes at least the following steps.

And S310, sending a second network switching request to the target CU node under the condition of triggering the switching.

The second network handover request at least includes context information of a first network node, where the context information is context information of the first network node when handover is triggered, and at least part of information that changes with respect to the context information of the first network node included in the first network handover request, the first network handover request is sent to the target CU node by the original CU node before handover is triggered, and the first network node is any network node in the IAB network to be handed over, such as an IAB node or a UE served by the IAB node.

Accordingly, the context information of the first network node may be different according to the first network node, for example, in the case that the first network node is an IAB node, the context information includes the context information of an IAB-MT and/or the context information of an F1 connection of an IAB-DU; for another example, in case the first network node is a UE, the context information of the RRC connection.

It is to be understood that the first network handover request, i.e. the early handover request, is sent by the original CU node to the target CU node before the handover is triggered, to acquire the reconfiguration information of each network node in the IAB network to be switched in advance before triggering the switching, therefore, in the case of triggering the handover, the original CU node can be enabled to acquire a small amount of reconfiguration information by sending a second network handover request (namely, a later handover request), for example, the reconfiguration information corresponding to the information that the context information of the first network node changes relative to the context information of the first network node included in the first network handover request, so as to greatly reduce the signaling amount (such as signaling and empty signaling) that needs to be transmitted after the handover is triggered, thereby avoiding the occurrence of signaling storm and shortening the switching time delay caused by the need of acquiring the reconfiguration information.

In addition, a preset time interval is arranged between the sending time of the first network switching request and the sending time of the second network switching request, so as to ensure that the original CU node has already acquired the reconfiguration information of each network node in the IAB network to be switched before the switching is triggered. That is, the original CU node triggers a pre-handover preparation for each network node to be handed over, one time advance before the handover trigger.

Optionally, the predetermined time interval and/or an actual sending time point of the first network handover request before triggering handover may be configured through a high-level signaling configuration or a protocol agreement, or configured by an OAM system, which is not limited in this embodiment.

And S320, receiving a second network switching response sent by the target CU node.

Wherein, corresponding to the second network handover request in the foregoing S320, the second network handover response at least includes second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network handover request. In this embodiment, since the second network handover request includes the context information or the changed part of the context information of the first network node, in response, the second network handover response sent by the target CU node to the original CU node may also include the handover reconfiguration information or the changed part of the handover reconfiguration information corresponding to the changed part of the context information or the context information.

Optionally, in a case that the first network node is a UE, the second reconfiguration information includes Radio Resource Control (RRC) reconfiguration information; in case the second network node is an IAB node, the second reconfiguration information comprises RRC reconfiguration information of an IAB-MT and/or F1 connection reconfiguration message of an IAB-DU.

In addition, the second network handover request may include indication information indicating that it is a late handover request, and the indication information may be agreed by a higher layer configuration or a protocol, which is not limited thereto.

S330, switching of the first network node from the original CU node to a target CU node is configured based on the first reconfiguration information and the second reconfiguration information.

Wherein the first reconfiguration information is generated by the target CU node according to the first network handover request before triggering handover. In addition, similar to the second reconfiguration information, in the case that the first network node is a UE, the first reconfiguration information may include RRC reconfiguration information; in case the second network node is an IAB node, the first reconfiguration information may comprise RRC reconfiguration information of an IAB-MT and/or F1 connection reconfiguration message of an IAB-DU.

For example, based on the foregoing descriptions of S310-S330, please refer to fig. 2b again, it is assumed that before triggering the handover, the original CU node sends context information of the IAB network 1 to be handed over (including the IAB1, the IAB2, the IAB3, the UE1, and the UE2 … …) to the target CU node through a first network handover request, and acquires the first reconfiguration information corresponding to the context information for the subsequent handover of each network node in the IAB network 1. However, in the case of triggering handover, if for some reason, the context information of the IAB1 node in the IAB network 1 changes with respect to the context information of the IAB1 node (i.e. the aforementioned first network node) included in the first network handover request, then the original CU node may send the changed context information of the IAB1 node to the target CU node through the second network handover request again to obtain the second reconfiguration information corresponding to the target CU node, and then configure the handover of the IAB1 node based on the first reconfiguration information and the second reconfiguration information, and configure the handovers of other network nodes except the IAB1 node in the IAB network 1 based on the first reconfiguration information, thereby greatly reducing the amount of signaling that needs to be transmitted after triggering handover after handover triggering, and further avoiding signaling storm, and shorten the switching time delay caused by needing to obtain the reconfiguration information, ensure the network switching performance.

As shown in fig. 4, which is a flowchart illustrating a switching method 400 of a self-backhaul network according to an exemplary embodiment of the present application, the method 400 may be executed by an original CU node, and specifically may be executed by software and/or hardware installed in the original CU node. The method 300 includes at least the following steps.

S410, under the condition that the IAB network switching is predicted to be needed, the first network switching request is sent to the target CU node.

Wherein the first network switch request at least includes context information of the first network node when the original CU node sends the first network switch request. It will be appreciated that when a plurality of network nodes are included in the IAB network to be handed over, the first network handover request may include context information for the plurality of network nodes.

In one implementation, the first network handover request may further include first information for indicating that the first network handover request is an early handover request to the target CU node. Optionally, the first network handover request may be used as an early handover request, a new RRC IE may be used, or an existing handover request IE may be reused, for example, an indication field (i.e., first information) is added to the existing handover request IE to indicate that the target CU node does not immediately reserve resources for the nodes to be switched, so as to avoid resource waste.

In this embodiment, the first information may include a handover occurrence location and/or a handover occurrence time point, where the handover occurrence location and/or the handover occurrence time point are predicted by the original CU node according to a predetermined movement route, a movement speed, and deployment information of the alternative IAB host of the mobile IAB system. It is to be understood that the predetermined moving route, the moving speed, and the deployment information of the alternative IAB host of the mobile IAB system may be protocol agreement or configured through high layer signaling, and the like, which is not limited herein.

And S420, receiving a first network switching response sent by the target CU node.

The first network handover response is generated by the target CU node according to the first network handover request, that is, the first reconfiguration information included in the first network handover response is generated by the target CU node according to the context information included in the first network handover request.

Corresponding to the first network handover request, the first network handover response may also include second information, where the second information is used to indicate that the first network handover response is an early handover response. In practical applications, the second network handover response may use a new RRC IE, or reuse an existing handover request response IE, for example, add an indication field (i.e., the second information) to the existing handover request IE to indicate that it is an early handover request response.

And S430, under the condition of triggering the switching, sending a second network switching request to the target CU node.

The second network handover request at least includes context information of a first network node, where the context information is context information of the first network node when handover is triggered, and at least part of information that changes with respect to the context information of the first network node included in the first network handover request, the first network handover request is sent to the target CU node by the original CU node before handover is triggered, and the first network node is any network node in the IAB network to be handed over.

S440, receiving a second network switching response sent by the target CU node.

Wherein the second network handover response includes at least second reconfiguration information generated by the target CU node according to the second network handover request.

S450, configuring the switching of the first network node from the original CU node to the target CU node based on the first reconfiguration information and the second reconfiguration information.

Wherein the first reconfiguration information is generated by the target CU node according to the first network handover request before handover is triggered.

It should be noted that, as a possible implementation manner in this embodiment, the implementation process of S430-S450 may include at least one of the following (1) to (2), besides referring to the related description in the foregoing method embodiment 300, and configuring, based on the first reconfiguration information and the second reconfiguration information, the switching of the first network node from the original CU node to the target CU node in S450.

(1) And the original CU node sends a switching trigger notice to the target CU node, wherein the switching trigger notice is used for informing the target CU node of the node information of the first network node. Optionally, the handover trigger notification may include a list of handover node identifiers, so as to indicate that the node corresponding to the handover node identifier is a node to be handed over (e.g., the first network node).

(2) And the original CU node sends a switching trigger notice to the target CU node, wherein the switching trigger notice is used for informing the target CU node that the switching of the first network node is about to occur.

It can be understood that the original CU node may indicate, to the target CU node, that the node information of the first network node and the handover of the first network node are about to occur simultaneously through one handover trigger notification, or may indicate, to the target CU node, that the node information of the first network node and the handover of the first network node are about to occur respectively through two handover trigger notifications, which is not limited to this.

On the basis, after receiving the switching trigger notification, the target CU node may configure resources for a node to be switched (e.g., a first network node) and send determination information to the original CU node, and the original CU node sends target reconfiguration information to the first network node when receiving confirmation information fed back by the target CU node, so that the timing of switching occurrence may be controlled without affecting the UE, and user communication experience is ensured.

It is to be understood that the target reconfiguration information is obtained by replacing or updating the first reconfiguration information with the second reconfiguration information. That is, if the second network handover response (i.e. the later handover response message of one node) received by the original CU node includes all the reconfiguration parameter settings of the first network node, the second reconfiguration information (i.e. the later reconfiguration message) is directly used to replace the first reconfiguration information (i.e. the earlier reconfiguration message), and is sent to the first network node as the target reconfiguration information; if the second network switch response (i.e. the later switch response message of one node) received by the original CU node only contains the reconfiguration parameter setting of the portion corresponding to the changed context information, the original CU combines the second reconfiguration information (i.e. the later reconfiguration message) corresponding to the first network node instead of the first reconfiguration information (i.e. the earlier reconfiguration message), and sends the combined reconfiguration information as the target reconfiguration information to the first network node to replace the earlier cached first reconfiguration information.

Further, after sending the target reconfiguration information to the first network node, if the first network node is an IAB node, the IAB node stores the received target reconfiguration information, and sends the stored target reconfiguration information to the UE served by the IAB node after the handover is triggered; or, the IAB node stores the received target reconfiguration information, simultaneously sends the target reconfiguration information to the UEs served by the IAB node, and then stores the respective reconfiguration information, so that each network node can directly perform handover based on the cached reconfiguration information when receiving the trigger notification by caching the respective reconfiguration information in advance, thereby greatly shortening the handover delay.

For example, the original CU node may send a handover start notification message to the first network node when determining to trigger handover (e.g., the original CU node receives measurement report information from the mobile IAB-MT and decides to perform handover of the mobile IAB system from the original CU node to the target CU node), where the handover start notification message is used to instruct the first network node to perform handover according to the cached target reconfiguration information, and accordingly, the first network node starts to initiate handover according to the handover start notification message when receiving the handover start notification message.

Alternatively, the handover start notification information may be transmitted through F1 signaling, RRC signaling, or BAP Control PDU signaling.

Further, in addition to the foregoing description, as a possible implementation manner, for a first network node whose context information has not changed, that is, after triggering a handover, the context information of the first network node has not changed with respect to the context information of the first network node included in the first network handover request, then, in case of triggering a handover, the original CU node may configure the handover of the first network node from the original CU node to a target CU node directly based on the first reconfiguration information.

For example, after triggering the handover, the original CU node sends a handover trigger notification to the target CU node to notify the target CU node of node information for notifying the target CU node of the first network node, and/or notifies the target CU node that the handover of the first network node is about to occur, and sends the first reconfiguration information to the first network node for caching, and/or the first network node forwards the reconfiguration information to the UE or the like served by the first network node, so that the first network node and/or the UE served by the first network node can perform the handover based on the respective cached reconfiguration information, thereby avoiding acquiring the reconfiguration information in case of the handover trigger, and thus being capable of greatly reducing the amount of signaling that needs to be transmitted after triggering the handover, and further avoiding the occurrence of a signaling storm, and shorten the switching time delay caused by needing to obtain the reconfiguration information, ensure the network switching performance.

The timing when the original CU node sends the first reconfiguration information to the first network node may be before the handover trigger, may be when it is determined that the context information of the first network node is not changed, or may be when it receives the confirmation information sent by the target CU node, which is not limited herein.

In this embodiment 400, based on the multi-stage handover process (e.g., the early handover preparation process corresponding to the first network handover request and the late handover preparation process corresponding to the second network handover request), most signaling (e.g., signaling of an Xn interface, etc.) interaction between the original CU node and the target CU node is completed before handover trigger, and there is a large time advance.

In addition, in the switching method of the self-backhaul network provided by this embodiment, the switching process is always under the control of the network, and the scale switching is achieved under the condition of avoiding the switching storm, for example, when the IAB network node to be switched includes a plurality of first network nodes, the scale switching of the plurality of first network nodes is simultaneously achieved.

Further, based on the description of the foregoing method embodiments 300 and 400, the following describes a handover procedure of the self-backhaul network provided by the present application with reference to fig. 5, which is as follows.

Early handover preparation procedure

And S502, the original CU node predicts whether the IAB network switching is required according to a preset moving route and moving speed of the mobile IAB system and the deployment information of the alternative IAB host.

S504, when it is predicted that the IAB network switching is required, the original CU node sends the first network switching request to the target CU node.

S506, the target CU node sends a first network switching response to the original CU node.

Late handover preparation procedure

And S508, under the condition that the original CU node determines to trigger the switching, sending a second network switching request to the target CU node.

S510, the target CU node sends a second network switching response to the original CU node.

S512, the original CU node sends a switching trigger notification to the target CU node.

And S514, the target CU node configures resources for the node to be switched, and feeds back confirmation information to the original CU node.

S516, the original CU node sends the target reconfiguration information as an IAB node 1, and/or the original CU node sends the first reconfiguration information as the IAB node 1, where the IAB node 1 indicates a node whose context information changes with respect to the context information of the IAB node 1 included in the first network handover request after the handover trigger, and the IAB node 2 indicates a node whose context information does not change with respect to the context information of the IAB node 2 included in the first network handover request after the handover trigger.

S518, the IAB node 1 caches the received target reconfiguration information, and/or the IAB node 2 caches the received first reconfiguration information.

S520, the IAB node 1 caches the received target reconfiguration information, and/or the IAB node 2 caches the received first reconfiguration information.

Optionally, IAB node 1 sends the received target reconfiguration information to the UE1 served by it, and/or IAB node 2 sends the received first reconfiguration information to the UE2 served by it.

S522, the original CU node sends a handover start notification message to the IAB node 1 and the IAB node 2.

S524, in the case of the received handover start notification information, the IAB node 1 and the IAB node 2 perform handover based on the cached reconfiguration information.

It should be noted that, for the specific implementation process of the foregoing S502-S524, reference may be made to the related description of the foregoing

method embodiment

300 or 400 to achieve the same technical effect, and further description is omitted here for avoiding repetition.

As shown in fig. 6, which is a flowchart illustrating a switching method 600 of a self-backhaul network according to an exemplary embodiment of the present application, the method 600 may be executed by a target CU node, and specifically may be executed by software and/or hardware installed in the target CU node. The method 600 includes at least the following steps.

S610, receiving a second network handover request sent by an original CU node when handover is triggered, where the second network handover request at least includes context information of a first network node, where the context information is context information of the first network node when handover is triggered, and with respect to at least part of information that the context information of the first network node included in the first network handover request changes, the first network handover request is sent to the target CU node by the original CU node before handover is triggered, and the first network node is any network node in the IAB network to be switched;

s620, sending a second network switching response to the original CU node, where the second network switching response includes second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network switching request.

In this embodiment 600, before the handover trigger, the target CU node generates first reconfiguration information according to the received first network handover request and sends the first reconfiguration information to the original CU node, such that, in the case of a handover trigger, only the second reconfiguration information needs to be generated and sent to the source CU node based on the received second network handover request, wherein the context information of the first network node at least included in the second network handover request is at least partial information of the change of the context information of the first network node relative to the context information of the first network node included in the first network handover request when the handover is triggered, so that the signaling amount required to be transmitted after the handover is triggered can be greatly reduced, and further avoiding the occurrence of signaling storm, shortening the switching time delay caused by the need of acquiring the reconfiguration information, and ensuring the network switching performance.

In a possible implementation manner, after sending the second network handover response to the original CU node, the method further includes at least one of the following (1) - (2).

(1) Receiving a switching trigger notification sent by the original CU node, wherein the switching trigger notification is used for notifying the target CU node of the node information of the first network node;

(2) and receiving a switching trigger notification sent by the original CU node, wherein the switching trigger notification is used for notifying the target CU node that the switching of the first network node is about to occur.

In another possible implementation manner, after receiving a handover trigger notification sent by the original CU node, the method further includes: and under the condition of receiving the switching trigger notification, feeding back confirmation information to the original CU node and/or configuring network switching resources corresponding to the first network node.

In another possible implementation manner, before receiving the second network handover request sent by the original CU node, the method further includes: receiving a first network switching request sent by the original CU node, wherein the first network switching request is sent by the original CU node under the condition that the IAB network switching is predicted to be needed, and the first network switching request at least comprises context information of the first network node when the original CU node sends the first network switching request; and sending a first network switching response to the original CU node, wherein the first network switching response comprises first reconfiguration information, and the first reconfiguration information is generated by the target CU node according to the first network switching request before switching is triggered.

In another possible implementation manner, the first network handover request further includes first information, which is used to indicate that the first network handover request is an early handover request; and/or

The first network handover response further includes second information, where the second information is used to indicate that the first network handover response is an early handover response.

In another possible implementation manner, the first information includes a handover occurrence location and/or a handover occurrence time point, where the handover occurrence location and/or the handover occurrence time point are predicted by the original CU node according to a predetermined movement route, a movement speed, and deployment information of the alternative IAB host of the mobile IAB system.

In another possible implementation manner, in a case that the first network node is a UE, the first reconfiguration information and the second reconfiguration information include RRC reconfiguration information; in a case where the second network node is an IAB node, the first reconfiguration information and the second reconfiguration information include RRC reconfiguration information of an IAB-MT and/or F1 connection reconfiguration messages of an IAB-DU.

It should be noted that, since the foregoing implementation manners provided in the method embodiment 600 have the same or corresponding technical features as those of the implementation manners in the method embodiments 300-500, the implementation process of the method embodiment 600 may refer to the related description of the method embodiment 300-500, and in order to avoid repetition, details are not repeated here.

It should be noted that, in the

switching method

300 and 600 for self-backhaul network provided in the embodiment of the present application, the execution subject may be a switching device for self-backhaul network, or a control module in the switching device for self-backhaul network for executing the

switching method

300 and 600 for self-backhaul network. In the embodiment of the present application, the

method

300 and 600 for executing the handover from the backhaul network by the handover device of the backhaul network are taken as an example to illustrate the handover device of the backhaul network provided in the embodiment of the present application.

As shown in fig. 7, a switching apparatus 700 of a self-backhaul network according to an exemplary embodiment of the present application is provided, where the apparatus 700 includes: a first sending module 710, configured to send a second network handover request to a target CU node when a handover is triggered, where the second network handover request includes at least context information of a first network node, where the context information is context information of the first network node when the handover is triggered, and is at least partial information that changes with respect to the context information of the first network node included in the first network handover request, where the first network handover request is sent to the target CU node by an original CU node before the handover is triggered, and the first network node is any network node in the IAB network to be handed over; a first receiving module 720, configured to receive a second network handover response sent by the target CU node, where the second network handover response at least includes second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network handover request; a configuring module 730, configured to configure switching of the first network node from the original CU node to a target CU node based on first reconfiguration information and the second reconfiguration information, where the first reconfiguration information is generated by the target CU node according to the first network switching request before triggering switching.

In one possible implementation, the configuration module 730 is configured to at least one of: sending a switching trigger notification to the target CU node, wherein the switching trigger notification is used for notifying the target CU node of the node information of the first network node; sending a handover trigger notification to the target CU node, the handover trigger notification to notify the target CU node that handover of the first network node is imminent.

In another possible implementation manner, the first sending module 710 is further configured to send, under the condition that the confirmation information fed back by the target CU node is received, target reconfiguration information to the first network node, where the target reconfiguration information is obtained by replacing or updating the first reconfiguration information with the second reconfiguration information.

In another possible implementation manner, the configuring module 730 is further configured to configure, based on the first reconfiguration information, the handover of the first network node from the original CU node to the target CU node in a case that the handover is triggered.

In another possible implementation manner, the first sending module 710 is further configured to send a handover start notification message to the first network node, where the handover start notification message is used to instruct the first network node to perform handover according to the cached target reconfiguration information and/or the first reconfiguration information.

In another possible implementation manner, the handover start notification information is transmitted through F1 signaling, RRC signaling, or BAP Control PDU signaling.

In another possible implementation manner, the first sending module 710 is further configured to send the first network handover request to the target CU node when it is predicted that the IAB network handover is needed, where the first network handover request at least includes context information of the first network node when the original CU node sends the first network handover request; the first receiving module 720 is further configured to receive a first network handover response sent by the target CU node, where the first network handover response includes the first reconfiguration information.

In another possible implementation manner, the first network handover request further includes first information, which is used to indicate that the first network handover request is an early handover request; and/or the first network handover response further comprises second information, wherein the second information is used for indicating that the first network handover response is an early handover response.

In another possible implementation manner, a predetermined time interval is provided between the sending time of the first network handover request and the sending time of the second network handover request.

As shown in fig. 8, a schematic block diagram of a switching apparatus 800 for a self-backhaul network according to an exemplary embodiment of the present application is provided, where the apparatus 800 includes: a second receiving module 810, configured to receive a second network handover request sent by an original CU node when handover is triggered, where the second network handover request at least includes context information of a first network node, where the context information is context information of the first network node when handover is triggered, and at least part of information that changes with respect to the context information of the first network node included in the first network handover request, the first network handover request is sent to a target CU node by the original CU node before handover is triggered, and the first network node is any network node in an IAB network to be handed over; a second sending module 820, configured to send a second network handover response to the original CU node, where the second network handover response includes second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network handover request.

In a possible implementation manner, the second receiving module 810 is further configured to at least one of: receiving a switching trigger notification sent by the original CU node, wherein the switching trigger notification is used for notifying the target CU node of the node information of the first network node; and receiving a switching trigger notification sent by the original CU node, wherein the switching trigger notification is used for notifying the target CU node that the switching of the first network node is about to occur.

In another possible implementation manner, the second sending module 820 is further configured to, in a case that the handover trigger notification is received, feed back acknowledgement information to the original CU node, and/or configure a network handover resource corresponding to the first network node.

In another possible implementation manner, the second receiving module 810 is further configured to receive a first network handover request sent by the original CU node, where the first network handover request is sent by the original CU node when the IAB network handover is predicted to be required, and the first network handover request at least includes context information of the first network node when the original CU node sends the first network handover request; the second sending module 820 is further configured to send a first network handover response to the original CU node, where the first network handover response includes first reconfiguration information, and the first reconfiguration information is generated by the target CU node according to the first network handover request before handover is triggered.

The

switching device

700 or 800 of the self-backhaul network in the embodiment of the present application may be a device, a device or an electronic device having an operating system, or may be a component, an integrated circuit, or a chip in a terminal. The device or the electronic equipment can be a mobile terminal or a non-mobile terminal. By way of example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.

The

switching device

700 or 800 of the self-backhaul network according to the embodiment of the present application can implement each process implemented by the method embodiments of fig. 3 to fig. 6, and achieve the same technical effect, and for avoiding repetition, the details are not described here again.

The embodiment of the present application further provides a network side device, which includes a processor and a communication interface, where the processor is configured to implement the steps in the foregoing method embodiment 300-600. The embodiment of the network side device corresponds to the embodiment of the method of the network side device, and all implementation processes and implementation manners of the embodiment of the method can be applied to the embodiment of the network side device and can achieve the same technical effect.

Specifically, the embodiment of the application further provides a network side device. As shown in fig. 9, the network device 900 includes: antenna 901, radio frequency device 902, baseband device 903. The antenna 901 is connected to a radio frequency device 902. In the uplink direction, rf device 902 receives information via antenna 901 and sends the received information to baseband device 903 for processing. In the downlink direction, the baseband device 903 processes information to be transmitted and transmits the processed information to the radio frequency device 902, and the radio frequency device 902 processes the received information and transmits the processed information through the antenna 901.

The above-mentioned frequency band processing means may be located in the baseband apparatus 903, and the method performed by the network side device in the above embodiment may be implemented in the baseband apparatus 903, where the baseband apparatus 903 includes a processor 904 and a memory 905.

The baseband device 903 may include at least one baseband board, for example, a plurality of chips are disposed on the baseband board, as shown in fig. 9, where one of the chips, for example, the processor 904, is connected to the memory 905 to call up a program in the memory 905 to perform the network device operations shown in the above method embodiments.

The baseband device 903 may further include a network interface 906 for exchanging information with the radio frequency device 902, for example, a Common Public Radio Interface (CPRI).

Specifically, the network side device according to the embodiment of the present invention further includes: the instructions or programs stored in the memory 905 and capable of being executed on the processor 904, and the processor 904 calls the instructions or programs in the memory 905 to execute the methods executed by the modules shown in fig. 7 or fig. 8, and achieve the same technical effects, which are not described herein in detail to avoid repetition.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the foregoing embodiment of the handover method for the self-backhaul network, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the above embodiment of the switching method for a self-backhaul network, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

The embodiment of the present application further provides a computer program product, where the computer program product includes a processor, a memory, and a program or an instruction stored in the memory and capable of running on the processor, and when the program or the instruction is executed by the processor, the processes of the embodiment of the switching method for a self-return network are implemented, and the same technical effects can be achieved, and are not described herein again to avoid repetition.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element identified by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatuses in the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions recited, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the present embodiments are not limited to those precise embodiments, which are intended to be illustrative rather than restrictive, and that various changes and modifications may be effected therein by one skilled in the art without departing from the scope of the appended claims.

Claims

1. A handover method from a backhaul network, performed by an original CU node, the method comprising:

under the condition of triggering handover, sending a second network handover request to a target CU node, wherein the second network handover request at least comprises context information of a first network node, the context information is the context information of the first network node when the handover is triggered, and at least part of information which is changed relative to the context information of the first network node and is included in the first network handover request is sent to the target CU node by the original CU node before the handover is triggered, and the first network node is any network node in an IAB network to be switched;

receiving a second network switching response sent by the target CU node, wherein the second network switching response at least comprises second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network switching request;

and configuring the switching of the first network node from the original CU node to a target CU node based on first reconfiguration information and the second reconfiguration information, wherein the first reconfiguration information is generated by the target CU node according to the first network switching request before the switching is triggered.

2. The method of claim 1, wherein configuring the handover of the first network node from the original CU node to a target CU node based on first reconfiguration information and the second reconfiguration information comprises at least one of:

sending a handover trigger notification to the target CU node, the handover trigger notification being used to notify the target CU node of node information of the first network node;

sending a handover trigger notification to the target CU node, the handover trigger notification to notify the target CU node that handover of the first network node is imminent.

3. The method of claim 2, wherein after sending a handover trigger notification to the target CU node, the method further comprises:

and under the condition of receiving the confirmation information fed back by the target CU node, sending target reconfiguration information to the first network node, wherein the target reconfiguration information is obtained by replacing or updating the first reconfiguration information by utilizing the second reconfiguration information.

4. The method of claim 1, wherein the method further comprises:

and under the condition of triggering switching, configuring switching of the first network node from the original CU node to a target CU node based on the first reconfiguration information.

5. The method of any one of claims 1-4, further comprising:

and sending a switching starting notification message to the first network node, wherein the switching starting notification message is used for indicating the first network node to switch according to the cached target reconfiguration information and/or the first reconfiguration information.

6. The method of claim 5, wherein the handover initiation notification information is transmitted through F1 signaling, RRC signaling, or BAP Control PDU signaling.

7. The method according to any of claims 1-6, wherein in case of triggering a handover, before sending a second network handover request to a target CU node, the method further comprises:

under the condition that the IAB network switching is predicted to be needed, sending the first network switching request to the target CU node, wherein the first network switching request at least comprises the context information of the first network node when the original CU node sends the first network switching request;

receiving a first network switching response sent by the target CU node, wherein the first network switching response comprises the first reconfiguration information.

8. The method of claim 7, wherein the first network handover request further includes first information indicating that the first network handover request is an early handover request; and/or

9. The method of claim 8, wherein the first information comprises a handover occurrence location and/or a handover occurrence time point, wherein the handover occurrence location and/or the handover occurrence time point are predicted by the original CU node according to a predetermined moving route, a moving speed of a mobile IAB system and deployment information of an alternative IAB host.

10. The method of claim 7, wherein a predetermined time interval is between a time of transmission of the first network handover request and a time of transmission of the second network handover request.

11. The method of any of claims 1-10, wherein, in a case that the first network node is a UE, the first reconfiguration information and the second reconfiguration information comprise RRC reconfiguration information;

in a case where the second network node is an IAB node, the first reconfiguration information and the second reconfiguration information include RRC reconfiguration information of an IAB-MT and/or F1 connection reconfiguration messages of an IAB-DU.

12. A handover method from a backhaul network, performed by a target CU node, the method comprising:

receiving a second network switching request sent by an original CU node when switching is triggered, wherein the second network switching request at least comprises context information of a first network node, the context information is the context information of the first network node when switching is triggered, and at least part of information which is changed relative to the context information of the first network node and is included in the first network switching request is sent to a target CU node by the original CU node before switching is triggered, and the first network node is any network node in an IAB network to be switched;

and sending a second network switching response to the original CU node, wherein the second network switching response comprises second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network switching request.

13. The method of claim 12, wherein after sending a second network handover response to the original CU node, the method further comprises at least one of:

receiving a switching trigger notification sent by the original CU node, wherein the switching trigger notification is used for notifying the target CU node of the node information of the first network node;

and receiving a switching trigger notification sent by the original CU node, wherein the switching trigger notification is used for notifying the target CU node that the switching of the first network node is about to occur.

14. The method as recited in claim 13, wherein after receiving a handover trigger notification sent by the original CU node, the method further comprises:

and under the condition of receiving the switching trigger notification, feeding back confirmation information to the original CU node and/or configuring network switching resources corresponding to the first network node.

15. The method as recited in claim 12, wherein prior to receiving the second network handover request sent by the original CU node, the method further comprises:

receiving a first network switching request sent by the original CU node, wherein the first network switching request is sent by the original CU node under the condition that the IAB network switching is predicted to be needed, and the first network switching request at least comprises context information of the first network node when the original CU node sends the first network switching request;

and sending a first network switching response to the original CU node, wherein the first network switching response comprises first reconfiguration information, and the first reconfiguration information is generated by the target CU node according to the first network switching request before switching is triggered.

16. The method of claim 15, wherein the first network handover request further includes first information indicating that the first network handover request is an early handover request; and/or

17. The method of claim 16, wherein the first information comprises a switch occurrence location and/or a switch occurrence time point, wherein the switch occurrence location and/or switch occurrence time point is predicted by the original CU node according to a predetermined moving route, moving speed of a mobile IAB system and deployment information of an alternative IAB host.

18. The method of any of claims 12-17, wherein, in a case that the first network node is a UE, the first reconfiguration information and the second reconfiguration information comprise RRC reconfiguration information;

19. A switching device for a self-backhauled network, the device comprising:

a first sending module, configured to send a second network handover request to a target CU node under a condition that handover is triggered, where the second network handover request at least includes context information of a first network node, where the context information is context information of the first network node when handover is triggered, and at least part of information that changes with respect to the context information of the first network node included in the first network handover request, the first network handover request is sent by an original CU node to the target CU node before handover is triggered, and the first network node is any network node in an IAB network to be handed over;

a first receiving module, configured to receive a second network handover response sent by the target CU node, where the second network handover response at least includes second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network handover request;

a configuration module, configured to configure switching of the first network node from the original CU node to a target CU node based on first reconfiguration information and the second reconfiguration information, where the first reconfiguration information is generated by the target CU node according to the first network switching request before triggering switching.

20. The apparatus of claim 19, wherein the configuration module is to at least one of:

21. The apparatus of claim 20, wherein the first sending module is further configured to send target reconfiguration information to the first network node when receiving the acknowledgement information fed back by the target CU node, and wherein the target reconfiguration information is obtained by replacing or updating the first reconfiguration information with the second reconfiguration information.

22. The apparatus of claim 19, wherein the configuration module is further for configuring the handover of the first network node from the original CU node to a target CU node based on the first reconfiguration information if a handover is triggered.

23. The apparatus according to any of claims 19-22, wherein the first sending module is further configured to send a handover start notification message to the first network node, where the handover start notification message is used to instruct the first network node to perform handover according to the cached target reconfiguration information and/or the first reconfiguration information.

24. The apparatus of claim 23, wherein the handover start notification information is transmitted through F1 signaling, RRC signaling, or BAP Control PDU signaling.

25. The apparatus of any of claims 19-24, wherein the first sending module is further to send the first network switch request to the target CU node if the IAB network switch is predicted to be needed, the first network switch request including at least context information of the first network node at the time the original CU node sent the first network switch request;

the first receiving module is further configured to receive a first network handover response sent by the target CU node, where the first network handover response includes the first reconfiguration information.

26. The apparatus of claim 25, wherein the first network handover request further includes first information indicating that the first network handover request is an early handover request; and/or

27. The apparatus of claim 26, wherein the first information comprises a handover occurrence location and/or a handover occurrence time point, wherein the handover occurrence location and/or the handover occurrence time point are predicted by the original CU node according to a predetermined moving route, a moving speed of a mobile IAB system, and deployment information of an alternative IAB host.

28. The apparatus of claim 25, wherein a predetermined time interval is between a time of transmission of the first network handover request and a time of transmission of the second network handover request.

29. The apparatus of any one of claims 19-28, wherein the first reconfiguration information and the second reconfiguration information include RRC reconfiguration information, if the first network node is a UE;

30. A switching device for a self-backhauled network, the device comprising:

a second receiving module, configured to receive a second network handover request sent by an original CU node when handover is triggered, where the second network handover request at least includes context information of a first network node, where the context information is context information of the first network node when handover is triggered, and at least part of information that changes with respect to the context information of the first network node included in the first network handover request, the first network handover request is sent by the original CU node to a target CU node before handover is triggered, and the first network node is any network node in an IAB network to be handed over;

a second sending module, configured to send a second network handover response to the original CU node, where the second network handover response includes second reconfiguration information, and the second reconfiguration information is generated by the target CU node according to the second network handover request.

31. The apparatus of claim 30, wherein the second receiving means is further for at least one of:

32. The apparatus as claimed in claim 31, wherein the second sending module is further configured to feed back acknowledgement information to the original CU node and/or configure network handover resources corresponding to the first network node in case of receiving the handover trigger notification.

33. The apparatus of claim 31, wherein the second receiving module is further configured to receive a first network handover request sent by the original CU node, the first network handover request being sent by the original CU node when the IAB network handover is predicted to be needed, the first network handover request including at least context information of the first network node when the original CU node sent the first network handover request;

the second sending module is further configured to send a first network handover response to the original CU node, where the first network handover response includes first reconfiguration information, and the first reconfiguration information is generated by the target CU node according to the first network handover request before handover is triggered.

34. The apparatus of claim 33, wherein the first network handover request further comprises first information indicating that the first network handover request is an early handover request; and/or

35. The apparatus of claim 34, wherein the first information comprises a handover occurrence location and/or a handover occurrence time point, wherein the handover occurrence location and/or the handover occurrence time point are predicted by the original CU node according to a predetermined moving route, a moving speed of a mobile IAB system, and deployment information of an alternative IAB host.

36. The apparatus of any one of claims 30-35, wherein the first reconfiguration information and the second reconfiguration information comprise RRC reconfiguration information, if the first network node is a UE;

37. A network-side device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the handover method for the self-backhauled network according to any of claims 1 to 11, or implement the steps of the handover method for the self-backhauled network according to any of claims 12 to 18.

38. A readable storage medium, characterized in that it stores thereon a program or instructions which, when executed by a processor, implement the steps of the handover method from backhaul network according to any one of claims 1 to 11, or implement the steps of the handover method from backhaul network according to any one of claims 12 to 18.