Integration method for integrated access and backhaul node, and apparatus

Abstract

The embodiments of the present application provide an integration method for an IAB (integrated access and backhaul) node, and an apparatus. The method comprises: by means of OAM, configuring a DU of an IAB node with a base station identifier of a CU of an F1-terminating IAB donor, or, a CU of an RRC-terminating IAB donor configuring an MT of the IAB node with said base station identifier; and on the basis of the base station identifier, the DU of the IAB node performing F1 setup with the CU of the F1-terminating IAB donor. Therefore, the present application solves the integration problem of IAB nodes, so that the IAB-MT and the collocated IAB-DU can be integrated onto different donor-CUs, thus improving the flexibility of network configuration.

Description

Integration method and device for access backhaul integrated node Technical Field

[0001] The present application relates to the field of communications. Background Art

[0002] Integrated access and backhaul (IAB) implements the wireless relay function in the next generation radio access network (NG-RAN). This relay node is called an IAB-node, which supports both access and backhaul (BH) through 5G NR (new radio). All IAB nodes are connected to an IAB-donor node through one or more hops. These multi-hop connections form a directed acyclic graph (DAG) topology with the IAB-donor node as the root node. The IAB-donor node is responsible for performing centralized resource management, topology management, and routing management in the IAB network topology.

[0003] The IAB node supports the functions of the gNB-distributed unit (gNB-DU), referred to as the IAB-DU, and can serve both standard UEs (user equipment) and IAB child nodes. The IAB node also supports some UE functions and is referred to as the IAB-MT (mobile termination). The IAB-MT supports functions such as the UE physical layer, access stratum (AS), radio resource control (RRC), and non-access stratum (NAS), and can connect to the IAB parent node. The network-side termination node, referred to as the IAB-donor, provides network access for the IAB-MT or UE via backhaul or access links. The IAB-donor is further divided into the IAB-donor-CU (central unit) and the IAB-donor-DU. The IAB-DU and IAB-donor-CU are connected via the F1 interface. In standalone networking scenarios, the gNB and IAB-donor-CU are connected via the Xn interface.

[0004] To support multi-hop routing of data packets, IAB introduces the BAP (Backhaul Adaptation Protocol) sublayer. Located above the RLC (radio link control) sublayer and below the IP (Internet Protocol) layer, the BAP sublayer supports functions such as selecting the destination node and path for data packets, routing and forwarding data packets, bearer mapping, flow control feedback, and notification of backhaul link failures.

[0005] In multi-hop scenarios, to relay data packets, the IAB node needs to determine the destination node for the packet, then determine the next hop node corresponding to the destination node based on the routing table and send the packet. In this scenario, the IAB-donor-CU (abbreviated as donor-CU, CU, or gNB-CU) configures the mapping of each F1-U (F1 user plane) tunnel, each non-UE associated F1AP message, each UE-associated F1AP message, and each non-F1 traffic message to a BAP routing identifier for uplink transmissions initiated from the IAB node via F1AP (F1 Application Protocol) signaling. The IAB node determines the BAP routing identifier corresponding to different types of uplink IP packets initiated from the IAB node based on this routing identifier mapping information and encapsulates these uplink IP packets with a BAP subheader containing the BAP routing identifier information. The IAB-donor-CU configures the mapping of different types of downlink data packets to BAP routing identifiers for the IAB-donor-DU (abbreviated as donor-DU) through F1AP signaling. The IAB-donor-DU determines the BAP routing identifier corresponding to the received downlink IP packets based on the routing identifier mapping information and encapsulates the BAP subheader containing the BAP routing identifier information for these downlink IP packets.

[0006] The BAP routing identifier includes the destination BAP address and the path identity from the IAB node to the IAB-donor-DU. The BAP address is also called the destination in the BAP header. Each IAB node and IAB-donor-DU is configured with a BAP address.

[0007] The IAB node integration process, also known as the startup process, refers to the process by which the IAB-MT accesses the network, obtains IAB-related configuration information, and activates some DU functions to provide services to the UE. Taking the IAB node integration process in a standalone network as an example, it can be divided into three stages.

[0008] In the first phase, the IAB-MT accesses the network. In this phase, the IAB-MT connects to the network as a normal UE, and this process basically reuses the initial access process of a normal UE.

[0009] The second phase involves BH RLC channel establishment and routing updates. During this phase, RRC can configure a default BH RLC channel and a default BAP routing identifier for non-F1-U traffic. The IAB-donor-CU may also establish additional BH RLC channels for the IAB-MT during this phase for subsequent data transmission. The IAB-donor-CU performs routing configuration for the newly integrated IAB node, the IAB-donor-DU, the parent node of the newly integrated IAB node, and all intermediate IAB nodes between the IAB-donor-DU and the IAB node. This phase also includes the IP address allocation process for the newly integrated IAB node.

[0010] The third phase is IAB-DU initiation. The IAB-DU uses the IP address obtained in the second phase to initiate SCTP (Stream Control Transmission Protocol) connection establishment and F1 connection establishment with the IAB-donor-CU. The IAB node can then begin providing air interface services to the UE.

[0011] The above is a brief description, and specific reference is made to the prior art.

[0012] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0013] Summary of the Invention

[0014] The inventors discovered that in existing IAB node integration processes, both the mobile and user-defined interface (DU) of an IAB node terminate on the same donor-CU. This approach fails to achieve the flexibility of mobile IAB nodes and cannot quickly support topological adaptation between IAB node hosts. Therefore, supporting the integration of the mobile and user-defined interface (DU) of an IAB node on different donor-CUs is a research goal in the industry.

[0015] To address the above-mentioned problems or similar problems or similar problems in other scenarios, embodiments of the present application provide an IAB node integration method and apparatus.

[0016] According to one aspect of an embodiment of the present application, an integrated device of an IAB node is provided, which is configured in the IAB node. The IAB node includes an MT (mobile terminal) and a DU (distributed unit), wherein:

[0017] The DU of the IAB node is configured by OAM or the MT of the IAB node is configured by RRC to terminate the CU of the IAB host. The base station identifier of the CU of the IAB host is terminated by F1;

[0018] The DU of the IAB node establishes F1 with the CU of the F1 termination IAB host according to the base station identifier.

[0019] According to another aspect of an embodiment of the present application, an integrated device of an IAB node is provided, which is configured in an RRC termination IAB host, wherein the RRC termination IAB host includes a CU and a DU, wherein:

[0020] The CU of the RRC termination IAB host sends first information to the MT of the IAB node, where the first information includes identification information of the IAB node and / or identification information of the RRC termination IAB host, so that the DU of the IAB node sends second information related to the first information to the F1 termination IAB host.

[0021] According to another aspect of an embodiment of the present application, an integrated device of an IAB node is provided, which is configured in an RRC termination IAB host, wherein the RRC termination IAB host includes a CU and a DU, wherein:

[0022] The CU of the RRC termination IAB host receives a first RRC message sent by the MT of the IAB node, where the first RRC message includes the identification information of the F1 termination IAB host. The RRC termination IAB host sends the identification information of the IAB node to the F1 termination IAB host according to the first RRC message.

[0023] According to another aspect of the embodiment of the present application, an integrated device of an IAB node is provided, which is configured in an F1 termination IAB host, wherein the F1 termination IAB host includes a CU and a DU, wherein:

[0024] The CU of the F1 terminating IAB host receives second information sent by the DU of the IAB node, where the second information is related to the first information, and the first information includes identification information of the IAB node and / or identification information of the RRC terminating IAB host.

[0025] According to another aspect of an embodiment of the present application, an integrated device of an IAB node is provided, which is configured in an RRC termination IAB host, wherein the RRC termination IAB host includes a CU (central unit) and a DU (distributed unit), wherein:

[0026] The RRC terminates the CU of the IAB host for the IAB node to determine the base station identifier of the CU of the IAB host for F1 termination;

[0027] The CU of the RRC-terminating IAB host sends the base station identifier of the CU of the F1-terminating IAB host to the MT of the IAB node, so that the DU of the IAB node performs F1 establishment with the CU of the F1-terminating IAB host according to the base station identifier.

[0028] According to another aspect of an embodiment of the present application, an integrated device of an IAB node is provided, which is configured in an F1 termination IAB host, wherein the F1 termination IAB host includes a CU (central unit) and a DU (distributed unit), wherein:

[0029] The F1 IAB termination host receives a first Xn message sent by the CU of the RRC IAB termination host, where the first Xn message includes a UE XnAP identifier generated by the RRC IAB termination host for the IAB node and / or a BAP address of the IAB node.

[0030] According to another aspect of the embodiment of the present application, a setting device is provided, which is configured in an IAB node, wherein the IAB node includes an MT and a DU, wherein:

[0031] The MT sends an RRC setup complete message to the RRC termination IAB host, where the RRC setup complete message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.

[0032] According to another aspect of the embodiment of the present application, a setting device is provided, which is configured in an IAB node, wherein the IAB node includes an MT and a DU, wherein:

[0033] The MT receives a broadcast message sent by the RRC termination IAB host, where the broadcast message indicates a cell supporting mobile IAB;

[0034] The MT performs cell selection according to the broadcast message.

[0035] One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, the integration problem of the IAB node is solved, so that the IAB-MT and the collocated IAB-DU can be integrated into different donor-CUs, thereby improving the flexibility of network configuration.

[0036] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0037] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0038] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0040] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0041] FIG1 is a schematic diagram of an example of an IAB network topology;

[0042] FIG2 is a schematic diagram of the integration process of the mobile IAB node according to an embodiment of the present application;

[0043] FIG3 is a schematic diagram of an IAB node integration method according to an embodiment of the first aspect of the present application;

[0044] FIG4 is a schematic diagram of the process of IAB-DU configuration during IAB node integration;

[0045] FIG5 is another schematic diagram of the process of IAB-DU configuration during IAB node integration;

[0046] FIG6a and FIG6b are schematic diagrams of two other examples of the IAB node integration method according to the embodiment of the first aspect of the present application;

[0047] FIG7a and FIG7b are schematic diagrams of two further examples of the IAB node integration method according to the embodiment of the first aspect of the present application;

[0048] FIG8 is a schematic diagram of an IAB node integration method according to an embodiment of the second aspect of the present application;

[0049] FIG9 is another schematic diagram of the process of IAB-DU configuration during IAB node integration;

[0050] FIG10 is another schematic diagram of the IAB node integration method according to the embodiment of the second aspect of the present application;

[0051] FIG11a and FIG11b are schematic diagrams of two further examples of the IAB node integration method according to the embodiment of the second aspect of the present application;

[0052] FIG12 is a schematic diagram of a setting method according to an embodiment of the present application;

[0053] FIG13 is another schematic diagram of a setting method according to an embodiment of the present application;

[0054] FIG14 is a schematic diagram of an integrated device of an IAB node according to an embodiment of the present application;

[0055] FIG15 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application;

[0056] FIG16 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application;

[0057] FIG17 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application;

[0058] FIG18 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application;

[0059] FIG19 is a schematic diagram of a setting device according to an embodiment of the present application;

[0060] FIG20 is another schematic diagram of the setting device according to an embodiment of the present application;

[0061] FIG21 is a schematic diagram of an IAB node according to an embodiment of the present application;

[0062] FIG22 is a schematic diagram of an IAB-donor node according to an embodiment of the present application. DETAILED DESCRIPTION

[0063] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0064] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0065] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0066] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0067] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), etc., and / or other currently known or future communication protocols to be developed.

[0068] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0069] Base stations may include, but are not limited to, NodeBs (NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0070] In the embodiments of the present application, the term "user equipment" (UE) refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "terminal equipment" (TE). Terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, etc.

[0071] Terminal devices may include, but are not limited to, cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, and IAB-MT, etc.

[0072] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0073] FIG1 is a schematic diagram of an example of an IAB network topology structure, showing a situation where the MT and DU of an IAB are terminated to different donor-CUs.

[0074] The inventors discovered that the mobility of a mobile IAB (mIAB) or mobile relay in a larger area faces a challenge. That is, when it is on the move, based on the needs of network coverage and QoS support, the F1 termination host and non-F1 termination host of the IAB node may be different, that is, the MT and DU of the IAB terminate to different IAB-donor-CUs.

