IAB donor equipment and transmission address setting method

Abstract

This invention provides IAB donor equipment and a transmission address setting method. [Solution] The IAB donor device includes a first transmitting unit and / or a first receiving unit, the first transmitting unit transmits IP address request information for a non-F1 terminating topology domain for the IAB node to a non-F1 terminating donor, and / or transmits IP address setting information for an F1 terminating topology domain to be assigned to the IAB node to the non-F1 terminating donor, and the first receiving unit receives the IP address setting information for a non-F1 terminating topology domain to be assigned to the IAB node transmitted by the non-F1 terminating donor.

Description

Technical Field

[0001] The present invention relates to the technical field of communications.

Background Art

[0002] The deployment of future seamless cellular networks requires the deployment of very flexible and ultra-high density new radio (NR) cells, and ultra-high density networks are one of the goals of 5G. The deployment of one NR network that does not require a wired backhaul is very important for the realization of 5G ultra-high density networks. Since the cell coverage is reduced by 5G millimeter waves, a wireless cell self-backhaul system requires multi-hop to meet the deployment needs. With the high bandwidth, massive multiple-input multiple-output (MIMO) and beam system of 5G, 5G makes it easier to develop a wireless cell self-backhaul system for ultra-high density NR cells than LTE. To develop such a multi-hop system with a wireless cell self-backhaul, 3GPP (registered trademark) started the research and standardization of the integrated access and backhaul (IAB) project in Rel-16.

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

[0004] In the IAB network architecture, a relay node refers to an IAB-node, which simultaneously supports access and backhaul functions. The last hop access node on the network side is called an IAB-donor, which supports gNB functionality and also supports access to IAB-nodes. All UE data can be backhauled to the IAB-donor via an IAB-node or multiple hops.

[0005] The functionality of an IAB-node is divided into two parts: one part is the gNB-DU function, called the IAB-DU (Distributed Unit), and the other part is the UE function, called the IAB-MT (Mobile Terminal). The IAB-DU implements network-side equipment functionality, is connected to downstream child IAB-nodes (or abbreviated as child nodes), provides NR air interface access to the UE and downstream child IAB-nodes, and establishes an F1 connection with the IAB donor-CU (Donor Central Unit). The IAB-MT implements some terminal equipment functionality, is connected to upstream parent IAB-nodes (or abbreviated as parent nodes) or IAB donor-DUs, and includes physical layer, layer 2, RRC (Radio Resource Control), and NAS (Non-Access Stratum) layer functionality, and is indirectly connected to the IAB Donor-CU and the Core Network (CN).

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

[0007] Figure 4 shows a single IAB node, a parent IAB node, and a child IAB node. As shown in Figure 4, the IAB-DU of the IAB node is connected to the IAB-MT of the child node as the network side, and the IAB-MT of the IAB node is connected to the IAB-DU of the parent node as the terminal side.

[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 established on top of the transmission (IP) layer between the IAB-DU and the IAB donor-CU, and Figures 5 and 6 include a two-hop wireless backhaul and a one-hop wired backhaul.

[0009] In a backhaul link, the transmission (IP) layer is carried by the backhaul adaptive protocol (BAP) sublayer. The BAP entity in the IAB-node implements the routing functionality of the IAB system, and the IAB donor-CU provides the routing table. BAP PDUs (Protocol Data Units) are transmitted over the RLC (Radio Link Control) channels of the backhaul link. Multiple RLC channels in the backhaul link can be configured by the IAB-donor to carry traffic with different priorities and QoS (Quality of Service), and the BAP entity maps the BAP PDUs to different backhaul RLC channels.

[0010] The above-mentioned introduction of background art is intended to clearly and completely explain the proposed technical aspects of the present invention and to facilitate understanding by those skilled in the art. These technical aspects, as described in the background art of the present invention, should not be construed as being well-known to those skilled in the art. [Overview of the project] [Problems that the invention aims to solve]

[0011] The inventors have discovered the following: When all or some of the operations of an IAB node need to be migrated or configured from an F1-terminating topology domain to a non-F1-terminating topology domain, all routing IDs of the IAB node belong to the non-F1-terminating topology domain, or the IAB node simultaneously transmits operations whose routing IDs belong to the F1-terminating topology domain and operations whose routing IDs belong to the non-F1-terminating topology domain. For routing IDs of the non-F1-terminating topology domain, the IAB node must use the IP address of the non-F1-terminating topology domain, and for routing IDs of the F1-terminating topology domain, the IAB node must use the IP address of the F1-terminating topology domain. The network needs to configure the IAB node with an IP address anchored to the donor-DU of the non-F1-terminating topology domain, or an IP address anchored to the donor-DU of the F1-terminating topology domain. However, there is currently no corresponding scheme for how to make requests to IP addresses in non-F1 terminated topology domains, or how to configure IP addresses in both F1 terminated and non-F1 terminated domains.

[0012] To solve at least one of the above-mentioned problems, embodiments of the present invention provide IAB donor equipment and a transmission address setting method. [Means for solving the problem]

[0013] According to one aspect of the embodiment of the present invention, a transmission address setting method is provided, which is applied to an F1 termination donor device of an IAB node, and the method is The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor; and / or The F1-terminated donor receives IP address configuration information for a non-F1-terminated topology domain to be assigned to the IAB node, transmitted by the non-F1-terminated donor; and / or This includes the F1-terminated donor transmitting IP address configuration information for the F1-terminated topology domain to be assigned to the IAB node to the non-F1-terminated donor.

[0014] According to another aspect of the embodiment of the present invention, a transmission addressing method is provided which is applied to a non-F1 terminated donor device of an IAB node, and the method is The non-F1 terminated donor receives IP address request information for the non-F1 terminated topology domain for the IAB node, transmitted by the F1 terminated donor; and / or The non-F1 terminating donor transmits IP address configuration information for the non-F1 terminating topology domain to be assigned to the IAB node to the F1 terminating donor; and / or The non-F1 terminating donor receives IP address configuration information for the F1 terminating topology domain assigned to the IAB node, which is transmitted by the F1 terminating donor.

[0015] According to another aspect of the embodiment of the present invention, an IAB donor device is provided, the IAB donor device being an F1-terminated donor device of an IAB node, the device comprising a first transmitting unit and / or a first receiving unit, The first transmitting unit is, Send IP address request information for the non-F1 termination topology domain for the IAB node to the non-F1 termination donor; and / or The non-F1 terminated donor transmits the IP address configuration information of the F1 terminated topology domain assigned to the IAB node. The first receiving unit receives IP address configuration information for a non-F1 terminating topology domain to be assigned to the IAB node, which is transmitted by the non-F1 terminating donor.

[0016] According to another aspect of the embodiments of the present invention, an IAB donor device is provided, the IAB donor device being a non-F1 terminated donor device of an IAB node, the device comprising a second receiving unit and / or a second transmitting unit, The second receiving unit is, Receive IP address request information for a non-F1 terminated topology domain for the IAB node transmitted by an F1 terminated donor; and / or The system receives IP address configuration information for the F1 termination topology domain assigned to the IAB node, transmitted by the F1 termination donor. The second transmission unit transmits IP address configuration information for the non-F1 termination topology domain assigned to the IAB node to the F1 termination donor.

[0017] According to another aspect of the embodiment of the present invention, a communication system is provided, the system including the IAB donor equipment described in the preceding aspect. [Effects of the Invention]

[0018] The advantageous effects of embodiments of the present invention are at least as follows: an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, or can cause an F1-terminated donor to request an IP address of a non-F1-terminated topology domain by further receiving IP address configuration information of a non-F1-terminated topology domain assigned for the IAB node by the non-F1-terminated donor, or can further send an IP address of a non-F1-terminated topology domain for the IAB node, for example, if the non-F1-terminated donor is unable to send a message to the IAB node. For example, if the non-F1-terminated donor is unable to send a message to the IAB node, the F1-terminated donor can send an IP address of a non-F1-terminated topology domain for the IAB node by receiving IP address configuration information of a non-F1-terminated topology domain that is voluntarily sent by the non-F1-terminated donor. Furthermore, for example, if an F1-terminated donor is unable to send a message to an IAB node, the F1-terminated donor can send IP address configuration information for the F1-terminated topology domain to a non-F1-terminated donor, thereby causing the non-F1-terminated donor to send the IP address of the F1-terminated topology domain to the IAB node. In this way, the IAB node can use the IP address of the non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain, and can use the IP address of the F1-terminated topology domain for the routing ID of the F1-terminated topology domain.

[0019] Specific embodiments of the present invention will be disclosed in detail by referring to the following description and drawings, and will show embodiments in which the principles of the present invention can be adopted. However, the embodiments of the present invention are not limited to these in scope. Embodiments of the present invention may include various changes, modifications and substitutions as long as they are within the scope of the attached claims.

[0020] Furthermore, features described and / or shown in one embodiment may be used in the same or similar manner in one or more other embodiments, combined with or substituting features in other embodiments.

[0021] Note that terms such as "comprising / including" when used in this specification also refer to the presence of features, elements, steps, or assemblies, but do not exclude the presence or addition of one or more other features, elements, steps, or assemblies.

Brief Description of the Drawings

[0022] Elements and features described in one drawing or one embodiment of the present invention can be combined with elements and features shown in one or more other drawings or embodiments. Also, in the drawings, like reference numerals indicate corresponding parts in several drawings and are also used to indicate corresponding parts used in multiple embodiments.

[0023] The included drawings are used to provide a further understanding of the embodiments of the present invention. These drawings form part of this specification, illustrate the embodiments of the present invention, and are used to explain the principles of the present invention together with the written description. Also, as is clear, the drawings described below are only for showing some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without creative labor. [[ID=!16]] [Figure 1] It is a diagram showing an IAB system. [Figure 2] It is a diagram showing the IAB architecture in SA mode. [Figure 3] It is a diagram showing the IAB architecture in EN-DC mode. [Figure 4] It is a diagram showing a parent IAB-node and a child IAB-node. [Figure 5] It is a diagram showing the F1-U protocol stack of an IAB system. [Figure 6] It is a diagram showing the F1-C protocol stack of an IAB system. [Figure 7] It is a diagram showing the routing of an IAB system. [Figure 8] It should be noted that in the translation, for the specific tags like , etc., they are preserved exactly as in the original because they are likely part of a specific technical or document format with their own significance and should not be modified without specific instructions. Also, the Japanese text in ID=3 is translated in a way that conforms to the common understanding of patent language in English. And for the text about combining elements from different drawings and embodiments in ID=10, the translation tries to convey the technical meaning accurately. Regarding the description of the role of drawings in ID=14, it is translated to clearly explain the function of the drawings in the context of the patent. For the descriptions of different diagrams in subsequent IDs, they are translated to be self - explanatory in the context of an IAB system related patent.This figure shows network topology adaptation. [Figure 9] This figure shows an IAB donor device in an embodiment of the present invention. [Figure 10] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 11] This is a diagram showing the switching scenario. [Figure 12] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 13] This figure shows dual connection scenario 1. [Figure 14] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 15] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 16] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 17] This figure shows dual connection scenario 2. [Figure 18] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 19] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 20] This figure shows the RLF recovery scenario. [Figure 21] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 22] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 23] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 24] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 25] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 26] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 27]This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 28] This figure shows a method for setting a transmission address in an embodiment of the present invention. [Figure 29] This figure shows an IAB donor device in an embodiment of the present invention. [Figure 30] This figure shows an IAB donor device in an embodiment of the present invention. [Modes for carrying out the invention]

[0024] The aforementioned and other features of the present invention will become clear by referring to the attached drawings and the following description. While the specification and drawings disclose specific embodiments of the present invention, these represent only a limited number of embodiments in which the principles of the present invention can be employed. It should be understood that the present invention is not limited to the described embodiments, but rather includes all modifications, variations, and substitutions within the scope of the attached claims.

[0025] In embodiments of the present invention, the terms "communication network" or "wireless communication network" may refer to a network conforming to any communication standard such as NR (New Radio), LTE (Long Term Evolution), LTE-A (LTE-Advanced), WCDMA (Wideband Code Division Multiple Access), HSPA (High-Speed ​​Packet Access), etc.

[0026] Furthermore, communication between devices in a communication system may be carried out according to any stage of communication protocol, and may include, but is not limited to, the following communication protocols: namely, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, New Radio (NR), and / or other conventional or future-developed communication protocols.

[0027] In embodiments of the present invention, the term "network device" refers, for example, to a device in a communication system that connects terminal devices to a communication network and provides services to said terminal devices. Network devices may include, but are not limited to, the following: "nodes" and / or "donors" in the IAB architecture, base stations (BS), access points (AP), transmission and reception points (TRP), broadcast transmitters, mobile management entities (MME), network gateways, servers, radio network controllers (RNC), base station controllers (BSC), etc.

[0028] Among these, base stations may include, but are not limited to, Node B (NodeB or NB), Evolutionary Node B (eNodeB or eNB), 5G base stations (gNB), and may also include RRH (Remote Radio Head), RRU (Remote Radio Unit), relay, or low-power nodes (e.g., femto, pico). Furthermore, the term “base station” may include some or all of these functions, and each base station can provide communication coverage to a specific geographical area. For example, a 5G base station gNB may include one gNB CU and one or more gNB DUs, where the CU / DU is a logical node of the gNB having some of the functions of the gNB. The term “cell” may refer to a base station and / or the area it covers, depending on the context in which the term is used.

[0029] In embodiments of the present invention, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer to devices that access a communication network via network equipment and receive services from the network. User equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), or station. For example, it may be terminal equipment served by an IAB node or IAB donor under an IAB architecture.

[0030] User devices may include, but are not limited to, the following: cellular phones, PDAs (Personal Digital Assistants), wireless modems, wireless communication devices, mobile devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smartwatches, digital cameras, etc.

[0031] Furthermore, in scenarios such as IoT (Internet of Things), user devices may also be monitoring or measuring devices or equipment, and may include, but are not limited to, the following: machine-type communication (MTC) terminals, in-vehicle communication terminals, D2D (device-to-device) terminals, M2M (machine-to-machine) terminals, etc.

[0032] Furthermore, the terms “network side” or “network device side” refer to the network side, which may be a base station and may include one or more network devices as described above. The terms “user side” or “terminal side” or “terminal device side” refer to the user or terminal side, which may be a UE and may include one or more terminal devices as described above.

[0033] The signaling radio bearers SRBs include SRB0, SRB1, SRB2, and SRB3, of which SRB0, SRB1, and SRB2 are for the MN, and SRB3 is for the SN. The signaling radio bearers are radio bearers for transmitting 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, and uses the dedicated control channel (DCCH) logical channel. SRB2 transmits RRC messages, including NAS messages and log measurement messages, and uses the DCCH logical channel. SRB2 has a lower priority than SRB1 and may be set up by the network after the access stratum (AS) has been safely activated. SRB3 is used for certain RRC messages when the UE is in (NG)EN-DC or NR-DC, and uses the DCCH logical channel.

[0034] The routing function of the IAB system is implemented by the BAP layer, and each IAB-node node stores routing configurations (BH routing configuration) and RLC channel mapping configurations (BH RLC Channel Mapping Configuration). The BAP entity performs routing based on the routing configuration, RLC channel mapping configuration, and routing ID in the BAP layer data packet header. The routing ID includes the destination BAP address and route indicator.

