IAB host device and transport address configuration method

CN118975317APending Publication Date: 2024-11-151FINITY INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094508.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-12
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

How to effectively configure IP addresses between the F1 termination point topology domain and the non-F1 termination point topology domain of IAB nodes to support the flexible deployment of multi-hop wireless self-backhaul systems, especially when IAB nodes are migrated or switched, is a problem that lacks corresponding solutions in the existing technology.

Method used

By collaborating between F1 endpoint hosts and non-F1 endpoint hosts, and utilizing existing RRC messages and Xn interface signaling, RRC containers and IAB transport migration management request/response messages are used to implement IP address requests and configurations, including the reuse of IABOtherInformation and RRCReconfiguration messages, ensuring IP address management for IAB nodes across different topologies.

Benefits of technology

The system enables IP address configuration for IAB nodes across different topology domains, ensuring communication continuity during topology domain migration or switching, thus improving system flexibility and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118975317A_ABST
    Figure CN118975317A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides IAB host equipment and a transmission address configuration method. The IAB host device comprises: a first transmission unit that transmits, to a non-F1 termination point host, IP address request information for a non-F1 termination point topological domain of the IAB node; and / or, IP address configuration information of an F1 termination point topological domain allocated for the IAB node is sent to a non-F1 termination point host; and / or a first receiving part for receiving the IP address configuration information of the non-F1 termination point topological domain allocated for the IAB node, which is sent by the non-F1 termination point host.
Need to check novelty before this filing date? Find Prior Art

Description

IAB host device and transmission address configuration method Technical Field

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

[0002] Future seamless cellular network deployment requires highly flexible and ultra-dense new radio (NR) cell deployment. Ultra-dense networks are one of the goals of 5G, and deploying an NR network without wired backhaul is crucial to achieving these ultra-dense 5G networks. Because 5G millimeter waves reduce cell coverage, wireless self-backhaul systems require multiple hops to meet deployment requirements. 5G's high bandwidth, massive multiple-input multiple-output (MIMO), and beamforming make it easier to develop ultra-dense NR cell wireless self-backhaul systems for 5G than for LTE. To develop this multi-hop system with wireless self-backhaul, 3GPP initiated research and standardization of the Integrated Access and Backhaul (IAB) project in Rel-16.

[0003] Figure 1 is a schematic diagram of the IAB system. As shown in Figure 1, in the IAB system, access and backhaul adopt NR's Uu air interface wireless transmission. The relay node supports both access and backhaul functions. The relay node multiplexes the access link and backhaul link in the time domain, frequency domain, or spatial domain. The access link and backhaul link can use the same or different frequency bands.

[0004] In the IAB network architecture, the relay node is referred to as the IAB-node, which supports both access and backhaul functions. The last-hop access node on the network side is called the IAB-donor, which supports gNB functions and access to the IAB-node. All UE data is backhauled to the IAB-donor via one or more hops via the IAB-node.

[0005] The IAB-node's functions are divided into two parts: the gNB-DU (gNB-DU) and the UE (mobile terminal) functions. The IAB-DU implements network-side device functions, connects to downstream child IAB-nodes (child IAB-nodes), provides NR air interface access to the UE and downstream child IAB-nodes, and establishes an F1 connection with the IAB donor-CU (host centralized unit). The IAB-MT implements some terminal device functions and connects to the upstream parent IAB-node or IAB donor-DU. The IAB-MT includes physical layer, layer 2, radio resource control (RRC), and non-access stratum (NAS) layer functions, and is indirectly connected to the IAB donor-CU and the core network (CN).

[0006] In the IAB system, an IAB-node can access the network in either standalone (SA) or non-standalone (EN-DC) mode. Figure 2 shows the IAB architecture in SA mode. Figure 3 shows the IAB architecture in EN-DC mode.

[0007] Figure 4 illustrates an IAB node, its parent IAB node, and its child IAB node. As shown in Figure 4, the IAB-DU of the IAB node connects to the IAB-MT of the child node on the network side, while the IAB-MT of the IAB node connects to the IAB-DU of the parent node on the terminal side.

[0008] Figure 5 shows the F1 user plane (F1-U) protocol stack between the IAB-DU and the IAB donor-CU. Figure 6 shows the F1 control plane (F1-C) protocol stack between the IAB-DU and the IAB donor-CU. As shown in Figures 5 and 6, F1-U and F1-C are built on the transport (IP) layer between the IAB-DU and the IAB donor-CU. In these figures, the two-hop wireless backhaul and one-hop wired backhaul are used.

[0009] On the backhaul link, the transport (IP) layer is carried on the Backhaul Adaptation Protocol (BAP) sublayer. The BAP entity in the IAB node implements the routing function of the IAB system, and the IAB donor-CU provides the routing table. BAP PDUs (Protocol Data Units) are transmitted on the backhaul link's RLC (Radio Link Control) channel. The IAB donor can configure multiple RLC channels on the backhaul link to carry services of different priorities and QoS (Quality of Service). The BAP entity maps BAP PDUs to different backhaul RLC channels.

[0010] It should be noted that the above introduction to the technical background is only for the convenience of providing a clear and complete description of the technical solutions of this application and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art simply because these solutions are explained in the background technology part of this application.

[0011] Summary of the Invention

[0012] The inventors discovered that if all or part of the services of the IAB node need to be migrated from the F1 termination point topology domain or configured to the non-F1 termination point topology domain, all routing IDs of the IAB node will belong to the non-F1-terminating topology domain, or the IAB node simultaneously transmits services whose routing IDs belong to the F1-terminating topology domain and services whose routing IDs belong to the non-F1-terminating topology domain. For the routing IDs of the non-F1-terminating topology domain, the IAB node needs to use the IP address of the non-F1-terminating topology domain, and for the routing IDs of the F1-terminating topology domain, the IAB node needs to use the IP address of the F1-terminating topology domain. The network needs to configure the IAB node with an IP address of the donor-DU anchored in the non-F1-terminating topology domain, or an IP address of the donor-DU anchored in the F1-terminating topology domain. However, there is currently no corresponding solution for how to request the IP address of the non-F1 termination point topology domain, or how to configure the IP addresses of the F1 termination domain and the non-F1 termination domain.

[0013] In order to solve at least one of the above problems, embodiments of the present application provide an IAB host device and a transport address configuration method.

[0014] According to one aspect of an embodiment of the present application, a transport address configuration method is provided, which is applied to an F1 termination point host device of an IAB node. The method includes:

[0015] The F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; and / or,

[0016] The F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node, which is sent by the non-F1 termination point host; and / or,

[0017] The F1 termination point host sends IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host.

[0018] According to another aspect of an embodiment of the present application, a transport address configuration method is provided, which is applied to a non-F1 termination point host device of an IAB node. The method includes:

[0019] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; and / or,

[0020] The non-F1 termination point host sends IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; and / or,

[0021] The non-F1 termination point host receives the IP address configuration information of the F1 termination point topology domain allocated to the IAB node, which is sent by the F1 termination point host.

[0022] According to another aspect of an embodiment of the present application, an IAB host device is provided. The IAB host device is an F1 termination point host device of an IAB node. The device includes:

[0023] A first sending unit, configured to send IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; and / or

[0024] Sending IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host; and / or,

[0025] The first receiving unit receives IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node and sent by the non-F1 termination point host.

[0026] According to another aspect of an embodiment of the present application, an IAB host device is provided. The IAB host device is a non-F1 termination point host device of an IAB node, and the device includes:

[0027] a second receiving unit configured to receive IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; and / or

[0028] receiving IP address configuration information of the F1 termination point topology domain allocated to the IAB node from the F1 termination point host; and / or,

[0029] The second sending unit sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host.

[0030] According to another aspect of an embodiment of the present application, a communication system is provided, the system comprising: the IAB host device described in the aforementioned aspect.

[0031] One of the beneficial effects of the embodiments of the present application is that an F1 termination point host can request a non-F1 termination point host to allocate an IP address of a non-F1 termination point topology domain, or further receive IP address configuration information of a non-F1 termination point topology domain allocated by the non-F1 termination point host to the IAB node, thereby enabling the F1 termination point host to request an IP address of a non-F1 termination point topology domain, or further send an IP address of a non-F1 termination point topology domain to the IAB node, for example, when the non-F1 termination point host is unable to send a message to the IAB node. The F1 termination point host can receive IP address configuration information of a non-F1 termination point topology domain proactively sent by the non-F1 termination point host, so as to send an IP address of a non-F1 termination point topology domain to the IAB node, for example, when the non-F1 termination point host is unable to send a message to the IAB node. Additionally, the F1 termination host can send IP address configuration information for the F1 termination topology domain to a non-F1 termination host, enabling the non-F1 termination host to send the IP address for the F1 termination topology domain to the IAB node, for example, when the F1 termination host is unable to send a message to the IAB node. This allows the IAB node to use the IP address for the non-F1 termination topology domain for routing IDs in the non-F1 termination topology domain, and to use the IP address for the F1 termination topology domain for routing IDs in the F1 termination topology domain.

[0032] With reference to the description and accompanying drawings that follow, specific embodiments of the present application are disclosed in detail, indicating how 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 accompanying notes, the embodiments of the present application include many variations, modifications, and equivalents.

[0033] 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.

[0034] 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

[0035] 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.

[0036] 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 skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0037] FIG1 is a schematic diagram of an IAB system;

[0038] FIG2 is a schematic diagram of the IAB architecture in SA mode;

[0039] FIG3 is a schematic diagram of the IAB architecture of the EN-DC mode;

[0040] FIG4 is a schematic diagram of a parent IAB-node and a child IAB-node;

[0041] FIG5 is a schematic diagram of the F1-U protocol stack of the IAB system;

[0042] FIG6 is a schematic diagram of the F1-C protocol stack of the IAB system;

[0043] FIG7 is a schematic diagram of IAB system routing;

[0044] FIG8 is a schematic diagram of network topology adaptation;

[0045] FIG9 is a schematic diagram of an IAB host device according to an embodiment of the present application;

[0046] FIG10 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0047] Figure 11 is a schematic diagram of a switching scene;

[0048] FIG12 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0049] FIG13 is a schematic diagram of a dual connection scenario;

[0050] FIG14 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0051] FIG15 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0052] FIG16 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0053] FIG17 is a schematic diagram of a second dual connection scenario;

[0054] FIG18 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0055] FIG19 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0056] FIG20 is a schematic diagram of an RLF recovery scenario;

[0057] FIG21 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0058] FIG22 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0059] FIG23 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0060] FIG24 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0061] FIG25 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0062] FIG26 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0063] FIG27 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0064] FIG28 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application;

[0065] FIG29 is a schematic diagram of an IAB host device according to an embodiment of the present application;

[0066] FIG30 is a schematic diagram of an IAB host device according to an embodiment of the present application. DETAILED DESCRIPTION

[0067] 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 drawings, specific embodiments of the present application are disclosed in detail, which show 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 attached notes.

[0068] 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.

[0069] 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.

[0070] 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 New Radio (NR), Long Term Evolution (LTE), Enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0071] 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, 6G, etc., and / or other communication protocols currently known or to be developed in the future.

[0072] 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.

[0073] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), 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.

[0074] 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.

[0075] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0076] 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.

[0077] Signaling radio bearers SRB include SRB0, SRB1, SRB2, and SRB3, among which SRB0, SRB1, and SRB2 are directed to the MN, and SRB3 is directed to the SN. Signaling radio bearers are radio bearers used to transmit RRC and NAS messages. SRB0 transmits RRC messages using the common control channel (CCCH) logical channel. SRB1 transmits RRC messages (which may include piggybacked NAS messages) and NAS messages before SRB2 is established, using the dedicated control channel (DCCH) logical channel. SRB2 transmits NAS messages and RRC messages including log measurement messages, using the DCCH logical channel. SRB2 has a lower priority than SRB1 and can be configured by the network after access stratum (AS) security activation. SRB3 is used for specific RRC messages when the UE is in (NG)EN-DC or NR-DC, using the DCCH logical channel.

[0078] The routing function of the IAB system is implemented by the BAP layer. Each IAB node stores the routing configuration (BH routing configuration) and the RLC channel mapping configuration (BH RLC Channel Mapping Configuration). The BAP entity performs routing based on the routing configuration, RLC channel mapping configuration, and the routing ID in the BAP layer packet header. The Routing ID contains the destination BAP address and the path identifier.

[0079] The routing configuration includes the mapping relationship between the Routing ID and the next-hop node BAP address. The RLC channel mapping configuration includes the mapping relationship between the prior-hop node BAP address, the ingress link RLC channel ID, and the next-hop node BAP address and the egress link RLC channel ID.

[0080] Figure 7 is a schematic diagram of IAB system routing. As shown in Figure 7, for each data packet, the next-hop node BAP address can be found from the routing configuration using the routing ID in the packet header. The previous-hop node BAP address and the ingress link RLC channel ID are both known. Once the next-hop node BAP address is determined, the outgress link RLC channel ID can be found using the RLC channel mapping configuration based on the previous-hop node BAP address, the ingress link RLC channel ID, and the next-hop node BAP address.

[0081] The IAB-donor DU stores the routing configuration (BH routing configuration) and the downlink RLC channel mapping configuration (Downlink Traffic to BH RLC Channel Mapping Configuration). The IAB-donor DU is routed based on the routing configuration, RLC channel mapping configuration, and the Routing ID in the BAP layer packet header. The routing configuration includes the mapping between the Routing ID and the next-hop node address. The downlink RLC channel mapping configuration includes the mapping between the destination IP address, DSCP (Differentiated Services Code Point), and the next-hop node address and the egress link RLC channel ID.