[0075] An F1-terminating node is a donor-CU that terminates the F1 interface of an IAB node, such as donor-CU2 in Figure 1. In Figure 1, IAB-DU1 is terminated to donor-CU2 via an F1 connection, making donor-CU2 the F1-terminating node for IAB node 1. An F1-terminating donor-CU is also called the donor-CU of an IAB-DU because the IAB-DU is configured by this CU.

[0076] A non-F1-terminating node is a CU with host functionality that does not terminate the F1 interface of an IAB node, such as donor-CU1 shown in Figure 1. Because a non-F1-terminating node has an RRC connection with the IAB-MT, a non-F1-terminating node can also be called a host node serving the IAB-MT. A non-F1-terminating host CU is also called an IAB-MT host CU or an RRC-terminating donor CU of an IAB node.

[0077] In Figure 1, IAB-MT1 is connected to its parent node, IAB Node 2, which then connects to donor-DU1 and donor-CU1. IAB-DU1 and donor-CU2 establish an F1 connection, but this F1 connection passes through IAB Node 2, donor-DU1, and ultimately to donor-CU2.

[0078] Since the RRC interface and the F1 interface of the IAB node 1 are terminated at different donor-CUs, the IAB node 1 is a boundary IAB node.

[0079] The inventors discovered that in the existing IAB node integration process, the IAB node's mobile and user-interface (DU) are both terminated on the same donor-CU. This fails to achieve the flexibility of mobile IAB nodes and cannot quickly support topological adaptation between IAB node hosts. Therefore, it is necessary to define how to support the integration of an IAB node's mobile and user-interface (MT) on different donor-CUs. In other words, this would support the network integration scenario shown in Figure 1 and enable integration of border IAB nodes. However, the integration process for connecting an IAB node's MT and user-interface (DU) to different donor-CUs is currently undefined.

[0080] In the embodiment of the present application, taking the 5G multi-hop IAB network deployment as an example, multiple UEs are connected to the IAB-donor through multi-hop IAB nodes and finally access the 5G network. The IAB nodes connected to the UEs can be mobile.

[0081] Figure 2 is a schematic diagram of the mobile IAB node integration process according to an embodiment of the present application, illustrating the network integration of a general-purpose IAB node (IAB node 1 in Figure 2 ). As shown in Figure 2 , the IAB-MT and IAB-DU of IAB node 1 are integrated into different IAB-donors. In Figure 2 , IAB-donor 1 is the RRC-terminating IAB donor, i.e., the donor to which the MT is connected; IAB-donor 2 is the F1-terminating IAB donor, i.e., the donor to which the DU is connected.

[0082] In Figure 2, the IAB-MT of IAB node 1 accesses the network in the first phase. In this phase, the IAB-MT connects to the network as a normal UE, and this process basically reuses the initial access process of a normal UE. The host to which the IAB-MT accesses is donor-CU1. In the second phase, donor-CU1 performs RRC configuration on the IAB-MT, including BH RLC channel establishment, etc. Donor-CU1 also performs routing updates on the IAB nodes between IAB node 1 and donor-DU1, such as IAB node 2, to support BAP routing from IAB node 1 to donor-DU1. In the third phase of the IAB-DU setup process, the IAB-DU of IAB node 1 establishes an F1 connection to donor-CU2, that is, F1 establishment is performed.

[0083] Various embodiments of the present application are described below with reference to the accompanying drawings. These embodiments are merely illustrative and are not intended to limit the present application. In the following description, expressions such as "if...", "in the case of...", and "when..." have the same meaning and are interchangeable.

[0084] Embodiments of the first aspect

[0085] An embodiment of the present application provides an IAB node integration method, which is applied to the scenario shown in FIG2 .

[0086] FIG3 is a schematic diagram of an IAB node integration method according to an embodiment of the present application, illustrating the method from the perspective of an IAB node. The IAB node is, for example, IAB node 1 in the scenario shown in FIG2 , and includes an MT and a DU. The MT may also be referred to as an IAB-MT, and the DU may be referred to as an IAB-DU. As shown in FIG3 , the method includes:

[0087] 301: The DU of the IAB node is configured by OAM F1 to terminate the base station identifier of the CU of the IAB host;

[0088] 302: The DU of the IAB node establishes F1 with the CU of the F1 termination IAB host according to the base station identifier.

[0089] It is worth noting that FIG3 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG3 above.

[0090] In the above embodiment, the base station identifier can be gNB ID, Global gNB ID, Global NG-RAN node ID, etc.

[0091] In the above embodiment, during the IAB-DU setup process in the third stage of FIG. 2 , the DU of the IAB node 1 needs to perform F1 setup to the CU of the F1-terminating IAB host. According to the embodiment of the present application, the IAB-DU is configured through OAM (Operation Administration and Maintenance), and the configuration content includes the base station identifier of the CU of the F1-terminating IAB host. Thus, the DU of the IAB node can perform F1 setup with the CU of the F1-terminating IAB host based on the base station identifier, thereby solving the problem of integrating the MT and DU of the mobile IAB node into different IAB-donors, thereby supporting the configuration flexibility of the IAB node and supporting the mobility of the IAB node in a wide area, and being able to provide high-quality services for UEs served by the mobile IAB node.

[0092] In an embodiment of the present application, the CU of the RRC-terminated IAB host is different from the CU of the F1-terminated IAB host. For example, as shown in Figure 2, the RRC-terminated IAB host is IAB-donor 1, and the CU of the RRC-terminated IAB host is IAB-Donor-CU1, which is also referred to as "CU1" or "donor-CU1" for the convenience of explanation; if the F1-terminated IAB host is IAB-donor 2, the CU of the F1-terminated IAB host is IAB-donor-CU2, which is also referred to as "CU2" or "donor-CU2" for the convenience of explanation.

[0093] In some embodiments, in the first or second phase shown in Figure 2, donor-CU1 allocates one or more IP addresses to IAB node 1 through RRC signaling. These IP addresses are anchored at IAB-donor-DU1. Thus, IAB node 1 can initiate TNL establishment and F1 establishment process to the CU (donor-CU2) of the F1 termination IAB host based on the IP address.

[0094] In some embodiments, the IAB node is only configured with the above-mentioned base station identifier, then the DU of the IAB node can also discover the TNL address of the CU (CU2) of the F1 termination host through the base station identifier, and establish F1 with CU2 based on the above-mentioned base station identifier and the TNL address.

[0095] In the above embodiment, if the TNL address of donor-CU2 is not configured for the IAB-DU, the IAB-DU can use the same method as the non-IAB gNB-DU to discover the TNL address of donor-CU2 through the base station identifier, such as using the Xn-C TNL address discovery process, etc. For details, please refer to the relevant technology.

[0096] In some embodiments, the IAB node is configured with both the above-mentioned base station identifier and the TNL address (i.e., IP address) of the CU (CU2) of the F1 termination host. The DU of the IAB node can establish F1 with the CU of the F1 termination IAB host based on the base station identifier and the TNL address.

[0097] In some embodiments, the IAB node is configured with multiple base station identifiers, and the DU of the IAB node can select a base station identifier from the multiple base station identifiers according to a predetermined policy to perform F1 establishment.

[0098] For example, OAM configures the base station identification information of multiple CUs for the IAB-DU, such as including them in a list, indicating candidate donor-CU information. The IAB-DU can then select a donor-CU (such as IAB-donor-CU2) and establish F1.

[0099] In some embodiments, the IAB node is further configured with priorities of multiple base station identifiers, and the DU of the IAB node may select a base station identifier with the highest priority among the multiple base station identifiers to perform F1 establishment.

[0100] For example, the list can also include the priority information of the IAB-donor-CU configured by OAM to provide further instructions to the IAB-DU and help it select the IAB-donor-CU. For example, the IAB-donor-CU indicated as high priority can be selected first. In case the F1 establishment fails, another IAB-donor-CU can be selected for F1 establishment.

[0101] In some embodiments, the DU of the IAB node initiates TNL establishment and F1 establishment procedures to the CU of the F1 terminating IAB host (IAB-donor-CU2) using the IP address allocated to the IAB node by the CU of the RRC terminating IAB host (IAB-donor-CU1).

[0102] In the above embodiment, the F1 setup request message (F1 SETUP REQUEST) may also include the BAP address of the IAB node. Therefore, after receiving the F1 setup request message, the CU (IAB-donor-CU2) that terminates the IAB host of the F1 may save the BAP address for the IAB node.

[0103] In the above embodiment, if the BAP address conflicts with the BAP address of other nodes in the topology of IAB-donor-CU2, IAB-donor-CU2 may use the BAP address as the BAP address used by the IAB node in the topology of IAB-donor-CU1, and IAB-donor-CU2 may also allocate a BAP address in the topology of IAB-donor-CU2 to the IAB node.

[0104] In the above embodiment, the IAB-donor-CU2 may send the allocated BAP address to the IAB-DU via the F1 SETUP RESPONSE message. For example, the BAP Address IE in the F1 SETUP RESPONSE message may be reused to indicate that the BAP address is allocated by the IAB-donor-CU2 to the IAB node. However, the present application is not limited thereto.

[0105] In the above embodiment, after IAB-donor-CU2 and IAB-DU establish an F1 connection, the IAB node is equivalent to a topology belonging to two CUs (IAB-donor-CU1 and IAB-donor-CU2) and is configured by the two CUs. The two CUs need to exchange further information to perform the IAB transmission migration management process and / or the IAB resource coordination process. These processes interact on the Xn interface between IAB-donor-CU1 and IAB-donor-CU2. Because IAB-donor-CU2 is the F1-terminating IAB host CU of the IAB node, these IAB-related Xn processes are generally initiated by the F1-terminating IAB host CU. Therefore, IAB-donor-CU2 needs to know the base station identifier of IAB-donor-CU1 and the UE XnAP ID of the IAB node in IAB-donor-CU1, that is, the NG-RAN node UE XnAP ID generated by IAB-donor-CU1 for the IAB node, also known as the Non F1-terminating IAB-Donor UE XnAP ID.

[0106] In an embodiment of the present application, the relevant information may be transmitted by the IAB node or by IAB-donor-CU1, so that IAB-donor-CU2 obtains the base station information of IAB-donor-CU1 and the UE XnAP ID generated by IAB-donor-CU1 for the IAB node.

[0107] The following explains them separately.

[0108] In some embodiments, the relevant information is transmitted by the IAB node.

[0109] In the above embodiment, the MT of the IAB node receives the first information sent by the CU (IAB-donor-CU1) of the RRC-terminated IAB host, where the first information includes the identification information of the IAB node and / or the identification information of the RRC-terminated IAB host; the DU of the IAB node sends the second information related to the above first information to the F1-terminated IAB host.

[0110] In the above embodiment, the identification information of the IAB node is, for example, the UE XnAP identifier generated by the RRC termination IAB host for the IAB node; the identification information of the RRC termination IAB host is, for example, the base station identification information of the CU of the RRC termination IAB host. Here, the base station identifier can be a gNB ID, a Global gNB ID, a Global NG-RAN node ID, etc.

[0111] In the above embodiment, the DU of the IAB node can send the above second information to the F1 termination IAB host through the F1 SETUP REQUEST message when establishing F1 with the (future) F1 termination IAB host. However, the present application is not limited to this. The DU of the IAB node can also send the above second information through other F1AP signaling after the F1 is established. When IAB-donor-CU2 receives the second information, it can be concluded that the MT part of the IAB node does not belong to the topology of IAB-donor-CU2, that is, the MT of the IAB node is terminated on another donor-CU, and the IAB node is a boundary IAB node. IAB-donor-CU2 can also determine that the MT of the IAB node is terminated on another donor-CU by judging that the BAP address of the IAB node in the received F1 SETUP REQUEST message or the IP address used is not within its own topology (that is, not allocated by IAB-donor-CU2).

[0112] In the above embodiment, in one example, the first information includes the identification information of the IAB node and the identification information of the RRC termination IAB host. In this example, the second information is identical to the first information. Therefore, the DU of the IAB node can simply send the first information obtained by the MT of the IAB node to the F1 termination IAB host. "Identical" here refers to the same content, meaning that the first and second information contain the same information.

[0113] In the above embodiment, in another example, the first information includes the identification information of the IAB node but does not include the identification information of the RRC termination IAB host. In this example, the second information includes the serving cell identity NCGI of the MT of the IAB node and the identification information of the IAB node.