[0035] Routing configurations include the mapping relationship between the Routing ID and the next-hop node BAP address. RLC channel mapping configurations include the mapping relationship between the prior-hop node BAP address, the inlet link RLC channel ID, the next-hop node BAP address, and the outlet link RLC channel ID.

[0036] Figure 7 shows the routing of the IAB system. As shown in Figure 7, for each data packet, the routing ID in the data packet header allows us to find the next-hop node BAP address from the routing configuration. The primary hop node BAP address and the inlet link RLC channel ID are all known. In this way, after the next-hop node BAP address is determined, the RLC channel mapping configuration allows us to find the exit link RLC channel ID based on the primary hop node BAP address + inlet link RLC channel ID + next-hop node BAP address.

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

[0038] For each downlink data packet reaching the IAB-donor DU, the IAB-donor DU can find the next-hop node address from the routing configuration based on the Routing ID in the data packet header. After the next-hop node address is determined in this way, the IAB-donor DU can find the exit link RLC channel ID from the downlink RLC channel mapping configuration based on the IP address and DSCP of the data packet.

[0039] Access IAB nodes store uplink backhaul information (BH information), which includes 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 sets the routing ID in the BAP layer data packet header for uplink services and selects the BH RLC channel and next-hop node for uplink service transmission.

[0040] The above describes the routing and BH RLC channel mapping of the IAB system. Next, we will describe the updating of the network topology of the IAB system. Rel-16 NR already standardizes the topology adaptation process when IAB-nodes move under the same donor-CU.

[0041] Figure 8 shows the intra-CU topology adaptation. When an IAB-node changes its parent node (from IAB-node 1 to IAB-node 2), the donor-CU uses an RRC reconfiguration message to set up path transition settings for the IAB-node, causing the IAB-node to perform the F1 transmission path transition.

[0042] The path transition settings include updating the default backhaul RLC channel (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 to which the data is routed to the Donor-DU. When an IAB-node accesses a new parent node, it begins applying the aforementioned path transition settings, and similarly configures its child nodes for path transitions.

[0043] 3GPP® Rel-17 supports network topology updates and backhaul (BH) radio link failure (RLF) recovery processes when an IAB-node moves under a different donor-CU. The IAB-node can switch or re-establish itself from a parent node served by a source donor (which may be called an F1-terminating CU or first donor-CU) to a parent node served by a target donor (which may be called a non-F1-terminating CU or second donor-CU), and all operations of the IAB-node (and the operations of its child nodes) must be migrated to the non-F1-terminating CU topology. Rel-17 also supports topology redundancy when an IAB-node establishes a dual connection with a non-F1-terminating CU, allowing the transmission paths of some operations of the IAB-node to be migrated to the non-F1-terminating CU topology.

[0044] After an IAB-node switches from donor-CU 1 (F1-terminating CU) to donor-CU 2 (non-F1-terminating CU) and recovers RLF, or after an increase in RRC connections with donor-CU 2, the RRC for IAB-MT only is connected to donor-CU 2, and the F1 interface is still terminated at donor-CU 1. At this point, the IAB-node may be called a boundary node. Since the RRC connections and F1 interfaces of the child nodes it serves still belong to donor-CU1, the routing ID, BH RLC channel, and next-hop BAP address of the child nodes' operations still belong to the topology domain of donor-CU1.

[0045] All routing IDs of a boundary node belong to a non-F1-terminating topology domain, or a boundary node simultaneously transmits traffic where routing IDs belong to an F1-terminating topology domain and traffic where routing IDs belong to a non-F1-terminating topology domain. For routing IDs in a non-F1-terminating topology domain, the boundary node must use IP addresses of the non-F1-terminating topology domain, and for routing IDs in an F1-terminating topology domain, the boundary node must use IP addresses of the F1-terminating topology domain. The network needs to configure IP addresses anchored to the donor-DU of a non-F1-terminating topology domain, or IP addresses anchored to the donor-DU of an F1-terminating topology domain, for the boundary node. However, there is currently no corresponding scheme for how to request IP addresses in a non-F1-terminating topology domain, or how to configure IP addresses in both F1-terminating and non-F1-terminating domains.

[0046] In embodiments of the present invention, unless otherwise specified, the IAB node equipment includes a transition node. Furthermore, “resources for serving the IAB node’s operations are already established in the donor-CU’s topology domain” may also be expressed as “the IAB node’s operations are being migrated to the donor-CU’s topology domain,” but the present invention is not limited to these expressions. Embodiments of the present invention will be further described below.

[0047] <Example of the first side view> An embodiment of the present invention provides a transmission address setting method, which will be explained from the perspective of the F1 termination donor device of the IAB node.

[0048] Figure 10 shows a method for setting a transmission address in an embodiment of the present invention. As shown in Figure 10, the method includes the following steps (operations).

[0049] 1001: The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor; and / or The F1-terminated donor receives IP address configuration information for the non-F1-terminated topology domain assigned to the IAB node, transmitted by the non-F1-terminated donor; and / or The F1-terminated donor transmits IP address configuration information for the F1-terminated topology domain assigned to the IAB node to the non-F1-terminated donor.

[0050] Figure 10 above is merely illustrative to illustrate an embodiment of the present invention, and the present invention is not limited thereto. For example, the execution order between each operation can be appropriately changed, or some operations can be added or removed. Those skilled in the art can make appropriate modifications based on the above description, without being limited to the description in Figure 10.

[0051] As can be seen from the embodiments described above, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, or can cause an F1-terminated donor to request an IP address of a non-F1-terminated topology domain by receiving IP address configuration information for a non-F1-terminated topology domain assigned for the IAB node by the non-F1-terminated donor, or can send an IP address of a non-F1-terminated topology domain for the IAB node, for example, if the non-F1-terminated donor is unable to send a message to the IAB node. For example, if the non-F1-terminated donor is unable to send a message to the IAB node, the F1-terminated donor can send an IP address of a non-F1-terminated topology domain for the IAB node by receiving IP address configuration information for a non-F1-terminated topology domain that is voluntarily sent by the non-F1-terminated donor. Furthermore, for example, if an F1-terminated donor is unable to send a message to an IAB node, the F1-terminated donor can send IP address configuration information for the F1-terminated topology domain to a non-F1-terminated donor, thereby causing the non-F1-terminated donor to send the IP address of the F1-terminated topology domain to the IAB node. In this way, the IAB node can use the IP address of the non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain, and can use the IP address of the F1-terminated topology domain for the routing ID of the F1-terminated topology domain.

[0052] In some embodiments, an IAB node includes a transition node (also called a boundary node), the F1 connection of the IAB node is terminated by an F1-terminated donor, and the IAB node has an RRC connection with the non-F1-terminated donor. For example, the IAB-MT of an IAB node maintains an RRC connection with the non-F1-terminated donor, the F1-terminated donor device may be a first IAB donor-CU (donor-centralized unit), and the non-F1-terminated donor device may be a second IAB donor-CU (donor-centralized unit). The F1-terminated donor device refers to a donor-CU that terminates the F1 interface of the boundary IAB node and its child IAB nodes, for example, the first IAB donor-CU. The non-F1-terminated donor device refers to a CU with donor functionality that does not terminate the F1 interface of the boundary IAB node and its child IAB nodes, for example, the second IAB donor-CU.

[0053] In some embodiments, the request and / or configured IP address refers to an IP address anchored to a donor-DU that is configured for (or relating to) the IAB node, and the IP address configuration information may include IP address configurations anchored to at least two donor-DUs, or at least one IP address configuration anchored to one donor-DU, and each IP address configuration may include an IP address index and a corresponding IP address, and embodiments of the present invention are not limited thereto.

[0054] In embodiments of the present invention, “IP address anchored to IAB donor-DU” may be understood as “IP address assigned by donor-DU” or “Transmission Network Layer (TNL) address(es) that is (are) routable via the IAB-donor-DU,” and these terms are interchangeable, but the present invention is not limited thereto. For example, the IP address of a donor-DU in a non-F1-terminated topology domain configured for the IAB node refers to a Transmission Network Layer (TNL) address configured for the IAB node that is routable via a donor-DU in a non-F1-terminated topology domain.

[0055] In some embodiments, the above-mentioned IP address request information and / or IP address configuration information may be carried by the RRC container, or by an IAB transmission transition management request / response or an IAB transmission transition change request. Each of these will be explained below.

[0056] (i) IP address request information and / or IP address configuration information are carried by the RRC container. In some embodiments, IP address request information is carried by a first RRC container, for example, by other IAB information messages (information element structure IABOtherInformation) or RRC reconfiguration messages contained within the first RRC container, the first RRC container containing IP address configuration information for the IAB node in the F1 termination topology domain. The IABOtherInformation message is an RRC message for the IAB node to request an IP address from the network and report the IP address it will actually use or the IP address the network has already assigned for the IAB node. In this embodiment, instead of the IAB node requesting an IP address in a non-F1 topology domain, the F1 termination donor simulates the IAB node to generate an IABOtherInformation message, includes it in the first RRC container, and sends it to the non-F1 termination donor. The RRC reconfiguration message is an RRC message in which the network configures an IP address for the IAB node. In this embodiment, the F1-terminated donor generates an RRC reconfiguration message and sends it to the non-F1-terminated donor, including it in the first RRC container, to request an IP address for the non-F1 topology domain.

[0057] In some embodiments, IP address configuration information is carried by a second RRC container, for example, by an RRC reconfiguration message contained within the second RRC container.

[0058] Existing RRC messages (e.g., IABOtherInformation) are used by IAB nodes to request IP addresses from donors, while RRCReconfiguration messages are used to configure IP addresses on IAB nodes. Therefore, by reusing RRC messages (e.g., IABOtherInformation) to carry IP address request information for boundary nodes, and reusing RRCReconfiguration messages to carry IP address configuration information for boundary nodes, IP address requests and configurations can be made simpler and more flexible.

[0059] In some embodiments, the aforementioned IP addresses may be requested and / or configured using existing Xn processes (which may be carried by Xn Interface Applying Protocol (XnAP) signaling), such as handover preparation, dual connection establishment or change processes, and UE context acquisition processes. For example, the first RRC container is carried by at least one of the following messages: a handover request message; a secondary node addition request message; a secondary node change request message; a secondary node change request message; and a UE context acquisition response message. The second RRC container is carried by at least one of the following messages: a handover request response message (also known as a handover request confirmation message); a secondary node addition response message; a secondary node change response message; and a secondary node change request message. Different scenarios will be explained below. Furthermore, since these Xn processes are processes for the boundary node, they can be naturally distinguished from IP address requests and configuration information for child nodes, thereby allowing the donor to send IP address configurations for the boundary node using the RRC connection with the boundary node.

[0060] I. Regarding the switching scenario In some embodiments, Figure 11 is a diagram illustrating a transition scenario, in which, as shown in Figure 11, all operations of the boundary node are migrated to a non-F1 terminated topology domain, the F1 terminated donor is the source donor for the IAB node transition, the non-F1 terminated donor is the target donor for the IAB node transition, the IP address of the non-F1 terminated topology domain refers to the IP address anchored to donor-DU2, and Figure 12 is a diagram illustrating a transmission address configuration method under the transition scenario, in which, as shown in Figure 12, the method includes the following steps.

[0061] 1201: The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor; and 1202: The F1-terminated donor receives IP address configuration information for the non-F1-terminated topology domain to be assigned to the IAB node, which is transmitted by the non-F1-terminated donor.

[0062] In some embodiments, the IP address request information is carried by a first RRC container, the IP address configuration information is carried by a second RRC container, the first RRC container is carried by a switching request message, and the second RRC container is carried by a switching request response message. Thus, an F1-terminated donor sends a switching request message (HANDOVER REQUEST) to a non-F1-terminated donor, for example, the switching request message includes an RRC message HandoverPreparationInformation, which may contain the entire RRC message IABOtherInformation generated by the F1-terminated donor, which is the first RRC container and carries the IP address request information (IAB-TNLAddressInfo area) of the non-F1-terminated topology domain, and which may further include IP address configuration information in the F1-terminated topology domain of the boundary node. A non-F1 terminating donor sends a switching request response (HANDOVER REQUEST ACKNOWLEDGE) back to the F1 terminating donor. For example, this switching request response includes the RRC message HandoverCommand, which carries the entire RRC message RRCReconfiguration generated by the non-F1 terminating donor. RRCReconfiguration becomes a second RRC container and carries the IP address configuration information (iab-IP-AddressConfigurationList-r16 area) for the non-F1 terminating topology domain.

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

[0064] [Table 1] The IABOtherInformation can be described using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0065] [Table 2] IABOtherInformation may carry over the number of IP addresses requested for various tasks, or the IP addresses actually used by various tasks.

[0066] The HandoverCommand can be written using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0067] [Table 3] The RRCReconfiguration can be written using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0068] [Table 4] In some embodiments, the IAB-IP-AddressConfigurationList-r16 of the non-F1 terminated topology domain carried by the RRCReconfiguration includes an IP address addition and modification list and an IP address release list, each list containing at least one IP address configuration IAB-IP-AddressConfiguration-r16, and each IP address configuration may contain an IP address index and a corresponding IP address.

[0069] Therefore, in order to request the IP address of a non-F1 terminated topology domain, a new RRC container IABOtherInformation can be introduced into the failover request message, and the IP address configuration information element contained in the RRC container RRCReconfiguration in the failover request response message can be used to carry the IP address of the non-F1 terminated topology domain for the boundary node.

[0070] The above is an example in which IP address request information is carried by IABOtherInformatio contained in the first RRC container. In addition, IP address request information may be further carried by RRC reconfiguration messages contained in the first RRC container, but the embodiments of the present invention are not limited to this.

[0071] In some embodiments, the method may further include the following steps:

[0072] 1203: The F1-terminated donor transmits the IP address configuration information it receives to the IAB node, for example, the F1-terminated donor forwards a HandoverCommand generated by a non-F1-terminated donor, the HandoverCommand carries the entire RRC message RRCReconfiguration generated by the non-F1-terminated donor, and RRCReconfiguration carries the IP address configuration information for the non-F1-terminated topology domain.

[0073] As can be seen from the embodiments described above, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, or can cause an F1-terminated donor to request an IP address of a non-F1-terminated topology domain by further receiving IP address configuration information of a non-F1-terminated topology domain assigned for the IAB node by the non-F1-terminated donor, or can further send an IP address of a non-F1-terminated topology domain for the IAB node if the non-F1-terminated donor is unable to send a message to the IAB node. In this way, the IAB node can use the IP address of a non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain.

[0074] II. Dual Connection Scenario 1 In some embodiments, Figure 13 shows a dual connection scenario 1. As shown in Figure 13, in dual connection scenario 1, the F1-terminated donor is the main node (also called the master node) MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node. After the dual connection is established, some operations of the boundary node can be migrated to the non-F1-terminated topology domain, while some operations remain in the F1-terminated donor topology domain. The IP address of the non-F1-terminated topology domain refers to the IP address anchored to donor-DU2. The IP address of the non-F1-terminated topology domain may be requested during the dual connection establishment process, or the IP address of the non-F1-terminated topology domain or the IP address of the F1-terminated topology domain may be requested / configured after the dual connection is established. Each of these will be explained below.