[0082] For each downlink data packet arriving at the IAB-donor DU, the IAB-donor DU uses the Routing ID in the packet header to query the next-hop node address from the routing configuration. Once the next-hop node address is determined, the outbound link RLC channel ID is retrieved from the downlink RLC channel mapping configuration based on the packet's IP address and DSCP.

[0083] The access IAB node stores uplink backhaul information (BH information), including the routing ID used by the service, the uplink backhaul RLC channel ID, and the next-hop node address. Based on the uplink BH information, the access IAB node configures the routing ID in the BAP layer packet header of the uplink service and selects the BH RLC channel and next-hop node for uplink service transmission.

[0084] The above schematically illustrates the routing and BH RLC channel mapping of the IAB system. The following describes the network topology update of the IAB system. Rel-16 NR has standardized the topology adaptation process when an IAB-node moves under the same donor-CU.

[0085] Figure 8 is a schematic diagram of intra-CU topology adaptation. When an IAB-node changes its parent node (from IAB-node 1 to IAB-node 2), the donor-CU configures the IAB-node with path migration-related configurations through an RRC reconfiguration message, enabling the IAB-node to migrate the F1 transmission path.

[0086] Path migration configuration includes updating the default BH RLC channel for uplink F1-C, F1-U, and non-F1 data, updating the default BAP routing ID, and updating the IP address used to route to the Donor-DU. These path migration configurations are applied when the IAB-node connects to a new parent node. The same path migration configuration is applied to the IAB-node's child nodes.

[0087] 3GPP Rel-17 supports network topology updates and backhaul (BH) radio link failure (RLF) recovery when an IAB-node moves between different donor-CUs. The IAB-node can switch or reestablish from the parent node served by the source host (also known as the F1-terminating CU or the first donor-CU) to the parent node served by the target host (also known as the non-F1-terminating CU or the second donor-CU). All services of the IAB-node (and the services of its child nodes) need to be migrated to the topology of the non-F1-terminating CU. Rel-17 also supports the topology redundancy process when the IAB-node establishes dual connections with the non-F1-terminating CU. The transmission path of some services of the IAB-node can be migrated to the non-F1-terminating CU topology.

[0088] After an IAB-node switches from donor-CU 1 (F1-terminating CU) to donor-CU 2 (non-F1-terminating CU) after handover / RLF recovery, or after establishing an RRC connection with donor-CU 2, only the IAB-MT's RRC connection remains with donor-CU 2, while the F1 interface still terminates at donor-CU 1. In this case, the IAB-node is also called a boundary node. The RRC connection and F1 interface of the subnodes it serves still belong to donor-CU 1. Therefore, the routing ID, BH RLC channel, and next-hop BAP address of the subnode services still belong to the donor-CU1 topology domain.

[0089] All routing IDs of a boundary node will belong to the non-F1-terminating topology domain, or the boundary node will transmit services with routing IDs belonging to both the F1-terminating and non-F1-terminating topology domains. For routing IDs in the non-F1-terminating topology domain, the boundary node needs to use an IP address in the non-F1-terminating topology domain, and for routing IDs in the F1-terminating topology domain, the boundary node needs to use an IP address in the F1-terminating topology domain. The network needs to configure the boundary node with an IP address of a donor-DU anchored in the non-F1-terminating topology domain or an IP address of a donor-DU anchored in the F1-terminating topology domain. However, there is currently no solution for requesting an IP address in a non-F1 terminating topology domain or configuring IP addresses in both the F1 terminating and non-F1 terminating domains.

[0090] In the embodiments of this application, unless otherwise specified, an IAB node device includes a migration node. Furthermore, "resources established in the donor-CU's topological domain for servicing the IAB node's services" may also be referred to as "migrating the IAB node's services to the donor-CU's topological domain," etc., although this application is not limited to these terms. The following further describes the embodiments of this application.

[0091] Embodiments of the first aspect

[0092] An embodiment of the present application provides a method for configuring a transport address, which is described from the perspective of an F1 termination point host device of an IAB node.

[0093] FIG10 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application. As shown in FIG10 , the method includes:

[0094] 1001, the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; and / or,

[0095] The F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node from the non-F1 termination point host; and / or,

[0096] The F1 termination point host sends the IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host.

[0097] It is worth noting that FIG10 above is merely a schematic illustration of 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 description, and are not limited to the description of FIG10 above.

[0098] As can be seen from the above embodiments, the F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain, or further receive IP address configuration information of the non-F1 termination domain allocated by the non-F1 termination host to the IAB node, thereby enabling the F1 termination host to request an IP address in the non-F1 termination topology domain, or further send an IP address in the non-F1 termination topology domain to the IAB node, for example, when the non-F1 termination host is unable to send a message to the IAB node. The F1 termination host can receive IP address configuration information of the non-F1 termination topology domain proactively sent by the non-F1 termination host, so as to send an IP address in the non-F1 termination topology domain to the IAB node, for example, when the non-F1 termination host is unable to send a message to the IAB node. Additionally, the F1 termination host can send IP address configuration information for the F1 termination topology domain to a non-F1 termination host, enabling the non-F1 termination host to send the IP address for the F1 termination topology domain to the IAB node, for example, when the F1 termination host is unable to send a message to the IAB node. This allows the IAB node to use the IP address for the non-F1 termination topology domain for routing IDs in the non-F1 termination topology domain, and to use the IP address for the F1 termination topology domain for routing IDs in the F1 termination topology domain.

[0099] In some embodiments, an IAB node includes a migration node (also known as a border node), wherein the F1 connection of the IAB node terminates at an F1 termination point host, and the IAB node maintains an RRC connection with the non-F1 termination point host. For example, the IAB-MT of the IAB node maintains an RRC connection with the non-F1 termination point host. The F1 termination point host device may be a first IAB donor-CU (host centralized unit), and the non-F1 termination point host device may be a second IAB donor-CU (host centralized unit). The F1 termination point host device refers to a donor-CU that terminates the F1 interface of the border IAB node and its child IAB nodes, such as the first IAB donor-CU. A non-F1 termination point host device refers to a CU with host functionality that does not terminate the F1 interface of the border IAB node and its child IAB nodes, such as the second IAB donor-CU.

[0100] In some embodiments, the requested and / or configured IP address refers to the IP address configured for the IAB node (or for the IAB node) anchored to the donor-DU. The IP address configuration information may include an IP address configuration anchored to at least two donor-DUs, or may include at least one IP address configuration anchored to one donor-DU. Each IP address configuration may include an IP address index and a corresponding IP address. The embodiments of the present application are not limited to this.

[0101] In the embodiment of the present application, "IP address anchored to IAB donor-DU" can be understood as "IP address assigned by donor-DU" or "TNL address (TNL address(es) that is (are) routable via the IAB-donor-DU"". The above terms can be interchangeable with each other. The present application is not limited thereto. For example, the IP address of the donor-DU in the non-F1 termination point topology domain configured for the IAB node refers to the transport network layer (TNL) address that is (are) routable via the donor-DU in the non-F1 termination point topology domain configured for the IAB node.

[0102] In some embodiments, the IP address request information and / or IP address configuration information may be carried by an RRC container, or may be carried by an IAB transport migration management request / response or an IAB transport migration modification request, as described below.

[0103] (1) IP address request information and / or IP address configuration information are carried by the RRC container

[0104] In some embodiments, the IP address request information is carried by a first RRC container, for example, the IP address request information is carried by other IAB information messages (information element structure IABOtherInformation) or RRC reconfiguration messages contained in the first RRC container, and the first RRC container includes the IP address configuration information of the IAB node in the F1 termination point topology domain. The IABOtherInformation message is an RRC message used by the IAB node to request an IP address from the network and to report the IP address actually used or allocated to the IAB node by the network. In this embodiment, the F1 termination point host simulates the IAB node to generate the IABOtherInformation message, and includes it in the first RRC container and sends it to the non-F1 termination point host to request the IP address of the non-F1 topology domain on behalf of the IAB node. The RRC reconfiguration message is an RRC message used by the network to configure the IP address to the IAB node. In this embodiment, the F1 termination point host generates the RRC reconfiguration message, and includes it in the first RRC container and sends it to the non-F1 termination point host to request the IP address of the non-F1 topology domain.

[0105] In some embodiments, the IP address configuration information is carried by the second RRC container, for example, the IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) included in the second RRC container.

[0106] Since the existing RRC message (such as IABOtherInformation) is the RRC message used by the IAB node to request an IP address from the host, and the RRC reconfiguration message (RRCReconfiguration) is the RRC message used to configure the IP address for the IAB node, the RRC message (such as IABOtherInformation) can be reused to carry the IP address request information for the border node, and the RRC reconfiguration message (RRCReconfiguration) can be reused to carry the IP address configuration information for the border node, making the request and configuration of the IP address simpler and more flexible.

[0107] In some embodiments, the above-mentioned IP address can be requested and / or configured using existing Xn procedures (which can be carried by Xn interface application protocol (XnAP) signaling), such as handover preparation, dual connection establishment or modification procedures, UE context acquisition procedures, etc. For example, the first RRC container is carried by at least one of the following messages: handover request message; secondary node addition request message; secondary node modification request message; secondary node modification requirement message; UE context acquisition response message. The second RRC container is carried by at least one of the following messages: handover request response message; secondary node addition response message; secondary node modification response message; secondary node modification requirement message. The following is explained in conjunction with different scenarios. In addition, since these Xn procedures are procedures for border nodes, they can be naturally distinguished from IP address requests and configuration information for child nodes, so that the host can use the RRC connection with the border node to send IP address configuration for the border node.

[0108] I. For switching scenes

[0109] In some embodiments, FIG11 is a schematic diagram of a handover scenario. As shown in FIG11 , in the handover scenario, all services of the border node are migrated to the non-F1 termination point topology domain. The F1 termination point host is the source host of the IAB node handover, and the non-F1 termination point host is the target host of the IAB node handover. The IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2. FIG12 is a schematic diagram of a transport address configuration method in this handover scenario. As shown in FIG12 , the method includes:

[0110] 1201, the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;

[0111] 1202. The F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node, which is sent by the non-F1 termination point host.

[0112] In some embodiments, the IP address request information is carried by a first RRC container, and the IP address configuration information is carried by a second RRC container. The first RRC container is carried by a handover request message, and the second RRC container is carried by a handover request response message. Therefore, the F1 termination point host sends a handover request message (HANDOVER REQUEST) to the non-F1 termination point host. For example, the handover request message includes an RRC message HandoverPreparationInformation. The entire RRC message IABOtherInformation generated by the F1 termination point host can be introduced in HandoverPreparationInformation. The IABOtherInformation serves as the first RRC container to carry the IP address request information (IAB-TNLAddressInfo field) of the non-F1 termination point topology domain. The IABOtherInformation can also include the IP address configuration information of the border node in the F1 termination point topology domain. The non-F1 termination point host replies with a handover request response (HANDOVER REQUEST ACKNOWLEDGE) to the F1 termination point host. For example, the handover request response includes an RRC message HandoverCommand, which carries the entire RRC message RRCReconfiguration generated by the non-F1 termination point host. RRCReconfiguration serves as the second RRC container to carry the IP address configuration information (iab-IP-AddressConfigurationList-r16 field) of the non-F1 termination point topology domain.

[0113] The HandoverPreparationInformation can be expressed using the Abstract Syntax Notation (ASN.1) data format as follows:

[0114]

[0115] The IABOtherInformation data format using the Abstract Syntax Notation ASN.1 can be expressed as follows:

[0116]

[0117]

[0118] IABOtherInformation can also carry the number of IP addresses requested for various services or the IP addresses actually used by various services.

[0119] The HandoverCommand data format using the Abstract Syntax Notation ASN.1 can be expressed as follows:

[0120]

[0121] The RRCReconfiguration data format using the Abstract Syntax Notation ASN.1 can be expressed as follows:

[0122]

[0123] In some embodiments, the RRCReconfiguration carries the IP address configuration information IAB-IP-AddressConfigurationList-r16 of the non-F1 termination point topology domain, including an IP address addition and modification list and an IP address release list, each list including at least one IP address configuration IAB-IP-AddressConfiguration-r16, and each IP address configuration may include an IP address index and a corresponding IP address.

[0124] Therefore, a new RRC container IABOtherInformation can be introduced in the handover request message to request the IP address of the non-F1 termination point topology domain, and the IP address configuration information element contained in the RRC container RRCReconfiguration in the handover request response message can be used to carry the IP address of the non-F1 termination point topology domain for the border node.

[0125] The above is an example of IP address request information being carried by IABOtherInformatio included in the first RRC container. In addition, the IP address request information can also be carried by the RRC reconfiguration message included in the first RRC container, which is not limited in this embodiment of the present invention.

[0126] In some embodiments, the method may further include:

[0127] 1203, the F1 termination point host sends the received IP address configuration information to the IAB node; for example, the F1 termination point host forwards the HandoverCommand generated by the non-F1 termination point host, and the HandoverCommand carries the entire RRC message RRCReconfiguration generated by the non-F1 termination point host, and RRCReconfiguration carries the IP address configuration information of the non-F1 termination point topology domain.

[0128] As can be seen from the above embodiment, the F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain, or further receive IP address configuration information in the non-F1 termination topology domain allocated by the non-F1 termination host for the IAB node. This allows the F1 termination host to request an IP address in the non-F1 termination topology domain, or to send an IP address in the non-F1 termination topology domain to the IAB node when the non-F1 termination host is unable to send a message to the IAB node. In this way, the IAB node can use an IP address in the non-F1 termination topology domain for the routing ID in the non-F1 termination topology domain.