[0114] In the above example, because the IAB-MT itself obtains the cell identification information (NCGI, NR Cell Global Identifier) ​​from the system information broadcast by IAB-donor-CU1, and the cell identification information implicitly contains the base station identification, IAB-donor-CU1 can only send the UE XnAP ID of the IAB node to IAB-MT, and the juxtaposed IAB-DU sends the IAB-MT's serving cell identification NCGI and the UE XnAP ID to IAB-donor-CU2. Therefore, IAB-donor-CU2 can determine the bit length of the base station identification through some method (such as based on OAM configuration) and then obtain the base station identification from NCGI.

[0115] In the above embodiment, the first information may be explicitly included in the RRC reconfiguration message or included in a container of the RRC reconfiguration message. For example, the RRC reconfiguration message includes a first IE, and the first IE includes the above first information; for another example, the bap-Config IE of the RRC reconfiguration message includes a second IE or a first field, and the second IE or the first field includes the above first information.

[0116] In the above embodiment, the second information may be explicitly included in the F1AP message or included in a container of the F1AP message. For example, the F1AP message includes a third IE, and the third IE includes the second information. The F1AP message may be, for example, an F1 setup request message, but the present application is not limited thereto.

[0117] Figure 4 is a schematic diagram of the IAB-DU configuration process during the IAB node integration process, illustrating the OAM-based IAB-DU configuration. As shown in Figure 4, the process includes:

[0118] 401: IAB-donor-CU1 sends an RRC reconfiguration message to IAB-MT;

[0119] 402: IAB-MT sends an RRC reconfiguration complete message to IAB-donor-CU1.

[0120] 403: The IAB-DU sends the second information to the IAB-donor-CU2.

[0121] 404: The 5G core network performs relevant configurations on IAB-donor-CU2.

[0122] 405: IAB-donor-CU2 returns an F1 setup response message to the IAB-DU, indicating that the IAB-DU setup is complete and the IAB node can start providing air interface services for the UE.

[0123] 406: IAB-donor-CU2 sends an "IAB TRANSPORT MIGRATION MANAGEMENT REQUEST" to IAB-donor-CU1.

[0124] 407: IAB-donor-CU1 sends "IAB TRANSPORT MIGRATION MANAGEMENT RESPOSE" to IAB-donor-CU2.

[0125] The above steps 401 and 402 are the process of IAB-donor-CU1 configuring IAB-MT. In step 401, IAB-donor-CU1 uses RRCReconfiguration message to configure the above first information.

[0126] In the above 401, the first information includes the UE XnAP ID of the IAB node and, optionally, the base station identifier of IAB-donor-CU1. This first information can be explicitly included in the RRC reconfiguration message or placed in a container in the RRC reconfiguration message. The IAB-DU directly places the container in the F1 setup request message and sends it to IAB-donor-CU2. In other words, the IAB node does not decode the container and directly transmits it transparently.

[0127] For example, a new IE (first IE) may be defined in the RRCReconfiguration message to indicate the first information, or a new sub-IE (second IE) or field (first field) may be defined in the bap-Config IE in the RRCReconfiguration message to indicate the first information.

[0128] The above 401 and 402 may occur at any stage before the third stage shown in FIG. 2 , for example, at any time from the first stage to the stage 2-2, and this application does not impose any limitation on this.

[0129] Before the above step 403, OAM has configured the IAB-DU, including the base station identifier of donor-CU2, etc., for the IAB-DU to establish F1 to the donor-CU2.

[0130] In the above 403, the IAB-DU can use the F1 SETUP REQUEST message to send the above second information. The second information may include the relevant identification information of the IAB-donor-CU1 and the UE XnAP ID of the IAB node in the IAB-donor-CU1 (from the first information). The relevant identification information of the IAB-donor-CU1 can be the base station identifier in the first information or the NCGI of the serving cell. The second information can be explicitly included in the F1AP message or placed in a container in the F1AP message. For example, a new IE (third IE) can be defined in the F1 SETUP REQUEST message to indicate the second information.

[0131] The above 406 and 407 are examples of IAB-related Xn processes between IAB-donor-CU2 and IAB-donor-CU1, which can be performed after the IAB integration process, such as the IAB Transport Migration Management process initiated by IAB-donor-CU2. The present application is not limited thereto.

[0132] According to the above embodiment, IAB-donor-CU2 can obtain the base station information of IAB-donor-CU1 and the UE XnAP ID generated by IAB-donor-CU1 for the IAB node from the IAB node.

[0133] In other embodiments, the relevant information is transmitted by IAB-donor-CU1.

[0134] In the above embodiment, OAM is configured for the IAB-DU. The MT of the IAB node sends a first RRC message to the CU of the RRC termination IAB host (IAB-donor-CU1). The first RRC message includes the OAM-configured identification information of the F1 termination IAB host, so that the RRC termination IAB host sends the identification information of the IAB node to the F1 termination IAB host.

[0135] In the above embodiment, the first RRC message is, for example, a UEAssistanceInformation message; the UEAssistanceInformation message includes a fourth IE, and the fourth IE includes identification information of the F1 termination IAB host.

[0136] In the above embodiment, the MT of the IAB node may optionally initiate a UE-assisted information reporting process after the DU of the IAB node completes the F1 establishment with the F1-terminating IAB host. The IAB node has the capability to provide identification information of the F1-terminating IAB host, is configured with capability reporting, and is in an RRC-connected state. That is, if the IAB node has the capability to provide identification information of the F1-terminating IAB host, and is configured with capability reporting, then the IAB, when in the RRC-connected state, may initiate the above-mentioned UE-assisted information reporting process after the IAB-DU completes the F1 establishment with CU2.

[0137] In the above embodiment, the CU of the RRC termination IAB host may send a first Xn message to the F1 termination IAB host. The first Xn message includes the UE XnAP identifier generated by the RRC termination IAB host for the IAB node and / or the BAP address of the IAB node.

[0138] In the above embodiment, the F1 terminated IAB host may further feed back a second Xn message to the CU of the RRC terminated IAB host, where the second Xn message includes confirmation information.

[0139] Figure 5 is another schematic diagram of the IAB-DU configuration process during the IAB node integration process, illustrating the OAM-based IAB-DU configuration. As shown in Figure 5, the process includes:

[0140] 501: IAB-DU and IAB-donor-CU2 establish F1;

[0141] 502: The 5G core network performs relevant configurations on IAB-donor-CU2.

[0142] 503: IAB-donor-CU2 responds with an F1 establishment response to IAB-DU;

[0143] 504: The IAB-MT sends an RRC message 1 to the IAB-donor-CU1. The RRC message 1 includes the base station identifier of the IAB-donor-CU2.

[0144] 505: IAB-donor-CU1 sends an XnAP message 1 to IAB-donor-CU2. The XnAP message 1 includes the UE XnAP ID and / or the BAP address of the IAB node.

[0145] 506: IAB-donor-CU2 sends XnAP message 2 to IAB-donor-CU1, where XnAP message 2 includes confirmation information.

[0146] 507: IAB-donor-CU2 sends "IAB TRANSPORT MIGRATION MANAGEMENT REQUEST" to IAB-donor-CU1;

[0147] 508: IAB-donor-CU1 sends "IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE" to IAB-donor-CU2.

[0148] The above 501 to 503 are the conventional F1 establishment process from IAB-DU to IAB-donor-CU2. For details, please refer to the relevant technology.

[0149] In the above 504, since the information of IAB-donor-CU2 is configured for the IAB node by OAM, the IAB node can inform IAB-donor-CU1 of the identification information of IAB-donor-CU2, so that IAB-donor-CU1 can send the IAB identification information to IAB-donor-CU2. Therefore, in 504, the IAB node can notify IAB-donor-CU1 via an uplink (UE to network side) RRC message. This RRC message is a first RRC message and includes the base station identifier of IAB-donor-CU2, that is, the F1-terminating host gNB ID of the IAB node, or the gNB ID of the CU of the IAB-DU collocated with the IAB-MT.

[0150] The first RRC message may reuse the UEAssistanceInformation message, for example, a new IE (fourth IE) is added to the UEAssistanceInformation message to include the base station identifier of IAB-donor-CU2.

[0151] In addition, in 504, the initialization part of the UE auxiliary information at the RRC layer can also be enhanced. For example, if a UE (IAB-MT) capable of providing F1 termination host node information is configured to report, it can initiate the UE auxiliary information reporting process in the connected state (RRC_CONNECTED) after the F1 establishment of the collocated IAB-DU is completed.

[0152] The above 505 and 506 are the XnAP process between RAN nodes, which is used for IAB-donor-CU1 to send the IAB identification information to IAB-donor-CU2.

[0153] In 505 and 506, a new XnAP process can be defined. For example, a UE-associated class 1 IAB process can be defined, which consists of a first Xn message and a second Xn message. The process is initiated by the non-F1-terminating IAB-donor-CU. The first Xn message contains the UE XnAP ID of the IAB-MT generated by IAB-donor-CU1, and can also contain the BAP address of the IAB node, which is used by IAB-donor-CU2 to identify the IAB node. The second Xn message is a confirmation message from IAB-donor-CU2.

[0154] In addition, the second Xn message is optional. For example, if the XnAP process of class 2 is defined, the second Xn message can be omitted.

[0155] In addition, the above 505 and 506 can also reuse the NG-RAN node Configuration Update process, and include the IAB identification information (UE XnAP ID, BAP address of the IAB node) as a new IE in the NG-RAN NODE CONFIGURATION UPDATE message.

[0156] The above 507 and 508 are examples of IAB-related Xn processes between IAB-donor-CU2 and IAB-donor-CU1, which can be performed after the integration process of the IAB node, such as the IAB Transport Migration Management process initiated by IAB-donor-CU2. The present application is not limited thereto.

[0157] According to the above embodiment, IAB-donor-CU2 can obtain the base station information of IAB-donor-CU1 and the UE XnAP ID generated by IAB-donor-CU1 for the IAB node from IAB-donor-CU1.

[0158] In some embodiments, the MT of the IAB node may send an RRC setup complete message to the RRC termination IAB host, where the RRC setup complete message includes third information indicating the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.

[0159] In the above embodiment, for the first stage shown in Figure 2, during the IAB-MT setup process, the IAB-MT can perform an RRC connection establishment process on the IAB-donor-CU1 and authenticate with the network. To indicate its mobile IAB capabilities, the IAB-MT can include an indication of the mobile IAB node in the RRCSetupComplete message (RRC Connection Setup Complete message, also called Message 5), which is used by the IAB-donor to select an AMF (Access and Mobility Management Function) that supports mobile IAB.

[0160] In some embodiments, the MT of an IAB node may receive a broadcast message sent by an RRC-terminated IAB host, which indicates cells supporting mobile IAB; the IAB node may select a cell based on the broadcast message. Specifically, the broadcast message is sent by a donor-DU or IAB-DU controlled by the IAB host.

[0161] In the above embodiment, for the first stage shown in FIG2 , during the cell selection process of the mobile IAB-MT, a cell that broadcasts "supports mobile IAB" can be selected, that is, the cell is selected as the parent cell. The broadcast message regarding the support of mobile IAB can be implemented by a SIB1 (System Information Block 1) message of the base station. The present application is not limited thereto.

[0162] Figure 6a is another schematic diagram of the IAB node integration method according to an embodiment of the present application, and Figure 6b is another schematic diagram of the IAB node integration method according to an embodiment of the present application. Both examples are described from the side of the RRC-terminated IAB host. The RRC-terminated IAB host is, for example, IAB-donor 1 shown in Figure 2, including CU (IAB-donor-CU1) and DU (IAB-donor-DU1). The same contents as in the previous embodiment will not be repeated.

[0163] As shown in FIG6a , in one example, the method includes:

[0164] 601a: The RRC termination IAB host sends first information to the MT of the IAB node (step 401), where the first information includes identification information of the IAB node and / or identification information of the RRC termination IAB host, so that the DU of the IAB node sends second information related to the first information to the F1 termination IAB host (step 403).

[0165] In some embodiments, the identification information of the IAB node may be a UE XnAP identifier generated by the RRC termination IAB host for the IAB node; the identification information of the RRC termination IAB host may be base station identification information of the CU of the RRC termination IAB host.

