CN116367243A

CN116367243A - Method, device, network equipment and storage medium for switching self-backhaul network

Info

Publication number: CN116367243A
Application number: CN202111616758.4A
Authority: CN
Inventors: 文鸣
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2021-12-27
Filing date: 2021-12-27
Publication date: 2023-06-30

Abstract

The application discloses a method, a device, network equipment and a storage medium for switching a self-backhaul network, and belongs to the field of communication. The method comprises the following steps: under the condition that an access backhaul integrated IAB node switches a mobile terminal IAB-MT of the IAB node from a second centralized unit CU to a third CU in a partial migration mode, the third CU receives identity information of a first CU, wherein the first CU is a termination node connected with F1 of a distributed unit IAB-DU of the IAB node; and maintaining F1 connection between the IAB-DU and the first CU according to the identity information of the first CU.

Description

Method, device, network equipment and storage medium for switching self-backhaul network

Technical Field

The embodiment of the invention relates to the field of communication, in particular to a method, a device, network equipment and a storage medium for switching a self-backhaul network.

Background

In a New air interface (NR) system, an access backhaul integration (Integrated Access Backhaul, IAB) may provide extended coverage for an NR cell, or may provide capacity enhancement for an NR cell, where an access node supporting wireless access of a User Equipment (UE) and performing wireless backhaul on data is called an IAB node (IAB node). Data is transmitted between the UE and the access node through a wireless access link (access link), and data can be transmitted between the access nodes through a wireless Backhaul (BH) link. In an IAB network architecture supporting separate deployment of Centralized Units (CUs) and/or Distributed Units (DUs), one IAB node may include a DU function part and a mobile terminal (Mobile Termination, MT) function part. By means of the MT function part, an access node IABN can find an upstream access node (i.e. a part IABN, P-IABN) and establish a wireless backhaul link with the DU of the upstream access node. After an IAB node establishes a complete backhaul link, the IAB node opens its DU function, and the DU provides cell service, i.e. the DU may provide network access service for the UE. However, in the related art, since the partial migration may cause a limitation in signaling interaction between CUs, it is difficult to implement the partial migration to the IAB node when a plurality of handovers occur (partial migration).

Disclosure of Invention

The embodiment of the application provides a method, a device, network equipment and a storage medium for switching a self-backhaul network, which can solve the problem that the F1 connection with a first CU cannot be maintained when multiple times of switching occur in an IAB system.

In a first aspect, a method for switching a self-backhaul network is provided, the method comprising: under the condition that an access backhaul integrated IAB node switches a mobile terminal IAB-MT of the IAB node from a second centralized unit CU to a third CU in a partial migration mode, the third CU receives identity information of a first CU, wherein the first CU is a termination node connected with F1 of a distributed unit IAB-DU of the IAB node; and maintaining F1 connection between the IAB-DU and the first CU according to the identity information of the first CU.

In a second aspect, a method for switching a self-backhaul network is provided, the method comprising: under the condition that an IAB node switches an IAB-MT from a second CU to a third CU in a partial migration mode, the second CU sends identification information of a first CU to the third CU, wherein the first CU is a termination node of F1 connection of an IAB-DU, and the identification information of the first CU is used for maintaining F1 connection between the IAB-DU and the first CU.

In a third aspect, an apparatus for switching a self-backhaul network is provided, the apparatus comprising: a switching module, configured to receive identity information of a first CU, where the first CU is a termination node connected to an F1 of a distributed unit IAB-DU of an IAB node, when an access backhaul integrated IAB node switches a mobile terminal IAB-MT of the IAB node from a second centralized unit CU to a third CU by adopting a partial migration manner; and the processing module is used for maintaining F1 connection between the IAB-DU and the first CU according to the identity information of the first CU.

In a fourth aspect, an apparatus for switching from a backhaul network is provided, the apparatus comprising: and the execution module is used for sending the identity information of the first CU to the third CU under the condition that the IAB node adopts a partial migration mode to switch the IAB-MT from the second CU to the third CU, wherein the first CU is a termination node of F1 connection of the IAB-DU, and the identity information of the first CU is used for maintaining the F1 connection between the IAB-DU and the first CU.

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

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

In a seventh aspect, there is provided a chip comprising a processor and a communication interface coupled to the processor, the processor being for running a program or instructions to implement the method of the first or second aspect.

In the embodiment of the application, under the condition that an access backhaul integrated IAB node switches a mobile terminal IAB-MT of the IAB node from a second centralized unit CU to a third CU by adopting a partial migration manner, the third CU receives identity information of a first CU, wherein the first CU is a termination node connected with an F1 of a distributed unit IAB-DU of the IAB node; according to the identity information of the first CU, the F1 connection between the IAB-DU and the first CU is maintained, so that the problem that the connection with the F1 of the first CU cannot be maintained when the IAB system is switched for multiple times, and the partial migration of the IAB node cannot be realized can be solved.

Drawings

Fig. 1 shows a schematic diagram of a wireless communication system to which embodiments of the present application are applicable;

Fig. 2 is a flow chart of a method of self-backhaul network handover according to an embodiment of the present invention;

fig. 3 is a flow chart of a method of self-backhaul network switching according to one embodiment of the present invention;

fig. 4 is a flow chart of a method of self-backhaul network switching according to one embodiment of the present invention;