[0129] II. For dual connection scenario 1

[0130] In some embodiments, FIG13 is a schematic diagram of a dual connectivity scenario 1. As shown in FIG13 , in dual connectivity scenario 1, the F1 termination point host is the primary node MN of the IAB node, and the non-F1 termination point host is the secondary node SN of the IAB node. After dual connectivity is established, some services of the border node can be migrated to the non-F1 termination point topology domain, while some services remain in the F1 termination point host topology domain. The IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2. The IP address of the non-F1 termination point topology domain can be requested during the dual connectivity establishment process, or the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be requested / configured after the dual connectivity is established. Each of these is explained below.

[0131] FIG14 is a schematic diagram of a method for configuring a transmission address in the dual-connection scenario. As shown in FIG14 , the method includes:

[0132] 1401, the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;

[0133] 1402. The F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node, which is sent by the non-F1 termination point host.

[0134] In some embodiments, during the process of adding a secondary cell group, an IP address of a non-F1 termination point topology domain is requested. The IP address request information is carried by a first RRC container, and the IP address configuration information is carried by a second RRC container. The first RRC container is carried by a secondary node addition request message, and the second RRC container is carried by a secondary node addition response message. During the process of adding a secondary cell group, the F1 termination point host sends a secondary node addition request message (S-node AdditionRequest) to the non-F1 termination point host. For example, the entire RRC message IABOtherInformation generated by the F1 termination point host is introduced into the RRC message CG-ConfigInfo contained therein. The IABOtherInformation serves as the first RRC container to carry the IP address request information (IAB-TNLAddressInfo field) of the non-F1 termination point topology domain. The non-F1 termination point host replies to the F1 termination point host with a secondary node addition response message (S-node Addition Response). The secondary cell group configuration information field scg-CellGroupConfig in the RRC message CG-Config contained therein carries the entire RRC message RRCReconfiguration generated by the non-F1 termination point host. When the SN does not establish SRB3 (in this case the SN cannot directly send an RRC message to the IAB node), RRCReconfiguration serves as the second RRC container to carry the IP address configuration information (iab-IP-AddressConfigurationList-r16 field) of the non-F1 termination point topology domain.

[0135] FIG15 is a schematic diagram of a method for configuring a transmission address in the dual-connection scenario. As shown in FIG15 , the method includes:

[0136] 1501, the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;

[0137] 1502. The F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node, which is sent by the non-F1 termination point host.

[0138] In some embodiments, after the dual connection is established, the IP address of the non-F1 termination point topology domain is requested during the process of modifying the secondary cell group. The IP address request information is carried by the first RRC container, and the IP address configuration information is carried by the second RRC container. The first RRC container is carried by the secondary node modification request message, and the second RRC container is carried by the secondary node modification response message. During the process of modifying the Secondary Cell Group, the F1 termination point host sends a secondary node modification request message (S-node Modification Request) to the non-F1 termination point host. For example, the entire RRC message IABOtherInformation generated by the F1 termination point host is introduced into the RRC message CG-ConfigInfo contained therein. The IABOtherInformation serves as the first RRC container to carry the IP address request information (IAB-TNLAddressInfo field) of the non-F1 termination point topology domain. The non-F1 termination point host replies with a secondary node modification response message (S-node Modification Response) to the F1 termination point host. The secondary cell group configuration information (scg-CellGroupConfig field) contained in the RRC message CG-Config carries the entire RRC message RRCReconfiguration generated by the non-F1 termination point host. If the SN does not establish SRB3, RRCReconfiguration serves as the second RRC container to carry the IP address configuration information (iab-IP-AddressConfigurationList-r16 field) of the non-F1 termination point topology domain.

[0139] The CG-ConfigInfo uses the abstract syntax notation ASN.1 data format and can be expressed as follows:

[0140]

[0141] The CG-Config uses the Abstract Syntax Notation ASN.1 data format and can be expressed as follows:

[0142]

[0143] The representation of the RRCReconfiguration data format using the Abstract Syntax Notation ASN.1 is as described above and will not be repeated here.

[0144] Therefore, a new RRC container IABOtherInformation can be introduced in the auxiliary node add / modify request message to request the IP address of the non-F1 termination point topology domain, and the IP address configuration information element contained in the RRC container RRCReonfiguration in the auxiliary node add / modify response message can be used to carry the IP address of the non-F1 termination point topology domain configured for the boundary node.

[0145] The above is an example of IP address request information being carried by IABOtherInformatio included in the first RRC container. In addition, the IP address request information can also be carried by the RRC reconfiguration message included in the first RRC container, which is not limited in this embodiment of the present invention.

[0146] In some embodiments, when the SN does not establish SRB3, the method may further include:

[0147] 1403 / 1503, the F1 termination point host sends the received IP address configuration information to the IAB node; for example, the F1 termination point host forwards the RRCReconfiguration in the CG-Config generated by the non-F1 termination point host, and the RRCReconfiguration carries the IP address configuration information of the non-F1 termination point topology domain.

[0148] In 1503, optionally, when the SN establishes SRB3, the non-F1 termination point host may also send the IP address configuration information to the IAB node, but the embodiment of the present application is not limited thereto.

[0149] As can be seen from the above embodiment, the F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain, or further receive IP address configuration information in the non-F1 termination topology domain allocated by the non-F1 termination host for the IAB node. This allows the F1 termination host to request an IP address in the non-F1 termination topology domain, or to send an IP address in the non-F1 termination topology domain to the IAB node when the non-F1 termination host is unable to send a message to the IAB node. In this way, the IAB node can use an IP address in the non-F1 termination topology domain for the routing ID in the non-F1 termination topology domain.

[0150] FIG16 is a schematic diagram of another method for configuring a transmission address in the dual-connection scenario. As shown in FIG16 , the method includes:

[0151] 1601. The F1 termination point host receives IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node from the non-F1 termination point host. The second RRC container is carried by the secondary node modification request message.

[0152] In some embodiments, the difference from FIG15 is that, after the dual connection is established, when the SN does not establish SRB3, the F1 termination point host does not need to actively request the IP address of the non-F1 termination point topology domain. The non-F1 termination point host can actively initiate IP address reconfiguration for the non-F1 termination point topology domain. The IP address configuration information is carried by the second RRC container, and the second RRC container is carried by the auxiliary node modification request message.

[0153] For example, in the process of modifying the secondary cell group, the non-F1 termination point host sends a secondary node modification requirement message (S-node Modification Required) to the F1 termination point host. For example, the secondary cell group configuration information (scg-CellGroupConfig field) in the RRC message CG-Config contained therein carries the entire RRC message RRCReconfiguration generated by the non-F1 termination point host. RRCReconfiguration serves as the second RRC container to carry the IP address configuration information of the non-F1 termination point topology domain, also known as IP address reconfiguration information.

[0154] Therefore, the IP address configuration information element included in the RRC container RRCReconfiguration in the secondary node modification request message may carry the IP address of the non-F1 termination point topology domain reconfigured for the border node.

[0155] In some embodiments, when the SN does not establish SRB3, the method may further include:

[0156] 1602. The F1 termination point host forwards the received IP address configuration information to the IAB node; for example, the F1 termination point host forwards the RRCReconfiguration in the CG-Config generated by the non-F1 termination point host, and the RRCReconfiguration carries the IP address configuration information of the non-F1 termination point topology domain.

[0157] As can be seen from the above embodiment, the F1 termination host can receive IP address configuration information for the non-F1 termination topology domain proactively sent by the non-F1 termination host. This allows the IAB node to receive the IP address for the non-F1 termination topology domain when the non-F1 termination host is unable to send a message to the IAB node. This allows the IAB node to use the IP address for the non-F1 termination topology domain for the routing ID.

[0158] III. Dual connection scenario 2

[0159] In some embodiments, FIG17 is a schematic diagram of dual connectivity scenario 2. As shown in FIG17 , in dual connectivity scenario 2, the F1 termination point host is the primary node SN CU of the IAB node, and the non-F1 termination point host is the secondary node MN CU of the IAB node. After dual connectivity is established, some services of the border node can be migrated to the non-F1 termination point topology domain, while some services remain in the F1 termination point host topology domain. The IP address of the non-F1 termination point topology domain is the IP address anchored to donor-DU1, and the IP address of the F1 termination point topology domain is the IP address anchored to donor-DU2. Because the F1 connection is established after dual connectivity is established, unlike dual connectivity scenario 1, the IP address of the non-F1 termination point topology domain cannot be requested during the dual connectivity establishment process. The IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can only be requested / configured after the dual connectivity is established. These are explained below.

[0160] FIG18 is a schematic diagram of a method for configuring a transmission address in the second dual-connection scenario. As shown in FIG18 , the method includes:

[0161] 1801, the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;

[0162] In some embodiments, after the dual connection is established, the IP address of the non-F1 termination point topology domain is requested during the process of modifying the secondary cell group. The IP address request information is carried by the first RRC container, and the first RRC container is carried by the secondary node modification request message. The F1 termination point host sends a secondary node modification request message to the non-F1 termination point host, for example, the IP address request information (IAB-TNLAddressInfo field) is introduced into the RRC message CG-Config contained therein to carry the entire RRC message IABOtherInformation generated by the F1 termination point host, and the IABOtherInformation serves as the first RRC container to carry the IP address request information of the non-F1 termination point topology domain. Since the IP address configured by the non-F1 termination point host can be directly sent by the non-F1 termination point host to the border node through SRB1, the non-F1 termination point host does not need to reply to the F1 termination point host with the IP address configuration information. In other words, the F1 termination point host will not receive the IP address configuration information sent by the non-F1 termination point host.

[0163] The CG-Config uses the Abstract Syntax Notation ASN.1 data format and can be expressed as follows:

[0164]

[0165] Therefore, a new RRC container IABOtherInformation may be introduced into the auxiliary node modification request message to request the IP address of the non-F1 termination point topology domain.

[0166] The above is an example of IP address request information being carried by IABOtherInformatio included in the first RRC container. In addition, the IP address request information can also be carried by the RRC reconfiguration message included in the first RRC container, which is not limited in this embodiment of the present invention.

[0167] In some embodiments, the method may further include:

[0168] 1802. The non-F1 termination point host sends IP address configuration information to the IAB node; for example, the non-F1 termination point host generates an RRCReconfiguration message, and the RRCReconfiguration message carries the IP address configuration information of the non-F1 termination point topology domain.

[0169] As can be seen from the above embodiment, an F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain. This allows the F1 termination host to request the IP address in the non-F1 termination topology domain and the non-F1 termination host to send the IP address in the non-F1 termination topology domain to the IAB node. In this way, the IAB node can use the IP address in the non-F1 termination topology domain for the routing ID in the non-F1 termination topology domain.

[0170] FIG19 is a schematic diagram of another method for configuring a transmission address in the dual connection scenario 2. As shown in FIG19 , the method includes:

[0171] 1901. The F1 termination point host sends IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host. The second RRC container is carried by the secondary node modification request message.

[0172] In some embodiments, after the dual connection is established, if the SN does not establish SRB3, the F1 termination point host can actively initiate IP address reconfiguration for the F1 termination point topology domain. The IP address configuration information is carried by the second RRC container, and the second RRC container is carried by the auxiliary node modification requirement message.

[0173] For example, in the process of modifying the secondary cell group, the F1 termination point host sends a secondary node modification requirement message (S-node Modification Required) to the non-F1 termination point host. For example, the secondary cell configuration information (scg-CellGroupConfig field) in the RRC message CG-Config contained therein carries the entire RRC message RRCReconfiguration generated by the F1 termination point host. RRCReconfiguration serves as the second RRC container to carry the IP address configuration information of the F1 termination point topology domain, also known as IP address reconfiguration information.

[0174] The CG-Config uses the Abstract Syntax Notation ASN.1 data format and can be expressed as follows:

[0175]

[0176] Therefore, the IP address of the F1 termination point topology domain reconfigured for the border node can be indicated by the existing IP address configuration information element in the secondary node modification request message.

[0177] In some embodiments, when the SN does not establish SRB3, the method may further include:

[0178] 1902. The non-F1 termination point host forwards the received IP address configuration information of the F1 termination point topology domain to the IAB node; for example, the non-F1 termination point host forwards the RRCReconfiguration in the CG-Config generated by the F1 termination point host, and the RRCReconfiguration carries the IP address configuration information of the F1 termination point topology domain.

[0179] As can be seen from the above embodiment, the F1 termination host can send the IP address configuration information of the F1 termination topology domain to non-F1 termination hosts. This allows the non-F1 termination host to send the IP address of the F1 termination topology domain to the IAB node when the F1 termination host is unable to send a message to the IAB node. In this way, the IAB node can use the IP address of the F1 termination topology domain for the routing ID of the F1 termination topology domain.

[0180] IV. For RLF recovery scenarios

[0181] In some embodiments, FIG20 is a schematic diagram of an RLF recovery scenario. As shown in FIG20 , in the RLF recovery scenario, the F1 termination point host is the host of the IAB node after RLF recovery (old host CU), the non-F1 termination point host is the host of the IAB node before RLF recovery (new host CU), and the IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2. FIG21 is a schematic diagram of a transport address configuration method in this switching scenario. As shown in FIG21 , the method includes:

[0182] 2101, the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;