[0075] Figure 14 is a diagram illustrating one method of setting the transmission address under the dual connection scenario 1, and as shown in Figure 14, the method includes the following steps.

[0076] 1401: The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor; and 1402: The F1-terminated donor receives IP address configuration information for the non-F1-terminated topology domain to be assigned to the IAB node, which is transmitted by the non-F1-terminated donor.

[0077] In some embodiments, during the process of adding a secondary cell group, an IP address of a non-F1 terminated topology domain is requested, the IP address request information is carried by a first RRC container, 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. In the process of adding a Secondary Cell Group, an F1 terminated donor sends a secondary node addition request message (S-node AdditionRequest) to a non-F1 terminated donor, for example, the RRC message CG-ConfigInfo contained therein contains the entire RRC message IABOtherInformation generated by the F1 terminated donor, the IABOtherInformation becomes the first RRC container, and carries the IP address request information (IAB-TNLAddressInfo area (field)) of the non-F1 terminated topology domain. A non-F1 terminating donor sends a secondary node addition response message (S-node Addition Response) back to the F1 terminating donor, and the secondary cell group configuration information area scg-CellGroupConfig in the RRC message CG-Config contained within it carries the entire RRC message RRCReconfiguration generated by the non-F1 terminating donor. If the SN does not establish SRB3 (in which case the SN cannot directly send an RRC message to the IAB node), RRCReconfiguration becomes a second RRC container and carries the IP address configuration information (iab-IP-AddressConfigurationList-r16 area) of the non-F1 terminating topology domain.

[0078] Figure 15 is a diagram illustrating another method of setting the transmission address under the dual connection scenario 1, which, as shown in Figure 15, includes the following steps:

[0079] 1501: The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor; and 1502: The F1-terminated donor receives IP address configuration information for the non-F1-terminated topology domain to be assigned to the IAB node, which is transmitted by the non-F1-terminated donor.

[0080] In some embodiments, after dual connection establishment is complete, during the process of changing the secondary cell pair, an IP address of a non-F1 terminated topology domain is requested, the IP address request information is carried by the first RRC container, the IP address configuration information is carried by the second RRC container, the first RRC container is carried by the secondary node change request message, and the second RRC container is carried by the secondary node change response message. In the process of modifying a Secondary Cell Group, an F1-terminal donor sends a Secondary Node Modification Request message (S-node Modification Request) to a non-F1-terminal donor. For example, the RRC message CG-ConfigInfo contained within it contains the entire RRC message IABOtherInformation generated by the F1-terminal donor. This IABOtherInformation acts as the first RRC container and carries the IP address request information (IAB-TNLAddressInfo area) of the non-F1-terminal topology domain. The non-F1-terminal donor then sends a Secondary Node Modification Response message (S-node Modification Response) back to the F1-terminal donor. The secondary cell group configuration information (scg-CellGroupConfig area) contained within the RRC message CG-Config contains the entire RRC message RRCReconfiguration generated by the non-F1-terminal donor. If SN does not establish SRB3, RRCReconfiguration becomes a second RRC container and carries IP address configuration information (iab-IP-AddressConfigurationList-r16 area) for non-F1 terminated topology domains.

[0081] The CG-ConfigInfo can be described using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0082] [Table 5] The CG-Config can be written using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0083] [Table 6] The description of the RRCReconfiguration using the Abstract Syntax Notation One (ASN.1) data format is as described above, and a detailed explanation is omitted here.

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

[0085] The above is an example in which IP address request information is carried by IABOtherInformatio contained in the first RRC container. In addition, IP address request information may be further carried by RRC reconfiguration messages contained in the first RRC container, but the embodiments of the present invention are not limited to this.

[0086] In some embodiments, if SN does not establish SRB3, the method may further include the following steps.

[0087] 1403 / 1503: The F1-terminated donor transmits the IP address configuration information it receives to the IAB node, for example, the F1-terminated donor forwards the RRCReconfiguration in the CG-Config generated by the non-F1-terminated donor, and the RRCReconfiguration carries the IP address configuration information of the non-F1-terminated topology domain.

[0088] In 1503, optionally, if the SN establishes SRB3, the non-F1 terminated donor may further transmit the IP address configuration information to the IAB node, but this is not limited to the embodiments of the present invention.

[0089] As can be seen from the embodiments described above, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, or can cause an F1-terminated donor to request an IP address of a non-F1-terminated topology domain by further receiving IP address configuration information of a non-F1-terminated topology domain assigned for the IAB node by the non-F1-terminated donor, or can further send an IP address of a non-F1-terminated topology domain for the IAB node if the non-F1-terminated donor is unable to send a message to the IAB node. In this way, the IAB node can use the IP address of a non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain.

[0090] Figure 16 is a diagram illustrating yet another method of setting the transmission address under the dual connection scenario 1, which, as shown in Figure 16, includes the following steps:

[0091] 1601: The F1-terminated donor receives IP address configuration information for the non-F1-terminated topology domain to be assigned to the IAB node, transmitted by the non-F1-terminated donor, and the second RRC container is carried by the secondary node change request message.

[0092] In some embodiments, the differences from Figure 15 are as follows: if the SN does not establish SRB3 after the dual connection is established, the F1-terminated donor is not required to spontaneously request an IP address for the non-F1-terminated topology domain. The non-F1-terminated donor can spontaneously initiate IP address reconfiguration for the non-F1-terminated topology domain, and this IP address configuration information is carried by a second RRC container, which is carried by a secondary node change request message.

[0093] For example, in the process of changing a secondary cell group, a non-F1 terminating donor sends a secondary node modification request message (S-node Modification Required) to an F1 terminating donor. The secondary cell group configuration information (scg-CellGroupConfig area) contained within this message, for example, carries the entire RRC message RRCReconfiguration generated by the non-F1 terminating donor. RRCReconfiguration is considered a second RRC container and carries the IP address configuration information for the non-F1 terminating topology domain, which is also called IP address reconfiguration information.

[0094] Therefore, the IP address configuration information element included in the RRC container RRCReconfiguration in the secondary node change request message can carry the IP address of the non-F1 terminated topology domain that is reconfigured for the boundary node.

[0095] In some embodiments, if SN does not establish SRB3, the method may further include the following steps.

[0096] 1602: The F1-terminated donor forwards the IP address configuration information it receives to the IAB node, for example, the F1-terminated donor forwards the RRCReconfiguration in the CG-Config generated by the non-F1-terminated donor, and the RRCReconfiguration carries the IP address configuration information of the non-F1-terminated topology domain.

[0097] As can be seen from the above embodiment, an F1-terminated donor can receive IP address configuration information for a non-F1-terminated topology domain voluntarily sent by a non-F1-terminated donor, and can then send the IP address of the non-F1-terminated topology domain on behalf of the IAB node if the non-F1-terminated donor is unable to send a message to the IAB node. In this way, the IAB node can use the IP address of the non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain.

[0098] III. Dual Connection Scenario 2 In some embodiments, Figure 17 shows a dual connection scenario 2. As shown in Figure 17, in dual connection scenario 2, the F1-terminated donor is the secondary node SN CU of the IAB node, and the non-F1-terminated donor is the main node MN CU of the IAB node. After the dual connection is established, some operations of the boundary node can be migrated to the non-F1-terminated topology domain, while some operations remain in the F1-terminated donor topology domain. The IP address of the non-F1-terminated topology domain refers to the IP address anchored to donor-DU1, and the IP address of the F1-terminated topology domain refers to the IP address anchored to donor-DU2. Since the F1 connection is completed after the dual connection is established, the difference from dual connection scenario 1 is as follows: the IP address of the non-F1-terminated topology domain cannot be requested during the dual connection establishment process, and the IP address of the non-F1-terminated topology domain or the IP address of the F1-terminated topology domain can only be requested / set after the dual connection is established. These will be explained below.

[0099] Figure 18 is a diagram illustrating one method of setting the transmission address under the dual connection scenario 2, and as shown in Figure 18, the method includes the following steps.

[0100] 1801: The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor.

[0101] In some embodiments, after dual connection establishment is complete, during the process of changing the secondary cell group, an IP address of a non-F1 terminating topology domain is requested, and this IP address request information is carried by a first RRC container, which in turn is carried by a secondary node change request message. The F1 terminating donor sends a secondary node change request message to the non-F1 terminating donor, for example, by introducing IP address request information (IAB-TNLAddressInfo area) into the RRC message CG-Config contained therein, which carries the entire RRC message IABOtherInformation generated by the F1 terminating donor, which serves as the first RRC container and carries the IP address request information of the non-F1 terminating topology domain. The IP address set by the non-F1 terminating donor can be sent directly to the boundary node by the non-F1 terminating donor via SRB1. Therefore, the non-F1 terminating donor does not need to send the IP address setting information back to the F1 terminating donor; in other words, the F1 terminating donor does not receive the IP address setting information sent by the non-F1 terminating donor.

[0102] The CG-Config can be written using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0103] [Table 7] Therefore, a new RRC container, IABOtherInformation, can be introduced in secondary node change request messages to request IP addresses for non-F1 terminated topology domains.

[0104] The above is an example in which IP address request information is carried by IABOtherInformatio contained in the first RRC container. In addition, IP address request information may be further carried by RRC reconfiguration messages contained in the first RRC container, but the embodiments of the present invention are not limited to this.

[0105] In some embodiments, the method may further include the following steps.

[0106] 1802: The non-F1 terminating donor sends IP address configuration information to the IAB node, for example, the non-F1 terminating donor generates an RRCReconfiguration, which carries the IP address configuration information for the non-F1 terminating topology domain.

[0107] As can be seen from the above embodiment, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, thereby causing the F1-terminated donor to request an IP address of a non-F1-terminated topology domain and the non-F1-terminated donor to send the IP address of the non-F1-terminated topology domain to the IAB node. In this way, the IAB node can use the IP address of the non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain.

[0108] Figure 19 is a diagram illustrating another method of setting the transmission address under the dual connection scenario 2, which, as shown in Figure 19, includes the following steps:

[0109] 1901: The F1-terminated donor transmits IP address configuration information for the F1-terminated topology domain to be assigned for the IAB node to the non-F1-terminated donor, and the second RRC container is carried by the secondary node change request message.

[0110] In some embodiments, if the SN does not establish SRB3 after the dual connection is established, the F1 termination donor may spontaneously initiate IP address reconfiguration for the F1 termination topology domain, the IP address configuration information being carried by a second RRC container, the second RRC container being carried by a secondary node change request message.

[0111] For example, in the process of changing a secondary cell group, an F1-terminated donor sends a secondary node modification request message (S-node Modification Required) to a non-F1-terminated donor. The secondary cell configuration information (scg-CellGroupConfig area) contained within this message, for example, carries the entire RRC message RRCReconfiguration generated by the F1-terminated donor. RRCReconfiguration acts as a second RRC container and carries the IP address configuration information for the F1-terminated topology domain, which is also called IP address reconfiguration information.

[0112] The CG-Config can be written using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0113] [Table 8] Therefore, the existing IP address configuration information element in the secondary node change request message can indicate the IP address of the F1 termination topology domain that will be reconfigured for the boundary node.

[0114] In some embodiments, if SN does not establish SRB3, the method may further include the following steps.

[0115] 1902: The non-F1 terminating donor forwards the IP address configuration information of the F1 terminating topology domain it receives to the IAB node. For example, the non-F1 terminating donor forwards the RRCReconfiguration in the CG-Config generated by the F1 terminating donor, and the RRCReconfiguration carries the IP address configuration information of the F1 terminating topology domain.

[0116] As can be seen from the above embodiment, an F1-terminated donor can send IP address configuration information for the F1-terminated topology domain to a non-F1-terminated donor, thereby causing the non-F1-terminated donor to send the IP address of the F1-terminated topology domain to the IAB node if the F1-terminated donor is unable to send a message to the IAB node. In this way, the IAB node can use the IP address of the F1-terminated topology domain for the routing ID of the F1-terminated topology domain.

[0117] IV. About the RLF Recovery Scenario In some embodiments, Figure 20 is a diagram illustrating an RLF recovery scenario, in which, as shown in Figure 20, the F1-terminated donor is the donor of the IAB node before RLF recovery (old donor CU), the non-F1-terminated donor is the donor of the IAB node after RLF recovery (new donor CU), the IP address of the non-F1-terminated topology domain refers to the IP address anchored to donor-DU2, and Figure 21 is a diagram illustrating a transmission address configuration method under the switching scenario, in which, as shown in Figure 21, the method includes the following steps.

[0118] 2101: The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor.

[0119] In some embodiments, the IP address of a non-F1 terminated topology domain is requested during the UE context acquisition process, the IP address request information is carried by a first RRC container, and the first RRC container is carried by the UE context acquisition response message. Therefore, a non-F1 terminating donor sends a RETRIEVE UE CONTEXT REQUEST message to an F1 terminating donor, and the F1 terminating donor sends a RETRIEVE UE CONTEXT RESPONSE message back to the non-F1 terminating donor. For example, the RETRIEVE UE CONTEXT RESPONSE message may contain an RRC message HandoverPreparationInformation, which may contain the entire RRC message IABOtherInformation generated by the F1 terminating donor. This IABOtherInformation serves as the first RRC container and carries IP address request information (IAB-TNLAddressInfo area) for the non-F1 terminating topology domain. The IABOtherInformation may further contain IP address configuration information for the boundary node in the F1 terminating topology domain. Since IP address configuration information can only be sent by the non-F1 terminating donor after the boundary node has re-established itself with the non-F1 terminating donor, the non-F1 terminating donor does not need to send the IP address configuration information back to the F1 terminating donor. In other words, the F1 terminating donor does not receive IP address configuration information sent by the non-F1 terminating donor.

[0120] Therefore, a new RRC container, IABOtherInformation, can be introduced in the UE context retrieval response message to request IP addresses for non-F1 terminated topology domains.

[0121] The above is an example in which IP address request information is carried by IABOtherInformatio contained in the first RRC container. In addition, IP address request information may be further carried by RRC reconfiguration messages contained in the first RRC container, but the embodiments of the present invention are not limited to this.

[0122] In some embodiments, the method may further include the following steps.

[0123] 2102: The non-F1 terminating donor sends IP address configuration information to the IAB node, for example, the non-F1 terminating donor generates an RRCReconfiguration, which carries the IP address configuration information for the non-F1 terminating topology domain.

[0124] As can be seen from the above embodiment, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, thereby causing the F1-terminated donor to request an IP address of a non-F1-terminated topology domain and the non-F1-terminated donor to send an IP address of a non-F1-terminated topology domain to the IAB node. In this way, the IAB node can use the IP address of a non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain.

[0125] (ii) IP address request information and / or IP address configuration information are carried by an IAB transmission transition management request / response or an IAB transmission transition change request. In some embodiments, IP address request information is carried by an IAB transmission transition management request message, which further includes a boundary node indicator used to indicate that the IAB node is a boundary node, i.e., indicates IP address request information for a boundary node; and IP address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message, which includes a boundary node indicator used to indicate that the IAB node is a boundary node, i.e., indicates IP address configuration information to be configured for a boundary node.