fig. 5 is a flow chart of a method of self-backhaul network switching according to one embodiment of the present invention;

fig. 6 is a flow chart of a method of self-backhaul network switching according to one embodiment of the present invention;

fig. 7 is a schematic structural diagram of an apparatus for switching from a backhaul network according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of an apparatus for switching from a backhaul network according to an embodiment of the present invention;

fig. 9 is a schematic diagram of a network device according to an embodiment of the present invention.

Detailed Description

Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects 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 sequences other than those illustrated or otherwise described herein, and that the terms "first" and "second" are generally intended to be used in a generic sense and not to limit the number of objects, for example, the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It is noted that the techniques described in embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the present application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a new air interface (NR) system for purposes of example and uses NR terminology in much of the description that follows, but these techniques are also applicable to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. As shown in fig. 1, in a CU-DU structure diagram of an IAB system provided in an embodiment of the present application, in a self-backhaul link, DUs in IAB network nodes are all connected to at least one CU network, and the CU network may configure DUs through an F1 application protocol and configure MTs through a radio resource control (RadioResource Control, RRC) protocol. Included in the self backhaul link is a home (Donor) IAB network node (otherwise known as an iabonor) that does not have an MT-capable portion, but has a wired transport network directly connected thereto.

The network-side devices comprised by the IAB system may comprise access network devices or core network devices, wherein the access network devices may also be referred to as radio access network devices, radio access networks (Radio Access Network, RAN), radio access network functions or radio access network elements. The access network device may include a base station, a WLAN access point, a WiFi node, or the like, where the base station may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home node B, a home evolved node B, a transmission receiving point (Transmitting Receiving Point, TRP), or some other suitable terminology in the field, and the base station is not limited to a specific technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiment of the present application, only the base station in the NR system is described by way of example, and the specific type of the base station is not limited. The core network device may include, but is not limited to, at least one of: core network nodes, core network functions, mobility management entities (Mobility Management Entity, MME), access mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), user plane functions (User Plane Function, UPF), policy control functions (Policy Control Function, PCF), policy and charging rules function units (Policy and Charging Rules Function, PCRF), edge application service discovery functions (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data repository (Unified Data Repository, UDR), home subscriber server (Home Subscriber Server, HSS), centralized network configuration (Centralized network configuration, CNC), network storage functions (Network Repository Function, NRF), network opening functions (Network Exposure Function, NEF), local NEF (or L-NEF), binding support functions (Binding Support Function, BSF), application functions (Application Function, AF), and the like. In the embodiment of the present application, only the core network device in the NR system is described as an example, and the specific type of the core network device is not limited.

The method for switching the self-backhaul network according to the embodiments of the present application is described in detail below with reference to the accompanying drawings.

As shown in fig. 2, one embodiment of the present invention provides a self-backhaul network switching method 200, which may be performed by a CU of an IAB system, in other words, by software or hardware installed at the CU, the method comprising the steps of:

s201: and in the case that the IAB node switches the IAB-MT from the second centralized unit CU to a third CU in a partial migration mode, the third CU receives the identification information of the first CU.

Wherein the first CU is an F1-terminating node (F1-terminating node) of the F1 connection of the IAB-DU.

Wherein the IAB-MT is further switched from at least the first CU to the second CU before the IAB-MT is switched from the second CU to the third CU. When the IAB node is switched from the first CU to the second CU, a partial migration/switching may be implemented, i.e. switching the MT of the IAB node, and the F1 connection between the DU of the IAB node and the F1-terminating node (terminating node) of the source CU is reserved. However, in the case where the IAB node is partially migrated/switched multiple times, for example, in the case where the IAB node is switched from the first CU to the second CU and then from the second CU to the third CU, since the third CU can only perform signaling interaction with the second CU, when the MT of the IAB node is switched to the third CU, the DU of the IAB node cannot continue to maintain the F1 connection with the first CU under the topology network of the third CU, that is, cannot implement the partial migration of the IAB node when multiple switching occurs.

In one implementation, the identification information of the first CU may include: an Identity (ID) of the first CU, and/or an internet protocol (Internet Protocol, IP) address used by the first CU to transmit F1control plane interface (F1 Controlplane interface, F1-C) data with the IAB node. The identity information of the first CU may be used to establish or maintain an F1 connection between the IAB-DU and the first CU.

S202: and maintaining F1 connection between the IAB-DU and the first CU according to the identity information of the first CU.

And the third CU maintains F1 connection between the IAB-DU and the first CU according to the identity information of the first CU.

In the method for switching the self-backhaul network provided by the embodiment of the present invention, when an IAB node switches a mobile terminal IAB-MT of the IAB node from a second CU to a third CU in a partial migration manner, the third CU receives identity information of a first CU, where the first CU is a termination node connected to an F1 of an IAB-DU; according to the identity information of the first CU, the F1 connection between the IAB-DU and the first CU is maintained, so that the problem that the F1 connection between the IAB node and the first CU cannot be maintained when the IAB system is switched for multiple times and the partial migration of the IAB node cannot be realized can be solved.

As shown in fig. 3, one embodiment of the present invention provides another self-backhaul network switching method 300, which may be performed by a CU of an IAB system, in other words, by software or hardware installed in the CU of the IAB system, comprising the steps of:

s301: under the condition that an IAB node adopts a partial migration mode to switch an IAB-MT from a second CU to a third CU, the third CU receives the identity information of a first CU, and the identity information of the first CU is carried in a first Xn message sent by the second CU or a radio resource control message sent by the IAB-MT.

Wherein the first CU is a termination node of an F1 connection of a distributed unit IAB-DU of the IAB node.

In one possible implementation manner, the identification information of the first CU is carried in a first Xn message sent by the second CU, where the first Xn message may be a newly added Xn message, or may multiplex related Xn messages.

In a first possible implementation manner, the first Xn message may include: a handover request message. Specifically, after receiving the measurement report sent by the IAB, the second CU carries information related to the identity of the first CU, such as the ID, the IP address, and the like of the first CU, in a first Xn message sent to the third CU requesting handover.

Specifically, the second CU may determine whether the received measurement report was sent by the UE or the IAB-MT, and also be able to know whether the IAB node implemented partial migration. If the DU of the IAB node that sent the current report is not connected to the F1 maintained by the CU receiving the report, the second CU determines that the node has already performed partial migration. In this case, when the second CU sends the measurement report to the third CU through the Xn interface, the identity information of the first CU may be added thereto.

The identity information of the first CU may be sent in an RRC message, and then transmitted through Xn transparent transmission, or may be sent along with a measurement report by being placed in Xn information.

For example, one implementation includes: xn message = { RRC container }, wherein RRC container = { measurement report + identity }; another implementation includes: xn message = { RRC container+identity }, where RRC container = { measurement report }.

In a second possible implementation manner, the first Xn message may include: and feeding back information. Specifically, in a case where the second CU determines that the termination node of the F1 connection of the IAB-DU is not the same CU node as the anchor point at which the IAB-MT currently maintains a radio resource control (Radio Resource Control, RRC) connection, the first identification information is transmitted to the third CU through a second Xn message. In other words, the second CU finds that the IAB node sending the measurement report does not proceed for the first time partial migration, and sends the first identification information to the third CU through the second Xn message. That is, the first identification information is carried in the second Xn message if: the second CU determines that the termination node of the IAB-DU is not the same CU node as the anchor point at which the IAB-MT currently maintains the RRC connection. The first identification information indicates that the F1 connection of the IAB node currently requesting the handover is not at the second CU, requiring the third CU to request the identification information of the first CU.

And the third CU receives the first identification information sent by the second CU through the second Xn message. The third CU sends the identity request information to the second CU via a third Xn message, such as a handover request message (Handover Request Acknowledge).

In a third possible implementation manner, the identity information of the first CU is carried in an RRC message sent by the IAB-MT, and optionally, the RRC message is reported after the IAB-MT completes the handover from the second CU to the third CU. Specifically, after the IAB-MT completes the handover from the second CU to the third CU, the identity information of the first CU is carried in an RRC message, for example, in an rrcrecconfiguration complete.

In one implementation, the method may be applicable to mobile (mobile) IAB nodes, i.e., IAB nodes installed on mobile devices, e.g., IAB nodes installed on vehicles. In other words, the IAB node may be a mobileIAB node. S302: and maintaining F1 connection between the IAB-DU and the first CU according to the identity information of the first CU.

In the method for switching the self-backhaul network provided by the embodiment of the present invention, when an IAB node switches an IAB-MT from a second CU to a third CU in a partial migration manner, the third CU receives identity information of a first CU, where the first CU is a termination node connected to an F1 of a distributed unit IAB-DU of the IAB node; according to the identity information of the first CU, maintaining the F1 connection between the IAB-DU and the first CU can solve the problem that partial migration of the IAB node cannot be achieved when multiple times of switching occurs in the IAB system, so that the IAB can be switched under different CU nodes for multiple times when the partial migration is performed, but still maintain the F1 connection between the IAB-DU and the first CU, that is, the CU to which the IAB is connected before the first time partial migration is performed. According to the method for switching the self-backhaul network, the identity information of the first CU can be conveniently transmitted by carrying the identity information of the first CU in the first Xn message sent by the second CU or the RRC message sent by the IAB-MT.

As shown in fig. 4, one embodiment of the present invention provides a self-backhaul network switching method 400, which may be performed by a terminal device and/or a network device, in other words, by software or hardware installed at the terminal device and/or the network device, the method comprising the steps of:

s401: and under the condition that the IAB node adopts a partial migration mode to switch the IAB-MT from the second CU to the third CU, the third CU receives the identification information of the first CU.

This step may take the form of a description of the corresponding steps in the embodiment of fig. 2-3, which is not repeated here.

S402: and the third CU establishes a first Xn connection with the first CU according to the identity information of the first CU.

S403: the third CU receives target quality of service information for the IAB node.

Wherein the target quality of service (Quality of Service, qoS) information includes: F1-U tunnel or backhaul radio link control channel (backhaul Radio Link Control channel, BH RLC CH) data of the uplink or downlink mobile IAB node.

In a first implementation, the target quality of service information is sent by the first CU over a first Xn connection, the first Xn connection being an Xn connection between the first CU and the third CU.

Since the second CU does not necessarily maintain the latest target quality of service information, the third CU can directly interact with the first CU to acquire QoS information. And the last step of the third CU establishes a first Xn connection with the first CU, allocates/configures an IP address for the mobile IAB, and sends the IP address belonging to the IP domain of the IAB-DONOR-DU@target CU to the first CU through an Xn message. After receiving the Xn message and including the new IP address of the mobile IAB, the first CU sends DL/UL QoS information at the mobile IAB, that is, qoS information corresponding to the transmission type of the data of the non-data plane, and/or QoS information corresponding to each F1-U channel (tunnel) of the data plane, to the third CU through the Xn information.

In a second implementation, the target quality of service information is sent by the second CU over a second Xn connection, the second Xn connection being an Xn connection between the second CU and the third CU.

Specifically, the second CU sends DL/UL QoS information at the mobile IAB, i.e. QoS information corresponding to the transmission type of the non-data plane data, and/or QoS information corresponding to each data plane interface (F1 User plane interface, F1-U) channel of the data plane, to the third CU through Xn information in the second Xn connection.

S404: and the third CU generates first information according to the target service quality information and the network topology structure under the third CU.

The first information includes at least one of: the uplink route data mapping configuration of the third CU, the downlink route data mapping configuration of the third CU, the IP addresses corresponding to the data types in the F1 connection and the return route configuration.

The uplink route data mapping configuration of the third CU and the downlink route data mapping configuration of the third CU are used for path selection of backhaul adaptation protocol (Backhaul Adaptation Protocol, BAP) data, and the IP address corresponding to each data type in the F1 connection includes the IP address corresponding to the F1-U channel. The backhaul routing configuration is used to implement the routing of BAP data. Wherein BH routing/path configuration is layer 2 information.

S405: the third CU sends the first information to the IAB node.

In one implementation, this step may include: sending the first information to the second CU through a fourth Xn message, and sending second information to the IAB-MT through an RRC message by the second CU; the second information includes at least part of the first information. For example, the third CU sends the BH routing configuration to the second CU via a fourth Xn message, such as a handover request acknowledgement (handover request acknowledge), and the second CU issues the BH routing configuration to the mobile IAB-MT via an RRC reconfiguration message. Before switching, the third CU sends corresponding information to the second CU through Xn, and the second CU sends the IP address and BH route configuration to the IAB-MT for reconfiguration through RRC reconfiguration information.

In one implementation, this step may include: and sending the first information to the IAB-MT which completes the switching through an RRC message, namely sending the BH route configuration to the mobile IAB-MT which completes the switching through the RRC message by a third CU. The switch is a switch from the second CU to the third CU.

In one implementation, this step may include: and sending the first information to a first CU through the fifth Xn message, and sending third information to the IAB-DU through F1 signaling by the first CU, wherein the third information comprises at least part of the first information.

S406: and the third CU maintains F1 connection between the IAB-DU and the first CU according to the identity information of the first CU.

In a first implementation, in case the target quality of service information is sent by the second CU over the second Xn connection, the step comprises: and sending the IP address corresponding to each data type in the F1 connection to a first CU through the first Xn connection. Namely, the third CU sends the F1-C of the mobile IAB node and the IP address corresponding to the F1-U to the first CU through the Xn interface. The first CU can determine the F1 data carried therein as mobile IAB by receiving the information transferred by the IP addresses.

In a second implementation, in case the target quality of service information is sent by the first CU over the first Xn connection, the step comprises: sending an IP address corresponding to F1-C data distributed by the third CU for the IAB node to the first CU through the first Xn connection; and sending the IP address corresponding to the F1 data type of the F1 data plane interface F1-U to the first CU through the first Xn connection.

In the method for switching the self-backhaul network provided by the embodiment of the present invention, when an IAB node switches an IAB-MT from a second CU to a third CU in a partial migration manner, the third CU receives identity information of a first CU, where the first CU is a termination node connected to an F1 of a distributed unit IAB-DU of the IAB node; according to the identity information of the first CU, maintaining the F1 connection between the IAB-DU and the first CU can solve the problem that the partial migration of the IAB node cannot be achieved when the multiple times of handover occur in the IAB system, so that the mobile IAB can be switched under different CU nodes for multiple times when the partial migration is performed, but still maintain the F1 connection between the mobile IAB-DU and the first CU, that is, the CU to which the IAB is connected before the first partial migration is performed.

Embodiments of the present application will be described below in terms of a source CU that is partially migrated, i.e., a second CU. It should be understood that the interactions between the first CU, the second CU, and the third CU described from the perspective of the second CU are the same as or corresponding to the description of the angles of the third CU, i.e., the target CU to be partially migrated from in the embodiment of fig. 2 to 4 described above, and the related descriptions are omitted for avoiding repetition.

As shown in fig. 5, one embodiment of the present invention provides a self-backhaul network switching method 500, which may be performed by a CU of an IAB system, in other words, by software or hardware installed on the CU, the method comprising the steps of:

s501: and under the condition that the IAB node adopts a partial migration mode to switch the IAB-MT from the second CU to the third CU, the second CU sends the identification information of the first CU to the third CU.

The first CU is a termination node of F1 connection of an IAB-DU, and the identity information of the first CU is used for maintaining F1 connection between the IAB-DU and the first CU.

In one implementation, the sending, by the second CU, identification information of the first CU to the third CU includes: the second CU sends a first Xn message to the third CU, and the identity information of the first CU is carried in the first Xn message.

In one implementation, the first Xn message includes: a handover request message and/or feedback information.

In one implementation, the handover request message is sent by the second CU after receiving a measurement report sent by the IAB node.

In one implementation, the second CU sends the first identification information to the third CU through a second Xn message if the second CU determines that the termination node of the F1 connection of the IAB-DU is not the same CU node as the anchor point at which the IAB-MT currently maintains the RRC connection. The first identification information indicates that the third CU requests identification information of the first CU. And the second CU receives a third Xn message sent by the third CU, wherein the third Xn message carries the identity request information. The second CU sends feedback information, and the feedback information carries the identity information of the first CU.

In one implementation, the identification information of the first CU includes: the ID of the first CU and/or the IP address of the first CU is used for transmitting F1-C data between the first CU and the IAB node.

The above steps may be described in the corresponding steps of the embodiment of fig. 2-4 and are not repeated here.

According to the self-backhaul network switching method provided by the embodiment of the invention, under the condition that an IAB node switches an IAB-MT from a second CU to a third CU in a partial migration manner, the second CU sends the identity information of a first CU to the third CU, wherein the first CU is a termination node connected with F1 of an IAB-DU, and the identity information of the first CU is used for maintaining F1 connection between the IAB-DU and the first CU, so that the problem that the F1 connection with the first CU cannot be maintained when the IAB system is switched for multiple times can be solved.

As shown in fig. 6, an embodiment of the present invention provides a self-backhaul network switching method 600, which may be performed by a CU of an IAB system, in other words, by software or hardware installed at the CU, the method comprising the steps of:

s601: and under the condition that the IAB node adopts a partial migration mode to switch the IAB-MT from the second CU to the third CU, the second CU sends the identification information of the first CU to the third CU.

S602: and the second CU sends target service quality information of the IAB node to the third CU through a second Xn connection.

Wherein the target quality of service information includes: and the second Xn connection is an Xn connection between the second CU and the third CU.

S603: and receiving the first information sent by the third CU through a fourth Xn message.

Wherein the first information includes at least one of: the method comprises the steps of uplink route data mapping configuration of a third CU, downlink route data mapping configuration of the third CU, IP addresses corresponding to data types in F1 connection and backhaul route configuration;

S604: and sending the second information to the IAB-MT through an RRC message.

The second information includes at least part of the first information.

It should be noted that, in the embodiment of the present application, the execution body may be a device for switching a self-backhaul network, and in the embodiment of the present application, the device for switching a self-backhaul network provided in the embodiment of the present application is described by taking a method for executing loading of the self-backhaul network switching by the device for switching a self-backhaul network as an example.

Fig. 7 is a schematic structural diagram of an apparatus for switching from a backhaul network according to an embodiment of the present invention. As shown in fig. 7, the apparatus 700 for switching from backhaul network includes: a switching module 710, configured to receive identity information of a first CU, where the first CU is a termination node connected to an F1 of a distributed unit IAB-DU of an IAB node, when an access backhaul integrated IAB node switches a mobile terminal IAB-MT of the IAB node from a second centralized unit CU to a third CU by adopting a partial migration manner; and a processing module 720, configured to maintain an F1 connection between the IAB-DU and the first CU according to the identity information of the first CU.

In one implementation, the identification information of the first CU is carried in a first Xn message sent by the second CU or a radio resource control RRC message sent by the IAB-MT.

In one implementation, the processing module 720 is further configured to, in a case where the first Xn message includes the feedback information, receive, through a second Xn message, first identification information sent by the second CU before the third CU receives the feedback information; and sending the identification request information to the second CU through a third Xn message.

In one implementation, the first identification information is carried in the second Xn message when: the second CU determines that the termination node of the IAB-DU is not the same CU node as the anchor point at which the IAB-MT currently maintains the RRC connection.

In one implementation, the RRC message is reported after the IAB-MT completes the handover from the second CU to the third CU.

In one implementation, the identification information of the first CU includes: the identity ID of the first CU and/or the internet protocol IP address of the first CU used to transmit F1-C data with the F1 control plane interface between the IAB nodes.

In one implementation, the processing module 720 is further configured to, before maintaining the F1 connection between the IAB-DU and the first CU, establish a first Xn connection with the first CU according to the identity information of the first CU; the third CU receives target service quality information of the IAB node; wherein the target quality of service information is sent by the first CU through a first Xn connection or by the second CU through a second Xn connection, the target quality of service information comprising: uplink and/or downlink quality of service information, the first Xn connection being an Xn connection between the first CU and the third CU, the second Xn connection being an Xn connection between the second CU and the third CU; generating first information according to the target service quality information and the network topology structure under the third CU, wherein the first information comprises at least one of the following: the method comprises the steps of uplink route data mapping configuration of a third CU, downlink route data mapping configuration of the third CU, IP addresses corresponding to data types in F1 connection and backhaul route configuration; and sending the first information to the IAB node.

In one implementation manner, the processing module 720 is further configured to send, if the target quality of service information is sent by the second CU through the second Xn connection, an IP address corresponding to each data type in the F1 connection to the first CU through the first Xn connection.

In one implementation manner, the processing module 720 is further configured to, when the target quality of service information is sent by the first CU through the first Xn connection, send, to the first CU through the first Xn connection, an IP address corresponding to the F1-C data allocated by the third CU to the IAB node; and sending the IP address corresponding to the F1 data type of the F1 data plane interface F1-U to the first CU through the first Xn connection.

In one implementation, the processing module 720 is further configured to send the first information to the IAB node, including at least one of: sending the first information to the second CU through a fourth Xn message, and sending second information to the IAB-MT through an RRC message by the second CU; the second information includes at least part of the first information; transmitting the first information to the IAB-MT having completed the handover through an RRC message; and sending the first information to a first CU through the fifth Xn message, and sending third information to the IAB-DU through F1 signaling by the first CU, wherein the third information comprises at least part of the first information.

In one implementation, the processing module 720 is further configured to switch the IAB-MT from the first CU to the second CU before the IAB-MT is switched from the second CU to the third CU.

The device for switching from the backhaul network in the embodiments of the present application may be an electronic apparatus, for example, an electronic apparatus with an operating system, or may be a component in an electronic apparatus, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the application are not specifically limited.

The device for switching the self-backhaul network according to the embodiment of the present application can implement each process implemented by the embodiments of the methods of fig. 2 to fig. 4, and achieve the same technical effects, so that repetition is avoided, and no further description is given here.

Fig. 8 is a schematic structural diagram of an apparatus for switching from a backhaul network according to an embodiment of the present invention. As shown in fig. 8, the apparatus 800 for switching from backhaul network includes: and the execution module 810 is configured to send, to a third CU, identification information of a first CU when the IAB node switches the IAB-MT from the second CU to the third CU in a partial migration manner, where the first CU is a termination node of F1 connection of an IAB-DU, and the identification information of the first CU is used to maintain the F1 connection between the IAB-DU and the first CU.

In one implementation, the apparatus 800 may further include: and the determining module is used for determining the identity information of the first CU.

In one implementation, the execution module 810 is further configured to send, by the second CU, a first Xn message to the third CU, where identification information of the first CU is carried in the first Xn message.

In one implementation, the handover request message is sent after receiving a measurement report sent by the IAB node.

In one implementation, the execution module 810 is further configured to, in a case where the first Xn message includes the feedback information, send, by a second Xn message, first identification information to the third CU before the second CU sends the first Xn message to the third CU; and receiving a third Xn message sent by the third CU, wherein the third Xn message carries the identity request information.

In one implementation, the execution module 810 is further configured to send, by a second Xn message, the first identification information to the third CU if the second CU determines that the termination node of the F1 connection of the IAB-DU is not the same CU node as the anchor point at which the IAB-MT currently maintains the RRC connection.

In one implementation, the execution module 810 is further configured to send, by the second CU, target quality of service information of the IAB node to the third CU through a second Xn connection; wherein the target quality of service information includes: and the second Xn connection is an Xn connection between the second CU and the third CU.

In one implementation, the execution module 810 is further configured to, after the second CU sends the target quality of service information of the IAB node to the third CU through the second Xn connection, receive first information sent by the third CU through a fourth Xn message, where the first information includes at least one of: the method comprises the steps of uplink route data mapping configuration of a third CU, downlink route data mapping configuration of the third CU, IP addresses corresponding to data types in F1 connection and backhaul route configuration; sending second information to the IAB-MT through an RRC message; the second information includes at least part of the first information.

In one implementation, execution module 810 is further to switch the IAB-MT from the first CU to the second CU before the IAB-MT is switched from the second CU to the third CU.

The device for switching the self-backhaul network according to the embodiment of the present application can implement each process implemented by the embodiments of the methods of fig. 5 to 6, and achieve the same technical effects, so that repetition is avoided, and no further description is given here.

The embodiment of the application also provides network side equipment. As shown in fig. 9, the network device 900 includes: an antenna 901, a radio frequency device 902, a baseband device 903, a processor 904, and a memory 905. The antenna 901 is connected to a radio frequency device 902. In the uplink direction, the radio frequency device 902 receives information via the antenna 901, and transmits the received information to the 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 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 baseband processor.

The baseband apparatus 903 may, for example, include at least one baseband board, where a plurality of chips are disposed, as shown in fig. 9, where one chip, for example, a baseband processor, is connected to the memory 905 through a bus interface, so as to call a program in the memory 905 to perform the network device operation shown in the above method embodiment.

The network-side device may also include a network interface 906, such as a common public radio interface (common public radio interface, CPRI).

Specifically, the network side device 900 of the embodiment of the present invention further includes: instructions or programs stored on the memory 905 and executable on the processor 904, the processor 904 calling for instructions or programs in the memory 905 to perform: under the condition that an access backhaul integrated IAB node switches a mobile terminal IAB-MT of the IAB node from a second centralized unit CU to a third CU in a partial migration mode, the third CU receives identity information of a first CU, wherein the first CU is a termination node connected with F1 of a distributed unit IAB-DU of the IAB node; and maintaining F1 connection between the IAB-DU and the first CU according to the identity information of the first CU.

In one implementation, where the first Xn message includes the feedback information, before the third CU receives the feedback information, further performing: receiving first identification information sent by the second CU through a second Xn message; and sending the identification request information to the second CU through a third Xn message.

In one implementation, before maintaining the F1 connection between the IAB-DU and the first CU, further performing:

establishing a first Xn connection with the first CU according to the identity information of the first CU; the third CU receives target service quality information of the IAB node; wherein the target quality of service information is sent by the first CU through a first Xn connection or by the second CU through a second Xn connection, the target quality of service information comprising: uplink and/or downlink quality of service information, the first Xn connection being an Xn connection between the first CU and the third CU, the second Xn connection being an Xn connection between the second CU and the third CU;

generating first information according to the target service quality information and the network topology structure under the third CU, wherein the first information comprises at least one of the following: the method comprises the steps of uplink route data mapping configuration of a third CU, downlink route data mapping configuration of the third CU, IP addresses corresponding to data types in F1 connection and backhaul route configuration;

and sending the first information to the IAB node.

In one implementation, where the target quality of service information is sent by a second CU over a second Xn connection, the maintaining the F1 connection between the IAB-DU and the first CU comprises:

And sending the IP address corresponding to each data type in the F1 connection to a first CU through the first Xn connection.

In one implementation, where the target quality of service information is sent by a first CU over a first Xn connection, the maintaining the F1 connection between the IAB-DU and the first CU comprises: sending an IP address corresponding to F1-C data distributed by the third CU for the IAB node to the first CU through the first Xn connection; and sending the IP address corresponding to the F1 data type of the F1 data plane interface F1-U to the first CU through the first Xn connection.

In one implementation, the sending the first information to the IAB node includes at least one of:

sending the first information to the second CU through a fourth Xn message, and sending second information to the IAB-MT through an RRC message by the second CU; the second information includes at least part of the first information;

transmitting the first information to the IAB-MT having completed the handover through an RRC message;

and sending the first information to a first CU through the fifth Xn message, and sending third information to the IAB-DU through F1 signaling by the first CU, wherein the third information comprises at least part of the first information.

In one implementation, the IAB-MT is switched from the first CU to the second CU before the IAB-MT is switched from the second CU to the third CU.

Or the processor performs: under the condition that an IAB node switches an IAB-MT from a second CU to a third CU in a partial migration mode, the second CU sends identification information of a first CU to the third CU, wherein the first CU is a termination node of F1 connection of an IAB-DU, and the identification information of the first CU is used for maintaining F1 connection between the IAB-DU and the first CU.

In one implementation, where the first Xn message includes the feedback information, before the second CU sends the first Xn message to the third CU, further performing: sending first identification information to the third CU through a second Xn message; and receiving a third Xn message sent by the third CU, wherein the third Xn message carries the identity request information.

In one implementation, the sending, by the second Xn message, the first identification information to the third CU includes: and under the condition that the second CU determines that the termination node of the F1 connection of the IAB-DU and the anchor point of the current IAB-MT maintaining RRC connection are not the same CU node, sending first identification information to the third CU through a second Xn message.

In one implementation, the processor further: the second CU sends target service quality information of the IAB node to the third CU through a second Xn connection; wherein the target quality of service information includes: and the second Xn connection is an Xn connection between the second CU and the third CU.

In one implementation, after the second CU sends target quality of service information of an IAB node to the third CU over a second Xn connection, the first information sent by the third CU over a fourth Xn message is received, wherein the first information includes at least one of: the method comprises the steps of uplink route data mapping configuration of a third CU, downlink route data mapping configuration of the third CU, IP addresses corresponding to data types in F1 connection and backhaul route configuration; sending second information to the IAB-MT through an RRC message; the second information includes at least part of the first information.

The steps of the methods shown in fig. 2 to 6 or the methods executed by the modules shown in fig. 7 or fig. 8 may be executed specifically, and the same technical effects are achieved, so that repetition is avoided and therefore are not repeated here.

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 processes of the foregoing method embodiment of self-backhaul network switching are implemented, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, the processor is configured to run a program or an instruction, implement each process of the above embodiment of the method for switching the self-backhaul network, and achieve the same technical effect, so that repetition is avoided, and no further description is provided herein.

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

The embodiments of the present application further provide a computer program/program product, where the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement each process of the above-mentioned method embodiment of self-backhaul network switching, and the same technical effects can be achieved, so that repetition is avoided, and details are not repeated herein.

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 defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A method for self-backhauling network handover, the method comprising:

under the condition that an access backhaul integrated IAB node switches a mobile terminal IAB-MT of the IAB node from a second centralized unit CU to a third CU in a partial migration mode, the third CU receives identity information of a first CU, wherein the first CU is a termination node connected with F1 of a distributed unit IAB-DU of the IAB node;

and maintaining F1 connection between the IAB-DU and the first CU according to the identity information of the first CU.

2. The method of claim 1, wherein the identity information of the first CU is carried in a first Xn message sent by the second CU or a radio resource control, RRC, message sent by the IAB-MT.

3. The method of claim 2, wherein the first Xn message comprises: a handover request message and/or feedback information.

4. The method of claim 3, wherein, in the case where the first Xn message includes the feedback information, before the third CU receives the feedback information, the method further comprises:

receiving first identification information sent by the second CU through a second Xn message;

And sending the identification request information to the second CU through a third Xn message.

5. The method of claim 4, wherein the first identification information is carried in the second Xn message if:

the termination node of the IAB-DU is not the same CU node as the anchor point at which the IAB-MT currently maintains the RRC connection.

6. The method of claim 2, wherein the RRC message is reported after the IAB-MT completes a handover from a second CU to a third CU.

7. The method of claim 1, wherein the identification information of the first CU comprises: the identity ID of the first CU and/or the internet protocol IP address of the first CU used to transmit F1-C data with the F1 control plane interface between the IAB nodes.

8. The method of claim 1, wherein prior to maintaining the F1 connection between the IAB-DU and the first CU, the method further comprises:

establishing a first Xn connection with the first CU according to the identity information of the first CU;

the third CU receives target service quality information of the IAB node;

wherein the target quality of service information is sent by the first CU through a first Xn connection or by the second CU through a second Xn connection, the target quality of service information comprising: uplink and/or downlink quality of service information, the first Xn connection being an Xn connection between the first CU and the third CU, the second Xn connection being an Xn connection between the second CU and the third CU;

and sending the first information to the IAB node.

9. The method of claim 8, wherein the maintaining the F1 connection between the IAB-DU and the first CU if the target quality of service information is sent by a second CU over a second Xn connection comprises:

10. The method of claim 8, wherein the maintaining the F1 connection between the IAB-DU and the first CU if the target quality of service information is sent by the first CU over a first Xn connection comprises:

sending an IP address corresponding to F1-C data distributed by the third CU for the IAB node to the first CU through the first Xn connection;

and sending the IP address corresponding to the F1 data type of the F1 data plane interface F1-U to the first CU through the first Xn connection.

11. The method of claim 8, wherein transmitting the first information to the IAB node comprises at least one of:

12. The method of claim 1, wherein the IAB-MT is switched from the first CU to the second CU before the IAB-MT is switched from the second CU to a third CU.

13. A method for self-backhauling network handover, the method comprising:

under the condition that an IAB node switches an IAB-MT from a second CU to a third CU in a partial migration mode, the second CU sends identification information of a first CU to the third CU, wherein the first CU is a termination node of F1 connection of an IAB-DU, and the identification information of the first CU is used for maintaining F1 connection between the IAB-DU and the first CU.

14. The method of claim 13, wherein the second CU sends identification information of a first CU to the third CU, comprising:

the second CU sends a first Xn message to the third CU, and the identity information of the first CU is carried in the first Xn message.

15. The method of claim 14, wherein the first Xn message comprises: a handover request message and/or feedback information.

16. The method of claim 15 wherein the handover request message is sent after receiving a measurement report sent by the IAB node.

17. The method of claim 15, wherein, in the case where the first Xn message includes the feedback information, before the second CU sends the first Xn message to the third CU, the method further comprises:

sending first identification information to the third CU through a second Xn message;

and receiving a third Xn message sent by the third CU, wherein the third Xn message carries the identity request information.

18. The method of claim 17, wherein the sending the first identification information to the third CU via the second Xn message comprises:

And under the condition that the second CU determines that the termination node of the F1 connection of the IAB-DU and the anchor point of the current IAB-MT maintaining RRC connection are not the same CU node, sending first identification information to the third CU through a second Xn message.

19. The method of claim 13, wherein the identification information of the first CU comprises: the ID of the first CU and/or the IP address of the first CU is used for transmitting F1-C data between the first CU and the IAB node.

20. The method of claim 13, wherein the method further comprises:

the second CU sends target service quality information of the IAB node to the third CU through a second Xn connection; wherein the target quality of service information includes: and the second Xn connection is an Xn connection between the second CU and the third CU.

21. The method of claim 20, wherein after the second CU sends target quality of service information for an IAB node to the third CU over a second Xn connection, the method further comprises:

receiving first information sent by the third CU through a fourth Xn message, wherein the first information includes at least one of: the method comprises the steps of uplink route data mapping configuration of a third CU, downlink route data mapping configuration of the third CU, IP addresses corresponding to data types in F1 connection and backhaul route configuration;

Sending second information to the IAB-MT through an RRC message; the second information includes at least part of the first information.

22. The method of claim 13, wherein prior to the IAB-MT being handed over from the second CU to the third CU, the method further comprises:

the IAB-MT is switched from the first CU to the second CU.

23. An apparatus for self-backhauling network handover, the apparatus comprising:

a switching module, configured to receive identity information of a first CU, where the first CU is a termination node connected to an F1 of a distributed unit IAB-DU of an IAB node, when an access backhaul integrated IAB node switches a mobile terminal IAB-MT of the IAB node from a second centralized unit CU to a third CU by adopting a partial migration manner;

and the processing module is used for maintaining F1 connection between the IAB-DU and the first CU according to the identity information of the first CU.

24. An apparatus for self-backhauling network handover, the apparatus comprising:

and the execution module is used for sending the identity information of the first CU to the third CU under the condition that the IAB node adopts a partial migration mode to switch the IAB-MT from the second CU to the third CU, wherein the first CU is a termination node of F1 connection of the IAB-DU, and the identity information of the first CU is used for maintaining the F1 connection between the IAB-DU and the first CU.

25. A network side device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method of self-backhauled network handover as claimed in any one of claims 1 to 12; or alternatively

A step of implementing a method of self-backhauling network handover according to any one of claims 13 to 22.

26. A readable storage medium, wherein a program or instructions is stored on the readable storage medium, which when executed by a processor, performs the steps of the method of self-backhauling network handover as claimed in any one of claims 1 to 12; alternatively, the method of implementing a self-backhauling network handover as claimed in any one of claims 13 to 22.