[0183] In some embodiments, during a UE context acquisition process, an IP address of a non-F1 termination point topology domain is requested. The IP address request information is carried by a first RRC container, and the first RRC container is carried by a UE context acquisition response message. Therefore, the non-F1 termination point host sends a UE context acquisition request message (RETRIEVE UE CONTEXT REQUEST) to the F1 termination point host, and the F1 termination point host replies with a UE context acquisition response message (RETRIEVE UE CONTEXT RESPONSE) to the non-F1 termination point host. For example, the UE context acquisition response message includes an RRC message HandoverPreparationInformation. The entire RRC message IABOtherInformation generated by the F1 termination point host can be included in the HandoverPreparationInformation. The IABOtherInformation serves as the first RRC container to carry the IP address request information (IAB-TNLAddressInfo field) of the non-F1 termination point topology domain. The IABOtherInformation can also include IP address configuration information of the border node in the F1 termination point topology domain. Since the IP address configuration information can only be sent by the non-F1 termination host after the border node is re-established to the non-F1 termination host, the non-F1 termination host does not need to reply to the F1 termination host with the IP address configuration information. In other words, the F1 termination host will not receive the IP address configuration information sent by the non-F1 termination host.

[0184] Therefore, a new RRC container IABOtherInformation may be introduced into the UE context acquisition response message to request the IP address of the non-F1 termination point topology domain.

[0185] The above is an example of IP address request information being carried by IABOtherInformatio included in the first RRC container. In addition, the IP address request information can also be carried by the RRC reconfiguration message included in the first RRC container, which is not limited in this embodiment of the present invention.

[0186] In some embodiments, the method may further include:

[0187] 2102. The non-F1 termination point host sends IP address configuration information to the IAB node; for example, the non-F1 termination point host generates an RRCReconfiguration message, and the RRCReconfiguration message carries the IP address configuration information of the non-F1 termination point topology domain.

[0188] As can be seen from the above embodiment, an F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain. This allows the F1 termination host to request the IP address in the non-F1 termination topology domain and the non-F1 termination host to send the IP address in the non-F1 termination topology domain to the IAB node. In this way, the IAB node can use the IP address in the non-F1 termination topology domain for the routing ID in the non-F1 termination topology domain.

[0189] (2) IP address request information and / or IP address configuration information is carried by the IAB in a migration management request / response or a migration modification request.

[0190] In some embodiments, the IP address request information is carried by an IAB transmission migration management request message, and the IP address request information also includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate the IP address request information for the border node; the IP address configuration information is carried by an IAB transmission migration management response message or an IAB transmission migration modification request message, and the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate the IP address configuration information configured for the border node.

[0191] Since the IAB transmission of migration management requests / responses or the IAB transmission of migration modification requests is dedicated to the IAB node and does not involve AS layer configuration, the transmission of migration management requests / responses or the IAB transmission of migration modification requests and the configuration of IP addresses in non-F1 termination point topology domains can make the request and configuration of IP addresses simpler and more flexible.

[0192] I. For switching scenes

[0193] In some embodiments, as shown in FIG11 , in a handover scenario, all services of the border node are migrated to a non-F1 termination point topology domain. The F1 termination point host is the source host of the IAB node handover, and the non-F1 termination point host is the target host of the IAB node handover. The IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2. FIG22 is a schematic diagram of a transport address configuration method in this handover scenario. As shown in FIG22 , the method includes:

[0194] 2201, the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;

[0195] In some embodiments, the IP address request information is carried by an IAB transport migration management request message (IAB TRANSPORT MIGRATION MANAGEMENT REQUEST). Therefore, after handover preparation, the F1 termination host sends an IAB transport migration management request message to the non-F1 termination host. For example, the IAB transport migration management request message may carry the IP address request information (IAB TNL ADDRESS REQUEST) for the non-F1 termination topology domain. The IP address request information also includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address request information is for the non-F1 termination topology domain of the border node.

[0196] The IAB TNL ADDRESS REQUEST data format using the Abstract Syntax Notation ASN.1 can be expressed as follows:

[0197]

[0198] The IAB TNL ADDRESS REQUEST includes the IAB TNL Addresses Requested field, which is the request information for the IPv4 or IPv6 address, and the Boundary Node field, which is the boundary node identifier.

[0199] The data format of IAB TNL Addresses Requested can be expressed as:

[0200]

[0201] The IAB TNL Addresses Requested field contains requests for the number of IP addresses for various services.

[0202] Since the RRC message can only be sent to the border node by the target host after the handover, the non-F1 termination point host does not need to reply to the F1 termination point host with the IP address configuration information of the non-F1 termination point topology domain.

[0203] Therefore, a new information element IAB TNL ADDRESS REQUEST may be introduced into the IAB transport migration management request message to request the IP address of the non-F1 termination point topology domain of the border node.

[0204] In some embodiments, the method may further include:

[0205] At 2202, the non-F1 termination point host sends IP address configuration information to the IAB node. For example, the non-F1 termination point host generates an entire RRC message, RRCReconfiguration, which carries the IP address configuration information for the non-F1 termination point topology domain and sends it to the border node. The RRCReconfiguration message uses the Abstract Syntax Notation (ASN.1) data format as previously described and will not be repeated here.

[0206] In some embodiments, the RRCReconfiguration carries the IP address configuration information IAB-IP-AddressConfigurationList-r16 of the non-F1 termination point topology domain, including at least one IP address configuration IAB-IP-AddressConfiguration-r16. Each IP address configuration may include an IP address index and a corresponding IP address.

[0207] As can be seen from the above embodiment, an F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain. This allows the F1 termination host to request the IP address in the non-F1 termination topology domain and the non-F1 termination host to send the IP address in the non-F1 termination topology domain to the IAB node. In this way, the IAB node can use the IP address in the non-F1 termination topology domain for the routing ID in the non-F1 termination topology domain.

[0208] II. For dual connection scenario 1

[0209] In some embodiments, as shown in FIG13 , in dual-connection scenario 1, the F1 termination point host is the primary node MN of the IAB node, and the non-F1 termination point host is the secondary node SN of the IAB node. After dual connectivity is established, part of the services of the border node can be migrated to the non-F1 termination point topology domain, and part of the services remain in the F1 termination point host topology domain. The IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2.

[0210] FIG23 is a schematic diagram of a method for configuring a transmission address in the dual-connection scenario. As shown in FIG23 , the method includes:

[0211] 2301, the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;

[0212] 2302. The F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node, which is sent by the non-F1 termination point host.

[0213] In some embodiments, after the process of adding a secondary cell group, an IP address of a non-F1 termination point topology domain is requested. The IP address request information is carried by an IAB Transmission Migration Management Request message, and the IP address configuration information is carried by an IAB Transmission Migration Management Response message. For example, an IAB Transmission Migration Management Request message includes an IAB TNL ADDRESS REQUEST message requesting an IP address of a non-F1 termination point topology domain. The IP address request information also includes a border node identifier. The border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address request information is an IP address request information of a non-F1 termination point topology domain for a border node. If the SN does not establish SRB3, the non-F1 termination point host replies to the F1 termination point host with an IAB Transmission Migration Management Response message, for example, carrying IP address configuration information of a non-F1 termination point topology domain (information element structure IAB TNL Address Response). The IP address configuration information may also include a border node identifier. The border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address configuration information is IP address configuration information of a non-F1 termination point topology domain for a border node.

[0214] The IAB TNL Address Response uses the Abstract Syntax Notation (ASN.1) data format and can be expressed as follows:

[0215]

[0216] The IP address configuration IAB Allocated TNL Address List field and the boundary node identifier Boundary Node field of at least one non-F1 termination point topology domain are included. Each IP address configuration includes a specific IP address IAB TNL Address and a corresponding donor-DU address Associated Donor DU Address.

[0217] Therefore, a new information element IP address request information IAB TNL ADDRESS REQUEST can be introduced in the transport migration management request message to request the IP address of the non-F1 termination point topology domain, and the information element IAB TNL Address Response in the IAB transport migration management response message can be used to indicate the IP address of the non-F1 termination point topology domain configured for the border node (not the child node).

[0218] In some embodiments, when the SN does not establish SRB3, the method may further include:

[0219] 2303. The F1 termination point host sends the received IP address configuration information to the IAB node. For example, the non-F1 termination point host generates an entire RRC message, RRCReconfiguration, which carries the IP address configuration information for the non-F1 termination point topology domain and sends it to the border node. The representation of RRCReconfiguration in the Abstract Syntax Notation (ASN.1) data format is as previously described and will not be repeated here.

[0220] In 2303, optionally, when the SN establishes SRB3, the non-F1 termination host can also send the IP address configuration information to the IAB node, but the embodiments of the present application are not limited to this. As can be seen from the above embodiments, the F1 termination host needs to request an IP address from the non-F1 termination host. The non-F1 termination host configures and replies to the F1 termination host with the IP address of the non-F1 termination topology domain in response to the request. The F1 termination host then forwards the IP address to the border node. In this way, for the routing ID of the non-F1 termination topology domain, the IAB node can use the IP address of the non-F1 termination topology domain.

[0221] FIG24 is a schematic diagram of a method for configuring a transmission address in the dual-connection scenario. As shown in FIG24 , the method includes:

[0222] 2401. The F1 termination point host receives IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node, which is sent by the non-F1 termination point host.

[0223] In some embodiments, the difference from FIG. 23 is that, when the SN does not establish SRB3, the F1 termination point host does not need to actively request the IP address of the non-F1 termination point topology domain. The non-F1 termination point host can actively initiate IP address reconfiguration for the non-F1 termination point topology domain, and the IP address configuration information is carried by the IAB transport modification request message (IAB TRANSPORT MODIFIATION REQUEST).

[0224] For example, after the secondary node addition process, if the SN has not established SRB3, the non-F1 termination point host sends an IAB transport migration modification request message to the F1 termination point host, which, for example, carries the IP address configuration information of the non-F1 termination point topology domain (the information element structure IAB TNL Address Response, the specific data format is as described above and will not be repeated here), also known as IP address reconfiguration information. The IP address configuration information also includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address configuration information is the IP address reconfiguration information of the non-F1 termination point topology domain for the border node. Therefore, the IP address of the non-F1 termination point topology domain reconfigured for the border node (rather than the child node) can be indicated by the information element IAB TNL Address Response in the IAB transport migration modification request message.

[0225] In some embodiments, when the SN does not establish SRB3, the method may further include:

[0226] 2402. The F1 termination point host forwards the received IP address configuration information to the IAB node; for example, the F1 termination point host forwards the RRCReconfiguration generated by the non-F1 termination point host, and the RRCReconfiguration carries the IP address configuration information of the non-F1 termination point topology domain.

[0227] As can be seen from the above embodiment, the F1 termination host can receive IP address configuration information for the non-F1 termination topology domain proactively sent by the non-F1 termination host. This allows the IAB node to receive the IP address for the non-F1 termination topology domain when the non-F1 termination host is unable to send a message to the IAB node. This allows the IAB node to use the IP address for the non-F1 termination topology domain for the routing ID.

[0228] III. Dual connection scenario 2

[0229] In some embodiments, as shown in FIG17 , in dual connectivity scenario 2, the F1 termination point host is the primary node SN CU of the IAB node, and the non-F1 termination point host is the secondary node MN CU of the IAB node. After dual connectivity is established, some services at the border node can be migrated to the non-F1 termination point topology domain, while some services remain in the F1 termination point host topology domain. The IP address of the non-F1 termination point topology domain is the IP address anchored to donor-DU1, and the IP address of the F1 termination point topology domain is the IP address anchored to donor-DU2. After dual connectivity is established, the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be requested / configured, as described below.

[0230] FIG25 is a schematic diagram of a method for configuring a transmission address in the dual connectivity scenario 2. As shown in FIG25 , the method includes:

[0231] 2501, the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;

[0232] In some embodiments, after dual connectivity is established, an IP address of a non-F1 termination point topology domain is requested. This IP address request information is carried in an IAB transport migration management request message (IAB TRANSPORT MIGRATION MANAGEMENT REQUEST). The F1 termination point host sends an IAB transport migration management request message to the non-F1 termination point host, for example, including an IAB TNL ADDRESS REQUEST message requesting an IP address of a non-F1 termination point topology domain (the specific data format is as described above and will not be repeated here). The IP address request message also includes a border node identifier. The border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address request information is an IP address request information of a non-F1 termination point topology domain for a border node. Since the IP address configured by the non-F1 termination point host can be directly sent by the non-F1 termination point host to the border node via SRB1, the non-F1 termination point host does not need to reply to the F1 termination point host with the IP address configuration information. In other words, the F1 termination point host will not receive the IP address configuration information sent by the non-F1 termination point host.

[0233] Therefore, a new information element IAB TNL ADDRESS REQUEST can be introduced into the IAB transport migration management request message to request the IP address of the non-F1 termination point topology domain.

[0234] In some embodiments, the method may further include:

[0235] 2502. The non-F1 termination point host sends IP address configuration information to the IAB node; for example, the non-F1 termination point host generates an RRCReconfiguration, and the RRCReconfiguration carries the IP address configuration information IAB TNL ADDRESS of the non-F1 termination point topology domain. The IP address configuration information also includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address configuration information is the IP address configuration information of the non-F1 termination point topology domain for the border node.

[0236] As can be seen from the above embodiment, an F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain. This allows the F1 termination host to request the IP address in the non-F1 termination topology domain and the non-F1 termination host to send the IP address in the non-F1 termination topology domain to the IAB node. In this way, the IAB node can use the IP address in the non-F1 termination topology domain for the routing ID in the non-F1 termination topology domain.