[0166] In the above embodiment, in one example, the first information includes the identification information of the IAB node and the identification information of the RRC termination IAB host, and the second information is the same as the first information; in another example, the first information includes the identification information of the IAB node; the second information includes the serving cell identifier NCGI of the MT of the IAB node and the identification information of the IAB node.

[0167] In the above embodiment, the first information may be explicitly included in the RRC reconfiguration message or included in a container of the RRC reconfiguration message.

[0168] In the above embodiment, in one example, the RRC reconfiguration message includes a first IE, and the first IE includes the above first information; in another example, the bap-Config IE of the RRC reconfiguration message includes a second IE or a first field, and the second IE or the first field includes the above first information.

[0169] As shown in FIG6b , in another example, the method includes:

[0170] 601b: The CU of the RRC termination IAB host receives a first RRC message sent by the MT of the IAB node (step 504). The first RRC message includes the identification information of the F1 termination IAB host. The RRC termination IAB host sends the identification information of the IAB node to the F1 termination IAB host according to the first RRC message.

[0171] In some embodiments, the first RRC message may be a UEAssistanceInformation message; for example, the UEAssistanceInformation message includes a fourth IE, and the fourth IE includes identification information of the F1 termination IAB host.

[0172] In some embodiments, the CU of the RRC terminating IAB host sends a first Xn message to the F1 terminating IAB host (step 505 ). The first Xn message includes the UE XnAP identifier generated by the RRC terminating IAB host for the IAB node and / or the BAP address of the IAB node.

[0173] In some embodiments, optionally, the CU of the RRC terminated IAB host may further receive a second Xn message sent by the F1 terminated IAB host (step 506 ), where the second Xn message includes confirmation information.

[0174] In the above two examples, the CU (IAB-donor-CU1) of the RRC-terminated IAB host and the CU (IAB-donor-CU2) of the F1-terminated IAB host are different.

[0175] In the above two examples, the CU of the RRC-terminated IAB host allocates one or more IP addresses to the IAB node, so that the IAB node can use the IP addresses to initiate TNL establishment and F1 establishment procedures to the CU of the F1-terminated IAB host. The IP addresses can be anchored to the DU of the RRC-terminated IAB host.

[0176] In the above two examples, in some embodiments, the RRC termination IAB host may further receive an RRC establishment completion message sent by the MT of the IAB node, where the RRC establishment completion message includes third information indicating the mobile IAB capability of the IAB node; the RRC termination IAB host selects an AMF that supports mobile IAB based on the third information.

[0177] In the above two examples, in some implementations, the RRC termination IAB host may further send a broadcast message indicating cells supporting mobile IAB; thus, after receiving the broadcast message, the IAB node may perform cell selection according to the broadcast message.

[0178] Figure 7a is another schematic diagram of the IAB node integration method according to an embodiment of the present application, and Figure 7b is another schematic diagram of the IAB node integration method according to an embodiment of the present application. Both examples are described from the side of the F1-terminating IAB host. The F1-terminating IAB host is, for example, IAB-donor 2 shown in Figure 2, including CU (IAB-donor-CU2) and DU (IAB-donor-DU2). The method of Figure 7a corresponds to the method of Figure 6a, and the method of Figure 7b corresponds to the method of Figure 6b. The same content as the previous embodiment will not be repeated.

[0179] As shown in FIG7a , in one example, the method includes:

[0180] 701a: The F1 IAB termination host receives second information sent by the DU of the IAB node, where the second information is related to the first information, and the first information includes identification information of the IAB node and / or identification information of the RRC IAB termination host.

[0181] In some embodiments, the identification information of the IAB node is the UE XnAP identification generated by the RRC termination IAB host for the IAB node; the identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.

[0182] In some embodiments, in one example, the first information includes identification information of the IAB node and identification information of the RRC termination IAB host, and the second information is the same as the first information; in another example, the first information includes identification information of the IAB node; the second information includes the service cell identifier NCGI of the MT of the IAB node and the identification information of the IAB node.

[0183] In some embodiments, the second information is explicitly included in the F1AP message or included in a container of the F1AP message. The F1AP message may be an F1 setup request message. In addition, the F1AP message may include a third IE, which includes the second information.

[0184] In some embodiments, the CU of the F1 terminating IAB host receives an F1 setup request message sent by the DU of the IAB node, where the F1 setup request message includes the BAP address of the IAB node; the F1 terminating IAB host saves the BAP address for the IAB node.

[0185] As shown in FIG7b , in another example, the method includes:

[0186] 701b: The F1 IAB termination host receives a first Xn message sent by the CU of the RRC IAB termination host. The first Xn message includes the UE XnAP identifier generated by the RRC IAB termination host for the IAB node and / or the BAP address of the IAB node.

[0187] In some embodiments, the F1 termination IAB host may further send a second Xn message to the CU of the RRC termination IAB host, where the second Xn message includes confirmation information.

[0188] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0189] According to the method of the embodiment of the present application, the integration problem of the IAB node is solved, so that the IAB-MT and the collocated IAB-DU can be integrated into different donor-CUs, thereby improving the flexibility of network configuration.

[0190] Embodiments of the second aspect

[0191] This embodiment of the present application provides an IAB node integration method, applicable to the scenario shown in Figure 2. Unlike the embodiment of the first aspect, in this embodiment, IAB-donor-CU1 specifies the F1-terminating donor-CU (i.e., IAB-donor-CU2) of the IAB node. In other words, the relevant information about IAB-donor-CU2 is not configured to the IAB-DU by OAM, but rather by the CU terminating the IAB host via RRC and configured to the IAB-MT.

[0192] FIG8 is a schematic diagram of an IAB node integration method according to an embodiment of the present application, illustrating the method from the perspective of an RRC-terminated IAB host. The RRC-terminated IAB host is, for example, IAB-donor 1 shown in FIG2 , including a CU (IAB-donor-CU1) and a DU (IAB-donor-DU1). Details identical to those in the embodiment of the first aspect are not repeated here. As shown in FIG8 , the method includes:

[0193] 801: The CU of the RRC-terminated IAB host determines the base station identifier of the CU of the F1-terminated IAB host for the IAB node;

[0194] 802: The CU of the RRC-terminating IAB host sends the base station identifier of the CU of the F1-terminating IAB host to the MT of the IAB node, so that the DU of the IAB node establishes F1 with the CU of the F1-terminating IAB host according to the base station identifier.

[0195] It is worth noting that FIG8 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG8 above.

[0196] In some embodiments, the CU of the RRC terminated IAB host is configured with the base station identifier of the F1 terminated IAB host by OAM, thereby obtaining the base station identifier of the CU of the F1 terminated IAB host.

[0197] For example, OAM configures multiple base station identifiers of IAB-donor-CUs, and the CU of the RRC-terminated IAB host selects a base station identifier from the multiple base station identifiers according to a predetermined policy.

[0198] For another example, OAM configures multiple IAB-donor-CU base station identifiers and the priority of each base station identifier, and the CU that terminates the IAB host by RRC selects the base station identifier with the highest priority among the multiple base station identifiers.

[0199] In other embodiments, the CU of the RRC IAB termination host selects the F1 IAB termination host based on information (eg, neighbor cell information) obtained based on the ANR (Automatic neighbor relations) function, thereby obtaining the base station identifier of the F1 IAB termination host.

[0200] In some embodiments, the CU of the RRC termination IAB host sends the base station identifier of the F1 termination IAB host to the MT of the IAB node via an RRC reconfiguration message. Thus, the IAB node obtains the base station identifier of the F1 termination IAB host.

[0201] In the above embodiment, the base station identifier of the F1 terminating IAB host is obtained, and the DU of the IAB node can establish F1 with the CU of the F1 terminating IAB host based on the base station identifier and the TNL address of the CU of the F1 terminating IAB host discovered through the base station identifier. For details, please refer to the embodiment of the first aspect.

[0202] In the above embodiment, the CU of the RRC-terminated IAB host optionally also sends the TNL address of the CU of the F1-terminated IAB host to the MT of the IAB node via an RRC reconfiguration message. Thus, the DU of the IAB node establishes an F1 connection with the CU of the F1-terminated IAB host based on the base station identifier and the TNL address. For details, please refer to the embodiment of the first aspect.

[0203] In the above embodiment, there is no limitation on the manner in which the RRC reconfiguration message carries the above base station identifier. For example, a new IE (referred to as the fifth IE) may be added to the RRC reconfiguration message, or a new sub-IE (referred to as the sixth IE) or field (referred to as the second field) may be defined in the bap-Config IE of the RRC reconfiguration message to indicate the base station identifier and TNL address (optional) of the F1-terminating IAB host. For example, the fifth IE includes the base station identifier and TNL address (optional) of the F1-terminating IAB host; for another example, the sixth IE or the second field includes the base station identifier and TNL address (optional) of the F1-terminating IAB host.

[0204] In some embodiments, the CU of the RRC-terminated IAB host allocates one or more IP addresses to the IAB node, and these IP addresses are anchored to the DU of the RRC-terminated IAB host. Thus, the IAB node can use the allocated IP addresses to initiate TNL establishment and F1 establishment procedures with the CU of the F1-terminated IAB host. For details, please refer to the embodiments of the first aspect.

[0205] In some embodiments, the CU (IAB-donor-CU1) of the RRC-terminated IAB host further sends first information to the MT of the IAB node, where the first information includes identification information of the IAB node and / or identification information of the RRC-terminated IAB host; the DU of the IAB node sends second information related to the above-mentioned first information to the F1-terminated IAB host.

[0206] The identification information of the IAB node, the identification information of the RRC termination IAB host, the content related to the first information, and the content related to the second information can refer to the embodiment of the first aspect and will not be repeated here.

[0207] The first information may be sent via an RRC reconfiguration message. For example, the first information may be sent along with the base station identifier of the F1 IAB termination host via the RRC reconfiguration message. For a detailed process, please refer to FIG. 4 . The difference is that, in step 401, the RRC reconfiguration message may include not only the first information but also the base station identifier of the F1 IAB termination host.

[0208] In some embodiments, the CU of the RRC terminating IAB host sends a first Xn message to the F1 terminating IAB host, where the first Xn message includes the UE XnAP identifier generated by the RRC terminating IAB host for the IAB node and / or the BAP address of the IAB node. For details, reference may be made to the embodiment of the first aspect, such as operation 505 shown in FIG5 .

[0209] In the above embodiment, optionally, the CU of the RRC terminated IAB host receives a second Xn message sent by the F1 terminated IAB host, where the second Xn message includes confirmation information. For details, reference may be made to the embodiment of the first aspect, such as operation 506 shown in FIG5 .

[0210] Figure 9 is another schematic diagram of the IAB-DU setup process during the IAB node integration process, showing the situation where IAB-donor-CU1 specifies IAB-donor-CU2. As shown in Figure 9, the process includes:

[0211] 901: IAB-donor-CU1 sends an RRC reconfiguration message to IAB-MT. The RRC reconfiguration message includes the base station identifier and TNL address (optional) of IAB-donor-CU2.

[0212] 902: IAB-MT sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to IAB-donor-CU1;

[0213] 903: IAB-DU establishes F1 with IAB-donor-CU2;

[0214] 904: The 5G core network performs relevant configurations on IAB-donor-CU2.

[0215] 905: IAB-donor-CU2 responds with an F1 establishment response to the IAB-DU;

[0216] 906: IAB-donor-CU1 sends an XnAP message 1 to IAB-donor-CU2. The XnAP message 1 includes the UE XnAP ID and / or the BAP address of the IAB node.

[0217] 907: IAB-donor-CU2 sends XnAP message 2 to IAB-donor-CU1, where XnAP message 2 includes confirmation information.

[0218] 908: IAB-donor-CU2 sends "IAB TRANSPORT MIGRATION MANAGEMENT REQUEST" to IAB-donor-CU1;

[0219] 909: IAB-donor-CU1 sends an "IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE" to IAB-donor-CU2.

[0220] The above operations 906 to 909 are the same as operations 505 to 508 in FIG. 5 , and reference may be made to the embodiment of the first aspect for details.

[0221] In other embodiments, IAB-donor-CU1 broadcasts a list through the cell, which includes one or more base station identifiers of IAB-donor-CUs that support mobile IAB and have IP connections with IAB-donor-DU1. When IAB-MT accesses in the first phase, it selects IAB-donor-CU2 by receiving the broadcast message. The selection criteria can be based on OAM configuration, or by comparing the IAB-donor-CU list configured in OAM with the broadcast IAB-donor-CU list to determine whether to access the cell and whether cell reselection is required.