[0126] Since IAB transmission transition management requests / responses, or IAB transmission transition change requests, are specific to IAB nodes and do not relate to AS layer configuration, requesting and configuring IP addresses for non-F1 terminated topology domains using IAB transmission transition management requests / responses, or IAB transmission transition change requests makes requesting and configuring IP addresses simpler and more flexible.

[0127] I. Regarding the switching scenario In some embodiments, as shown in Figure 11, in the transition scenario, all operations of the boundary node are migrated to a non-F1 terminated topology domain, the F1 terminated donor is the source donor for the IAB node transition, the non-F1 terminated donor is the target donor for the IAB node transition, the IP address of the non-F1 terminated topology domain refers to the IP address anchored to donor-DU2, Figure 22 is a diagram showing how to configure the transmission address under the transition scenario, and as shown in Figure 22, the method includes the following steps.

[0128] 2201: The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor.

[0129] In some embodiments, the IP address request information is carried by an IAB Transport Migration Management Request message. Thus, after switching preparations, an F1-terminated donor sends an IAB Transport Migration Management Request message to a non-F1-terminated donor, which may carry, for example, an IAB TNL Address Request for an IP address request information for a non-F1-terminated topology domain, which may further include a boundary node indicator used to indicate that the IAB node is a boundary node, i.e., that the IP address request information is an IP address request information for a non-F1-terminated topology domain for a boundary node.

[0130] The IAB TNL ADDRESS REQUEST can be written using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0131] [Table 9] Of these, the IAB TNL ADDRESS REQUEST field includes the IAB TNL Addresses Requested area, which contains request information for IPv4 or IPv6 addresses, and the Boundary Node area, which indicates a boundary node.

[0132] The data format for IAB TNL Addresses Requested can be described as follows:

[0133] [Table 10] Among these, "IAB TNL Addresses Requested" includes requests for the number of IP addresses for various services.

[0134] Since RRC messages can be sent to boundary nodes only by the target donor after the switchover, non-F1 terminating donors do not need to send back IP address configuration information for their non-F1 terminating topology domain to the F1 terminating donors.

[0135] Therefore, a new information element, IAB TNL ADDRESS REQUEST, can be introduced into the IAB Transmission Transition Management Request message to request the IP address of a non-F1 terminated topology domain for a boundary node.

[0136] In some embodiments, the method may further include the following steps.

[0137] 2202: The non-F1 terminating donor sends IP address configuration information to the IAB node. For example, the non-F1 terminating donor generates the entire RRC message RRCReconfiguration, which carries the IP address configuration information for the non-F1 terminating topology domain and sends it to the boundary node. The description of RRCReconfiguration using the Abstract Syntax Notation One (ASN.1) data format is as described above, and a detailed explanation is omitted here.

[0138] In some embodiments, the IAB-IP-AddressConfigurationList-r16 of the non-F1 terminated topology domain carried by the RRCReconfiguration includes at least one IAB-IP-AddressConfiguration-r16, each of which may include an IP address index and a corresponding IP address.

[0139] As can be seen from the above embodiment, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, thereby causing the F1-terminated donor to request an IP address of a non-F1-terminated topology domain and the non-F1-terminated donor to send an IP address of a non-F1-terminated topology domain to the IAB node. In this way, the IAB node can use the IP address of a non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain.

[0140] II. Dual Connection Scenario 1 In some embodiments, as shown in Figure 13, in dual connection scenario 1, the F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node. After the dual connection is established, some operations of the boundary node can be moved to the non-F1-terminated topology domain, while some operations remain in the F1-terminated donor topology domain. The IP address of the non-F1-terminated topology domain refers to the IP address anchored to donor-DU2.

[0141] Figure 23 is a diagram illustrating one method of setting the transmission address under the dual connection scenario 1, and as shown in Figure 23, the method includes the following steps.

[0142] 2301: The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor; and 2302: The F1-terminated donor receives IP address configuration information for the non-F1-terminated topology domain to be assigned to the IAB node, which is transmitted by the non-F1-terminated donor.

[0143] In some embodiments, after the process of adding a secondary cell group, an IP address for a non-F1 terminated topology domain is requested, the IP address request information is carried by an IAB transmission transition management request message, and the IP address configuration information is carried by an IAB transmission transition management response message. For example, an IAB transmission transition management request message may include an IAB TNL ADDRESS REQUEST for a non-F1 terminating topology domain, which may further include a boundary node indicator used to indicate that the IAB node is a boundary node, i.e., that the IP address request information is for a non-F1 terminating topology domain for a boundary node. If the SN does not establish an SRB3, the non-F1 terminating donor sends an IAB transmission transition management response message back to the F1 terminating donor, which may, for example, carry an IAB TNL Address Response for a non-F1 terminating topology domain, which may further include a boundary node indicator used to indicate that the IAB node is a boundary node, i.e., that the IP address configuration information is for a non-F1 terminating topology domain for a boundary node.

[0144] The IAB TNL Address Response can be written using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0145] [Table 11] This includes the IAB Allocated TNL Address List area and the Boundary Node area for at least one non-F1 terminated topology domain to be assigned, with each IP address configuration including a specific IP address IAB TNL Address and a corresponding donor-DU address Associated Donor DU Address.

[0146] Therefore, by introducing a new information element, IAB TNL ADDRESS REQUEST, into the transmission transition management request message to request the IP address of a non-F1 terminated topology domain, and by utilizing the information element IAB TNL Address Response in the IAB transmission transition management response message, it is possible to specify the IP address of a non-F1 terminated topology domain that is set for a boundary node (not a child node).

[0147] In some embodiments, if SN does not establish SRB3, the method may further include the following steps.

[0148] 2303: The F1-terminated donor transmits the received IP address configuration information to the IAB node. For example, a non-F1-terminated donor generates the entire RRC message RRCReconfiguration, which carries the IP address configuration information of the non-F1-terminated topology domain and transmits it to the boundary node. The description of RRCReconfiguration using the Abstract Syntax Notation One (ASN.1) data format is as described above, and a detailed explanation is omitted here.

[0149] In 2303, optionally, when the SN establishes an SRB3, the non-F1 terminating donor may further transmit the IP address configuration information to the IAB node, but the embodiments of the present invention are not limited thereto. As can be seen from the embodiments described above, the F1 terminating donor needs to request an IP address from the non-F1 terminating donor, the non-F1 terminating donor responds to the request by configuring and sending back the IP address of the non-F1 terminating topology domain to the F1 terminating donor, and the F1 terminating donor forwards it to the boundary node, so that the IAB node can use the IP address of the non-F1 terminating topology domain for the routing ID of the non-F1 terminating topology domain.

[0150] Figure 24 is a diagram illustrating another method of setting the transmission address under the dual connection scenario 1, and as shown in Figure 24, this method includes the following steps:

[0151] 2401: The F1-terminated donor receives IP address configuration information for the non-F1-terminated topology domain to be assigned to the IAB node, which is transmitted by the non-F1-terminated donor.

[0152] In some embodiments, the differences from Figure 23 are as follows: if the SN does not establish SRB3, the F1-terminated donor is not required to spontaneously request an IP address for the non-F1-terminated topology domain; the non-F1-terminated donor can spontaneously initiate IP address reconfiguration for the non-F1-terminated topology domain, and the IP address configuration information is carried by an IAB Transport Modification Request message.

[0153] For example, if the SN does not establish SRB3 after the secondary node addition process, the non-F1 terminating donor sends an IAB transmission transition change request message to the F1 terminating donor, which may carry, for example, IP address configuration information for the non-F1 terminating topology domain (information element structure IAB TNL Address Response, the specific data format is as described above and will not be explained in detail here), also known as IP address reconfiguration information, which may further include a boundary node indicator, which is used to indicate that the IAB node is a boundary node, i.e., the IP address configuration information indicates that the IP address configuration information is IP address reconfiguration information for the non-F1 terminating topology domain for the boundary node. Thus, the information element IAB TNL Address Response in the IAB transmission transition change request message can indicate the IP address of the non-F1 terminating topology domain to be reconfigured for the boundary node (not the child node).

[0154] In some embodiments, if SN does not establish SRB3, the method may further include the following steps.

[0155] 2402: The F1-terminated donor forwards the IP address configuration information it receives to the IAB node, for example, the F1-terminated donor forwards the RRCReconfiguration generated by the non-F1-terminated donor, and the RRCReconfiguration carries the IP address configuration information for the non-F1-terminated topology domain.

[0156] As can be seen from the above embodiment, an F1-terminated donor can receive IP address configuration information for a non-F1-terminated topology domain voluntarily sent by a non-F1-terminated donor, and can then send the IP address of the non-F1-terminated topology domain on behalf of the IAB node if the non-F1-terminated donor is unable to send a message to the IAB node. In this way, the IAB node can use the IP address of the non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain.

[0157] III. Dual Connection Scenario 2 In some embodiments, as shown in Figure 17, in dual connection scenario 2, the F1-terminated donor is the secondary node SN CU of the IAB node, and the non-F1-terminated donor is the main node MN CU of the IAB node. After the dual connection is established, some operations of the boundary node are migrated to the non-F1-terminated topology domain, while some operations remain in the F1-terminated donor topology domain. The IP address of the non-F1-terminated topology domain is the IP address anchored to donor-DU1, and the IP address of the F1-terminated topology domain is the IP address anchored to donor-DU2. After the dual connection is established, the IP address of the non-F1-terminated topology domain or the IP address of the F1-terminated topology domain can be requested / configured, and each is described below.

[0158] Figure 25 is a diagram illustrating one method of setting the transmission address under the dual connection scenario 2, and as shown in Figure 25, the method includes the following steps.

[0159] 2501: The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor.

[0160] In some embodiments, after dual connectivity is established, an IP address for a non-F1 terminated topology domain is requested, and this IP address request information is carried by an IAB Transport Migration Management Request message. The F1-terminated donor sends an IAB transmission transition management request message to the non-F1-terminated donor, which includes, for example, an IAB TNL ADDRESS REQUEST (the specific data format is as described above and will not be explained in detail here) for the non-F1-terminated topology domain. This IP address request information further includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node, that is, that the IP address request information indicates that the IP address request information is for a non-F1-terminated topology domain for a boundary node. Since the IP address set by the non-F1-terminated donor can be sent directly to the boundary node by the non-F1-terminated donor via SRB1, the non-F1-terminated donor does not need to send the IP address setting information back to the F1-terminated donor. In other words, the F1-terminated donor does not receive the IP address setting information sent by the non-F1-terminated donor.

[0161] Therefore, a new information element, IAB TNL ADDRESS REQUEST, can be introduced into the IAB Transmission Transition Management Request message to request an IP address for a non-F1 terminated topology domain.

[0162] In some embodiments, the method may further include the following steps.

[0163] 2502: The non-F1 terminating donor transmits IP address configuration information to the IAB node, for example, the non-F1 terminating donor generates an RRCReconfiguration, which carries the IP address configuration information IAB TNL ADDRESS for the non-F1 terminating topology domain, which further includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node, i.e., that the IP address configuration information is IP address configuration information for the non-F1 terminating topology domain for a boundary node.

[0164] As can be seen from the above embodiment, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, thereby causing the F1-terminated donor to request an IP address of a non-F1-terminated topology domain and the non-F1-terminated donor to send the IP address of the non-F1-terminated topology domain to the IAB node. In this way, the IAB node can use the IP address of the non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain.

[0165] Figure 26 is a diagram illustrating another method of setting the transmission address under the dual connection scenario 2, which, as shown in Figure 26, includes the following steps:

[0166] 2601: The F1-terminated donor transmits to the non-F1-terminated donor the IP address configuration information for the F1-terminated topology domain assigned to the IAB node.

[0167] In some embodiments, if the SN does not establish SRB3 after dual connection establishment is complete, the F1-terminated donor does not need to request an IP address for the non-F1-terminated topology domain, and the F1-terminated donor can spontaneously initiate IP address reconfiguration for the F1-terminated topology domain, the IP address configuration information being carried by an IAB transmission transition management request message, the IP address configuration information further including a boundary node indicator, the boundary node indicator being used to indicate that the IAB node is a boundary node, i.e., indicating that the IP address configuration information is IP address configuration information for a non-F1-terminated topology domain for a boundary node.

[0168] For example, an F1-terminated donor sends an IAB transmission transition management request message to a non-F1-terminated donor, which carries, for example, IP address configuration information for an F1-terminated topology domain (information element structure IAB TNL Address Response), which further includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node, that is, that the IP address configuration information is IP address configuration information for a non-F1-terminated topology domain for a boundary node, and this is also called IP address reconfiguration information. The description of the IAB TNL Address Response using the Abstract Syntax Notation One (ASN.1) data format is as described above, and a detailed explanation is omitted here.

[0169] Therefore, by introducing a new information element, IAB TNL Address Response, into the IAB Transmission Transition Management Request Message, it is possible to specify the IP address of the F1 termination topology domain that will be reconfigured for the boundary node (not the child node).

[0170] In some embodiments, if SN does not establish SRB3, the method may further include the following steps.

[0171] 2602: The non-F1 terminating donor forwards the IP address configuration information of the F1 terminating topology domain it receives to the IAB node, for example, the non-F1 terminating donor generates an RRCReconfiguration, which carries the IP address configuration information of the F1 terminating topology domain.

[0172] As can be seen from the above embodiment, an F1-terminated donor can send IP address configuration information for the F1-terminated topology domain to a non-F1-terminated donor, thereby causing the non-F1-terminated donor to send the IP address of the F1-terminated topology domain to the IAB node if the F1-terminated donor is unable to send a message to the IAB node. In this way, the IAB node can use the IP address of the F1-terminated topology domain for the routing ID of the F1-terminated topology domain.

[0173] IV. About the RLF Recovery Scenario In some embodiments, as shown in Figure 20, in the RLF recovery scenario, the F1-terminated donor is the donor of the IAB node before RLF recovery (old donor CU), the non-F1-terminated donor is the donor of the IAB node after RLF recovery (new donor CU), the IP address of the non-F1-terminated topology domain refers to the IP address anchored to donor-DU2, Figure 27 is a diagram showing a transmission address configuration method under the RLF recovery scenario, and as shown in Figure 27, the method includes the following steps.

[0174] 2701: The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor.

[0175] In some embodiments, after sending a UE context acquisition response message, an IP address for a non-F1 terminating topology domain is requested, and this IP address request information is carried by an IAB transmission transition management request message. Thus, an F1 terminating donor sends an IAB transmission transition management request message to a non-F1 terminating donor, which for example includes an IAB TNL ADDRESS REQUEST containing IP address request information for a non-F1 terminating topology domain, and this IP address request information further includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node, i.e., that the IP address request information is IP address request information for a non-F1 terminating topology domain for a boundary node. Since the IP address configuration information can only be sent by the non-F1 terminating donor after the boundary node has re-established with the non-F1 terminating donor, the non-F1 terminating donor does not need to send the IP address configuration information for the non-F1 terminating topology domain back to the F1 terminating donor; in other words, the F1 terminating donor does not receive the IP address configuration information sent by the non-F1 terminating donor.

[0176] Therefore, a new information element, IAB TNL ADDRESS REQUEST, can be introduced into the IAB Transmission Transition Management Request message to request an IP address for a non-F1 terminated topology domain.