[0237] FIG26 is a schematic diagram of another method for configuring a transmission address in the dual-connection scenario 2. As shown in FIG26 , the method includes:

[0238] 2601. The F1 termination point host sends the IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host.

[0239] In some embodiments, after the dual connection is established, if the SN does not establish SRB3, the F1 termination point host does not need to request the IP address of the non-F1 termination point topology domain. The F1 termination point host can actively initiate IP address reconfiguration for the F1 termination point topology domain. The IP address configuration information is carried by the IAB transmission migration management request message, and the IP address configuration information also includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address configuration information is the IP address configuration information for the non-F1 termination point topology domain of the border node.

[0240] For example, an F1 termination host sends an IAB transport migration management request message to a non-F1 termination host. For example, the message carries IP address configuration information for the F1 termination topology domain (information cell structure: IAB TNL Address Response). The IP address configuration information also includes a border node identifier. The border node identifier indicates that the IAB node is a border node, that is, indicates that the IP address configuration information is IP address configuration information for the non-F1 termination topology domain of the border node, also known as IP address reconfiguration information. The abstract syntax example used by the IAB TNL Address Response is described above and will not be repeated here.

[0241] Therefore, the IP address of the F1 termination point topology domain reconfigured for the border node (instead of the child node) can be indicated by introducing a new information element IAB TNL Address Response into the IAB transport migration management request message.

[0242] In some embodiments, when the SN does not establish SRB3, the method may further include:

[0243] 2602. The non-F1 termination point host forwards the received IP address configuration information of the F1 termination point topology domain to the IAB node; for example, the non-F1 termination point host generates an RRCReconfiguration, and the RRCReconfiguration carries the IP address configuration information of the F1 termination point topology domain.

[0244] As can be seen from the above embodiment, the F1 termination host can send the IP address configuration information of the F1 termination topology domain to non-F1 termination hosts. This allows the non-F1 termination host to send the IP address of the F1 termination topology domain to the IAB node when the F1 termination host is unable to send a message to the IAB node. In this way, the IAB node can use the IP address of the F1 termination topology domain for the routing ID of the F1 termination topology domain.

[0245] IV. For RLF recovery scenarios

[0246] In some embodiments, as shown in FIG20 , in an RLF recovery scenario, the F1 termination point host is the host of the IAB node after RLF recovery (the old host CU), the non-F1 termination point host is the host of the IAB node before RLF recovery (the new host CU), and the IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2. FIG27 is a schematic diagram of a transport address configuration method in this switching scenario. As shown in FIG27 , the method includes:

[0247] 2701, the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;

[0248] In some embodiments, after the UE context acquisition response message is sent, an IP address of a non-F1 termination point topology domain is requested, and the IP address request information is carried by an IAB transport migration management request message. Therefore, the F1 termination point host sends an IAB transport migration management request message to the non-F1 termination point host, for example, introducing the IP address request information IAB TNL ADDRESS REQUEST of the non-F1 termination point topology domain. The IP address request information also includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address request information is an IP address request information of the non-F1 termination point topology domain for the border node. Since the IP address configuration information can only be sent by the non-F1 termination point host after the border node is re-established to the non-F1 termination point host, the non-F1 termination point host does not need to reply to the F1 termination point host with the IP address configuration information of the non-F1 termination point topology domain. In other words, the F1 termination point host will not receive the IP address configuration information sent by the non-F1 termination point host.

[0249] Therefore, a new information element IAB TNL ADDRESS REQUEST can be introduced into the IAB transport migration management request message to request the IP address of the non-F1 termination point topology domain.

[0250] In some embodiments, the method may further include:

[0251] 2702, the non-F1 termination point host sends IP address configuration information to the IAB node; for example, the non-F1 termination point host generates RRCReconfiguration, and the RRCReconfiguration carries the IP address configuration information of the non-F1 termination point topology domain.

[0252] As can be seen from the above embodiment, an F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain. This allows the F1 termination host to request the IP address in the non-F1 termination topology domain and the non-F1 termination host to send the IP address in the non-F1 termination topology domain to the IAB node. In this way, the IAB node can use the IP address in the non-F1 termination topology domain for the routing ID in the non-F1 termination topology domain.

[0253] The above signaling process is only a schematic illustration of the embodiment of the present application, but the present application is not limited thereto. For more specific information about the signaling, please refer to the relevant art. In addition, for example, the execution order between the various operations can be appropriately adjusted, and other operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the descriptions of the above Figures 12, 14-16, 18-19, and 21.

[0254] 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 individually, or one or more of the above embodiments may be combined.

[0255] As can be seen from the above embodiments, the F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain, or further receive IP address configuration information of the non-F1 termination domain allocated by the non-F1 termination host to the IAB node, thereby enabling the F1 termination host to request an IP address in the non-F1 termination topology domain, or further send an IP address in the non-F1 termination topology domain to the IAB node, for example, when the non-F1 termination host is unable to send a message to the IAB node. The F1 termination host can receive IP address configuration information of the non-F1 termination topology domain proactively sent by the non-F1 termination host, so as to send an IP address in the non-F1 termination topology domain to the IAB node, for example, when the non-F1 termination host is unable to send a message to the IAB node. Additionally, the F1 termination host can send IP address configuration information for the F1 termination topology domain to a non-F1 termination host, enabling the non-F1 termination host to send the IP address for the F1 termination topology domain to the IAB node, for example, when the F1 termination host is unable to send a message to the IAB node. This allows the IAB node to use the IP address for the non-F1 termination topology domain for routing IDs in the non-F1 termination topology domain, and to use the IP address for the F1 termination topology domain for routing IDs in the F1 termination topology domain.

[0256] Embodiments of the second aspect

[0257] The embodiment of the present application provides a method for configuring a transport address, which is described from the perspective of a non-F1 termination point host. The same contents as those in the embodiment of the first aspect are not repeated here.

[0258] FIG28 is another schematic diagram of the transmission address configuration method according to an embodiment of the present application. As shown in FIG28 , the method includes:

[0259] 2801, the non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; and / or,

[0260] The non-F1 termination point host sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; and / or,

[0261] The non-F1 termination point host receives the IP address configuration information of the F1 termination point topology domain allocated to the IAB node, which is sent by the F1 termination point host.

[0262] In some embodiments, the method may further include: (not shown)

[0263] The non-F1 termination point host sends the IP address configuration information to the IAB node.

[0264] In some embodiments, the IP address request information is carried by a first RRC container, which also includes the IP address configuration information of the IAB node in the F1 termination point topology domain. For example, the IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.

[0265] In some embodiments, the first RRC container is carried by at least one of the following messages:

[0266] Handover request message;

[0267] Auxiliary node addition request message;

[0268] Auxiliary node modification request message;

[0269] The auxiliary node modifies the demand message;

[0270] UE context acquisition response message.

[0271] In some embodiments, the IP address configuration information is carried by the second RRC container, for example, the IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) included in the second RRC container.

[0272] In some embodiments, the second RRC container is carried by at least one of the following messages:

[0273] Handover request response message;

[0274] The auxiliary node adds a response message;

[0275] The auxiliary node modifies the response message;

[0276] The auxiliary node modifies the request message.

[0277] In some embodiments, the F1 termination point host is a source host of the IAB node handover, and the non-F1 termination point host is a target host of the IAB node handover. The method includes:

[0278] The non-F1 termination point host receives the IP address request information of the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the non-F1 termination point host sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host. The first RRC container is carried by the handover request message, and the second RRC container is carried by the handover request response message.

[0279] In some embodiments, the F1 termination point host is a primary node MN of the IAB node, and the non-F1 termination point host is a secondary node SN of the IAB node. The method includes:

[0280] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the first RRC container is carried by a secondary node add request message or a secondary node modify request message. Further, the non-F1 termination point host sends IP address configuration information for the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host, and the second RRC container is carried by a secondary node add response message or a secondary node modify response message. Optionally, the non-F1 termination point host also sends the IP address configuration information to the IAB node.

[0281] In some embodiments, the F1 termination point host is a primary node MN of the IAB node, and the non-F1 termination point host is a secondary node SN of the IAB node. The method includes:

[0282] The non-F1 termination point host sends IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host, and the second RRC container is carried by the secondary node modification request message.

[0283] In some embodiments, the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node. The method includes:

[0284] The non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the first RRC container is carried by the secondary node modification request message. Optionally, the non-F1 termination point host also sends the IP address configuration information to the IAB node.

[0285] In some embodiments, the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node. The method includes:

[0286] The non-F1 termination point host receives the IP address configuration information of the F1 termination point topology domain allocated to the border node sent by the F1 termination point host, and the second RRC container is carried by the secondary node modification request message. Optionally, the non-F1 termination point host also sends the IP address configuration information to the IAB node.

[0287] In some embodiments, the F1 termination point host is the host of the IAB node after RLF recovery, and the non-F1 termination point host is the host of the IAB node before RLF recovery. The method includes:

[0288] The non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the first RRC container is carried by the UE context acquisition response message. Optionally, the non-F1 termination point host also sends the IP address configuration information to the IAB node.

[0289] In some embodiments, the IP address request information is carried by an IAB transport migration management request message, wherein the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0290] In some embodiments, the IP address configuration information is carried by an IAB transport migration management response message or an IAB transport migration modification request message, and the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0291] In some embodiments, the F1 termination point host is a source host of the IAB node handover, and the non-F1 termination point host is a target host of the IAB node handover. The method includes:

[0292] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, the IP address request information being carried by the IAB transport migration management request message. Optionally, the non-F1 termination point host also sends the IP address configuration information to the IAB node.

[0293] In some embodiments, wherein the F1 termination point host is a primary node MN of the IAB node and the non-F1 termination point host is a secondary node SN of the IAB node, the method includes:

[0294] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, the IP address request information being carried in an IAB Transport Migration Management Request message. Furthermore, the non-F1 termination point host sends IP address configuration information for the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host, the IP address configuration information being carried in an IAB Transport Migration Management Response message. Optionally, the non-F1 termination point host also sends the IP address configuration information to the IAB node.

[0295] In some embodiments, the F1 termination point host is a primary node MN of the IAB node, and the non-F1 termination point host is a secondary node SN of the IAB node. The method includes:

[0296] The non-F1 termination point host sends IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host. The IP address configuration information is carried by the IAB transport migration modification request message.

[0297] In some embodiments, the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node. The method includes:

[0298] The non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, the IP address request information being carried by the IAB transport migration management request message. Optionally, the non-F1 termination point host also sends the IP address configuration information to the IAB node.

[0299] In some embodiments, the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node. The method includes:

[0300] The non-F1 termination point host receives the IP address configuration information of the F1 termination point topology domain allocated to the border node from the F1 termination point host, the IP address configuration information being carried by the IAB transport migration management request message. Optionally, the non-F1 termination point host also sends the IP address configuration information to the IAB node.

[0301] In some embodiments, the F1 termination point host is the host of the IAB node after RLF recovery, and the non-F1 termination point host is the host of the IAB node before RLF recovery. The method includes:

[0302] The non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, the IP address request information being carried by the IAB transport migration management request message. Optionally, the non-F1 termination point host also sends the IP address configuration information to the IAB node.

[0303] The above signaling process is only a schematic illustration of the embodiment of the present application, but the present application is not limited thereto. For more specific content of the signaling, reference may be made to the relevant technology. In addition, for example, the execution order between the various operations may be appropriately adjusted, and other operations may be added or some of the operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content. The specific signaling process corresponds to the records of Figures 12, 14-16, 18-19, and 21 in the embodiment of the first aspect, and will not be repeated here.

[0304] As can be seen from the above embodiments, the F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain, or further receive IP address configuration information of the non-F1 termination domain allocated by the non-F1 termination host to the IAB node, thereby enabling the F1 termination host to request an IP address in the non-F1 termination topology domain, or further send an IP address in the non-F1 termination topology domain to the IAB node, for example, when the non-F1 termination host is unable to send a message to the IAB node. The F1 termination host can receive IP address configuration information of the non-F1 termination topology domain proactively sent by the non-F1 termination host, so as to send an IP address in the non-F1 termination topology domain to the IAB node, for example, when the non-F1 termination host is unable to send a message to the IAB node. Additionally, the F1 termination host can send IP address configuration information for the F1 termination topology domain to a non-F1 termination host, enabling the non-F1 termination host to send the IP address for the F1 termination topology domain to the IAB node, for example, when the F1 termination host is unable to send a message to the IAB node. This allows the IAB node to use the IP address for the non-F1 termination topology domain for routing IDs in the non-F1 termination topology domain, and to use the IP address for the F1 termination topology domain for routing IDs in the F1 termination topology domain.

[0305] Embodiments of the third aspect

[0306] This embodiment of the present application provides an IAB host device. Details common to the embodiment of the first aspect are omitted. This device may, for example, be an IAB donor-CU in an IAB system (e.g., the first donor-CU or F1 termination host in the embodiments of the first and second aspects), or may be one or more components, assemblies, or modules configured within the IAB donor-CU or F1 termination host.

[0307] FIG29 is a schematic diagram of an IAB host device according to an embodiment of the present application. As shown in FIG29 , the IAB host device 2900 includes:

[0308] The first sending unit 2901 sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; and / or

[0309] Sending IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host; and / or,

[0310] The first receiving unit 2902 receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node and sent by the non-F1 termination point host.

[0311] In some embodiments, the IP address request information is carried by a first RRC container.

[0312] In some embodiments, the first RRC container further includes IP address configuration information of the IAB node in the F1 termination point topology domain.