[0222] In some embodiments, similar to the embodiment of the first aspect, the RRC termination IAB host may further receive an RRC setup complete message sent by the MT of the IAB node, where the RRC setup complete message includes third information indicating the mobile IAB capability of the IAB node. Thus, the RRC termination IAB host may select an AMF that supports mobile IAB based on the third information. For details, reference may be made to the embodiment of the first aspect.

[0223] In some embodiments, similar to the embodiment of the first aspect, the DU of the RRC-terminated IAB host may also send a broadcast message indicating cells supporting mobile IAB, so that the IAB node performs cell selection based on the broadcast message. For details, please refer to the embodiment of the first aspect.

[0224] FIG10 is another schematic diagram of an IAB node integration method according to an embodiment of the present application, illustrating the method from the perspective of the IAB node. The contents identical to those in the first aspect and the previous embodiments will not be repeated. As shown in FIG10 , the method includes:

[0225] 1001: The MT of the IAB node is configured by the CU of the IAB host to terminate the IAB host by RRC. The base station identifier of the CU of the IAB host is terminated by F1.

[0226] 1002: The DU of the IAB node establishes F1 with the CU of the F1 termination IAB host according to the base station identifier.

[0227] In the above embodiment, optionally, the MT of the IAB node is further configured with the TNL address of the CU of the F1 terminating IAB host. The behavior of the IAB node is the same as that of the IAB node in the embodiment of the first aspect, and the description thereof is omitted here.

[0228] In some embodiments, the MT of the IAB node further receives first information from IAB-donor-CU1 and sends second information to IAB-donor-CU2 accordingly. The details have been explained in the previous embodiment and the embodiment of the first aspect and will not be repeated here.

[0229] FIG11a is another schematic diagram of the IAB node integration method according to an embodiment of the present application, and FIG11b is another schematic diagram of the IAB node integration method according to an embodiment of the present application. Both examples are described from the perspective of the F1 terminating IAB host. The same contents as those in the embodiment of the first aspect and the previous embodiments will not be repeated.

[0230] As shown in FIG11a , in one example, the method includes:

[0231] 1101a: The F1 IAB termination host receives second information sent by the DU of the IAB node, where the second information is related to the first information, and the first information includes identification information of the IAB node and / or identification information of the RRC IAB termination host.

[0232] The implementation of the above steps is the same as that of 701a in Figure 7a, and will not be repeated here.

[0233] As shown in FIG. 11 b , in another example, the method includes:

[0234] 1101b: The F1 IAB termination host receives a first Xn message sent by the CU of the RRC IAB termination host, where the first Xn message includes the UE XnAP identifier generated by the RRC IAB termination host for the IAB node and / or the BAP address of the IAB node.

[0235] In some embodiments, the F1 terminating IAB host further sends a second Xn message to the CU of the RRC terminating IAB host, where the second Xn message includes confirmation information.

[0236] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0237] According to the method of the embodiment of the present application, the integration problem of the IAB node is solved, so that the IAB-MT and the collocated IAB-DU can be integrated into different donor-CUs, thereby improving the flexibility of network configuration.

[0238] Embodiments of the third aspect

[0239] An embodiment of the present application provides a setting method, which is applied to the scenario shown in Figure 2 and is explained from the side of the IAB node. The IAB node is, for example, the IAB node 1 in the scenario shown in Figure 2, which includes an MT and a DU. The MT can also be called an IAB-MT, and the DU can be called an IAB-DU.

[0240] FIG12 is a schematic diagram of a setting method according to an embodiment of the present application. As shown in FIG12 , the method includes:

[0241] 1201: The MT of the IAB node sends an RRC setup complete message to the RRC termination IAB host. The RRC setup complete message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.

[0242] In the above embodiment, for the first stage shown in Figure 2, during the IAB-MT setup process, the IAB-MT can perform an RRC connection establishment process on the IAB-donor-CU1 and authenticate with the network. To indicate its mobile IAB capabilities, the IAB-MT can include an indication of the mobile IAB node in the RRCSetupComplete message (RRC Setup Complete message, also called Message 5), which is used by the IAB-donor to select an AMF (Access and Mobility Management Function) that supports mobile IAB.

[0243] FIG13 is another schematic diagram of a setting method according to an embodiment of the present application. As shown in FIG13 , the method includes:

[0244] 1301: The MT of the IAB node receives a broadcast message sent by the RRC termination IAB host, where the broadcast message indicates cells supporting mobile IAB.

[0245] 1302: The MT of the IAB node performs cell selection according to the broadcast message.

[0246] In the above embodiment, the broadcast message is, for example, a SIB message, but the present application is not limited thereto.

[0247] In the above embodiment, for the first stage shown in FIG2 , during the cell selection process of the mobile IAB-MT, a cell that broadcasts "supports mobile IAB" can be selected, that is, the cell is selected as the parent cell. The broadcast message regarding the support of mobile IAB can be implemented by a SIB (System Information Block) message of the base station. The present application is not limited to this.

[0248] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0249] According to the method of the embodiment of the present application, the integration problem of the IAB node is solved, so that the IAB-MT and the collocated IAB-DU can be integrated into different donor-CUs, thereby improving the flexibility of network configuration.

[0250] Embodiments of the fourth aspect

[0251] An embodiment of the present application provides an integrated device for an IAB node.

[0252] FIG14 is a schematic diagram of an integrated device for an IAB node according to an embodiment of the present application. This device may be, for example, an IAB node in an IAB network, or one or more components or assemblies configured within the IAB node. The IAB node corresponds to IAB node 1 in FIG2 , and details common to the embodiment of the first aspect will not be repeated.

[0253] As shown in Figure 14, the device includes an IAB-MT (mobile terminal) 1401 and an IAB-DU (distributed unit) 1402, wherein the IAB-DU 1402 is configured by OAM or the IAB-MT 1401 is configured by the CU of the RRC-terminated IAB host with the base station identifier of the CU of the F1-terminated IAB host; the IAB-DU 1402 establishes F1 with the CU of the F1-terminated IAB host according to the base station identifier.

[0254] In some embodiments, the CU of the RRC-terminated IAB host is different from the CU of the F1-terminated IAB host.

[0255] In some embodiments, the IAB-DU 1402 discovers the TNL address of the CU of the F1 terminating IAB host through the base station identifier; the IAB-DU 1402 establishes F1 with the CU of the F1 terminating IAB host according to the base station identifier and the TNL address.

[0256] In some embodiments, the IAB-DU 1402 is further configured by the OAM with the TNL address of the CU of the F1 terminating IAB host; the IAB-DU 1402 establishes F1 with the CU of the F1 terminating IAB host according to the base station identifier and the TNL address.

[0257] In some embodiments, the OAM is configured with multiple base station identifiers, and the IAB-DU 1402 selects a base station identifier from the multiple base station identifiers according to a predetermined policy to perform F1 establishment.

[0258] In the above embodiment, the OAM may further configure the priorities of the multiple base station identifiers, and the IAB-DU 1402 selects a base station identifier with the highest priority among the multiple base station identifiers to establish F1.

[0259] In some embodiments, the IAB-DU 1402 initiates TNL establishment and F1 establishment procedures to the CU of the F1 terminating IAB host using the IP address allocated to the IAB node by the CU of the RRC terminating IAB host.

[0260] In the above embodiment, the F1 setup request message may include the BAP address of the IAB node; after receiving the F1 setup request message, the CU of the F1 terminating IAB host saves the BAP address for the IAB node.

[0261] In the above embodiment, the CU of the RRC-terminating IAB host may allocate one or more IP addresses to the IAB node, and the IP addresses are anchored to the DU of the RRC-terminating IAB host.

[0262] In some embodiments, the IAB-MT 1401 receives first information sent by the CU of the RRC-terminating IAB host, where the first information includes identification information of the IAB node and / or identification information of the RRC-terminating IAB host; and the IAB-DU 1402 sends second information related to the first information to the F1-terminating IAB host.

[0263] In the above embodiment, the identification information of the IAB node may be the UE XnAP identifier generated by the RRC termination IAB host for the IAB node; the identification information of the RRC termination IAB host may be the base station identification information of the CU of the RRC termination IAB host.

[0264] In the above embodiment, the first information may include the identification information of the IAB node and the identification information of the RRC termination IAB host, and the second information is the same as the first information; or, the first information may include the identification information of the IAB node; the second information includes the serving cell identifier NCGI of the MT of the IAB node and the identification information of the IAB node.

[0265] In the above embodiment, the first information may be explicitly included in the RRC reconfiguration message or included in a container of the RRC reconfiguration message.

[0266] In the above embodiment, the RRC reconfiguration message may include a first IE, which includes the first information; or, the bap-Config IE of the RRC reconfiguration message may include a second IE or a first field, which includes the first information.

[0267] In the above embodiment, the second information may be explicitly included in the F1AP message or included in a container of the F1AP message.

[0268] In the above embodiment, the F1AP message may be an F1 establishment request message.

[0269] In the above embodiment, the F1AP message may include a third IE, and the third IE includes the second information.

[0270] In some embodiments, the IAB-MT 1401 sends a first RRC message to the CU of the RRC termination IAB host, where the first RRC message includes identification information of the F1 termination IAB host, so that the RRC termination IAB host sends the identification information of the IAB node to the F1 termination IAB host.

[0271] In the above embodiment, the first RRC message may be a UEAssistanceInformation message; the UEAssistanceInformation message may include a fourth IE, and the fourth IE may include identification information of the F1 termination IAB host.

[0272] In the above embodiment, the IAB-MT 1401 can initiate the UE auxiliary information reporting process after the F1 establishment between the IAB-DU 1402 and the F1 termination IAB host is completed; wherein the IAB node has the ability to provide identification information of the F1 termination IAB host, and the IAB node is configured with capability reporting, and the IAB node is in an RRC connected state.

[0273] In the above embodiment, the CU of the RRC termination IAB host may send a first Xn message to the F1 termination IAB host, where the first Xn message includes the UE XnAP identifier generated by the RRC termination IAB host for the IAB node and / or the BAP address of the IAB node.

[0274] In the above embodiment, the CU of the RRC termination IAB host may receive the second Xn message sent by the F1 termination IAB host, where the second Xn message includes confirmation information.

[0275] In some embodiments, the IAB-MT 1401 sends an RRC setup complete message to the RRC termination IAB host, where the RRC setup complete message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.

[0276] In some embodiments, the IAB-MT 1401 receives a broadcast message sent by the RRC termination IAB host, where the broadcast message indicates cells supporting mobile IAB; and the IAB-MT 1401 performs cell selection according to the broadcast message.

[0277] FIG15 is another schematic diagram of an integrated device for an IAB node according to an embodiment of the present application. This device may be, for example, an IAB host in an IAB network, or one or more components or assemblies configured within the IAB host. The IAB host corresponds to the RRC-terminating IAB host in FIG2 , i.e., IAB-donor 1. Details common to the embodiment of the first aspect will not be repeated.

[0278] As shown in FIG15 , the integrated device 1500 of the IAB node includes a central unit (IAB-donor-CU1) 1501 and a distributed unit (IAB-donor-DU1) 1502 .

[0279] In some embodiments, the IAB-donor-CU1 1501 sends first information to the MT of the IAB node, where the first information includes identification information of the IAB node and / or identification information of the RRC termination IAB host, so that the DU of the IAB node sends second information related to the first information to the F1 termination IAB host.

[0280] In the above embodiment, the identification information of the IAB node may be the UE XnAP identifier generated by the RRC termination IAB host for the IAB node; the identification information of the RRC termination IAB host may be the base station identification information of the CU of the RRC termination IAB host.

[0281] In the above embodiment, the first information may include the identification information of the IAB node and the identification information of the RRC termination IAB host, and the second information is the same as the first information; or, the first information may include the identification information of the IAB node; the second information includes the serving cell identifier NCGI of the MT of the IAB node and the identification information of the IAB node.

[0282] In the above embodiment, the first information may be explicitly included in the RRC reconfiguration message or included in a container of the RRC reconfiguration message.

[0283] In the above embodiment, the RRC reconfiguration message may include a first IE, which includes the first information; or, the bap-Config IE of the RRC reconfiguration message may include a second IE or a first field, which includes the first information.