[0177] In some embodiments, the method may further include the following steps.

[0178] 2702: The non-F1 terminating donor sends IP address configuration information to the IAB node, for example, the non-F1 terminating donor generates an RRCReconfiguration, which carries the IP address configuration information for the non-F1 terminating topology domain.

[0179] As can be seen from the above embodiment, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, thereby causing the F1-terminated donor to request an IP address of a non-F1-terminated topology domain and the non-F1-terminated donor to send the IP address of the non-F1-terminated topology domain to the IAB node. In this way, the IAB node can use the IP address of the non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain.

[0180] The signaling processes described above are merely illustrative examples of embodiments of the present invention, and the present invention is not limited thereto. For more specific details of signaling, further reference can be found in related technologies. For example, the order in which operations are performed can be appropriately changed, or some operations can be added or removed. Those skilled in the art can make appropriate modifications based on the above description, without being limited to the descriptions in Figures 12, 14-16, 18-19, and 21.

[0181] The embodiments described above are illustrative examples illustrating embodiments of the present invention, but the present invention is not limited thereto, and further appropriate modifications may be made based on the embodiments described above. For example, the embodiments described above may be used individually, or a combination of several of the embodiments described above may be used.

[0182] As can be seen from the embodiments described above, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, or can cause an F1-terminated donor to request an IP address of a non-F1-terminated topology domain by receiving IP address configuration information for a non-F1-terminated topology domain assigned for the IAB node by the non-F1-terminated donor, or can send an IP address of a non-F1-terminated topology domain for the IAB node, for example, if the non-F1-terminated donor is unable to send a message to the IAB node. For example, if the non-F1-terminated donor is unable to send a message to the IAB node, the F1-terminated donor can send an IP address of a non-F1-terminated topology domain for the IAB node by receiving IP address configuration information for a non-F1-terminated topology domain that is voluntarily sent by the non-F1-terminated donor. Furthermore, for example, if an F1-terminated donor is unable to send a message to an IAB node, the F1-terminated donor can send IP address configuration information for the F1-terminated topology domain to a non-F1-terminated donor, thereby causing the non-F1-terminated donor to send the IP address of the F1-terminated topology domain to the IAB node. In this way, the IAB node can use the IP address of the non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain, and can use the IP address of the F1-terminated topology domain for the routing ID of the F1-terminated topology domain.

[0183] <Example of the second aspect> An embodiment of the present invention provides a transmission address setting method, which will be explained from the perspective of a non-F1 termination donor. Note that the same information as in the embodiment described in the first aspect will be omitted here.

[0184] Figure 28 is another diagram illustrating a transmission address setting method in an embodiment of the present invention. As shown in Figure 28, the method includes the following steps.

[0185] 2801: The non-F1 terminating donor receives the IP address request information for the non-F1 terminating topology domain for the IAB node from the F1 terminating donor transmission; and / or The non-F1 terminating donor transmits IP address configuration information for the non-F1 terminating topology domain to be assigned to the IAB node to the F1 terminating donor; and / or The non-F1 termination donor receives the IP address configuration information for the F1 termination topology domain assigned to the IAB node, transmitted by the F1 termination donor.

[0186] In some embodiments, the method may further include the following steps (not shown).

[0187] The non-F1 termination donor transmits the IP address configuration information to the IAB node.

[0188] In some embodiments, the IP address request information is carried by a first RRC container, which further includes IP address configuration information for the F1 termination topology domain of the IAB node, 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.

[0189] In some embodiments, the first RRC container is carried by at least one of the following messages: Switch request message; Secondary node addition request message; Secondary node change request message; Secondary node change request message; and UE context acquisition response message That is the case.

[0190] In some embodiments, the IP address configuration information is carried by a second RRC container, for example, by an RRC reconfiguration message contained in the second RRC container.

[0191] In some embodiments, the second RRC container is carried by at least one of the following messages: Switching request response message; Secondary node addition response message; Secondary node change response message; and Secondary node change request message That is the case.

[0192] In some embodiments, the F1-terminated donor is the source donor for the IAB node switching, and the non-F1-terminated donor is the target donor for the IAB node switching, and the method includes the following steps:

[0193] The non-F1 terminating donor receives IP address request information for the non-F1 terminating topology domain for the IAB node from the F1 terminating donor, the non-F1 terminating donor sends IP address configuration information for the non-F1 terminating topology domain to be assigned for the IAB node to the F1 terminating donor, the first RRC container is carried by the switching request message, and the second RRC container is carried by the switching request response message.

[0194] In some embodiments, the F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method includes the following steps.

[0195] The non-F1 terminating donor receives the IP address request information for the non-F1 terminating topology domain for the IAB node from the F1 terminating donor, and the first RRC container is carried by a secondary node addition request message or a secondary node change request message. The non-F1 terminating donor also sends the IP address configuration information for the non-F1 terminating topology domain to be assigned for the IAB node to the F1 terminating donor, and the second RRC container is carried by a secondary node addition response message or a secondary node change response message. Optionally, the non-F1 terminating donor further sends the IP address configuration information to the IAB node.

[0196] In some embodiments, the F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method includes the following steps.

[0197] The non-F1 terminating donor sends IP address configuration information for the non-F1 terminating topology domain to be assigned to the IAB node to the F1 terminating donor, and the second RRC container is carried by the secondary node change request message.

[0198] In some embodiments, the non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method includes the following steps.

[0199] The non-F1 terminating donor receives the IP address request information for the non-F1 terminating topology domain for the IAB node, transmitted by the F1 terminating donor, and the first RRC container is carried by the secondary node change request message. Optionally, the non-F1 terminating donor further transmits the IP address configuration information to the IAB node.

[0200] In some embodiments, the non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method includes the following steps.

[0201] The non-F1 termination donor receives the IP address configuration information for the F1 termination topology domain to be assigned to the boundary node, and the second RRC container is carried by the secondary node change request message. Optionally, the non-F1 termination donor further transmits the IP address configuration information to the IAB node.

[0202] In some embodiments, the F1-terminated donor is the donor of the IAB node after RLF recovery, and the non-F1-terminated donor is the donor of the IAB node before RLF recovery, and the method includes the following steps.

[0203] The non-F1 terminating donor receives the IP address request information for the non-F1 terminating topology domain for the IAB node, transmitted by the F1 terminating donor, and the first RRC container is carried by the UE context acquisition response message. Optionally, the non-F1 terminating donor further transmits the IP address configuration information to the IAB node.

[0204] In some embodiments, the IP address request information is carried by an IAB transmission transition management request message. This IP address request information includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node.

[0205] In some embodiments, the IP address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message, and the IP address configuration information includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node.

[0206] In some embodiments, the F1-terminated donor is the source donor for the IAB node switching, and the non-F1-terminated donor is the target donor for the IAB node switching, and the method includes the following steps:

[0207] The non-F1 terminating donor receives the IP address request information for the non-F1 terminating topology domain for the IAB node transmitted by the F1 terminating donor, and the IP address request information is carried by the IAB transmission transition management request message. Optionally, the non-F1 terminating donor further transmits the IP address configuration information to the IAB node.

[0208] In some embodiments, the F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method includes the following steps.

[0209] The non-F1 terminating donor receives IP address request information for the non-F1 terminating topology domain for the IAB node from the F1 terminating donor, and the IP address request information is carried by an IAB transmission transition management request message. The non-F1 terminating donor also sends IP address configuration information for the non-F1 terminating topology domain to be assigned for the IAB node to the F1 terminating donor, and the IP address configuration information is carried by an IAB transmission transition management response message. Optionally, the non-F1 terminating donor further transmits the IP address configuration information to the IAB node.

[0210] In some embodiments, the F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method includes the following steps.

[0211] The non-F1 terminating donor transmits IP address configuration information for the non-F1 terminating topology domain to be assigned to the IAB node to the F1 terminating donor, and this IP address configuration information is carried by an IAB transmission transition change request message.

[0212] In some embodiments, the non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method includes the following steps.

[0213] The non-F1 terminating donor receives the IP address request information for the non-F1 terminating topology domain for the IAB node transmitted by the F1 terminating donor, and the IP address request information is carried by the IAB transmission transition management request message. Optionally, the non-F1 terminating donor further transmits the IP address configuration information to the IAB node.

[0214] In some embodiments, the non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method includes the following steps.

[0215] The non-F1 termination donor receives the IP address configuration information for the F1 termination topology domain assigned to the boundary node in the F1 termination donor transmission, and this IP address configuration information is carried by the IAB transmission transition management request message. Optionally, the non-F1 termination donor further transmits the IP address configuration information to the IAB node.

[0216] In some embodiments, the F1-terminated donor is the donor of the IAB node after RLF recovery, and the non-F1-terminated donor is the donor of the IAB node before RLF recovery, and the method includes the following steps.

[0217] The non-F1 terminating donor receives the IP address request information for the non-F1 terminating topology domain for the IAB node transmitted by the F1 terminating donor, and the IP address request information is carried by the IAB transmission transition management request message. Optionally, the non-F1 terminating donor further transmits the IP address configuration information to the IAB node.

[0218] The signaling process described above is for illustrative purposes to illustrate embodiments of the present invention, but the present invention is not limited thereto, and related technologies can be consulted for more specific details of signaling. Furthermore, for example, the execution order between each operation can be appropriately changed, or some operations can be added or removed. Those skilled in the art can make appropriate modifications based on the above description, and specific signaling processes correspond to those described in Figures 12, 14-16, 18-19, and 21 in the embodiments of the first aspect, and a detailed explanation thereof is omitted here.

[0219] As can be seen from the embodiments described above, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, or can cause an F1-terminated donor to request an IP address of a non-F1-terminated topology domain by receiving IP address configuration information for a non-F1-terminated topology domain assigned for the IAB node by the non-F1-terminated donor, or can send an IP address of a non-F1-terminated topology domain for the IAB node, for example, if the non-F1-terminated donor is unable to send a message to the IAB node. For example, if the non-F1-terminated donor is unable to send a message to the IAB node, the F1-terminated donor can send an IP address of a non-F1-terminated topology domain for the IAB node by receiving IP address configuration information for a non-F1-terminated topology domain that is voluntarily sent by the non-F1-terminated donor. Furthermore, for example, if an F1-terminated donor is unable to send a message to an IAB node, the F1-terminated donor can send IP address configuration information for the F1-terminated topology domain to a non-F1-terminated donor, thereby causing the non-F1-terminated donor to send the IP address of the F1-terminated topology domain to the IAB node. In this way, the IAB node can use the IP address of the non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain, and can use the IP address of the F1-terminated topology domain for the routing ID of the F1-terminated topology domain.

[0220] <Example of the third side> In embodiments of the present invention, an IAB donor device is provided, and the description of the same content as in the embodiment of the first aspect is omitted here. The device may be, for example, an IAB donor-CU in an IAB system (e.g., the first donor-CU or F1 terminal donor in the embodiments of the first and second aspects), or one or more components, assemblies, or modules provided on the IAB donor-CU or F1 terminal donor.

[0221] Figure 29 shows an IAB donor device in an embodiment of the present invention. As shown in Figure 29, the IAB donor device 2900 includes the following:

[0222] First transmitting unit 2901: Sends IP address request information for the non-F1 termination topology domain for the IAB node to the non-F1 termination donor; and / or Send IP address configuration information for the F1 termination topology domain assigned to the IAB node to the non-F1 termination donor; and / or First receiving unit 2902: Receives IP address configuration information for the non-F1 terminated topology domain to be assigned to the IAB node, transmitted by the non-F1 terminated donor.

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

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

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

[0226] In some embodiments, the first RRC container is carried by at least one of the following messages: Switch request message; Secondary node addition request message; Secondary node change request message; Secondary node change request message; and UE context acquisition response message That is the case.

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

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

[0229] In some embodiments, the second RRC container is carried by at least one of the following messages: Switching request response message; Secondary node addition response message; Secondary node change response message; and Secondary node change request message That is the case.

[0230] In some embodiments, the F1-terminated donor is the source donor for the IAB node switchover, the non-F1-terminated donor is the target donor for the IAB node switchover, the first transmitter transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, the first receiver receives IP address configuration information for the non-F1-terminated topology domain to be assigned for the IAB node, the first RRC container is carried by the switchover request message, and the second RRC container is carried by the switchover request response message. Optionally, the first transmitter further transmits the IP address configuration information to the IAB node.

[0231] In some embodiments, the F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, the first transmitter transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, the first RRC container is carried by a secondary node addition request message or a secondary node change request message, and the first receiver receives IP address configuration information for the non-F1-terminated topology domain to be assigned for the IAB node, transmitted by the non-F1-terminated donor, the second RRC container is carried by a secondary node addition response message or a secondary node change response message. Optionally, the first transmitter further transmits the IP address configuration information to the IAB node.

[0232] In some embodiments, the F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, the first receiver receives IP address configuration information for the non-F1-terminated topology domain assigned to the IAB node, transmitted by the non-F1-terminated donor, and the second RRC container is carried by a secondary node change request message. Optionally, the first transmitter further transmits the IP address configuration information to the IAB node.

[0233] In some embodiments, the non-F1 terminated donor is the main node MN of the IAB node, the F1 terminated donor is the secondary node SN of the IAB node, the first transmitter sends IP address request information for the non-F1 terminated topology domain for the IAB node to the non-F1 terminated donor, and the first RRC container is carried by the secondary node change request message.

[0234] In some embodiments, the non-F1 termination donor is the main node MN of the IAB node, the F1 termination donor is the secondary node SN of the IAB node, the first transmitter transmits IP address configuration information for the F1 termination topology domain assigned to the boundary node to the non-F1 termination donor, and the second RRC container is carried by a secondary node change request message.

[0235] In some embodiments, the F1-terminated donor is the donor of the IAB node after RLF recovery, the non-F1-terminated donor is the donor of the IAB node before RLF recovery, the first transmitter sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, and the first RRC container is carried by a UE context acquisition response message.

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

[0237] In some embodiments, the IP address request information includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node.

[0238] In some embodiments, the IP address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message.

[0239] In some embodiments, the IP address configuration information includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node.

[0240] In some embodiments, the F1 termination donor is the source donor for the IAB node switch, the non-F1 termination donor is the target donor for the IAB node switch, the first transmission unit transmits non-F1 termination topology domain IP address request information about the IAB node to the non-F1 termination donor, and the IP address request information is carried by an IAB transmission migration management request message.

[0241] In some embodiments, the F1 termination donor is the main node MN of the IAB node, the non-F1 termination donor is the secondary node SN of the IAB node, the first transmission unit transmits non-F1 termination topology domain IP address request information about the IAB node to the non-F1 termination donor, the IP address request information is carried by an IAB transmission migration management request message, and the first reception unit receives non-F1 termination topology domain IP address setting information assigned to the IAB node, transmitted by the non-F1 termination donor, and the IP address setting information is carried by an IAB transmission migration management response message. Optionally, the first transmission unit further transmits the IP address setting information to the IAB node.

[0242] In some embodiments, the F1 termination donor is the main node MN of the IAB node, the non-F1 termination donor is the secondary node SN of the IAB node, the first reception unit receives non-F1 termination topology domain IP address setting information assigned to the IAB node, transmitted by the non-F1 termination donor, and the IP address setting information is carried by an IAB transmission migration change request message. Optionally, the first transmission unit further transmits the IP address setting information to the IAB node.