[0313] In some embodiments, the IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) included in the first RRC container.

[0314] In some embodiments, the first RRC container is carried by at least one of the following messages:

[0315] Handover request message;

[0316] Auxiliary node addition request message;

[0317] Auxiliary node modification request message;

[0318] The auxiliary node modifies the demand message;

[0319] UE context acquisition response message.

[0320] In some embodiments, the IP address configuration information is carried by a second RRC container.

[0321] In some embodiments, the IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container.

[0322] In some embodiments, the second RRC container is carried by at least one of the following messages:

[0323] Handover request response message;

[0324] The auxiliary node adds a response message;

[0325] The auxiliary node modifies the response message;

[0326] The auxiliary node modifies the request message.

[0327] In some embodiments, the F1 termination point host is the source host for the IAB node handover, and the non-F1 termination point host is the target host for the IAB node handover. The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host. The first receiving unit receives IP address configuration information for the non-F1 termination point topology domain allocated to the IAB node from the non-F1 termination point host. The first RRC container is carried by a handover request message, and the second RRC container is carried by a handover request response message. Optionally, the first sending unit also sends the IP address configuration information to the IAB node.

[0328] In some embodiments, the F1 termination point host is a primary node (MN) of the IAB node, and the non-F1 termination point host is a secondary node (SN) of the IAB node. The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host, and the first RRC container is carried by a secondary node add request message or a secondary node modify request message. Furthermore, the first receiving unit receives IP address configuration information for the non-F1 termination point topology domain allocated to the IAB node, sent by the non-F1 termination point host, and the second RRC container is carried by a secondary node add response message or a secondary node modify response message. Optionally, the first sending unit also sends the IP address configuration information to the IAB node.

[0329] In some embodiments, the F1 termination point host is a primary node (MN) of the IAB node, the non-F1 termination point host is a secondary node (SN) of the IAB node, the first receiving unit receives IP address configuration information for the non-F1 termination point topology domain allocated to the IAB node, and the second RRC container is carried by a secondary node modification request message. Optionally, the first sending unit further sends the IP address configuration information to the IAB node.

[0330] In some embodiments, the non-F1 termination point host is the master node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host, and the first RRC container is carried by the secondary node modification request message.

[0331] In some embodiments, the non-F1 termination point host is the master node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, the first sending unit sends the IP address configuration information of the F1 termination point topology domain allocated to the border node to the non-F1 termination point host, and the second RRC container is carried by the secondary node modification request message.

[0332] In some embodiments, the F1 termination point host is the host of the IAB node after RLF recovery, the non-F1 termination point host is the host of the IAB node before RLF recovery, the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host, and the first RRC container is carried by the UE context acquisition response message.

[0333] In some embodiments, the IP address request information is carried by an IAB transmission migration management request message.

[0334] In some embodiments, the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0335] In some embodiments, the IP address configuration information is carried by an IAB transport migration management response message or an IAB transport migration modification request message.

[0336] In some embodiments, the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0337] In some embodiments, the F1 termination point host is the source host of the IAB node switching, the non-F1 termination point host is the target host of the IAB node switching, and the IP address request information for the non-F1 termination point topology domain of the IAB node is sent to the non-F1 termination point host. The IP address request information is carried by the IAB transmission migration management request message.

[0338] In some embodiments, the F1 termination host is a primary node (MN) of the IAB node, and the non-F1 termination host is a secondary node (SN) of the IAB node. The first sending unit sends IP address request information for the non-F1 termination topology domain of the IAB node to the non-F1 termination host. The IP address request information is carried by an IAB transport migration management request message. Furthermore, the first receiving unit receives IP address configuration information for the non-F1 termination topology domain allocated to the IAB node from the non-F1 termination host. The IP address configuration information is carried by an IAB transport migration management response message. Optionally, the first sending unit also sends the IP address configuration information to the IAB node.

[0339] In some embodiments, the F1 termination point host is a primary node (MN) of the IAB node, and the non-F1 termination point host is a secondary node (SN) of the IAB node. The first receiving unit receives IP address configuration information for the non-F1 termination point topology domain allocated to the IAB node, sent by the non-F1 termination point host. The IP address configuration information is carried in an IAB transport migration modification request message. Optionally, the first sending unit further sends the IP address configuration information to the IAB node.

[0340] In some embodiments, the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host. The IP address request information is carried by the IAB transmission migration management request message.

[0341] In some embodiments, the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the first sending unit sends the IP address configuration information of the F1 termination point topology domain allocated to the boundary node to the non-F1 termination point host, and the IP address configuration information is carried by the IAB transmission migration management request message.

[0342] In some embodiments, the F1 termination point host is the host of the IAB node after RLF recovery, the non-F1 termination point host is the host of the IAB node before RLF recovery, and the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host, and the IP address request information is carried by the IAB transmission migration management request message.

[0343] 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.

[0344] 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 IAB host device 2900 of the embodiment 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.

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

[0346] As can be seen from the above embodiments, the F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain, or further receive IP address configuration information of the non-F1 termination domain allocated by the non-F1 termination host to the IAB node, thereby enabling the F1 termination host to request an IP address in the non-F1 termination topology domain, or further send an IP address in the non-F1 termination topology domain to the IAB node, for example, when the non-F1 termination host is unable to send a message to the IAB node. The F1 termination host can receive IP address configuration information of the non-F1 termination topology domain proactively sent by the non-F1 termination host, so as to send an IP address in the non-F1 termination topology domain to the IAB node, for example, when the non-F1 termination host is unable to send a message to the IAB node. Additionally, the F1 termination host can send IP address configuration information for the F1 termination topology domain to a non-F1 termination host, enabling the non-F1 termination host to send the IP address for the F1 termination topology domain to the IAB node, for example, when the F1 termination host is unable to send a message to the IAB node. This allows the IAB node to use the IP address for the non-F1 termination topology domain for routing IDs in the non-F1 termination topology domain, and to use the IP address for the F1 termination topology domain for routing IDs in the F1 termination topology domain.

[0347] Embodiments of the fourth aspect

[0348] This embodiment of the present application provides an IAB host device. Details common to the embodiment of the second aspect are omitted. This device may, for example, be an IAB donor-CU in an IAB system (e.g., the second donor-CU or non-F1 termination host in the embodiments of the first and second aspects), or may be one or more components, assemblies, or modules configured within the IAB donor-CU or non-F1 termination host.

[0349] FIG30 is a schematic diagram of an IAB host device according to an embodiment of the present application. As shown in FIG30 , the IAB host device 3000 includes:

[0350] The second receiving unit 3001 receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; and / or

[0351] receiving IP address configuration information of the F1 termination point topology domain allocated to the IAB node from the F1 termination point host; and / or,

[0352] The second sending unit 3002 sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host.

[0353] In some embodiments, the IP address request information is carried by a first RRC container.

[0354] In some embodiments, the first RRC container further includes IP address configuration information of the IAB node in the F1 termination point topology domain.

[0355] In some embodiments, the IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) included in the first RRC container.

[0356] In some embodiments, the first RRC container is carried by at least one of the following messages:

[0357] Handover request message;

[0358] Auxiliary node addition request message;

[0359] Auxiliary node modification request message;

[0360] The auxiliary node modifies the demand message;

[0361] UE context acquisition response message.

[0362] In some embodiments, the IP address configuration information is carried by a second RRC container.

[0363] In some embodiments, the IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container.

[0364] In some embodiments, the second RRC container is carried by at least one of the following messages:

[0365] Handover request response message;

[0366] The auxiliary node adds a response message;

[0367] The auxiliary node modifies the response message;

[0368] The auxiliary node modifies the request message.

[0369] In some embodiments, the F1 termination point host is the source host of the IAB node switching, the non-F1 termination point host is the target host of the IAB node switching, the second receiving unit receives the IP address request information of the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the second sending unit sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host. The first RRC container is carried by the switching request message, and the second RRC container is carried by the switching request response message.

[0370] In some embodiments, the F1 termination point host is a primary node (MN) of the IAB node, the non-F1 termination point host is a secondary node (SN) of the IAB node, the second receiving unit receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, the first RRC container is carried by a secondary node add request message or a secondary node modify request message, and further, the second sending unit sends IP address configuration information for the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host, the second RRC container is carried by a secondary node add response message or a secondary node modify response message. Optionally, the second sending unit also sends the IP address configuration information to the IAB node.

[0371] In some embodiments, the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, the second sending unit sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host, and the second RRC container is carried by the secondary node modification request message.

[0372] In some embodiments, the non-F1 termination point host is a primary node (MN) of the IAB node, the F1 termination point host is a secondary node (SN) of the IAB node, the second receiving unit receives IP address request information for the non-F1 termination point topology domain of the IAB node, sent by the F1 termination point host, and the first RRC container is carried by a secondary node modification request message. Optionally, the second sending unit further sends the IP address configuration information to the IAB node.

[0373] In some embodiments, the non-F1 termination point host is a primary node (MN) of the IAB node, the F1 termination point host is a secondary node (SN) of the IAB node, the second receiving unit receives IP address configuration information of the F1 termination point topology domain allocated to the border node, and the second RRC container is carried by the secondary node modification request message. Optionally, the second sending unit further sends the IP address configuration information to the IAB node.

[0374] In some embodiments, the F1 termination point host is the host of the IAB node after RLF recovery, and the non-F1 termination point host is the host of the IAB node before RLF recovery. The second receiving unit receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the first RRC container is carried by a UE context acquisition response message. Optionally, the second sending unit further sends the IP address configuration information to the IAB node.

[0375] In some embodiments, the IP address request information is carried by an IAB transmission migration management request message.

[0376] In some embodiments, the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0377] In some embodiments, the IP address configuration information is carried by an IAB transport migration management response message or an IAB transport migration modification request message.

[0378] In some embodiments, the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0379] In some embodiments, the F1 termination host is the source host for the IAB node handover, and the non-F1 termination host is the target host for the IAB node handover. The second receiving unit receives IP address request information sent by the F1 termination host for the non-F1 termination topology domain of the IAB node, the IP address request information being carried by an IAB transport migration management request message. Optionally, the second sending unit further sends the IP address configuration information to the IAB node.

[0380] In some embodiments, the F1 termination point host is a primary node (MN) of the IAB node, and the non-F1 termination point host is a secondary node (SN) of the IAB node. The second receiving unit receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, where the IP address request information is carried by an IAB Transport Migration Management Request message. Furthermore, the second sending unit sends IP address configuration information for the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host, where the IP address configuration information is carried by an IAB Transport Migration Management Response message. Optionally, the second sending unit also sends the IP address configuration information to the IAB node.

[0381] In some embodiments, the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the second sending unit sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host. The IP address configuration information is carried by the IAB transmission migration modification request message.

[0382] In some embodiments, the non-F1 termination point host is a primary node (MN) of the IAB node, and the F1 termination point host is a secondary node (SN) of the IAB node. The second receiving unit receives IP address request information for the non-F1 termination point topology domain of the IAB node, sent by the F1 termination point host. The IP address request information is carried by an IAB transport migration management request message. Optionally, the second sending unit further sends the IP address configuration information to the IAB node.

[0383] In some embodiments, the non-F1 termination point host is a primary node (MN) of the IAB node, the F1 termination point host is a secondary node (SN) of the IAB node, and the second receiving unit receives IP address configuration information of the F1 termination point topology domain allocated to the border node, sent by the F1 termination point host. The IP address configuration information is carried in an IAB transport migration management request message. Optionally, the second sending unit further sends the IP address configuration information to the IAB node.

[0384] In some embodiments, the F1 termination point host is the host of the IAB node after RLF recovery, and the non-F1 termination point host is the host of the IAB node before RLF recovery. The second receiving unit receives IP address request information for the non-F1 termination point topology domain of the IAB node, sent by the F1 termination point host. The IP address request information is carried by an IAB transport migration management request message. Optionally, the second sending unit also sends the IP address configuration information to the IAB node.

[0385] 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.

[0386] 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 IAB host device 3000 of the embodiment 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.

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

[0388] As can be seen from the above embodiments, the F1 termination host can request a non-F1 termination host to allocate an IP address in the non-F1 termination topology domain, or further receive IP address configuration information of the non-F1 termination domain allocated by the non-F1 termination host to the IAB node, thereby enabling the F1 termination host to request an IP address in the non-F1 termination topology domain, or further send an IP address in the non-F1 termination topology domain to the IAB node, for example, when the non-F1 termination host is unable to send a message to the IAB node. The F1 termination host can receive IP address configuration information of the non-F1 termination topology domain proactively sent by the non-F1 termination host, so as to send an IP address in the non-F1 termination topology domain to the IAB node, for example, when the non-F1 termination host is unable to send a message to the IAB node. Additionally, the F1 termination host can send IP address configuration information for the F1 termination topology domain to a non-F1 termination host, enabling the non-F1 termination host to send the IP address for the F1 termination topology domain to the IAB node, for example, when the F1 termination host is unable to send a message to the IAB node. This allows the IAB node to use the IP address for the non-F1 termination topology domain for routing IDs in the non-F1 termination topology domain, and to use the IP address for the F1 termination topology domain for routing IDs in the F1 termination topology domain.

[0389] Embodiments of the fifth aspect

[0390] An embodiment of the present application provides a communication system, which includes: the IAB host device 2900 of the third embodiment and / or the IAB host device 3000 of the fourth embodiment, and also includes an IAB node (border node). Regarding the network architecture of the host (donor) device and the IAB node, reference can be made to related technologies and the description is omitted here.