[0284] In some other embodiments, the IAB-donor-CU1 1501 receives a first RRC message sent by the MT of the IAB node, where the first RRC message includes identification information of the F1-terminated IAB host; and the IAB-donor-CU1 1501 sends the identification information of the IAB node to the F1-terminated IAB host according to the first RRC message.

[0285] In the above embodiment, the first RRC message may be a UEAssistanceInformation message; the UEAssistanceInformation message may include a fourth IE, and the fourth IE includes identification information of the F1 termination IAB host.

[0286] In the above embodiment, the IAB-donor-CU1 1501 may send a first Xn message to the F1 termination IAB host, where the first Xn message includes the UE XnAP identifier generated by the RRC termination IAB host for the IAB node and / or the BAP address of the IAB node.

[0287] In the above embodiment, the IAB-donor-CU1 1501 may also receive a second Xn message sent by the F1 terminating IAB host, where the second Xn message includes confirmation information.

[0288] In some embodiments, the CU of the RRC-terminated IAB host and the CU of the F1-terminated IAB host are different.

[0289] In some embodiments, the IAB-donor-CU1 1501 allocates one or more IP addresses to the IAB node, so that the IAB node initiates TNL establishment and F1 establishment process to the CU of the F1 termination IAB host according to the IP addresses.

[0290] In the above embodiment, the IP address is anchored at the DU of the RRC-terminated IAB host.

[0291] In some embodiments, the IAB-donor-CU1 1501 receives an RRC setup completion message sent by the MT of the IAB node, where the RRC setup completion message includes third information, where the third information indicates the mobile IAB capability of the IAB node; the IAB-donor-CU1 1501 selects an AMF that supports mobile IAB based on the third information.

[0292] In some embodiments, the IAB-donor-CU1 1501 sends a broadcast message indicating cells supporting mobile IAB, so that the IAB node selects a cell according to the broadcast message after receiving the broadcast message.

[0293] FIG16 is another schematic diagram of an integrated device for an IAB node according to an embodiment of the present application. This device may be, for example, an IAB host in an IAB network, or one or more components or assemblies configured within the IAB host. The IAB host corresponds to the F1-terminating IAB host in FIG2 , i.e., IAB-donor 2. Details common to the embodiment of the first aspect will not be repeated.

[0294] As shown in FIG16 , the integrated device 1600 of the IAB node includes a central unit (IAB-donor-CU2) 1601 and a distributed unit (IAB-donor-DU2) 1602 .

[0295] In some embodiments, the IAB-donor-CU2 1601 receives second information sent by the DU of the IAB node, where the second information is related to the first information, and the first information includes identification information of the IAB node and / or identification information of the RRC termination IAB host.

[0296] In the above embodiment, the identification information of the IAB node is the UE XnAP identifier generated by the RRC termination IAB host for the IAB node; the identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.

[0297] In the above embodiment, the first information includes the identification information of the IAB node and the identification information of the RRC termination IAB host, and the second information is the same as the first information; or, the first information includes the identification information of the IAB node; the second information includes the serving cell identifier NCGI of the MT of the IAB node and the identification information of the IAB node.

[0298] In the above embodiment, the second information is explicitly included in the F1AP message or included in a container of the F1AP message.

[0299] In the above embodiment, the F1AP message may be an F1 establishment request message.

[0300] In the above embodiment, the F1AP message may include a third IE, and the third IE includes the second information.

[0301] In some embodiments, the IAB-donor-CU2 1601 receives an F1 setup request message sent by a DU of an IAB node, where the F1 setup request message includes a BAP address of the IAB node; and the IAB-donor-CU2 saves the BAP address for the IAB node.

[0302] In some embodiments, the IAB-donor-CU2 1601 receives a first Xn message sent by the CU of the RRC termination IAB host, where the first Xn message includes a UE XnAP identifier generated by the RRC termination IAB host for the IAB node and / or a BAP address of the IAB node.

[0303] In the above embodiment, the IAB-donor-CU2 1601 may further send a second Xn message to the CU of the RRC termination IAB host, where the second Xn message includes confirmation information.

[0304] FIG17 is another schematic diagram of an integrated device for an IAB node according to an embodiment of the present application. This device may be, for example, an IAB host in an IAB network, or one or more components or assemblies configured within the IAB host. The IAB host corresponds to the RRC-terminating IAB host in FIG2 , i.e., IAB-donor 1. Details common to the embodiment of the second aspect will not be repeated.

[0305] As shown in FIG17 , the integrated device 1700 of the IAB node includes a central unit (IAB-donor-CU1) 1701 and a distributed unit (IAB-donor-DU1) 1702 .

[0306] In this embodiment of the present application, IAB-donor-CU1 1701 determines the base station identifier of the CU of the F1-terminating IAB host; and sends the base station identifier of the CU of the F1-terminating IAB host to the MT of the IAB node, so that the DU of the IAB node establishes F1 with the CU of the F1-terminating IAB host according to the base station identifier.

[0307] In some embodiments, the IAB-donor-CU1 1701 determines the base station identifier of the F1 terminated IAB host, including:

[0308] IAB-donor-CU1 1701 is configured by OAM with the base station identifier of the F1 terminating IAB host; or,

[0309] The IAB-donor-CU1 1701 selects an F1 termination IAB host according to the information obtained based on the ANR function, thereby obtaining the base station identifier of the F1 termination IAB host.

[0310] In the above embodiment, the OAM may be configured with multiple base station identifiers, and the IAB-donor-CU1 1701 selects a base station identifier from the multiple base station identifiers according to a predetermined policy.

[0311] In the above embodiment, the OAM may further configure the priorities of the multiple base station identifiers, and the IAB-donor-CU1 1701 selects a base station identifier with the highest priority among the multiple base station identifiers.

[0312] In some embodiments, the IAB-donor-CU1 1701 sends the base station identifier of the F1 terminated IAB host to the MT of the IAB node through an RRC reconfiguration message.

[0313] In the above embodiment, the DU of the IAB node may establish F1 with the CU of the F1 terminating IAB host according to the base station identifier and the TNL address of the CU of the F1 terminating IAB host discovered through the base station identifier.

[0314] In the above embodiment, the IAB-donor-CU1 1701 may also send the TNL address of the CU of the F1 termination IAB host to the MT of the IAB node through an RRC reconfiguration message; the DU of the IAB node establishes F1 with the CU of the F1 termination IAB host according to the base station identifier and the TNL address.

[0315] In the above embodiment, the RRC reconfiguration message may include a fifth IE, and the fifth IE includes the base station identifier of the F1 termination IAB host; or, the bap-Config IE of the RRC reconfiguration message may include a sixth IE or a second field, and the sixth IE or the second field includes the base station identifier.

[0316] In some embodiments, the IAB-donor-CU1 1701 sends a first Xn message to the F1 termination IAB host, where the first Xn message includes a UE XnAP identifier generated by the RRC termination IAB host for the IAB node and / or a BAP address of the IAB node.

[0317] In the above embodiment, the IAB-donor-CU1 1701 may also receive a second Xn message sent by the F1 terminating IAB host, where the second Xn message includes confirmation information.

[0318] In some embodiments, the IAB-donor-CU1 1701 allocates one or more IP addresses to the IAB node, and the IP addresses are anchored to the DU of the RRC-terminated IAB host.

[0319] In some embodiments, the IAB-donor-CU1 1701 receives an RRC setup complete message sent by the MT of the IAB node, where the RRC setup complete message includes third information, where the third information indicates the mobile IAB capability of the IAB node; and the IAB-donor-CU1 1701 selects an AMF that supports mobile IAB according to the third information.

[0320] In some embodiments, the IAB-donor-DU1 1702 sends a broadcast message, where the broadcast message indicates cells supporting mobile IAB, so that the IAB node performs cell selection according to the broadcast message.

[0321] FIG18 is another schematic diagram of an integrated device for an IAB node according to an embodiment of the present application. This device may be, for example, an IAB host in an IAB network, or one or more components or assemblies configured within the IAB host. The IAB host corresponds to the F1-terminating IAB host in FIG2 , i.e., IAB-donor 2. Details common to the embodiment of the second aspect will not be repeated.

[0322] As shown in FIG18 , the integrated device 1800 of the IAB node includes a central unit (IAB-donor-CU1) 1801 and a distributed unit (IAB-donor-DU1) 1802 .

[0323] In this embodiment of the present application, IAB-donor-CU1 1801 receives a first Xn message sent by the CU of the RRC termination IAB host, where the first Xn message includes a UE XnAP identifier generated by the RRC termination IAB host for the IAB node and / or a BAP address of the IAB node.

[0324] In some embodiments, IAB-donor-CU1 1801 further sends a second Xn message to the CU of the RRC-terminated IAB host, where the second Xn message includes confirmation information.

[0325] Embodiments of the present application provide a configuration device. This device may be, for example, an IAB node in an IAB network, or may be one or more components or assemblies configured within the IAB node. The IAB node corresponds to IAB node 1 in FIG. 2 , and the same details as those in the first through third aspects will not be repeated.

[0326] FIG19 is a schematic diagram of a setting device according to an embodiment of the present application. As shown in FIG19 , the device 1900 includes: a mobile terminal (IAB-MT) 1901 and a distributed unit (IAB-DU) 1902 .

[0327] In this embodiment of the present application, the IAB-MT 1901 sends an RRC setup complete message to the RRC termination IAB host, where the RRC setup complete message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.

[0328] FIG20 is another schematic diagram of a setting device according to an embodiment of the present application. As shown in FIG20 , the device 2000 includes: a mobile terminal (IAB-MT) 2001 and a distributed unit (IAB-DU) 2002 .

[0329] In the embodiment of the present application, the IAB-MT 2001 receives a broadcast message sent by the RRC termination IAB host, where the broadcast message indicates cells supporting mobile IAB; the IAB-MT 2001 performs cell selection according to the broadcast message.

[0330] In some embodiments, the above-mentioned broadcast message is a SIB message, but the present application is not limited to this.

[0331] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The devices 1400-2000 of the embodiments of the present application may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0332] In addition, for the sake of simplicity, Figures 14 to 20 only illustrate the connection relationships or signal paths between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connections can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; this application is not limited to this.

[0333] The apparatus according to the embodiment of the present application solves the problem of IAB node integration, so that the IAB-MT and the collocated IAB-DU can be integrated into different donor-CUs, thereby improving the flexibility of network configuration.

[0334] Embodiments of the fifth aspect

[0335] An embodiment of the present application provides an IAB communication system, including an IAB node and an IAB-donor node. The IAB node is configured to execute the method performed by the IAB node in the embodiment of any one of the first to third aspects, and the IAB-donor node is configured to execute the method performed by IAB-donor 1 or IAB-donor 2 in the embodiment of any one of the first to third aspects. The specific behaviors of the IAB node and the IAB-donor node have been described in detail in the embodiments of the first to third aspects, and their contents are incorporated herein and will not be repeated here.

[0336] An embodiment of the present application further provides an IAB node, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method performed by the IAB node in the embodiment of any one of the first to third aspects.

[0337] Figure 21 is a schematic diagram of an IAB node according to an embodiment of the present application. As shown in Figure 14 , IAB node 2100 may include a processor 2101 and a memory 2102. Memory 2102 stores data and programs and is coupled to processor 2101. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunications or other functions.

[0338] For example, the processor 2101 may be configured to execute a program to implement the method performed by the IAB node in the embodiment of any one of the first aspect to the third aspect.

[0339] As shown in Figure 21 , the IAB node 2100 may further include: a communication module 2103, an input unit 2104, a display 2105, and a power supply 2106. The functions of these components are similar to those in the prior art and are not further described here. It is worth noting that the IAB node 2100 does not necessarily include all of the components shown in Figure 21 , and these components are not essential. Furthermore, the IAB node 2100 may also include components not shown in Figure 21 , for which reference may be made to the prior art.

[0340] An embodiment of the present application also provides an IAB-donor node, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method performed by IAB-donor 1 or IAB-donor 2 in the embodiment of any one of the first to third aspects.

[0341] Figure 22 is a schematic diagram of an IAB-donor node according to an embodiment of the present application. As shown in Figure 22, IAB-donor node 2200 may include a central processing unit (CPU) 2201 and a memory 2202; the memory 2202 is coupled to the CPU 2201. The memory 2202 can store various data and information processing programs, which are executed under the control of the CPU 2201 to receive various information from IAB nodes and send various information to IAB nodes.