[0243] In some embodiments, the non-F1 termination donor is the main node MN of the IAB node, the F1 termination donor is the secondary node SN of the IAB node, the first transmitter transmits IP address request information for the non-F1 termination topology domain for the IAB node to the non-F1 termination donor, and the IP address request information is carried by an IAB transmission transition management request message.

[0244] In some embodiments, the non-F1 terminating donor is the main node MN of the IAB node, the F1 terminating donor is the secondary node SN of the IAB node, the first transmitter transmits to the non-F1 terminating donor IP address configuration information for the F1 terminating topology domain assigned to the boundary node, and the IP address configuration information is carried by an IAB transmission transition management request message.

[0245] In some embodiments, the F1-terminated donor is the donor of the IAB node after RLF recovery, the non-F1-terminated donor is the donor of the IAB node before RLF recovery, the first transmitter sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, and the IP address request information is carried by an IAB transmission transition management request message.

[0246] The embodiments described above are illustrative examples illustrating embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the embodiments described above. For example, the embodiments described above may be used individually, or a combination of several of the embodiments described above may be used.

[0247] Although only the components or modules relating to the present invention have been described above, the present invention is not limited to these. The IAB donor device 2900 in the embodiments of the present invention may include other components or modules, and the specific details of these components or modules can be found in the relevant technologies.

[0248] Furthermore, for convenience, Figure 29 only shows the connection relationships or signal directions between each component or module; however, various related technologies such as bus connections may be employed so that those skilled in the art can understand them. Also, the above-mentioned components or modules may be realized by hardware such as processors, memory devices, transmitters, and receivers, and the implementation of the present invention is not limited to these.

[0249] As can be seen from the embodiments described above, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, or can cause an F1-terminated donor to request an IP address of a non-F1-terminated topology domain by receiving IP address configuration information for a non-F1-terminated topology domain assigned for the IAB node by the non-F1-terminated donor, or can send an IP address of a non-F1-terminated topology domain for the IAB node, for example, if the non-F1-terminated donor is unable to send a message to the IAB node. For example, if the non-F1-terminated donor is unable to send a message to the IAB node, the F1-terminated donor can send an IP address of a non-F1-terminated topology domain for the IAB node by receiving IP address configuration information for a non-F1-terminated topology domain that is voluntarily sent by the non-F1-terminated donor. Furthermore, for example, if an F1-terminated donor is unable to send a message to an IAB node, the F1-terminated donor can send IP address configuration information for the F1-terminated topology domain to a non-F1-terminated donor, thereby causing the non-F1-terminated donor to send the IP address of the F1-terminated topology domain to the IAB node. In this way, the IAB node can use the IP address of the non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain, and can use the IP address of the F1-terminated topology domain for the routing ID of the F1-terminated topology domain.

[0250] <Example of the fourth side view> In embodiments of the present invention, an IAB donor device is provided, and the description of the same content as in the embodiment of the second aspect is omitted here. The device may be, for example, an IAB donor-CU in an IAB system (e.g., the second donor-CU or non-F1 terminated donor in the embodiments of the first and second aspects), or one or more components, assemblies or modules provided on the IAB donor-CU or non-F1 terminated donor.

[0251] Figure 30 shows an IAB donor device in an embodiment of the present invention. As shown in Figure 30, the IAB donor device 3000 includes the following:

[0252] Second receiving unit 3001: Receives IP address request information for a non-F1 termination topology domain for the IAB node of an F1 termination donor transmission; and / or For F1 termination donor transmissions, receive IP address configuration information for the F1 termination topology domain assigned to the IAB node; and / or Second transmission unit 3002: Transmits IP address configuration information for the non-F1 termination topology domain assigned to the IAB node to the F1 termination donor.

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

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

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

[0256] In some embodiments, the first RRC container is carried by at least one of the following messages: Switch request message; Secondary node addition request message; Secondary node change request message; Secondary node change request message; and UE context acquisition response message is.

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

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

[0259] In some embodiments, the second RRC container is carried by at least one of the following messages, namely, Switch request response message; Secondary node addition response message; Secondary node change response message; and Secondary node change request message is.

[0260] In some embodiments, the F1 terminating donor is the source donor for the IAB node's switch, the non-F1 terminating donor is the target donor for the IAB node's switch, the second receiving unit receives IP address request information for the non-F1 terminating topology domain of the IAB node transmitted by the F1 terminating donor, the second transmitting unit transmits IP address setting information for the non-F1 terminating topology domain assigned to the IAB node to the F1 terminating donor, the first RRC container is carried by a switch request message, and the second RRC container is carried by a switch request response message.

[0261] In some embodiments, the F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, the second receiver receives the IP address request information for the non-F1-terminated topology domain for the IAB node from the F1-terminated donor, the first RRC container is carried by a secondary node addition request message or a secondary node change request message, and the second transmitter sends the IP address configuration information for the non-F1-terminated topology domain to be assigned for the IAB node to the F1-terminated donor, the second RRC container is carried by a secondary node addition response message or a secondary node change response message. Optionally, the second transmitter further transmits the IP address configuration information to the IAB node.

[0262] In some embodiments, the F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, the second transmitter transmits IP address configuration information for the non-F1-terminated topology domain assigned to the IAB node to the F1-terminated donor, and the second RRC container is carried by a secondary node change request message.

[0263] In some embodiments, the non-F1-terminated donor is the main node MN of the IAB node, the F1-terminated donor is the secondary node SN of the IAB node, the second receiver receives the IP address request information for the non-F1-terminated topology domain for the IAB node from the F1-terminated donor transmission, and the first RRC container is carried by the secondary node change request message. Optionally, the second transmitter further transmits the IP address configuration information to the IAB node.

[0264] In some embodiments, the non-F1 termination donor is the main node MN of the IAB node, the F1 termination donor is the secondary node SN of the IAB node, the second receiver receives the IP address configuration information for the F1 termination topology domain assigned to the boundary node from the F1 termination donor transmission, and the second RRC container is carried by the secondary node change request message. Optionally, the second transmitter further transmits the IP address configuration information to the IAB node.

[0265] In some embodiments, the F1-terminated donor is the donor of the IAB node after RLF recovery, the non-F1-terminated donor is the donor of the IAB node before RLF recovery, the second receiver receives the IP address request information for the non-F1-terminated topology domain for the IAB node from the F1-terminated donor transmission, and the first RRC container is carried by the UE context acquisition response message. Optionally, the second transmitter further transmits the IP address configuration information to the IAB node.

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

[0267] In some embodiments, the IP address request information includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node.

[0268] In some embodiments, the IP address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message.

[0269] In some embodiments, the IP address configuration information includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node.

[0270] In some embodiments, the F1-terminated donor is the source donor for the IAB node switching, the non-F1-terminated donor is the target donor for the IAB node switching, the second receiver receives the F1-terminated donor transmission for the non-F1-terminated topology domain of the IAB node, and the IP address request information is carried by an IAB transmission transition management request message. Optionally, the second transmitter further transmits the IP address configuration information to the IAB node.

[0271] In some embodiments, the F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, the second receiver receives IP address request information for the non-F1-terminated topology domain for the IAB node from the F1-terminated donor transmission, the IP address request information is carried by an IAB transmission transition management request message, and the second transmitter transmits IP address configuration information for the non-F1-terminated topology domain to be assigned for the IAB node to the F1-terminated donor, the IP address configuration information is carried by an IAB transmission transition management response message. Optionally, the second transmitter further transmits the IP address configuration information to the IAB node.

[0272] In some embodiments, the F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, the second transmitter transmits to the F1-terminated donor IP address configuration information for the non-F1-terminated topology domain assigned to the IAB node, and the IP address configuration information is carried by an IAB transmission transition change request message.

[0273] In some embodiments, the non-F1 terminated donor is the main node MN of the IAB node, the F1 terminated donor is the secondary node SN of the IAB node, the second receiver receives the IP address request information for the non-F1 terminated topology domain for the IAB node from the F1 terminated donor transmission, the IP address request information is carried by an IAB transmission transition management request message. Optionally, the second transmitter further transmits the IP address configuration information to the IAB node.

[0274] In some embodiments, the non-F1 termination donor is the main node MN of the IAB node, the F1 termination donor is the secondary node SN of the IAB node, the second receiver receives the F1 termination donor transmission for the F1 termination topology domain assigned to the boundary node, and the IP address configuration information is carried by an IAB transmission transition management request message. Optionally, the second transmitter further transmits the IP address configuration information to the IAB node.

[0275] In some embodiments, the F1-terminated donor is the donor of the IAB node after RLF recovery, the non-F1-terminated donor is the donor of the IAB node before RLF recovery, the second receiver receives the IP address request information for the non-F1-terminated topology domain for the IAB node from the F1-terminated donor transmission, the IP address request information is carried by an IAB transmission transition management request message. Optionally, the second transmitter further transmits the IP address configuration information to the IAB node.

[0276] The embodiments described above are merely illustrative examples illustrating embodiments of the present invention, and the present invention is not limited thereto. Further appropriate modifications may be made based on the embodiments described above. For example, the embodiments described above may be used individually, or a combination of several of the embodiments described above may be used.

[0277] Although only the components or modules relating to the present invention have been described above, the present invention is not limited to these. The IAB donor device 3000 in the embodiments of the present invention may further include other components or modules, and the specific details of these components or modules can be found in the relevant technologies.

[0278] Furthermore, for convenience, Figure 30 only shows the connection relationships or signal directions between each component or module, but various related technologies such as bus connections may be used so that those skilled in the art can understand them. Also, each of the above-mentioned components or modules may be realized by hardware such as processors, memory devices, transmitters, and receivers, and the implementation of the present invention is not limited to these.

[0279] As can be seen from the embodiments described above, an F1-terminated donor can request a non-F1-terminated donor to assign an IP address of a non-F1-terminated topology domain, or can cause an F1-terminated donor to request an IP address of a non-F1-terminated topology domain by receiving IP address configuration information for a non-F1-terminated topology domain assigned for the IAB node by the non-F1-terminated donor, or can send an IP address of a non-F1-terminated topology domain for the IAB node, for example, if the non-F1-terminated donor is unable to send a message to the IAB node. For example, if the non-F1-terminated donor is unable to send a message to the IAB node, the F1-terminated donor can send an IP address of a non-F1-terminated topology domain for the IAB node by receiving IP address configuration information for a non-F1-terminated topology domain that is voluntarily sent by the non-F1-terminated donor. Furthermore, for example, if an F1-terminated donor is unable to send a message to an IAB node, the F1-terminated donor can send IP address configuration information for the F1-terminated topology domain to a non-F1-terminated donor, thereby causing the non-F1-terminated donor to send the IP address of the F1-terminated topology domain to the IAB node. In this way, the IAB node can use the IP address of the non-F1-terminated topology domain for the routing ID of the non-F1-terminated topology domain, and can use the IP address of the F1-terminated topology domain for the routing ID of the F1-terminated topology domain.

[0280] <Example of the fifth side> In embodiments of the present invention, a communication system is provided, which includes an IAB donor device 2900 in the third embodiment and / or an IAB donor device 3000 in the fourth embodiment, and also includes IAB nodes (boundary nodes). The network architecture of the donor devices and IAB nodes can be found in related technologies, which are omitted here for further detail.

[0281] In embodiments of the present invention, an IAB donor device is further provided.

[0282] Figure 9 shows an IAB donor device in an embodiment of the present invention. As shown in Figure 9, the IAB device 900 may include a processor (e.g., a central processor CPU) 901 and a memory unit 902, the memory unit 902 being connected to the processor 901. The memory unit 902 can store various data and also store a program 905 for information processing, and can execute the program 905 under the control of the central processor 901.

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

[0284] Furthermore, for example, the processor 901 may be configured to execute a program to implement the transmission address setting method in the second embodiment.

[0285] Furthermore, as shown in Figure 9, the IAB donor equipment 900 may also include a transceiver 903, an antenna 904, etc., and the functions of these components are the same as in the prior art, so a detailed explanation is omitted here. Note that the IAB equipment 900 does not need to include all the components shown in Figure 9. Also, the IAB equipment 900 may include components not shown in Figure 9, for which prior art can be referred.

[0286] In embodiments of the present invention, a computer-readable program is further provided, wherein when the program is executed on an IAB donor device, the program causes the computer to execute the transmission address setting method in the first or second embodiment on the IAB donor device.

[0287] In embodiments of the present invention, a storage medium storing a computer-readable program is further provided, wherein the computer-readable program causes a computer to execute the transmission address setting method in the first and second embodiments using IAB donor equipment.

[0288] Furthermore, the above-described apparatus and method may be implemented by software or hardware, or by a combination of hardware and software. The present invention further relates to a computer-readable program as described below, that is, the program, when executed by a logic component, causes the logic component to implement the above-described apparatus or component, or to the logic component to implement each of the above-described method or step. The logic component may be, for example, an FPGA (Field Programmable Gate Array), a microprocessor, or a processor used in a computer. The present invention further relates to a storage medium storing the above-described program, for example, a hard disk, a magnetic disk, an optical hard disk, a DVD, a flash memory, etc.

[0289] Furthermore, one or more combinations of the functional blocks shown in the drawings and / or one or more combinations of functional blocks may be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic component, discrete gate or transistor logic component, discrete hardware assembly or any other suitable combination for performing the functions described herein. Also, one or more combinations of the functional blocks shown in the drawings and / or one or more combinations of functional blocks may further be configured as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors connected to a DSP by communication or any other combination of any other configuration.

[0290] Although preferred embodiments of the present invention have been described above, the present invention is not limited to such embodiments, and any modifications to the present invention that do not deviate from the spirit of the invention fall within the technical scope of the present invention.

[0291] Furthermore, the following additional information is disclosed regarding the above-mentioned embodiments.

[0292] <f1> (Note 1) A transmission address setting method, which is applied to an F1 termination donor device of an IAB node, and the method is The F1-terminated donor sends IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor; and / or The F1-terminated donor receives IP address configuration information for a non-F1-terminated topology domain to be assigned to the IAB node, transmitted by the non-F1-terminated donor; and / or A method comprising the F1-terminated donor transmitting IP address configuration information for an F1-terminated topology domain to be assigned for the IAB node to a non-F1-terminated donor.

[0293] (Note 2) The method described in Appendix 1, The aforementioned IP address request information is carried by the first RRC container in a manner.

[0294] (Note 3) The method described in Appendix 2, The method further includes IP address configuration information in the F1 termination topology domain of the IAB node, wherein the first RRC container further includes IP address configuration information.

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

[0296] (Note 5) The method described in any one of the appendices 2 to 4, The first RRC container is carried by at least one message, namely, Switch request message; Secondary node addition request message; Secondary node change request message; Secondary node change request message; and UE context acquisition response message The method.

[0297] (Note 6) The method described in Appendix 1, The aforementioned IP address configuration information is carried by a second RRC container.

[0298] (Note 7) The method described in Appendix 6, The IP address configuration information is carried by an RRC reconfiguration message contained in the second RRC container.

[0299] (Note 8) The method described in Appendix 6 or 7, The second RRC container is carried by at least one of the following messages, namely, Switching request response message; Secondary node addition response message; Secondary node change response message; and Secondary node change request message The method.