[0391] The embodiment of the present application also provides an IAB host device.

[0392] Figure 9 is a schematic diagram of an IAB host device according to an embodiment of the present application. As shown in Figure 9 , IAB device 900 may include a processor (e.g., a central processing unit (CPU)) 901 and a memory 902 ; the memory 902 is coupled to the processor 901 . The memory 902 may store various data and may also store an information processing program 905 , which is executed under the control of the CPU 901 .

[0393] For example, the processor 901 may be configured to execute a program to implement the transmission address configuration method in the embodiment of the first aspect.

[0394] For another example, the processor 901 may be configured to execute a program to implement the transmission address configuration method in the embodiment of the second aspect.

[0395] Furthermore, as shown in FIG9 , the IAB host device 900 may further include a transceiver 903 and an antenna 904. 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 device 900 does not necessarily include all of the components shown in FIG9 ; furthermore, the IAB device 900 may also include components not shown in FIG9 , for which reference may be made to the prior art.

[0396] An embodiment of the present application further provides a computer-readable program, wherein when the program is executed in an IAB host device, the program enables a computer to execute the transmission address configuration method in the embodiments of the first to second aspects in the IAB host device.

[0397] 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 the transmission address configuration method in the embodiments of the first to second aspects in an IAB host device.

[0398] 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.

[0399] 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).

[0400] 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.

[0401] 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.

[0402] 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.

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

[0404] F1

[0405] 1. A transport address configuration method, applied to an F1 termination point host device of an IAB node, characterized in that the method comprises:

[0406] The F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; and / or,

[0407] The F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node, which is sent by the non-F1 termination point host; and / or,

[0408] The F1 termination point host sends IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host.

[0409] 2. The method according to Note 1, wherein the IP address request information is carried by the first RRC container.

[0410] 3. The method according to Note 2, wherein the first RRC container also includes IP address configuration information of the IAB node in the F1 termination point topology domain.

[0411] 4. The method according to Note 2 or 3, wherein the IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.

[0412] 5. The method according to any one of Notes 2 to 4, wherein the first RRC container is carried by at least one of the following messages:

[0413] Handover request message;

[0414] Auxiliary node addition request message;

[0415] Auxiliary node modification request message;

[0416] The auxiliary node modifies the demand message;

[0417] UE context acquisition response message.

[0418] 6. The method according to Note 1, wherein the IP address configuration information is carried by a second RRC container.

[0419] 7. The method according to Note 6, wherein the IP address configuration information is carried by the RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container.

[0420] 8. The method according to Note 6 or 7, wherein the second RRC container is carried by at least one of the following messages:

[0421] Handover request response message;

[0422] The auxiliary node adds a response message;

[0423] The auxiliary node modifies the response message;

[0424] The auxiliary node modifies the request message.

[0425] 9. The method according to note 5 or 8, wherein the F1 termination point host is a source host of the IAB node handover, and the non-F1 termination point host is a target host of the IAB node handover, the method comprising:

[0426] The F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host, and the F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node sent by the non-F1 termination point host; wherein the first RRC container is carried by the handover request message, and the second RRC container is carried by the handover request response message.

[0427] 9.1. The method according to Note 9, further comprising:

[0428] The F1 termination point host sends the IP address configuration information to the IAB node.

[0429] 10. The method according to note 5 or 8, wherein the F1 termination point host is a primary node MN of the IAB node, and the non-F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0430] The F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is carried by a secondary node add request message or a secondary node modify request message.

[0431] 10.1. The method according to Note 10, further comprising:

[0432] The F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node from the non-F1 termination point host, and the second RRC container is carried by a secondary node addition response message or a secondary node modification response message.

[0433] 10.2. The method according to Note 10 or 10.1, further comprising:

[0434] The F1 termination point host sends the IP address configuration information to the IAB node.

[0435] 11. The method according to note 5 or 8, wherein the F1 termination point host is a primary node MN of the IAB node, and the non-F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0436] The F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node and sent by the non-F1 termination point host; wherein the second RRC container is carried by the secondary node modification request message.

[0437] 11.1. The method according to Note 11, further comprising:

[0438] The F1 termination point host sends the IP address configuration information to the IAB node.

[0439] 12. The method according to note 5 or 8, wherein the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0440] The F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is carried by a secondary node modification request message.

[0441] 13. The method according to note 5 or 8, wherein the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0442] The F1 termination point host sends IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host; wherein the second RRC container is carried by a secondary node modification request message.

[0443] 14. The method according to note 5 or 8, wherein the F1 termination point host is the host of the IAB node after RLF recovery, and the non-F1 termination point host is the host of the IAB node before RLF recovery, the method comprising:

[0444] The F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is carried by a UE context acquisition response message.

[0445] 15. The method according to Note 1, wherein the IP address request information is carried by an IAB transmission migration management request message.

[0446] 16. The method according to Note 15, wherein the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0447] 17. The method according to Note 1, wherein the IP address configuration information is carried by an IAB transport migration management response message or an IAB transport migration modification request message.

[0448] 18. The method according to Note 17, wherein the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0449] 19. The method according to note 15 or 17, wherein the F1 termination point host is a source host of the IAB node handover, and the non-F1 termination point host is a target host of the IAB node handover, the method comprising:

[0450] The F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transport migration management request message.

[0451] 20. The method according to note 15 or 17, wherein the F1 termination point host is a primary node MN of the IAB node, and the non-F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0452] The F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transport migration management request message.

[0453] 20.1. The method according to Note 20, further comprising:

[0454] The F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node and sent by the non-F1 termination point host; wherein the IP address configuration information is carried by the IAB transport migration management response message.

[0455] 20.2. The method according to Note 20.1, further comprising:

[0456] The F1 termination point host sends the IP address configuration information to the IAB node.

[0457] 21. The method according to note 15 or 17, wherein the F1 termination point host is a primary node MN of the IAB node, and the non-F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0458] The F1 termination point host receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node and sent by the non-F1 termination point host; wherein the IP address configuration information is carried by the IAB transport migration modification request message.

[0459] 21.1. The method according to Note 21, further comprising:

[0460] The F1 termination point host sends the IP address configuration information to the IAB node.

[0461] 22. The method according to note 15 or 17, wherein the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0462] The F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transport migration management request message.

[0463] 23. The method according to note 15 or 17, wherein the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0464] The F1 termination point host sends IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host; wherein the IP address configuration information is carried by the IAB transport migration management request message.

[0465] 24. The method according to note 15 or 17, wherein the F1 termination point host is the host of the IAB node after RLF recovery, and the non-F1 termination point host is the host of the IAB node before RLF recovery, the method comprising:

[0466] The F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transport migration management request message.

[0467] 25. An IAB donor device, comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the transmission address configuration method as described in any one of Notes 1 to 25.

[0468] Non-F1

[0469] 1. A transport address configuration method, applied to a non-F1 termination point host device of an IAB node, characterized in that the method comprises:

[0470] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; and / or,

[0471] The non-F1 termination point host sends IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; and / or,

[0472] The non-F1 termination point host receives the IP address configuration information of the F1 termination point topology domain allocated to the IAB node, which is sent by the F1 termination point host.

[0473] 2. The method according to Note 1, wherein the IP address request information is carried by the first RRC container.

[0474] 3. The method according to Note 2, wherein the first RRC container also includes IP address configuration information of the IAB node in the F1 termination point topology domain.

[0475] 4. The method according to Note 2 or 3, wherein the IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.

[0476] 5. The method according to any one of Notes 2 to 4, wherein the first RRC container is carried by at least one of the following messages:

[0477] Handover request message;

[0478] Auxiliary node addition request message;

[0479] Auxiliary node modification request message;

[0480] The auxiliary node modifies the demand message;

[0481] UE context acquisition response message.

[0482] 6. The method according to Note 1, wherein the IP address configuration information is carried by a second RRC container.

[0483] 7. The method according to Note 6, wherein the IP address configuration information is carried by the RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container.

[0484] 8. The method according to Note 6 or 7, wherein the second RRC container is carried by at least one of the following messages:

[0485] Handover request response message;

[0486] The auxiliary node adds a response message;

[0487] The auxiliary node modifies the response message;

[0488] The auxiliary node modifies the request message.

[0489] 9. The method according to note 5 or 8, wherein the F1 termination point host is a source host of the IAB node handover, and the non-F1 termination point host is a target host of the IAB node handover, the method comprising:

[0490] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the non-F1 termination point host sends IP address configuration information for the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; wherein the first RRC container is carried by the handover request message, and the second RRC container is carried by the handover request response message.

[0491] 10. The method according to note 5 or 8, wherein the F1 termination point host is a primary node MN of the IAB node, and the non-F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0492] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is carried by a secondary node addition request message or a secondary node modification request message.

[0493] 10.1. The method according to Note 10, further comprising:

[0494] The non-F1 termination point host sends IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; wherein the second RRC container is carried by a secondary node addition response message or a secondary node modification response message.

[0495] 10.2. The method according to Note 10 or 10.1, further comprising:

[0496] The non-F1 termination point host sends the IP address configuration information to the IAB node.

[0497] 11. The method according to note 5 or 8, wherein the F1 termination point host is a primary node MN of the IAB node, and the non-F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0498] The non-F1 termination point host sends IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; wherein the second RRC container is carried by a secondary node modification request message.

[0499] 12. The method according to note 5 or 8, wherein the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0500] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is carried by the secondary node modification request message.

[0501] 12.1. The method according to Note 12, further comprising:

[0502] The non-F1 termination point host sends the IP address configuration information to the IAB node.

[0503] 13. The method according to note 5 or 8, wherein the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0504] The non-F1 termination point host receives the IP address configuration information of the F1 termination point topology domain allocated to the IAB node and sent by the F1 termination point host; wherein the second RRC container is carried by the secondary node modification request message.

[0505] 13.1. The method according to Note 13, further comprising:

[0506] The non-F1 termination point host sends the IP address configuration information to the IAB node.

[0507] 14. The method according to note 5 or 8, wherein the F1 termination point host is the host of the IAB node after RLF recovery, and the non-F1 termination point host is the host of the IAB node before RLF recovery, the method comprising:

[0508] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is carried by a UE context acquisition response message.

[0509] 14.1. The method according to Note 14, further comprising:

[0510] The non-F1 termination point host sends the IP address configuration information to the IAB node.

[0511] 15. The method according to Note 1, wherein the IP address request information is carried by an IAB transmission migration management request message.

[0512] 16. The method according to Note 15, wherein the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0513] 17. The method according to Note 1, wherein the IP address configuration information is carried by an IAB transport migration management response message or an IAB transport migration modification request message.

[0514] 18. The method according to Note 17, wherein the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0515] 19. The method according to note 15 or 17, wherein the F1 termination point host is a source host of the IAB node handover, and the non-F1 termination point host is a target host of the IAB node handover, the method comprising:

[0516] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the IP address request information is carried by an IAB transport migration management request message.

[0517] 19.1. The method according to Note 19, further comprising:

[0518] The non-F1 termination point host sends the IP address configuration information to the IAB node.

[0519] 20. The method according to note 15 or 17, wherein the F1 termination point host is a primary node MN of the IAB node, and the non-F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0520] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the IP address request information is carried by the IAB transport migration management request message.

[0521] 20.1. The method according to Note 20, further comprising:

[0522] The non-F1 termination point host sends IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; wherein the IP address configuration information is carried by an IAB transport migration management response message.

[0523] 20.2. The method according to Note 20 or 20.1, further comprising:

[0524] The non-F1 termination point host sends the IP address configuration information to the IAB node.

[0525] 21. The method according to note 15 or 17, wherein the F1 termination point host is a primary node MN of the IAB node, and the non-F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0526] The non-F1 termination point host sends IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; wherein the IP address configuration information is carried by the IAB transport migration modification request message.

[0527] 22. The method according to note 15 or 17, wherein the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0528] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the IP address request information is carried by the IAB transport migration management request message.

[0529] 22.1. The method according to Note 22, further comprising:

[0530] The non-F1 termination point host sends the IP address configuration information to the IAB node.

[0531] 23. The method according to note 15 or 17, wherein the non-F1 termination point host is a primary node MN of the IAB node, and the F1 termination point host is a secondary node SN of the IAB node, the method comprising:

[0532] The non-F1 termination point host receives the IP address configuration information of the F1 termination point topology domain allocated to the IAB node and sent by the F1 termination point host; wherein the IP address configuration information is carried by the IAB transport migration management request message.

[0533] 23.1. The method according to Note 23, further comprising:

[0534] The non-F1 termination point host sends the IP address configuration information to the IAB node.

[0535] 24. The method according to note 15 or 17, wherein the F1 termination point host is the host of the IAB node after RLF recovery, and the non-F1 termination point host is the host of the IAB node before RLF recovery, the method comprising:

[0536] The non-F1 termination point host receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the IP address request information is carried by the IAB transport migration management request message.

[0537] 24.1. The method according to Note 24, further comprising:

[0538] The non-F1 termination point host sends the IP address configuration information to the IAB node.

[0539] 25. An IAB donor device, comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the transmission address configuration method as described in any one of Notes 1 to 25.

[0540] F1

[0541] 1. An IAB host device, wherein the IAB host device is an F1 termination point host device of an IAB node, wherein the device comprises:

[0542] A first sending unit, configured to send IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; and / or

[0543] Sending IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host; and / or,

[0544] The first receiving unit receives IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node and sent by the non-F1 termination point host.

[0545] 2. The device according to Note 1, wherein the IP address request information is carried by a first RRC container.