[0342] For example, the processor 2201 may be configured to execute a program to implement the method performed by IAB-donor 1 or IAB-donor 2 in the embodiment of any one of the first to third aspects.

[0343] Furthermore, as shown in Figure 22 , IAB-donor node 2200 may further include: a transceiver 2203 and an antenna 2204; the functions of these components are similar to those in the prior art and are not further described here. It is worth noting that IAB-donor node 2200 does not necessarily include all of the components shown in Figure 22 ; furthermore, IAB-donor node 2200 may also include components not shown in Figure 22 , for which reference may be made to the prior art.

[0344] An embodiment of the present application further provides a computer-readable program, wherein when the program is executed in an IAB node, the program causes a computer to execute in the IAB node the method performed by the IAB node in the embodiment of any one of the first to third aspects.

[0345] An embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute, in an IAB node, the method executed by the IAB node in the embodiment of any one of the first to third aspects.

[0346] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in an IAB-donor node, the program causes the computer to execute in the IAB-donor node the method performed by IAB-donor 1 or IAB-donor 2 in the embodiment of any one of the first to third aspects.

[0347] An embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute, in an IAB-donor node, the method performed by IAB-donor 1 or IAB-donor 2 in the embodiment of any one of the first to third aspects.

[0348] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, etc. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0349] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

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

[0351] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0352] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0353] Regarding the above implementation methods disclosed in this embodiment, the following additional notes are also disclosed:

[0354] 1. An IAB node integration method, applied to an IAB node, wherein the IAB node includes an MT (mobile terminal) and a DU (distributed unit), wherein the method comprises:

[0355] The DU of the IAB node is configured by OAM or the MT of the IAB node is configured by RRC to terminate the CU of the IAB host. F1 terminates the base station identifier of the CU of the IAB host;

[0356] The DU of the IAB node establishes F1 with the CU of the F1 termination IAB host according to the base station identifier.

[0357] 2. The method according to Supplement 1, wherein:

[0358] The CU of the RRC-terminated IAB host is different from the CU of the F1-terminated IAB host.

[0359] 3. The method according to Supplementary Note 1, wherein the method further comprises:

[0360] The DU of the IAB node discovers the TNL address of the CU of the F1-terminated IAB host through the base station identifier;

[0361] The DU of the IAB node performs F1 establishment with the CU of the F1 termination IAB host according to the base station identifier and the TNL address.

[0362] 4. The method according to Supplement 1, wherein:

[0363] The DU of the IAB node is also configured by the OAM with the TNL address of the CU of the F1 terminating IAB host;

[0364] The DU of the IAB node performs F1 establishment with the CU of the F1 termination IAB host according to the base station identifier and the TNL address.

[0365] 5. The method according to Supplement 1, wherein:

[0366] The OAM is configured with multiple base station identifiers.

[0367] The DU of the IAB node selects a base station identifier from the multiple base station identifiers according to a predetermined policy and performs F1 establishment.

[0368] 6. The method according to Supplementary Note 5, wherein:

[0369] The OAM further configures the priorities of the multiple base station identifiers,

[0370] The DU of the IAB node selects a base station identifier with the highest priority among the multiple base station identifiers to perform F1 establishment.

[0371] 7. The method according to Supplementary Note 1, wherein the method further comprises:

[0372] The DU of the IAB node uses the IP address allocated to the IAB node by the CU of the RRC termination IAB host to initiate a TNL establishment and F1 establishment process to the CU of the F1 termination IAB host.

[0373] 8. The method according to Supplementary Note 7, wherein:

[0374] The F1 establishment request message includes the BAP address of the IAB node;

[0375] After receiving the F1 establishment request message, the CU of the F1 terminating IAB host saves the BAP address for the IAB node.

[0376] 9. The method according to Supplementary Note 7, wherein:

[0377] The number of IP addresses allocated by the CU of the RRC termination IAB host to the IAB node is one or more, and the IP address is anchored to the DU of the RRC termination IAB host.

[0378] 10. The method according to any one of Notes 1 to 9, wherein:

[0379] The MT of the IAB node receives first information sent by the CU of the RRC termination IAB host, where the first information includes identification information of the IAB node and / or identification information of the RRC termination IAB host;

[0380] The DU of the IAB node sends second information related to the first information to the F1 termination IAB host.

[0381] 11. The method according to Supplementary Note 10, wherein:

[0382] The identification information of the IAB node is the UE XnAP identifier generated by the RRC termination IAB host for the IAB node;

[0383] The identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.

[0384] 12. The method according to Supplement 10, wherein:

[0385] The first information includes identification information of the IAB node and identification information of the RRC termination IAB host, and the second information is the same as the first information; or,

[0386] The first information includes identification information of the IAB node; the second information includes a serving cell identifier NCGI of the MT of the IAB node and identification information of the IAB node.

[0387] 13. The method according to any one of Notes 10 to 12, wherein:

[0388] The first information is explicitly included in the RRC reconfiguration message or included in a container of the RRC reconfiguration message.

[0389] 14. The method according to Supplement 13, wherein:

[0390] The RRC reconfiguration message includes a first IE, where the first IE includes the first information; or,

[0391] The bap-Config IE of the RRC reconfiguration message includes a second IE or a first field, and the second IE or the first field includes the first information.

[0392] 15. The method according to any one of Notes 10 to 12, wherein:

[0393] The second information is explicitly included in the F1AP message or included in a container of the F1AP message.

[0394] 16. The method according to Supplement 15, wherein:

[0395] The F1AP message is an F1 establishment request message.

[0396] 17. The method according to Supplement 15, wherein:

[0397] The F1AP message includes a third IE, and the third IE includes the second information.

[0398] 18. The method according to any one of Notes 1 to 9, wherein:

[0399] The MT of the IAB node sends a first RRC message to the CU of the RRC termination IAB host, where the first RRC message includes identification information of the F1 termination IAB host, so that the RRC termination IAB host sends the identification information of the IAB node to the F1 termination IAB host.

[0400] 19. The method according to Supplement 18, wherein:

[0401] The first RRC message is a UEAssistanceInformation message;

[0402] The UEAssistanceInformation message includes a fourth IE, and the fourth IE includes identification information of the F1 termination IAB host.

[0403] 20. The method according to Supplementary Note 18, wherein the method further comprises:

[0404] The MT of the IAB node initiates the UE assistance information reporting process after the F1 establishment between the DU of the IAB node and the F1 termination IAB host is completed;

[0405] The IAB node has the capability of providing identification information of an F1-terminating IAB host, is configured with capability reporting, and is in an RRC connected state.

[0406] 21. The method according to Supplement 18, wherein:

[0407] The CU of the RRC termination IAB host sends a first Xn message to the F1 termination IAB host, where the first Xn message includes the UE XnAP identifier generated by the RRC termination IAB host for the IAB node and / or the BAP address of the IAB node.

[0408] 22. The method according to Supplementary Note 21, wherein:

[0409] The CU of the RRC termination IAB host receives a second Xn message sent by the F1 termination IAB host, where the second Xn message includes confirmation information.

[0410] 23. The method according to any one of Notes 1 to 22, wherein the method further comprises:

[0411] The MT of the IAB node sends an RRC setup complete message to the RRC termination IAB host, where the RRC setup complete message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.

[0412] 24. The method according to any one of Notes 1 to 22, wherein the method further comprises:

[0413] The MT of the IAB node receives a broadcast message sent by the RRC termination IAB host, where the broadcast message indicates a cell supporting mobile IAB;

[0414] The IAB node performs cell selection according to the broadcast message.

[0415] 25. A method for integrating an IAB node, applied to an RRC-terminated IAB host, wherein the RRC-terminated IAB host includes a CU and a DU, wherein the method comprises:

[0416] The RRC termination IAB host sends first information to the MT of the IAB node, where the first information includes identification information of the IAB node and / or identification information of the RRC termination IAB host, so that the DU of the IAB node sends second information related to the first information to the F1 termination IAB host.

[0417] 26. The method according to Note 25, wherein:

[0418] The identification information of the IAB node is the UE XnAP identifier generated by the RRC termination IAB host for the IAB node;

[0419] The identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.

[0420] 27. The method according to Supplement 25, wherein:

[0421] The first information includes identification information of the IAB node and identification information of the RRC termination IAB host, and the second information is the same as the first information; or,

[0422] The first information includes identification information of the IAB node; the second information includes a serving cell identifier NCGI of the MT of the IAB node and identification information of the IAB node.

[0423] 28. The method according to any one of Notes 25 to 27, wherein:

[0424] The first information is explicitly included in the RRC reconfiguration message or included in a container of the RRC reconfiguration message.

[0425] 29. The method according to Supplementary Note 28, wherein:

[0426] The RRC reconfiguration message includes a first IE, where the first IE includes the first information; or,

[0427] The bap-Config IE of the RRC reconfiguration message includes a second IE or a first field, and the second IE or the first field includes the first information.

[0428] 30. A method for integrating an IAB node, applied to an RRC-terminated IAB host, wherein the RRC-terminated IAB host includes a CU and a DU, wherein the method further comprises:

[0429] The CU of the RRC termination IAB host receives a first RRC message sent by the MT of the IAB node, where the first RRC message includes identification information of the F1 termination IAB host;

[0430] The RRC termination IAB host sends the identification information of the IAB node to the F1 termination IAB host according to the first RRC message.

[0431] 31. The method according to Note 30, wherein:

[0432] The first RRC message is a UEAssistanceInformation message;

[0433] The UEAssistanceInformation message includes a fourth IE, and the fourth IE includes identification information of the F1 termination IAB host.

[0434] 32. The method according to Note 30 or 31, wherein the method further comprises:

[0435] The CU of the RRC termination IAB host sends a first Xn message to the F1 termination IAB host, where the first Xn message includes the UE XnAP identifier generated by the RRC termination IAB host for the IAB node and / or the BAP address of the IAB node.

[0436] 33. The method according to Note 32, wherein:

[0437] The CU of the RRC termination IAB host receives a second Xn message sent by the F1 termination IAB host, where the second Xn message includes confirmation information.

[0438] 34. The method according to any one of Notes 25 to 33, wherein:

[0439] The CU of the RRC-terminated IAB host is different from the CU of the F1-terminated IAB host.

[0440] 35. The method according to any one of Notes 25 to 33, further comprising:

[0441] The CU of the RRC-terminating IAB host allocates one or more IP addresses to the IAB node, so that the IAB node uses the IP addresses to initiate TNL establishment and F1 establishment processes to the CU of the F1-terminating IAB host.

[0442] 36. The method according to Note 35, wherein:

[0443] The IP address is anchored at the DU of the RRC-terminated IAB host.

[0444] 37. The method according to any one of Notes 25 to 36, further comprising:

[0445] The RRC termination IAB host receives an RRC setup completion message sent by the MT of the IAB node, where the RRC setup completion message includes third information, and the third information indicates the mobile IAB capability of the IAB node;

[0446] The RRC termination IAB host selects an AMF that supports mobile IAB according to the third information.

[0447] 38. The method according to any one of Notes 25 to 36, wherein the method further comprises:

[0448] The RRC termination IAB host sends a broadcast message, where the broadcast message indicates cells supporting mobile IAB, so that the IAB node selects a cell according to the broadcast message after receiving the broadcast message.

[0449] 39. An IAB node integration method, applied to an F1 termination IAB host, wherein the F1 termination IAB host includes a CU and a DU, wherein the method comprises:

[0450] The F1 IAB termination host receives second information sent by the DU of the IAB node, where the second information is related to the first information, and the first information includes identification information of the IAB node and / or identification information of the RRC IAB termination host.

[0451] 40. The method according to Supplement 39, wherein:

[0452] The identification information of the IAB node is the UE XnAP identifier generated by the RRC termination IAB host for the IAB node;

[0453] The identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.

[0454] 41. The method according to Supplement 39, wherein:

[0455] The first information includes identification information of the IAB node and identification information of the RRC termination IAB host, and the second information is the same as the first information; or,

[0456] The first information includes identification information of the IAB node; the second information includes a serving cell identifier NCGI of the MT of the IAB node and identification information of the IAB node.

[0457] 42. The method according to Supplement 39, wherein:

[0458] The second information is explicitly included in the F1AP message or included in a container of the F1AP message.

[0459] 43. The method according to Note 42, wherein:

[0460] The F1AP message is an F1 establishment request message.

[0461] 44. The method according to Note 42, wherein:

[0462] The F1AP message includes a third IE, and the third IE includes the second information.

[0463] 45. The method according to Supplementary Note 39, wherein the method further comprises:

[0464] The CU of the F1 terminating IAB host receives the F1 establishment request message sent by the DU of the IAB node, where the F1 establishment request message includes the BAP address of the IAB node;

[0465] The F1 terminating IAB host stores the BAP address for the IAB node.

[0466] 46. ​​A method for integrating an IAB node, applied to an RRC termination IAB host, wherein the RRC termination IAB host includes a CU (central unit) and a DU (distributed unit), wherein the method comprises:

[0467] The CU of the RRC-terminated IAB host determines the base station identifier of the CU of the F1-terminated IAB host for the IAB node;

[0468] The CU of the RRC-terminating IAB host sends the base station identifier of the CU of the F1-terminating IAB host to the MT of the IAB node, so that the DU of the IAB node performs F1 establishment with the CU of the F1-terminating IAB host according to the base station identifier.

[0469] 47. The method according to note 46, wherein the CU of the RRC termination IAB host determines the base station identifier of the F1 termination IAB host for the IAB node, including:

[0470] The CU of the RRC termination IAB host is configured with the base station identifier of the F1 termination IAB host by OAM; or,

[0471] The CU of the RRC IAB termination host selects the F1 IAB termination host according to the information obtained based on the ANR function, thereby obtaining the base station identifier of the F1 IAB termination host.

[0472] 48. The method according to Note 47, wherein:

[0473] The OAM is configured with multiple base station identifiers.

[0474] The CU of the RRC termination IAB host selects a base station identifier from the multiple base station identifiers according to a predetermined policy.

[0475] 49. The method according to Note 48, wherein:

[0476] The OAM further configures the priorities of the multiple base station identifiers,

[0477] The CU of the RRC termination IAB host selects a base station identifier with the highest priority among the multiple base station identifiers.

[0478] 50. The method according to Supplement 46, wherein:

[0479] The CU of the RRC termination IAB host sends the base station identifier of the F1 termination IAB host to the MT of the IAB node through an RRC reconfiguration message.

[0480] 51. The method according to Note 50, wherein:

[0481] The DU of the IAB node establishes F1 with the CU of the F1 terminating IAB host according to the base station identifier and the TNL address of the CU of the F1 terminating IAB host discovered through the base station identifier.

[0482] 52. The method according to Note 50, wherein:

[0483] The CU of the RRC-terminated IAB host also sends the TNL address of the CU of the F1-terminated IAB host to the MT of the IAB node through an RRC reconfiguration message;

[0484] The DU of the IAB node performs F1 establishment with the CU of the F1 termination IAB host according to the base station identifier and the TNL address.

[0485] 53. The method according to any one of Notes 50 to 52, wherein:

[0486] The RRC reconfiguration message includes a fifth IE, and the fifth IE includes the base station identifier of the F1 termination IAB host; or

[0487] The bap-Config IE of the RRC reconfiguration message includes a sixth IE or a second field, and the sixth IE or the second field includes the base station identifier.

[0488] 53a. The method according to any one of Notes 46-53, wherein the method further comprises:

[0489] The CU of the RRC termination IAB host sends first information to the MT of the IAB node, where the first information includes identification information of the IAB node and / or identification information of the RRC termination IAB host; so that the DU of the IAB node sends second information related to the first information to the F1 termination IAB host.

[0490] 53b. The method according to Note 53a, wherein

[0491] The identification information of the IAB node is the UE XnAP identifier generated by the RRC termination IAB host for the IAB node;

[0492] The identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.

[0493] 53c. The method according to note 53a, wherein

[0494] The first information includes identification information of the IAB node and identification information of the RRC termination IAB host, and the second information is the same as the first information; or,

[0495] The first information includes identification information of the IAB node; the second information includes a serving cell identifier NCGI of the MT of the IAB node and identification information of the IAB node.

[0496] 53d. The method according to any one of Notes 53a-53c, wherein:

[0497] The first information is explicitly included in the RRC reconfiguration message or included in a container of the RRC reconfiguration message.

[0498] 53e. The method according to note 53d, wherein:

[0499] The RRC reconfiguration message includes a first IE, where the first IE includes the first information; or,

[0500] The bap-Config IE of the RRC reconfiguration message includes a second IE or a first field, and the second IE or the first field includes the first information.

[0501] 53f. The method according to any one of Notes 53a-53c, wherein:

[0502] The second information is explicitly included in the F1AP message or included in a container of the F1AP message.

[0503] 53g. The method according to note 53f, wherein

[0504] The F1AP message is an F1 establishment request message.

[0505] 53h. The method according to note 53f, wherein

[0506] The F1AP message includes a third IE, and the third IE includes the second information.

[0507] 54. The method according to any one of Notes 46 to 53, wherein the method further comprises:

[0508] The CU of the RRC termination IAB host sends a first Xn message to the F1 termination IAB host, where the first Xn message includes the UE XnAP identifier generated by the RRC termination IAB host for the IAB node and / or the BAP address of the IAB node.

[0509] 55. The method according to Note 54, wherein:

[0510] The CU of the RRC termination IAB host receives a second Xn message sent by the F1 termination IAB host, where the second Xn message includes confirmation information.

[0511] 56. The method according to any one of Notes 46 to 55, wherein the method further comprises:

[0512] The CU of the RRC-terminating IAB host allocates one or more IP addresses to the IAB node, and the IP addresses are anchored to the DU of the RRC-terminating IAB host.

[0513] 57. The method according to any one of Notes 46 to 56, wherein the method further comprises:

[0514] The RRC termination IAB host receives an RRC establishment completion message sent by the MT of the IAB node, where the RRC establishment completion message includes third information, and the third information indicates the mobile IAB capability of the IAB node;

[0515] The RRC termination IAB host selects an AMF that supports mobile IAB according to the third information.

[0516] 58. The method according to any one of Notes 46 to 56, wherein the method further comprises:

[0517] The DU of the RRC-terminated IAB host sends a broadcast message, where the broadcast message indicates cells supporting mobile IAB, so that the IAB node performs cell selection according to the broadcast message.

[0518] 59. An IAB node integration method, applied to an F1 termination IAB host, wherein the F1 termination IAB host includes a CU (central unit) and a DU (distributed unit), wherein the method comprises:

[0519] The F1 IAB termination host receives a first Xn message sent by the CU of the RRC IAB termination host, where the first Xn message includes a UE XnAP identifier generated by the RRC IAB termination host for the IAB node and / or a BAP address of the IAB node.

[0520] 60. The method according to Supplementary Note 59, wherein the method further comprises:

[0521] The F1 terminated IAB host sends a second Xn message to the CU of the RRC terminated IAB host, where the second Xn message includes confirmation information.

[0522] 61. A setting method, applied to an IAB node, wherein the IAB node includes a MT and a DU, wherein the method comprises:

[0523] The MT of the IAB node sends an RRC setup complete message to the RRC termination IAB host, where the RRC setup complete message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.

[0524] 62. A setting method, applied to an IAB node, wherein the IAB node includes a MT and a DU, wherein the method comprises:

[0525] The MT of the IAB node receives a broadcast message sent by the RRC termination IAB host, where the broadcast message indicates a cell supporting mobile IAB;

[0526] The MT of the IAB node performs cell selection according to the broadcast message.

[0527] 63. The method according to Note 62, wherein:

[0528] The broadcast message is a SIB message.

[0529] 64. An IAB node, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 1 to 24 and 61-63.

[0530] 65. An IAB-donor node, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 25 to 60.

[0531] 66. An IAB communication system, comprising an IAB node and an IAB-donor node, wherein the IAB node is configured to execute the method described in any one of Notes 1 to 24 and 61 to 63, and the IAB-donor node is configured to execute the method described in any one of Notes 25 to 60.

Claims

1. An integrated device of an IAB node, applied to an IAB node, the device comprises an IAB-MT (mobile terminal) and an IAB-DU (distributed unit), wherein: The IAB-DU is configured by OAM or the IAB-MT is configured by RRC to terminate the CU of the IAB host. F1 is the base station identifier of the CU that terminates the IAB host; The IAB-DU performs F1 establishment with the CU of the F1 termination IAB host according to the base station identifier.

2. The device according to claim 1, wherein: The CU of the RRC-terminated IAB host is different from the CU of the F1-terminated IAB host.

3. The device according to claim 1, wherein: The IAB-DU is also configured by the OAM with the TNL address of the CU of the F1-terminating IAB host; The IAB-DU performs F1 establishment with the CU of the F1 termination IAB host according to the base station identifier and the TNL address.

4. The device according to claim 1, wherein: The IAB-DU uses the IP address allocated by the CU of the RRC terminating IAB host to the IAB node to initiate the TNL establishment and F1 establishment process to the CU of the F1 terminating IAB host.

5. The device according to claim 4, wherein: In the F1 establishment request message, the BAP address of the IAB node is included; After receiving the F1 establishment request message, the CU of the F1 terminating IAB host saves the BAP address for the IAB node.

6. The device according to claim 4, wherein: The number of IP addresses allocated by the CU of the RRC terminating IAB host to the IAB node is one or more, and the IP address is anchored at the DU of the RRC terminating IAB host.

7. The device according to claim 1, wherein: The IAB-MT receives first information sent by the CU of the RRC termination IAB host, where the first information includes identification information of the IAB node and / or identification information of the RRC termination IAB host; The IAB-DU sends second information related to the first information to the F1 terminating IAB host.

8. The device according to claim 7, wherein: The identification information of the IAB node is the UE ID generated by the RRC termination IAB host for the IAB node. XnAP logo; The identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.

9. The device according to claim 7, wherein: The first information includes identification information of the IAB node and identification information of the RRC termination IAB host, and the second information is the same as the first information; or, The first information includes identification information of the IAB node; the second information includes a serving cell identifier NCGI of the MT of the IAB node and identification information of the IAB node.

10. The device according to claim 7, wherein: The first information is explicitly included in the RRC reconfiguration message or is included in a container of the RRC reconfiguration message.

11. The device according to claim 7, wherein: The second information is explicitly included in the F1AP message or included in a container of the F1AP message.

12. The device according to claim 11, wherein The F1AP message is an F1 establishment request message.

13. The device according to claim 1, wherein: The IAB-MT sends a first RRC message to the CU of the RRC termination IAB host, where the first RRC message includes identification information of the F1 termination IAB host, so that the RRC termination IAB host sends the identification information of the IAB node to the F1 termination IAB host.

14. The device according to claim 1, wherein: The device also includes: The IAB-MT sends an RRC setup complete message to the RRC termination IAB host, where the RRC setup complete message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.

15. The device according to claim 1, wherein: The device also includes: The IAB-MT receives a broadcast message sent by the RRC termination IAB host, where the broadcast message indicates a cell supporting mobile IAB; The IAB-MT performs cell selection according to the broadcast message.

16. An integrated device of an IAB node, applied to an RRC terminating IAB host, the device comprising an IAB-donor CU and an IAB-donor DU, wherein: The IAB-donor CU receives a first RRC message sent by the MT of the IAB node, where the first RRC message includes identification information of the F1 terminating IAB host; The IAB-donor CU sends the identification information of the IAB node to the F1 termination IAB host according to the first RRC message.

17. The device according to claim 16, wherein: The first RRC message is a UEAssistanceInformation message; The UEAssistanceInformation message includes a fourth IE, and the fourth IE includes identification information of the F1 termination IAB host.

18. The device according to claim 16, wherein: The device also includes: The IAB-donor CU sends a first Xn message to the F1 termination IAB host, where the first Xn message includes a UE XnAP identifier generated by the RRC termination IAB host for the IAB node and / or a BAP address of the IAB node.

19. The device according to claim 18, wherein: The IAB-donor CU receives a second Xn message sent by the F1 termination IAB host, where the second Xn message includes confirmation information.

20. A setting device, applied to an IAB node, the device comprising an IAB-MT and an IAB-DU, wherein: The IAB-MT sends an RRC setup complete message to the RRC termination IAB host, where the RRC setup complete message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.

Images