[0300] (Note 9) The method described in Appendix 5 or 8, The F1-terminated donor is the source donor for the IAB node switching, the non-F1-terminated donor is the target donor for the IAB node switching, and the method is The F1-terminated donor transmits IP address request information for a non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, and the F1-terminated donor receives IP address configuration information for a non-F1-terminated topology domain to be assigned to the IAB node, transmitted by the non-F1-terminated donor. A method in which the first RRC container is carried by a switching request message, and the second RRC container is carried by a switching request response message.

[0301] (Note 9.1) The method described in Appendix 9, wherein the method further comprises: A method comprising the F1 termination donor transmitting the IP address configuration information to the IAB node.

[0302] (Note 10) The method described in Appendix 5 or 8, The F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method is The F1-terminated donor transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, The first RRC container is carried by a secondary node addition request message or a secondary node modification request message, in this manner.

[0303] (Note 10.1) The method described in Appendix 10, wherein the method further includes: The F1-terminated donor receives IP address configuration information for a non-F1-terminated topology domain to be assigned to the IAB node, transmitted by the non-F1-terminated donor. In this method, the second RRC container is carried by a secondary node addition response message or a secondary node modification response message.

[0304] (Appendix 10.2) The method described in Appendix 10 or 10.1, wherein the method further includes: A method comprising the F1 termination donor transmitting the IP address configuration information to the IAB node.

[0305] (Note 11) The method described in Appendix 5 or 8, The F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method is The F1-terminated donor receives IP address configuration information for a non-F1-terminated topology domain to be assigned to the IAB node, transmitted by the non-F1-terminated donor. In this manner, the second RRC container is carried by a secondary node change request message.

[0306] (Note 11.1) The method described in Appendix 11, wherein the method further includes: A method comprising the F1 termination donor transmitting the IP address configuration information to the IAB node.

[0307] (Note 12) The method described in Appendix 5 or 8, The non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method is The F1-terminated donor transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, In this manner, the first RRC container is carried by a secondary node change request message.

[0308] (Note 13) The method described in Appendix 5 or 8, The non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method is The F1-terminated donor transmits IP address configuration information for the F1-terminated topology domain to be assigned to the IAB node to the non-F1-terminated donor, In this manner, the second RRC container is carried by a secondary node change request message.

[0309] (Note 14) The method described in Appendix 5 or 8, The F1-terminated donor is the donor of the IAB node after RLF recovery, and the non-F1-terminated donor is the donor of the IAB node before RLF recovery, and the method is The F1-terminated donor transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, In this method, the first RRC container is carried by the UE context retrieval response message.

[0310] (Note 15) The method described in Appendix 1, The IP address request information is carried by an IAB transmission transition management request message.

[0311] (Note 16) The method described in Appendix 15, A method wherein the IP address request information includes a boundary node indicator, and the boundary node indicator is used to indicate that the IAB node is a boundary node.

[0312] (Note 17) The method described in Appendix 1, The IP address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message, in a manner that allows this to be done.

[0313] (Note 18) The method described in Appendix 17, A method wherein the IP address configuration information includes a boundary node indicator, and the boundary node indicator is used to indicate that the IAB node is a boundary node.

[0314] (Note 19) The method described in Appendix 15 or 17, The F1-terminated donor is the source donor for the IAB node switching, the non-F1-terminated donor is the target donor for the IAB node switching, and the method is The F1-terminated donor transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, The method involves the IP address request information being carried by an IAB transmission transition management request message.

[0315] (Note 20) The method described in Appendix 15 or 17, The F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method is The F1-terminated donor transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, The method involves the IP address request information being carried by an IAB transmission transition management request message.

[0316] (Note 20.1) The method described in Appendix 20, wherein the method further includes: The F1-terminated donor receives IP address configuration information for a non-F1-terminated topology domain to be assigned to the IAB node, transmitted by the non-F1-terminated donor. The method involves the IP address configuration information being carried by an IAB transmission transition management response message.

[0317] (Appendix 20.2) The method described in Appendix 20.1, wherein the method further includes: A method comprising the F1 termination donor transmitting the IP address configuration information to the IAB node.

[0318] (Note 21) The method described in Appendix 15 or 17, The F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method is The F1-terminated donor receives IP address configuration information for a non-F1-terminated topology domain to be assigned to the IAB node, transmitted by the non-F1-terminated donor. The method involves the IP address configuration information being carried by an IAB transmission transition change request message.

[0319] (Note 21.1) The method described in Appendix 21, wherein the method further includes: A method comprising the F1 termination donor transmitting the IP address configuration information to the IAB node.

[0320] (Note 22) The method described in Appendix 15 or 17, The non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method is The F1-terminated donor transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, The method involves the IP address request information being carried by an IAB transmission transition management request message.

[0321] (Note 23) The method described in Appendix 15 or 17, The non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method is The F1-terminated donor transmits IP address configuration information for the F1-terminated topology domain to be assigned to the IAB node to the non-F1-terminated donor, The method involves the IP address configuration information being carried by an IAB transmission transition management request message.

[0322] (Note 24) The method described in Appendix 15 or 17, The F1-terminated donor is the donor of the IAB node after RLF recovery, and the non-F1-terminated donor is the donor of the IAB node before RLF recovery, and the method is The F1-terminated donor transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, The method involves the IP address request information being carried by an IAB transmission transition management request message.

[0323] (Note 25) IAB donor device, Including memory and processing units, The memory device stores a computer program. Among these, the processing device is configured to execute the computer program and perform the transmission address setting method described in any one of the appendices 1 to 25.

[0324] <Non-F1> (Note 1) A transmission address setting method, applicable to a non-F1 terminated donor device of an IAB node, wherein the method is The non-F1 terminated donor receives IP address request information for the non-F1 terminated topology domain for the IAB node, transmitted by the F1 terminated donor; and / or The non-F1 terminating donor transmits IP address configuration information for the non-F1 terminating topology domain to be assigned to the IAB node to the F1 terminating donor; and / or A method comprising the non-F1 terminating donor receiving IP address configuration information for an F1 terminating topology domain to be assigned to the IAB node, transmitted by the F1 terminating donor.

[0325] (Note 2) The method described in Appendix 1, The aforementioned IP address request information is carried by the first RRC container in a manner.

[0326] (Note 3) The method described in Appendix 2, The method further includes IP address configuration information in the F1 termination topology domain of the IAB node, wherein the first RRC container further includes IP address configuration information.

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

[0328] (Note 5) The method described in any one of the appendices 2 to 4, The first RRC container is carried by at least one message, namely, Switch request message; Secondary node addition request message; Secondary node change request message; Secondary node change request message; and UE context acquisition response message The method.

[0329] (Note 6) The method described in Appendix 1, The aforementioned IP address configuration information is carried by a second RRC container.

[0330] (Note 7) The method described in Appendix 6, The IP address configuration information is carried by an RRC reconfiguration message contained in the second RRC container.

[0331] (Note 8) The method described in Appendix 6 or 7, The second RRC container is carried by at least one of the following messages, namely, Switching request response message; Secondary node addition response message; Secondary node change response message; and Secondary node change request message The method.

[0332] (Note 9) The method described in Appendix 5 or 8, The F1-terminated donor is the source donor for the IAB node switching, the non-F1-terminated donor is the target donor for the IAB node switching, and the method is The non-F1 terminating donor receives IP address request information for a non-F1 terminating topology domain for the IAB node from the F1 terminating donor transmission, and the non-F1 terminating donor transmits IP address configuration information for a non-F1 terminating topology domain to be assigned for the IAB node to the F1 terminating donor, A method in which the first RRC container is carried by a switching request message, and the second RRC container is carried by a switching request response message.

[0333] (Note 10) The method described in Appendix 5 or 8, The F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method is The non-F1 terminating donor receives IP address request information for the non-F1 terminating topology domain for the IAB node from the F1 terminating donor transmission, The first RRC container is carried by a secondary node addition request message or a secondary node modification request message, in this manner.

[0334] (Note 10.1) The method described in Appendix 10, wherein the method further includes: The non-F1 terminating donor transmits IP address configuration information for the non-F1 terminating topology domain to be assigned to the IAB node to the F1 terminating donor, In this method, the second RRC container is carried by a secondary node addition response message or a secondary node modification response message.

[0335] (Appendix 10.2) The method described in Appendix 10 or 10.1, wherein the method further includes: A method comprising the non-F1 terminating donor transmitting the IP address configuration information to the IAB node.

[0336] (Note 11) The method described in Appendix 5 or 8, The F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method is The non-F1 terminating donor transmits IP address configuration information for the non-F1 terminating topology domain to be assigned to the IAB node to the F1 terminating donor, In this manner, the second RRC container is carried by a secondary node change request message.

[0337] (Note 12) The method described in Appendix 5 or 8, The non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method is The non-F1 terminating donor receives IP address request information for the non-F1 terminating topology domain for the IAB node from the F1 terminating donor transmission, In this manner, the first RRC container is carried by a secondary node change request message.

[0338] (Note 12.1) The method described in Appendix 12, wherein the method further includes: A method comprising the non-F1 terminating donor transmitting the IP address configuration information to the IAB node.

[0339] (Note 13) The method described in Appendix 5 or 8, The non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method is The non-F1 terminating donor receives the F1 terminating donor transmission, which includes IP address configuration information for the F1 terminating topology domain assigned to the IAB node. In this manner, the second RRC container is carried by a secondary node change request message.

[0340] (Note 13.1) The method described in Appendix 13, wherein the method further includes: A method comprising the non-F1 terminating donor transmitting the IP address configuration information to the IAB node.

[0341] (Note 14) The method described in Appendix 5 or 8, The F1-terminated donor is the donor of the IAB node after RLF recovery, and the non-F1-terminated donor is the donor of the IAB node before RLF recovery, and the method is The non-F1 terminating donor receives IP address request information for the non-F1 terminating topology domain for the IAB node from the F1 terminating donor transmission, In this method, the first RRC container is carried by the UE context retrieval response message.

[0342] (Appendix 14.1) The method described in Appendix 14, wherein the method further includes: A method comprising the non-F1 terminating donor transmitting the IP address configuration information to the IAB node.

[0343] (Note 15) The method described in Appendix 1, The IP address request information is carried by an IAB transmission transition management request message.

[0344] (Note 16) The method described in Appendix 15, A method wherein the IP address request information includes a boundary node indicator, and the boundary node indicator is used to indicate that the IAB node is a boundary node.

[0345] (Note 17) The method described in Appendix 1, The IP address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message, in a manner that allows this to be done.

[0346] (Note 18) The method described in Appendix 17, A method wherein the IP address configuration information includes a boundary node indicator, and the boundary node indicator is used to indicate that the IAB node is a boundary node.

[0347] (Note 19) The method described in Appendix 15 or 17, The F1-terminated donor is the source donor for the IAB node switching, the non-F1-terminated donor is the target donor for the IAB node switching, and the method is The non-F1 terminating donor receives IP address request information for the non-F1 terminating topology domain for the IAB node from the F1 terminating donor transmission, The method involves the IP address request information being carried by an IAB transmission transition management request message.

[0348] (Appendix 19.1) The method described in Appendix 19, wherein the method further includes: A method comprising the non-F1 terminating donor transmitting the IP address configuration information to the IAB node.

[0349] (Note 20) The method described in Appendix 15 or 17, The F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method is The non-F1 terminating donor receives IP address request information for the non-F1 terminating topology domain for the IAB node from the F1 terminating donor transmission, The method involves the IP address request information being carried by an IAB transmission transition management request message.

[0350] (Note 20.1) The method described in Appendix 20, wherein the method further includes: The non-F1 terminating donor transmits IP address configuration information for the non-F1 terminating topology domain to be assigned to the IAB node to the F1 terminating donor, The method involves the IP address configuration information being carried by an IAB transmission transition management response message.

[0351] (Appendix 20.2) The method described in Appendix 20 or 20.1, wherein the method further includes: A method comprising the non-F1 terminating donor transmitting the IP address configuration information to the IAB node.

[0352] (Note 21) The method described in Appendix 15 or 17, The F1-terminated donor is the main node MN of the IAB node, and the non-F1-terminated donor is the secondary node SN of the IAB node, and the method is The non-F1 terminating donor transmits IP address configuration information for the non-F1 terminating topology domain to be assigned to the IAB node to the F1 terminating donor, The method involves the IP address configuration information being carried by an IAB transmission transition change request message.

[0353] (Note 22) The method described in Appendix 15 or 17, The non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method is The non-F1 terminating donor receives IP address request information for the non-F1 terminating topology domain for the IAB node from the F1 terminating donor transmission, The method involves the IP address request information being carried by an IAB transmission transition management request message.

[0354] (Note 22.1) The method described in Appendix 22, wherein the method further includes: A method comprising the non-F1 terminating donor transmitting the IP address configuration information to the IAB node.

[0355] (Note 23) The method described in Appendix 15 or 17, The non-F1 terminated donor is the main node MN of the IAB node, and the F1 terminated donor is the secondary node SN of the IAB node, and the method is The non-F1 terminating donor receives the F1 terminating donor transmission, which includes IP address configuration information for the F1 terminating topology domain assigned to the IAB node. The method involves the IP address configuration information being carried by an IAB transmission transition management request message.

[0356] (Note 23.1) The method described in Appendix 23, wherein the method further includes: A method comprising the non-F1 terminating donor transmitting the IP address configuration information to the IAB node.

[0357] (Note 24) The method described in Appendix 15 or 17, The F1-terminated donor is the donor of the IAB node after RLF recovery, and the non-F1-terminated donor is the donor of the IAB node before RLF recovery, and the method is The non-F1 terminating donor receives IP address request information for the non-F1 terminating topology domain for the IAB node from the F1 terminating donor transmission, The method involves the IP address request information being carried by an IAB transmission transition management request message.

[0358] (Note 24.1) The method described in Appendix 24, wherein the method further includes: A method comprising the non-F1 terminating donor transmitting the IP address configuration information to the IAB node.

[0359] (Note 25) IAB donor device, Including memory and processing units, The memory device stores a computer program. Among these, the processing unit is configured to execute the computer program and realize the transmission address setting method described in any one of the appendices 1 to 25.

[0360] <f1> (Note 1) IAB donor device, The aforementioned IAB donor device is the F1 termination donor device of the IAB node. The aforementioned equipment includes a first transmitting unit and / or a first receiving unit, The first transmitting unit is, Send IP address request information for the non-F1 termination topology domain for the IAB node to the non-F1 termination donor; and / or The non-F1 terminated donor transmits the IP address configuration information of the F1 terminated topology domain assigned to the IAB node. The first receiving unit is a device that receives IP address configuration information of a non-F1 terminating topology domain assigned to the IAB node, transmitted by the non-F1 terminating donor.

[0361] (Note 2) The equipment described in Appendix 1, The aforementioned IP address request information is carried by the first RRC container, the device.

[0362] (Note 3) The equipment described in Appendix 2, The first RRC container further includes IP address configuration information in the F1 termination topology domain of the IAB node.

[0363] (Note 4) The equipment described in Appendix 2 or 3, The IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.