[0546] 3. The device according to Note 2, wherein the first RRC container also includes IP address configuration information of the IAB node in the F1 termination point topology domain.

[0547] 4. The device according to Note 2 or 3, wherein the IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.

[0548] 5. The device according to any one of Notes 2 to 4, wherein the first RRC container is carried by at least one of the following messages:

[0549] Handover request message;

[0550] Auxiliary node addition request message;

[0551] Auxiliary node modification request message;

[0552] The auxiliary node modifies the demand message;

[0553] UE context acquisition response message.

[0554] 6. The device according to Note 1, wherein the IP address configuration information is carried by a second RRC container.

[0555] 7. The device according to Note 6, wherein the IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container.

[0556] 8. The device according to Note 6 or 7, wherein the second RRC container is carried by at least one of the following messages:

[0557] Handover request response message;

[0558] The auxiliary node adds a response message;

[0559] The auxiliary node modifies the response message;

[0560] The auxiliary node modifies the request message.

[0561] 9. The device according to Note 5 or 8, wherein the F1 termination point host is the source host of the IAB node switching, the non-F1 termination point host is the target host of the IAB node switching, the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host, and the first receiving unit receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node sent by the non-F1 termination point host; wherein the first RRC container is carried by the switching request message, and the second RRC container is carried by the switching request response message.

[0562] 10. The device according to Note 5 or 8, wherein the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is carried by a secondary node addition request message or a secondary node modification request message.

[0563] 10.1. The device according to Note 10, wherein the first receiving unit also receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node sent by the non-F1 termination point host; wherein the second RRC container is carried by a secondary node addition response message or a secondary node modification response message.

[0564] 11. The device according to Note 5 or 8, wherein the F1 termination point host is the master node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the first receiving unit receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node sent by the non-F1 termination point host; wherein the second RRC container is carried by the secondary node modification request message.

[0565] 12. The device according to Note 5 or 8, wherein the non-F1 termination point host is the master node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is carried by the secondary node modification request message.

[0566] 13. The device according to Note 5 or 8, wherein the non-F1 termination point host is the master node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the first sending unit sends the IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host; wherein the second RRC container is carried by the secondary node modification request message.

[0567] 14. The device according to Note 5 or 8, wherein the F1 termination point host is the host of the IAB node after RLF recovery, the non-F1 termination point host is the host of the IAB node before RLF recovery, and the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is carried by a UE context acquisition response message.

[0568] 15. The device according to Note 1, wherein the IP address request information is carried by an IAB transmission migration management request message.

[0569] 16. The device according to note 15, wherein the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0570] 17. The device according to Note 1, wherein the IP address configuration information is carried by an IAB transport migration management response message or an IAB transport migration modification request message.

[0571] 18. The device according to Note 17, wherein the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0572] 19. The device according to Note 15 or 17, wherein the F1 termination point host is the source host of the IAB node switching, the non-F1 termination point host is the target host of the IAB node switching, and the sending includes sending IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.

[0573] 20. The device according to Note 15 or 17, wherein the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.

[0574] 20.1. The device according to Note 20, wherein the first receiving unit further receives IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node sent by the non-F1 termination point host; wherein the IP address configuration information is carried by the IAB transmission migration management response message.

[0575] 21. The device according to Note 15 or 17, wherein the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the first receiving unit receives the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node sent by the non-F1 termination point host; wherein the IP address configuration information is carried by an IAB transmission migration modification request message.

[0576] 22. The device according to Note 15 or 17, wherein the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.

[0577] 23. The device according to Note 15 or 17, wherein the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the first sending unit sends the IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host; wherein the IP address configuration information is carried by the IAB transmission migration management request message.

[0578] 24. The device according to Note 15 or 17, wherein the F1 termination point host is the host of the IAB node after RLF recovery, the non-F1 termination point host is the host of the IAB node before RLF recovery, and the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.

[0579] 25. The device according to Note 9 or 10 or 10.1 or 11 or 20 or 20.1 or 21, wherein the first sending unit further sends the IP address configuration information to the IAB node.

[0580] Non-F1

[0581] 1. An IAB host device, wherein the IAB host device is a non-F1 termination point host device of an IAB node, characterized in that the device comprises:

[0582] a second receiving unit configured to receive IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; and / or

[0583] receiving IP address configuration information of the F1 termination point topology domain allocated to the IAB node from the F1 termination point host; and / or,

[0584] The second sending unit sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host.

[0585] 2. The device according to Note 1, wherein the IP address request information is carried by a first RRC container.

[0586] 3. The device according to Note 2, wherein the first RRC container also includes IP address configuration information of the IAB node in the F1 termination point topology domain.

[0587] 4. The device according to Note 2 or 3, wherein the IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.

[0588] 5. The device according to any one of Notes 2 to 4, wherein the first RRC container is carried by at least one of the following messages:

[0589] Handover request message;

[0590] Auxiliary node addition request message;

[0591] Auxiliary node modification request message;

[0592] The auxiliary node modifies the demand message;

[0593] UE context acquisition response message.

[0594] 6. The device according to Note 1, wherein the IP address configuration information is carried by a second RRC container.

[0595] 7. The device according to Note 6, wherein the IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container.

[0596] 8. The device according to Note 6 or 7, wherein the second RRC container is carried by at least one of the following messages:

[0597] Handover request response message;

[0598] The auxiliary node adds a response message;

[0599] The auxiliary node modifies the response message;

[0600] The auxiliary node modifies the request message.

[0601] 9. The device according to Note 5 or 8, wherein the F1 termination point host is the source host of the IAB node switching, the non-F1 termination point host is the target host of the IAB node switching, the second receiving unit receives the IP address request information of the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the second sending unit sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; wherein the first RRC container is carried by the switching request message, and the second RRC container is carried by the switching request response message.

[0602] 10. The device according to Note 5 or 8, wherein the F1 termination point host is the master node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the second receiving unit receives the IP address request information of the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is carried by a secondary node addition request message or a secondary node modification request message.

[0603] 10.1. According to the device described in Note 10, the second sending unit also sends IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host, and the second RRC container is carried by the auxiliary node add response message or the auxiliary node modify response message.

[0604] 11. The device according to Note 5 or 8, wherein the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the second sending unit sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; wherein the second RRC container is carried by the secondary node modification request message.

[0605] 12. The device according to Note 5 or 8, wherein the non-F1 termination point host is the master node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the second receiving unit receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is carried by the secondary node modification request message.

[0606] 13. The device according to Note 5 or 8, wherein the non-F1 termination point host is the master node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the second receiving unit receives the IP address configuration information of the F1 termination point topology domain allocated to the IAB node sent by the F1 termination point host; wherein the second RRC container is carried by the secondary node modification request message.

[0607] 14. The device according to Note 5 or 8, wherein the F1 termination point host is the host of the IAB node after RLF recovery, the non-F1 termination point host is the host of the IAB node before RLF recovery, and the second receiving unit receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is carried by a UE context acquisition response message.

[0608] 15. The device according to Note 1, wherein the IP address request information is carried by an IAB transmission migration management request message.

[0609] 16. The device according to Note 15, wherein the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0610] 17. The device according to Note 1, wherein the IP address configuration information is carried by an IAB transport migration management response message or an IAB transport migration modification request message.

[0611] 18. The device according to Note 17, wherein the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.

[0612] 19. The device according to Note 15 or 17, wherein the F1 termination point host is the source host of the IAB node switching, the non-F1 termination point host is the target host of the IAB node switching, and the second receiving unit receives the IP address request information sent by the F1 termination point host for the non-F1 termination point topology domain of the IAB node; wherein the IP address request information is carried by the IAB transmission migration management request message.

[0613] 20. The device according to Note 15 or 17, wherein the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the second receiving unit receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.

[0614] 20.1. The device according to Note 20, wherein the second sending unit further sends IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; wherein the IP address configuration information is carried by the IAB transport migration management response message.

[0615] 21. The device according to Note 15 or 17, wherein the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the second sending unit sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host; wherein the IP address configuration information is carried by the IAB transmission migration modification request message.

[0616] 22. The device according to Note 15 or 17, wherein the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the second receiving unit receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.

[0617] 23. The device according to Note 15 or 17, wherein the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the second receiving unit receives the IP address configuration information of the F1 termination point topology domain allocated to the IAB node sent by the F1 termination point host; wherein the IP address configuration information is carried by the IAB transmission migration management request message.

[0618] 24. The device according to Note 15 or 17, wherein the F1 termination point host is the host of the IAB node after RLF recovery, the non-F1 termination point host is the host of the IAB node before RLF recovery, and the second receiving unit receives IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.

[0619] 25. The device according to Note 10 or 10.1 or 12 or 13 or 4 or 19 or 20 or 20.1 or 22 or 23 or 24, wherein the second sending unit further sends the IP address configuration information to the IAB node.

Claims

1. An integrated access and backhaul IAB host device, wherein the IAB host device is an F1 termination point host device of an IAB node, characterized in that: The device comprises: A first sending unit, configured to send IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; and / or Sending IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host; and / or, The first receiving unit receives IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node and sent by the non-F1 termination point host.

2. The device according to claim 1, wherein The IP address request information is carried by the first RRC container.

3. The device according to claim 2, wherein The first RRC container also includes IP address configuration information of the IAB node in the F1 termination point topology domain.

4. The device according to claim 2 or 3, wherein The IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.

5. The apparatus according to claim 1, wherein The IP address configuration information is carried by the second RRC container.

6. The device according to claim 5, wherein The IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container.

7. The apparatus according to claim 3 or 6, wherein: The first RRC container is carried by at least one of the following messages: Handover request message; Auxiliary node addition request message; Auxiliary node modification request message; The auxiliary node modifies the demand message; UE context acquisition response message. The second RRC container is carried by at least one of the following messages: Handover request response message; The auxiliary node adds a response message; The auxiliary node modifies the response message; The auxiliary node modifies the request message.

8. The apparatus according to claim 7, wherein The F1 termination point host is the source host of the IAB node switching, and the non-F1 termination point host is the target host of the IAB node switching; The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host, and the first receiving unit receives IP address configuration information for the non-F1 termination point topology domain allocated to the IAB node sent by the non-F1 termination point host; The first RRC container is carried by a handover request message, and the second RRC container is carried by a handover request response message.

9. The apparatus according to claim 7, wherein The F1 termination point host is the master node MN of the IAB node, and the non-F1 termination point host is the secondary node SN of the IAB node. The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host, wherein the first RRC container is carried by a secondary node addition request message or a secondary node modification request message, or, The first receiving unit receives IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node and sent by the non-F1 termination point host; wherein the second RRC container is carried by a secondary node addition response message or a secondary node modification response message; or The first receiving unit receives IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node and sent by the non-F1 termination point host; wherein the second RRC container is carried by a secondary node modification request message.

10. The apparatus according to claim 7, wherein The non-F1 termination point host is the master node MN of the IAB node, and the F1 termination point host is the secondary node SN of the IAB node. The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host, and the first RRC container is carried by the secondary node modification request message, or, The first sending unit sends IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host; wherein the second RRC container is carried by a secondary node modification request message.

11. The apparatus according to claim 7, wherein The F1 termination point host is the host of the IAB node after RLF recovery, and the non-F1 termination point host is the host of the IAB node before RLF recovery; The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is carried by a UE context acquisition response message.

12. The apparatus according to claim 1, wherein The IP address request information is carried by an IAB Transmission Management Request message, and the IP address configuration information is carried by an IAB Transmission Management Response message or an IAB Transmission Modification Request message.

13. The apparatus according to claim 12, wherein The IP address request information includes a border node identifier, and the border node identifier is used to indicate that the IAB node is a border node; or the IP address configuration information includes a border node identifier, and the border node identifier is used to indicate that the IAB node is a border node.

14. The apparatus according to claim 12, wherein The F1 termination point host is the source host of the IAB node switching, and the non-F1 termination point host is the target host of the IAB node switching; The sending includes sending IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transport migration management request message.

15. The apparatus according to claim 12, wherein The F1 termination point host is the master node MN of the IAB node, and the non-F1 termination point host is the secondary node SN of the IAB node. The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transport migration management request message; or, The first receiving unit receives IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node and sent by the non-F1 termination point host; wherein the IP address configuration information is carried by an IAB transport migration management response message; or The first receiving unit receives IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node and sent by the non-F1 termination point host; wherein the IP address configuration information is carried by an IAB transport migration modification request message.

16. The apparatus according to claim 12, wherein The non-F1 termination point host is the master node MN of the IAB node, and the F1 termination point host is the secondary node SN of the IAB node. The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transport migration management request message, or, The first sending unit sends IP address configuration information of the F1 termination point topology domain allocated to the IAB node to the non-F1 termination point host; wherein the IP address configuration information is carried by an IAB transport migration management request message.

17. The apparatus according to claim 12, wherein: The F1 termination point host is the host of the IAB node after RLF recovery, and the non-F1 termination point host is the host of the IAB node before RLF recovery; The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transport migration management request message.

18. The apparatus according to claim 1, wherein The first sending unit further sends the IP address configuration information to the IAB node.

19. An integrated access and backhaul IAB host device, wherein the IAB host device is a non-F1 termination point host device of an IAB node, characterized in that: The device comprises: a second receiving unit configured to receive IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; and / or receiving IP address configuration information of the F1 termination point topology domain allocated to the IAB node from the F1 termination point host; and / or, The second sending unit sends the IP address configuration information of the non-F1 termination point topology domain allocated to the IAB node to the F1 termination point host.

20. A communication system, comprising: The device of claim 1 and / or the device of claim 19.