[0364] (Note 5) The equipment described in any one of the appendices 2 to 4, The first RRC container is carried by at least one message, namely, Switch request message; Secondary node addition request message; Secondary node change request message; Secondary node change request message; and UE context acquisition response message It is a device.

[0365] (Note 6) The equipment described in Appendix 1, The aforementioned IP address configuration information is carried by the second RRC container for the device.

[0366] (Note 7) The equipment described in Appendix 6, The aforementioned IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container of the device.

[0367] (Note 8) The equipment described in Appendix 6 or 7, The second RRC container is carried by at least one of the following messages, namely, Switching request response message; Secondary node addition response message; Secondary node change response message; and Secondary node change request message It is a device.

[0368] (Note 9) The equipment described in Appendix 5 or 8, The F1-terminated donor is the source donor for the IAB node switching, the non-F1-terminated donor is the target donor for the IAB node switching, the first transmitting unit transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor, and the first receiving unit receives IP address configuration information for the non-F1-terminated topology domain to be assigned to the IAB node, transmitted by the non-F1-terminated donor. The device wherein the first RRC container is carried by a switching request message, and the second RRC container is carried by a switching request response message.

[0369] (Note 10) The equipment described in Appendix 5 or 8, The F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, and the first transmission unit transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor. Among these, the first RRC container is carried by a secondary node addition request message or a secondary node modification request message.

[0370] (Note 10.1) The equipment described in Appendix 10, The first receiving unit further receives IP address configuration information of a non-F1 terminating topology domain assigned to the IAB node, transmitted by the non-F1 terminating donor. Of these, the second RRC container is carried by a secondary node addition response message or a secondary node modification response message.

[0371] (Note 11) The equipment described in Appendix 5 or 8, The F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, and the first receiving unit receives IP address configuration information of the non-F1-terminated topology domain assigned to the IAB node, transmitted by the non-F1-terminated donor. Of these, the second RRC container is carried by a secondary node change request message, and is a piece of equipment.

[0372] (Note 12) The equipment described in Appendix 5 or 8, The non-F1 terminating donor is the main node MN of the IAB node, the F1 terminating donor is the secondary node SN of the IAB node, and the first transmission unit transmits IP address request information for the non-F1 terminating topology domain for the IAB node to the non-F1 terminating donor. Of these, the first RRC container is carried by a secondary node change request message, and is a piece of equipment.

[0373] (Note 13) The equipment described in Appendix 5 or 8, The non-F1 termination donor is the main node MN of the IAB node, the F1 termination donor is the secondary node SN of the IAB node, and the first transmission unit transmits to the non-F1 termination donor IP address configuration information of the F1 termination topology domain assigned to the IAB node. Of these, the second RRC container is carried by a secondary node change request message, and is a piece of equipment.

[0374] (Note 14) The equipment described in Appendix 5 or 8, The F1-terminated donor is the donor of the IAB node after RLF recovery, the non-F1-terminated donor is the donor of the IAB node before RLF recovery, and the first transmission unit transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor. Of these, the first RRC container is carried by the UE context acquisition response message, and is a device.

[0375] (Note 15) The equipment described in Appendix 1, The aforementioned IP address request information is carried by an IAB transmission transition management request message for the device.

[0376] (Note 16) The equipment described in Appendix 15, The IP address request information includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node.

[0377] (Note 17) The equipment described in Appendix 1, The aforementioned IP address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message for the device.

[0378] (Note 18) The equipment described in Appendix 17, The IP address configuration information includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node.

[0379] (Note 19) The equipment described in Appendix 15 or 17, The F1-terminated donor is the source donor for the IAB node switching, the non-F1-terminated donor is the target donor for the IAB node switching, and the first transmission unit transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor. Among these, the IP address request information is carried by the IAB transmission transition management request message.

[0380] (Note 20) The equipment described in Appendix 15 or 17, The F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, and the first transmission unit transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor. Among these, the IP address request information is carried by the IAB transmission transition management request message.

[0381] (Note 20.1) The equipment described in Appendix 20, The first receiving unit further receives IP address configuration information of a non-F1 terminating topology domain assigned to the IAB node, transmitted by the non-F1 terminating donor. Among these, the IP address configuration information is carried by the IAB transmission transition management response message for the device.

[0382] (Note 21) The equipment described in Appendix 15 or 17, The F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, and the first receiving unit receives IP address configuration information of the non-F1-terminated topology domain assigned to the IAB node, transmitted by the non-F1-terminated donor. Among these, the IP address configuration information is carried by the IAB transmission transition change request message for the device.

[0383] (Note 22) The equipment described in Appendix 15 or 17, The non-F1 terminating donor is the main node MN of the IAB node, the F1 terminating donor is the secondary node SN of the IAB node, and the first transmission unit transmits IP address request information for the non-F1 terminating topology domain for the IAB node to the non-F1 terminating donor. Among these, the IP address request information is carried by the IAB transmission transition management request message.

[0384] (Note 23) The equipment described in Appendix 15 or 17, The non-F1 termination donor is the main node MN of the IAB node, the F1 termination donor is the secondary node SN of the IAB node, and the first transmission unit transmits to the non-F1 termination donor IP address configuration information of the F1 termination topology domain assigned to the IAB node. Among these, the IP address configuration information is carried by the IAB transmission transition management request message for the device.

[0385] (Note 24) The equipment described in Appendix 15 or 17, The F1-terminated donor is the donor of the IAB node after RLF recovery, the non-F1-terminated donor is the donor of the IAB node before RLF recovery, and the first transmission unit transmits IP address request information for the non-F1-terminated topology domain for the IAB node to the non-F1-terminated donor. Among these, the IP address request information is carried by the IAB transmission transition management request message.

[0386] (Note 25) The device described in Appendix 9, 10, 10.1, 11, 20, 20.1, or 21, wherein the first transmitting unit further transmits the IP address configuration information to the IAB node.

[0387] <Non-F1> (Note 1) IAB donor device, The aforementioned IAB donor device is a non-F1 terminated donor device of an IAB node. The aforementioned device includes a second receiving unit and / or a second transmitting unit, The second receiving unit is, Receive IP address request information for a non-F1 terminated topology domain for the IAB node transmitted by an F1 terminated donor; and / or The system receives IP address configuration information for the F1 termination topology domain assigned to the IAB node, transmitted by the F1 termination donor. The second transmitting unit is a device that transmits IP address configuration information for a non-F1 terminating topology domain assigned to the IAB node to an F1 terminating donor.

[0388] (Note 2) The equipment described in Appendix 1, The aforementioned IP address request information is carried by the first RRC container, the device.

[0389] (Note 3) The equipment described in Appendix 2, The first RRC container further includes IP address configuration information in the F1 termination topology domain of the IAB node.

[0390] (Note 4) The equipment described in Appendix 2 or 3, The IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.

[0391] (Note 5) The equipment described in any one of the appendices 2 to 4, The first RRC container is carried by at least one message, namely, Switch request message; Secondary node addition request message; Secondary node change request message; Secondary node change request message; and UE context acquisition response message It is a device.

[0392] (Note 6) The equipment described in Appendix 1, The aforementioned IP address configuration information is carried by the second RRC container for the device.

[0393] (Note 7) The equipment described in Appendix 6, The aforementioned IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container of the device.

[0394] (Note 8) The equipment described in Appendix 6 or 7, The second RRC container is carried by at least one of the following messages, namely, Switching request response message; Secondary node addition response message; Secondary node change response message; and Secondary node change request message It is a device.

[0395] (Note 9) The equipment described in Appendix 5 or 8, The F1-terminated donor is the source donor for the IAB node switching, the non-F1-terminated donor is the target donor for the IAB node switching, the second receiving unit receives IP address request information for the non-F1-terminated topology domain for the IAB node from the F1-terminated donor, and the second transmitting unit transmits IP address setting information for the non-F1-terminated topology domain to be assigned for the IAB node to the F1-terminated donor. The device wherein the first RRC container is carried by a switching request message, and the second RRC container is carried by a switching request response message.

[0396] (Note 10) The equipment described in Appendix 5 or 8, The F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, and the second receiving unit receives the IP address request information for the non-F1-terminated topology domain for the IAB node transmitted by the F1-terminated donor. Among these, the first RRC container is carried by a secondary node addition request message or a secondary node modification request message.

[0397] (Note 10.1) The equipment described in Appendix 10, The second transmission unit further transmits to the F1 termination donor IP address configuration information for the non-F1 termination topology domain assigned to the IAB node, Of these, the second RRC container is carried by a secondary node addition response message or a secondary node modification response message.

[0398] (Note 11) The equipment described in Appendix 5 or 8, The F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, and the second transmission unit transmits IP address configuration information for the non-F1-terminated topology domain assigned to the IAB node to the F1-terminated donor. Of these, the second RRC container is carried by a secondary node change request message, and is a piece of equipment.

[0399] (Note 12) The equipment described in Appendix 5 or 8, The non-F1 terminated donor is the main node MN of the IAB node, the F1 terminated donor is the secondary node SN of the IAB node, and the second receiving unit receives the IP address request information for the non-F1 terminated topology domain for the IAB node transmitted by the F1 terminated donor. Of these, the first RRC container is carried by a secondary node change request message, and is a piece of equipment.

[0400] (Note 13) The equipment described in Appendix 5 or 8, The non-F1 termination donor is the main node MN of the IAB node, the F1 termination donor is the secondary node SN of the IAB node, and the second receiving unit receives the IP address configuration information of the F1 termination topology domain assigned to the IAB node from the F1 termination donor transmission. Of these, the second RRC container is carried by a secondary node change request message, and is a piece of equipment.

[0401] (Note 14) The equipment described in Appendix 5 or 8, The F1-terminated donor is the donor of the IAB node after RLF recovery, and the non-F1-terminated donor is the donor of the IAB node before RLF recovery. The second receiving unit receives the IP address request information for the non-F1-terminated topology domain for the IAB node transmitted by the F1-terminated donor. Of these, the first RRC container is carried by the UE context acquisition response message, and is a device.

[0402] (Note 15) The equipment described in Appendix 1, The aforementioned IP address request information is carried by an IAB transmission transition management request message for the device.

[0403] (Note 16) The equipment described in Appendix 15, The IP address request information includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node.

[0404] (Note 17) The equipment described in Appendix 1, The aforementioned IP address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message for the device.

[0405] (Note 18) The equipment described in Appendix 17, The IP address configuration information includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node.

[0406] (Note 19) The equipment described in Appendix 15 or 17, The F1-terminated donor is the source donor for the IAB node switching, the non-F1-terminated donor is the target donor for the IAB node switching, and the second receiving unit receives the IP address request information for the non-F1-terminated topology domain for the IAB node transmitted by the F1-terminated donor. Among these, the IP address request information is carried by the IAB transmission transition management request message.

[0407] (Note 20) The equipment described in Appendix 15 or 17, The F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, and the second receiving unit receives the IP address request information for the non-F1-terminated topology domain for the IAB node transmitted by the F1-terminated donor. Among these, the IP address request information is carried by the IAB transmission transition management request message.

[0408] (Note 20.1) The equipment described in Appendix 20, The second transmission unit further transmits to the F1 termination donor IP address configuration information for the non-F1 termination topology domain assigned to the IAB node, Among these, the IP address configuration information is carried by the IAB transmission transition management response message for the device.

[0409] (Note 21) The equipment described in Appendix 15 or 17, The F1-terminated donor is the main node MN of the IAB node, the non-F1-terminated donor is the secondary node SN of the IAB node, and the second transmission unit transmits IP address configuration information for the non-F1-terminated topology domain assigned to the IAB node to the F1-terminated donor. Among these, the IP address configuration information is carried by the IAB transmission transition change request message for the device.

[0410] (Note 22) The equipment described in Appendix 15 or 17, The non-F1 terminated donor is the main node MN of the IAB node, the F1 terminated donor is the secondary node SN of the IAB node, and the second receiving unit receives the IP address request information for the non-F1 terminated topology domain for the IAB node transmitted by the F1 terminated donor. Among these, the IP address request information is carried by the IAB transmission transition management request message.

[0411] (Note 23) The equipment described in Appendix 15 or 17, The non-F1 termination donor is the main node MN of the IAB node, the F1 termination donor is the secondary node SN of the IAB node, and the second receiving unit receives the IP address configuration information of the F1 termination topology domain assigned to the IAB node from the F1 termination donor transmission. Among these, the IP address configuration information is carried by the IAB transmission transition management request message for the device.

[0412] (Note 24) The equipment described in Appendix 15 or 17, The F1-terminated donor is the donor of the IAB node after RLF recovery, and the non-F1-terminated donor is the donor of the IAB node before RLF recovery. The second receiving unit receives the IP address request information for the non-F1-terminated topology domain for the IAB node transmitted by the F1-terminated donor. Among these, the IP address request information is carried by the IAB transmission transition management request message.

[0413] (Note 25) The equipment described in Appendix 10 or 10.1 or 12 or 13 or 4 or 19 or 20 or 20.1 or 22 or 23 or 24, The second transmitting unit further transmits the IP address configuration information to the IAB node.

Claims

1. IAB node IAB donor CU equipment, The aforementioned IAB donor CU device is an F1-terminal donor CU device. The aforementioned IAB donor CU equipment includes a transmitter and a receiver. The transmitter transmits address request information for the non-F1 terminated topology domain for the IAB node to the non-F1 terminated donor CU, and the address request information includes a request for the TNL address of the non-F1 terminated topology domain for the IAB node. The receiver receives addressing information for the non-F1 terminating topology domain assigned to the IAB node, transmitted by the non-F1 terminating donor CU, and the addressing information for the non-F1 terminating topology domain includes the TNL address of the non-F1 terminating topology domain for the IAB node, in the IAB donor CU equipment.

2. IAB donor CU equipment according to claim 1, The aforementioned address request information is carried by the IAB transmission transition management request message. The address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message to an IAB donor CU device.

3. IAB donor CU equipment according to claim 1, The aforementioned address request information is carried by an IAB Other Information message to the IAB donor CU device.

4. IAB donor CU equipment according to claim 3, The F1 termination donor CU is the master node (MN) of the IAB node, The non-F1 terminated donor CU is an IAB donor CU device that is a secondary node (SN) of the IAB node.

5. IAB node IAB donor CU equipment, The aforementioned IAB donor CU equipment is a non-F1 terminated donor CU equipment. The aforementioned IAB donor CU equipment includes a receiver and a transmitter. The receiver receives address request information for a non-F1 terminated topology domain for the IAB node transmitted from the F1 terminated donor CU, and the address request information includes a request for a TNL address for a non-F1 terminated topology domain for the IAB node. The transmitter transmits address configuration information for the non-F1 terminated topology domain assigned to the IAB node, and the address configuration information for the non-F1 terminated topology domain includes the TNL address of the non-F1 terminated topology domain for the IAB node, in an IAB donor CU device.

6. IAB donor CU equipment according to claim 5, The non-F1 terminating donor CU device transmits the address setting information to the F1 terminating donor CU by carrying the address setting information to an IAB transmission transition management response message.

7. IAB donor CU equipment according to claim 5, The non-F1 terminated donor CU device is an IAB donor CU device that transfers the address setting information to the IAB node by carrying the address setting information in an RRC reconfiguration message.

Images