IAB donor device and transmission address setting method

Abstract

In an embodiment of the present invention, an IAB donor device and a transmission address configuration method are provided, the IAB donor device includes a first sending unit and / or a first receiving unit, the first sending unit sends IP address request information of a non-F1 termination topology domain for the IAB node to a non-F1 termination donor and / or sends IP address configuration information of a non-F1 termination topology domain assigned for the IAB node to the non-F1 termination donor, and the first receiving unit receives the IP address configuration information of a non-F1 termination topology domain assigned for the IAB node sent by the non-F1 termination donor.

Description

[Technical field]

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

[0002] The deployment of future seamless cellular networks requires highly flexible and ultra-dense new radio (NR) cell deployment, and ultra-dense networks are one of the goals of 5G. The deployment of one NR network without wired backhaul is very important for the realization of 5G ultra-dense networks. As the cell coverage is reduced by 5G mmWave, wireless self-backhaul systems require multi-hop to meet the deployment needs. Due to 5G's high bandwidth, massive multiple-input multiple-output (MIMO) and beam system, 5G makes it easier to develop ultra-dense NR cell wireless self-backhaul systems than LTE, and to develop such multi-hop systems with wireless self-backhaul, 3GPP has started research and standardization of the Integrated access and backhaul (IAB) project in Rel-16.

[0003] Figure 1 is a diagram showing an IAB system. As shown in Figure 1, in the IAB system, access and backhaul adopt wireless transmission via the NR Uu air interface, a relay node supports 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, the relay node refers to the IAB-node, which supports access and backhaul functions simultaneously. The last one-hop access node on the network side is called the IAB-donnor, which supports the function of gNB and also supports the access of the IAB-node. All UE data can be backhauled to the IAB-donnor via the IAB-node by one hop or multiple hops.

[0005] The function of the IAB-node is divided into two parts, one part is the gNB-DU function, called IAB-DU (distributed unit), and the other part is the UE function, called IAB-MT (mobile terminal). The IAB-DU realizes the network side equipment function, connects to the downstream child IAB-node (child IAB node (or abbreviated as child node)), provides NR air interface access for the UE and the downstream child IAB-node, and establishes F1 connection with the IAB donor-CU (donor centralized unit). The IAB-MT realizes some terminal equipment function, connects to the upstream parent IAB-node (parent IAB node (or abbreviated as parent node)) or IAB donor-DU, and the IAB-MT includes the functions of the physical layer, layer 2, RRC (Radio Resource Control) and NAS (Non-Access Stratum), and is indirectly connected to the IAB Donor-CU and the core network (Core Network, CN).

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

[0007] Figure 4 shows one 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 the transport (IP) layer between the IAB-DU and the IAB donor-CU, and Figures 5 and 6 include two-hop wireless backhaul and one-hop wired backhaul.

[0009] In the backhaul link, the transport (IP) layer is carried by the Backhaul Adaptation Protocol (BAP) sublayer, the BAP entity in the IAB-node realizes the routing function of the IAB system, and the IAB donor-CU provides the routing table. The BAP PDU (Protocol Data Unit) is carried by the RLC (Radio Link Control) channel of the backhaul link, and multiple RLC channels of the backhaul link can be configured by the IAB-donor to carry tasks (traffic) with different priorities and QoS (Quality of Service), and the BAP entity maps the BAP PDU to different backhaul RLC channels.

[0010] It should be noted that the introduction of the above background art is intended to clearly and completely explain the technical solutions of the present invention, and to facilitate understanding thereof by those skilled in the art, and these technical solutions are described in the background art of the present invention, and therefore should not be construed as being known to those skilled in the art. Summary of the Invention [Problem to be solved by the invention]

[0011] The inventor has found that, when all or part of the services of an IAB node need to be migrated or configured from an F1-terminating topology domain to a non-F1-terminating topology domain, all the routing IDs of the IAB node belong to the non-F1-terminating topology domain, or the IAB node simultaneously transmits the services whose routing IDs belong to the F1-terminating topology domain and whose routing IDs belong to the non-F1-terminating topology domain. For the routing IDs of the non-F1-terminating topology domain, the IAB node needs to use the IP addresses of the non-F1-terminating topology domain, and for the routing IDs of the F1-terminating topology domain, the IAB node needs to use the IP addresses of the F1-terminating topology domain. The network needs to configure the IAB node with an IP address anchored to a donor-DU of the non-F1-terminating topology domain, or an IP address anchored to a donor-DU of the F1-terminating topology domain. However, there is currently no corresponding scheme for how to request IP addresses of non-F1 terminating topology domains or how to configure IP addresses of F1 terminating domains and non-F1 terminating domains.

[0012] To solve at least one of the above problems, an embodiment of the present invention provides an IAB donor device and a transmission address setting method. [Means for solving the problem]

[0013] According to one aspect of an embodiment of the present invention, a transport address configuration method is provided, which is applied to an F1 termination donor device of an IAB node, the method comprising: the F1 termination donor sends to a non-F1 termination donor an IP address request information of a non-F1 termination topology domain for the IAB node; and / or the F1 termination donor receiving IP address configuration information of the non-F1 termination topology domain to be assigned for the IAB node, sent by the non-F1 termination donor; and / or The F1 termination donor transmits IP address configuration information of the F1 termination topology domain allocated for the IAB node to a non-F1 termination donor.

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

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

[0016] According to another aspect of an embodiment of the present invention, there is provided an IAB donor device, the IAB donor device being a non-F1 termination donor device of an IAB node, the IAB donor device including a second receiving unit and / or a second transmitting unit; The second receiving unit is receiving IP address request information of a non-F1 termination topology domain for said IAB node sent by an F1 termination donor; and / or Receive IP address configuration information of an F1 termination topology domain assigned for the IAB node sent by an F1 termination donor; The second sending unit sends IP address configuration information of a non-F1 termination topology domain assigned to the IAB node to an F1 termination donor.

[0017] According to another aspect of an embodiment of the present invention, there is provided a communication system, the system including an IAB donor device according to the previous aspect. Effect of the Invention

[0018] The advantageous effects of the embodiment of the present invention are at least as follows: the F1 termination donor can request the non-F1 termination donor to allocate an IP address of the non-F1 termination topology domain, or can cause the F1 termination donor to request an IP address of the non-F1 termination topology domain by further receiving IP address configuration information of the non-F1 termination topology domain allocated for the IAB node by the non-F1 termination donor, or can further send an IP address of the non-F1 termination topology domain for the IAB node when the non-F1 termination donor cannot send a message to the IAB node. For example, when the non-F1 termination donor cannot send a message to the IAB node, the F1 termination donor can send an IP address of the non-F1 termination topology domain for the IAB node by receiving IP address configuration information of the non-F1 termination topology domain spontaneously sent by the non-F1 termination donor. Also, for example, when the F1 termination donor cannot send a message to the IAB node, the F1 termination donor can cause the non-F1 termination donor to send the IP address of the F1 termination topology domain to the IAB node by sending IP address configuration information of the F1 termination topology domain to the non-F1 termination donor. In this way, the IAB node can use the IP address of the non-F1 termination topology domain for the routing ID of the non-F1 termination topology domain, and can use the IP address of the F1 termination topology domain for the routing ID of the F1 termination topology domain.

[0019] Specific embodiments of the present invention are disclosed in detail below with reference to the following description and drawings, which show how the principles of the present invention may be employed, but are not limited in scope to these embodiments, which may include various changes, modifications, and alternatives within the scope of the appended claims.

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

[0021] It should be noted that terms such as "comprise / have" when used in this specification refer to the presence of a feature, element, step, or assembly, 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 invention may be combined with elements and features shown in one or more other drawings or embodiments, and in the drawings, like reference numerals are used to indicate corresponding parts in several drawings and to indicate corresponding parts used in several embodiments.

[0023] The included drawings are used to provide a further understanding of the embodiments of the present invention, and these drawings constitute a part of this specification, illustrate the embodiments of the present invention, and together with the written description, are used to explain the principles of the present invention. Also, it is obvious that the drawings described below are only for illustrating some embodiments of the present invention, and a person skilled in the art can derive other drawings based on these drawings without creative labor. [Figure 1] FIG. 1 illustrates an IAB system. [Diagram 2] A diagram showing the IAB architecture in SA mode. [Diagram 3] A diagram showing the IAB architecture in EN-DC mode. [Figure 4] FIG. 2 is a diagram showing a parent node (parent IAB-node) and a child node (child IAB-node). [Diagram 5] FIG. 2 illustrates the F1-U protocol stack of the IAB system. [Figure 6] FIG. 2 illustrates the F1-C protocol stack of the IAB system. [Figure 7] FIG. 1 illustrates routing in an IAB system. [Figure 8]FIG. 1 illustrates network topology adaptation. [Figure 9] FIG. 1 illustrates an IAB donor device in accordance with an embodiment of the present invention. [Figure 10] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 11] FIG. 1 illustrates a switching scenario. [Figure 12] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 13] FIG. 1 illustrates a dual connection scenario 1. [Figure 14] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 15] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 16] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 17] FIG. 13 illustrates a dual connection scenario 2. [Figure 18] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 19] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 20] FIG. 1 illustrates an RLF recovery scenario. [Figure 21] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 22] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Diagram 23] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 24] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Diagram 25] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 26] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 27]FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 28] FIG. 2 is a diagram showing a transmission address setting method in an embodiment of the present invention. [Figure 29] FIG. 1 illustrates an IAB donor device in accordance with an embodiment of the present invention. [Diagram 30] FIG. 1 illustrates an IAB donor device in accordance with an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] The above and other features of the present invention will become apparent from the following detailed description and the accompanying drawings, in which: While the specification and drawings disclose certain embodiments of the present invention, these are illustrative of only some of the embodiments which may employ the principles of the present invention, and it is to be understood that the present invention is not limited to the described embodiments, but rather includes all modifications, variations and alternatives which fall within the scope of the appended claims.

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

[0026] Additionally, communications between devices in the communications system may be performed according to any stage of communications protocol, including, but not limited to, the following communications protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, New Radio (NR), and / or other conventional or future developed communications protocols.

[0027] In the embodiment of the present invention, the term "network device" refers to a device that connects a terminal device to a communication network and provides services to the terminal device in a communication system, for example. The network device may include, but is not limited to, a "node" and / or a "donor" in the IAB architecture, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a network gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0028] Among them, the base station may include, but is not limited to, the following: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 5G base station (gNB), etc., and may further include RRH (Remote Radio Head), RRU (Remote Radio Unit), relay, or low power node (e.g., femto, pico, etc.). The term "base station" may also include some or all of the functions thereof, and each base station can provide communication coverage for a specific geographical area. For example, a 5G base station gNB may include one gNB CU and one or more gNB DUs, in which a CU / DU is a logical node of a gNB having some functions of a gNB. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0029] In the embodiment of the present invention, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to a device that accesses a communication network and receives services from the network, for example, through a network device. The user equipment may be fixed or mobile, and may also be called a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc. For example, a terminal equipment served by an IAB node or an IAB donor under the IAB architecture.

[0030] Among these, user equipment may include, but is not limited to, the following: a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a mobile device, a machine type communication device, a laptop computer, a cordless telephone, a smartphone, a smart watch, a digital camera, etc.

[0031] Furthermore, in a scenario such as the Internet of Things (IoT), the user equipment may also be a monitoring or measuring device or apparatus, including, but not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, etc.

[0032] Additionally, the term "network side" or "network equipment side" refers to the side of a network, which may be a base station or may include one or more network equipment as described above. The term "user side" or "terminal side" or "terminal equipment side" refers to the side of a user or terminal, which may be a UE or may include one or more terminal equipment as described above.

[0033] The signaling radio bearers SRB include SRB0, SRB1, SRB2, and SRB3, among 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 (possibly including piggybacked NAS messages) and NAS messages before SRB2 establishment, and uses the dedicated control channel (DCCH) logical channel. SRB2 transmits RRC messages including NAS messages and logged measurement messages, and uses the DCCH logical channel. SRB2 has a lower priority than SRB1 and can be configured by the network after the access stratum (AS) is securely 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 realized by the BAP layer, and each IAB-node stores the BH routing configuration and the BH RLC channel mapping configuration. The BAP entity performs routing based on the routing configuration, the RLC channel mapping configuration, and the routing ID in the BAP layer data packet header. The Routing ID includes the destination BAP address and the route indicator.

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

[0036] Figure 7 is a diagram showing the routing of the IAB system. As shown in Figure 7, for each data packet, the next-hop node BAP address can be found from the routing configuration according to the routing ID in the data packet header. The prior hop node BAP address and the ingress link RLC channel ID are all known. In this way, after the next-hop node BAP address is determined, the egress link RLC channel ID can be found according to the prior hop node BAP address + ingress link RLC channel ID + next-hop node BAP address through the RLC channel mapping configuration.

[0037] The IAB-donor DU stores the BH routing configuration and the Downlink Traffic to BH RLC Channel Mapping Configuration. The IAB-donor DU performs routing based on the routing configuration, the 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, the Differentiated Services Code Point (DSCP), the next hop node address, and the egress link RLC channel ID.

[0038] For each downlink data packet arriving at the IAB-donor DU, the IAB-donor DU can find the next-hop node address from the routing configuration according to the Routing ID in the data packet header, and after the next-hop node address is determined in this way, it can find the egress link RLC channel ID from the downlink RLC channel mapping configuration according to the IP address and DSCP of the data packet.

[0039] The access IAB node stores uplink backhaul information (BH information), which includes a routing ID used by the service, an uplink backhaul RLC channel ID, and a next-hop node address. The access IAB node sets the routing ID in the BAP layer data packet header of the uplink service based on the uplink BH information, and selects a BH RLC channel and a next-hop node for the transmission of the uplink service.

[0040] The above describes the routing and BH RLC channel mapping of the IAB system. Below, we will explain the network topology update of the IAB system. Rel-16 NR has already standardized the topology adaptation process when an IAB-node moves under the same donor-CU.

[0041] Figure 8 shows intra-CU topology adaptation. When the IAB-node changes its parent node (from IAB-node 1 to IAB-node 2), the donor-CU configures the IAB-node with a RRC reconfiguration message to configure the path transition, so that the IAB-node performs the F1 transmission path transition.

[0042] The route transition configuration includes updates to the default backhaul RLC channel for uplink F1-C, F1-U and non-F1 data, updates to the default BH RLC channel, and updates to the IP address for routing to Donor-DU. When the IAB-node accesses the new parent node, it starts applying the above route transition configuration, and also applies route transition configuration to the child nodes of the IAB-node in the same way.

[0043] 3GPP Rel-17 supports network topology update and backhaul (BH) Radio Link Failure (RLF) recovery processes when an IAB-node moves under a different donor-CU, and the IAB-node can switch or re-establish a parent node serving a source donor (which may be called F1-terminating CU or first donor-CU) to a parent node serving a target donor (which may be called non-F1-terminating CU or second donor-CU), and all the services of the IAB-node (and the services of its child nodes) need to be migrated to the topology of the non-F1-terminating CU. Rel-17 also supports a topology redundancy process when an IAB-node establishes a dual connection with a non-F1-terminating CU, and the transmission paths of some services of the IAB-node can be migrated to the topology of the non-F1-terminating CU.

[0044] After the IAB-node switches / RLF recovers from donor- CU 1 (F1-terminating CU) to donor-CU 2 (non-F1-terminating CU) or increases the RRC connection with donor-CU 2, only the IAB-MT RRC is connected to donor- CU 2 and the F1 interface is still terminated on donor- CU 1, at this time the IAB-node may be called a boundary node. Because the RRC connection and F1 interface of its serving child node still belong to donor-CU1, the child node's service routing ID, BH RLC channel and next-hop BAP address 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 the boundary node simultaneously transmits the routing IDs belonging to the F1-terminating topology domain and the routing IDs belonging to the non-F1-terminating topology domain. For the routing IDs of a non-F1-terminating topology domain, the boundary node must use the IP addresses of the non-F1-terminating topology domain, and for the routing IDs of an F1-terminating topology domain, the boundary node must use the IP addresses of the F1-terminating topology domain. The network must configure an IP address anchored to a donor-DU of a non-F1-terminating topology domain or an IP address anchored to a donor-DU of an F1-terminating topology domain for a boundary node. However, there is currently no corresponding scheme for how to request an IP address of a non-F1-terminating topology domain or how to configure an IP address of an F1-terminating domain and a non-F1-terminating domain.

[0046] In the embodiment of the present invention, unless otherwise specified, the IAB node device includes a transition node. Also, "resources for serving the IAB node's business in the donor-CU's topology domain have already been established" may be expressed as "the IAB node's business is transitioned to the donor-CU's topology domain", but the present invention is not limited to these expressions. The embodiment of the present invention will be further described below.

[0047] <Example of the first aspect> In the embodiment of the present invention, a transport address configuration method is provided, which is described from the F1 termination donor equipment side of the IAB node.

[0048] 10 is a diagram illustrating a method for setting a transmission address in an embodiment of the present invention. As shown in FIG. 10, the method includes the following steps (operations):

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

[0050] It should be noted that the above-mentioned FIG. 10 is merely for illustrative purposes of the 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-mentioned contents without being limited to the description of the above-mentioned FIG. 10.

[0051] As can be seen from the above embodiment, the F1 termination donor can request the non-F1 termination donor to allocate an IP address of the non-F1 termination topology domain, or can cause the F1 termination donor to request an IP address of the non-F1 termination topology domain by further receiving IP address configuration information of the non-F1 termination topology domain allocated for the IAB node by the non-F1 termination donor, or can further transmit an IP address of the non-F1 termination topology domain for the IAB node, for example, when the non-F1 termination donor cannot send a message to the IAB node. For example, when the non-F1 termination donor cannot send a message to the IAB node, the F1 termination donor can transmit an IP address of the non-F1 termination topology domain for the IAB node by receiving IP address configuration information of the non-F1 termination topology domain voluntarily transmitted by the non-F1 termination donor. Also, for example, when the F1 termination donor cannot send a message to the IAB node, the F1 termination donor can cause the non-F1 termination donor to send the IP address of the F1 termination topology domain to the IAB node by sending IP address configuration information of the F1 termination topology domain to the non-F1 termination donor. In this way, the IAB node can use the IP address of the non-F1 termination topology domain for the routing ID of the non-F1 termination topology domain, and can use the IP address of the F1 termination topology domain for the routing ID of the F1 termination topology domain.

[0052] In some embodiments, the IAB node includes a transition node (also called a border node), an F1 connection of the IAB node is terminated at an F1 terminated donor, and the IAB node has an RRC connection with the non-F1 terminated donor. For example, an IAB-MT of the IAB node maintains an RRC connection with the non-F1 terminated donor, and 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), where the F1 terminated donor device refers to a donor-CU that terminates the F1 interface of the border IAB node and its child IAB nodes, e.g., the first IAB donor-CU. The non-F1 terminated donor device refers to a donor-capable CU that does not terminate the F1 interface of the border IAB node and its child IAB nodes, e.g., the second IAB donor-CU.

[0053] In some embodiments, the requested and / or configured IP address refers to an IP address anchored to a donor-DU that is configured for the IAB node (or may be said to be for the IAB node), and the IP address configuration information may include IP address configurations anchored to at least two donor-DUs, or may include 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 an embodiment of the present invention, an "IP address anchored to IAB donor-DU" may be understood as an "IP address assigned by the donor-DU" or "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, an IP address of a donor-DU of a non-F1 termination topology domain configured for the IAB node refers to a transport network layer (TNL) address that is routable via a donor-DU of a non-F1 termination topology domain configured for the IAB node.

[0055] In some embodiments, the above IP address request information and / or IP address configuration information may be carried by an RRC container, or may be carried by an IAB transport transition management request / response or an IAB transport transition change request, which will be described below.

[0056] (1) IP address request information and / or IP address configuration information is carried by an RRC container In some embodiments, the IP address request information is carried by a first RRC container, for example, the IP address request information is carried by another IAB information message (information element structure IABOtherInformation) or an RRC reconfiguration message included in the first RRC container, and the first RRC container includes IP address configuration information of 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 to report an IP address that is actually used or that 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 an IAB node to generate an IABOtherInformation message, and then sends it to the non-F1 termination donor in the first RRC container. The RRC reconfiguration message is an RRC message for the network to configure an IP address in the IAB node. In this embodiment, the F1 terminating donor generates an RRC reconfiguration message and sends it in a first RRC container to the non-F1 terminating donor, requesting an IP address of the non-F1 topology domain.

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

[0058] An existing RRC message (e.g., IABOtherInformation) is an RRC message for an IAB node to request an IP address from a donor, and an RRC reconfiguration message (RRCReconfiguration) is an RRC message for configuring an IP address in an IAB node. Therefore, by reusing an RRC message (e.g., IABOtherInformation) to carry IP address request information for a boundary node, and reusing an RRC reconfiguration message (RRCReconfiguration) to carry IP address configuration information for a boundary node, the request and configuration of an IP address can be made simpler and more flexible.

[0059] In some embodiments, the above IP address may be requested and / or configured using existing Xn processes (which may be carried by Xn Interface Adaptation Protocol (XnAP) signaling), such as handover preparation, dual connection establishment or modification process, UE context acquisition process, etc. For example, the first RRC container is carried by at least one of the following messages: a switch request message; a secondary node addition request message; a secondary node modification request message; a secondary node modification request message; and a UE context acquisition response message. The second RRC container is carried by at least one of the following messages: a switch request response message; a secondary node addition response message; a secondary node modification response message; and a secondary node modification request message. The following description will be given in conjunction with different scenarios. In addition, since these Xn processes are processes for a boundary node, they can be naturally distinguished from IP address requests and configuration information for a child node, so that the donor can send IP address configuration for the boundary node using an RRC connection with the boundary node.

[0060] I. Switching Scenarios In some embodiments, FIG. 11 is a diagram showing a switching scenario. As shown in FIG. 11, in the switching scenario, all operations of the boundary node are migrated to a non-F1 terminating topology domain, the F1 terminating donor is the source donor of the switching of the IAB node, the non-F1 terminating donor is the target donor of the switching of the IAB node, and the IP address of the non-F1 terminating topology domain refers to the IP address anchored to donor-DU2. FIG. 12 is a diagram showing a transmission address configuration method under the switching scenario. As shown in FIG. 12, the method includes the following steps:

[0061] 1201: The F1 termination donor sends to the non-F1 termination donor an IP address request information of the non-F1 termination topology domain for the IAB node; and 1202: The F1 termination donor receives IP address configuration information of the non-F1 termination topology domain assigned for the IAB node, sent by the non-F1 termination 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 switch request message, and the second RRC container is carried by a switch request response message. Thus, the F1 terminated donor sends a switch request message (HANDOVER REQUEST) to the non-F1 terminated donor, for example, the switch request message includes an RRC message HandoverPreparationInformation, the HandoverPreparationInformation may introduce the entire RRC message IABOtherInformation generated by the F1 terminated donor, the IABOtherInformation is the first RRC container, carries the IP address request information (IAB-TNLAddressInfo field) of the non-F1 terminated topology domain, and the IABOtherInformation may further include IP address configuration information in the F1 terminated topology domain of the border node. The non-F1 termination donor returns a handover request response (HANDOVER REQUEST ACKNOWLEDGE) to the F1 termination donor. For example, the handover request response includes an RRC message HandoverCommand, which carries the entire RRC message RRCReconfiguration generated by the non-F1 termination donor, and the RRCReconfiguration is made into a second RRC container and carries the IP address configuration information (iab-IP-AddressConfigurationList-r16 field) of the non-F1 termination topology domain.

[0063] The Handover Preparation Information can be described 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] The IABOtherInformation may further carry the number of IP addresses requested for the various services, or the IP addresses that the various services actually employ.

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

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

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

[0069] Therefore, a new RRC container IABOtherInformation is introduced in the switch request message to request an IP address of the non-F1 terminated topology domain, and an IP address configuration information element included in the RRC container RRCReconfiguration in the switch 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 the IP address request information is carried by the IABOtherInformation included in the first RRC container. In addition, the IP address request information may be further carried by the RRC reconfiguration message included in the first RRC container, but the embodiment of the present invention is not limited thereto.

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

[0072] 1203: The IP address configuration information received by the F1 termination donor is sent to the IAB node, for example, the F1 termination donor forwards a HandoverCommand generated by a non-F1 termination donor, the HandoverCommand carries the entire RRC message RRCReconfiguration generated by the non-F1 termination donor, and the RRCReconfiguration carries the IP address configuration information of the non-F1 termination topology domain.

[0073] As can be seen from the above embodiment, the F1 termination donor can request the non-F1 termination donor to allocate an IP address of the non-F1 termination topology domain, or can further receive the IP address configuration information of the non-F1 termination topology domain allocated for the IAB node by the non-F1 termination donor, thereby making the F1 termination donor request the IP address of the non-F1 termination topology domain, or can further send the IP address of the non-F1 termination topology domain for the IAB node when the non-F1 termination donor cannot send a message to the IAB node. In this way, for the routing ID of the non-F1 termination topology domain, the IAB node can use the IP address of the non-F1 termination topology domain.

[0074] II. Dual Connection Scenario 1 In some embodiments, Figure 13 is a diagram showing dual connection scenario 1, as shown in Figure 13, in dual connection scenario 1, 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, after the dual connection is established, some business of the border node can be transferred to the non-F1 termination topology domain, and some business is still in the F1 termination donor topology domain, and the IP address of the non-F1 termination topology domain refers to the IP address anchored to donor-DU2. The IP address of the non-F1 termination topology domain may be requested during the dual connection establishment process, or the IP address of the non-F1 termination topology domain or the IP address of the F1 termination topology domain may be requested / configured after the dual connection is established, which will be described respectively below.

[0075] FIG. 14 is a diagram showing one method of transmission address configuration under the dual connectivity scenario 1. As shown in FIG. 14, the method includes the following steps:

[0076] 1401: The F1 termination donor sends to the non-F1 termination donor an IP address request information of the non-F1 termination topology domain for the IAB node; and 1402: The F1 termination donor receives IP address configuration information of the non-F1 termination topology domain assigned for the IAB node, sent by a non-F1 termination 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, and the IP address request information is carried by a first RRC container, and the IP address configuration information is carried by a second RRC container, and 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, the F1 terminated donor transmits a secondary node addition request message (S-node AdditionRequest) to the non-F1 terminated donor, and for example, the RRC message CG-ConfigInfo contained therein introduces the entire RRC message IABOtherInformation generated by the F1 terminated donor, and the IABOtherInformation is the first RRC container and carries the IP address request information (IAB-TNLAddressInfo field) of the non-F1 terminated topology domain. The non-F1 termination donor returns a secondary node addition response message (S-node Addition Response) to the F1 termination donor, and the secondary cell group configuration information field scg-CellGroupConfig in the RRC message CG-Config contained therein carries the entire RRC message RRCReconfiguration generated by the non-F1 termination donor. If the SN does not establish an SRB3 (in such a case, the SN cannot directly send an RRC message to the IAB node), the RRCReconfiguration is made into a second RRC container and carries the IP address configuration information (iab-IP-AddressConfigurationList-r16 field) of the non-F1 termination topology domain.

[0078] FIG. 15 is a diagram showing another method for setting a transmission address under the dual connectivity scenario 1. As shown in FIG. 15, the method includes the following steps:

[0079] 1501: The F1 termination donor sends to the non-F1 termination donor an IP address request information of the non-F1 termination topology domain for the IAB node; and 1502: The F1 termination donor receives IP address configuration information of the non-F1 termination topology domain assigned for the IAB node, sent by the non-F1 termination donor.

[0080] In some embodiments, after the dual connection establishment is completed, an IP address of a non-F1 terminated topology domain is requested during the process of changing the secondary cell set, 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 change request message, and the second RRC container is carried by a secondary node change response message. In the process of changing the Secondary Cell Group, the F1 termination donor sends a secondary node modification request message (S-node Modification Request) to the non-F1 termination donor, and for example, the RRC message CG-ConfigInfo contained therein carries the entire RRC message IABOtherInformation generated by the F1 termination donor, and the IABOtherInformation is made into a first RRC container and carries IP address request information (IAB-TNLAddressInfo field) of the non-F1 termination topology domain, and the non-F1 termination donor returns a secondary node modification response message (S-node Modification Response) to the F1 termination donor, and the secondary cell group configuration information (scg-CellGroupConfig field) in the RRC message CG-Config contained therein carries the entire RRC message RRCReconfiguration generated by the non-F1 termination donor. If the SN does not establish an SRB3, the RRCReconfiguration is a second RRC container and carries the IP address configuration information of the non-F1 terminated topology domain (iab-IP-AddressConfigurationList-r16 field).

[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 described 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 description thereof will be omitted here.

[0084] Therefore, a new RRC container IABOtherInformation is introduced in the secondary node addition / modification request message to request an IP address of the non-F1 termination topology domain, and the IP address configuration information element included in the RRC container RRCReonfiguration in the secondary node addition / modification response message can be used to carry the IP address of the non-F1 termination topology domain configured for the border node.

[0085] The above is an example in which the IP address request information is carried by the IABOtherInformation included in the first RRC container. In addition, the IP address request information may be further carried by the RRC reconfiguration message included in the first RRC container, but the embodiment of the present invention is not limited thereto.

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

[0087] 1403 / 1503: The IP address configuration information received by the F1 termination donor is sent to the IAB node, for example, the F1 termination donor forwards an RRC Reconfiguration in CG-Config generated by the non-F1 termination donor, and the RRC Reconfiguration carries the IP address configuration information of the non-F1 termination topology domain.

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

[0089] As can be seen from the above embodiment, the F1 termination donor can request the non-F1 termination donor to allocate an IP address of the non-F1 termination topology domain, or can further receive the IP address configuration information of the non-F1 termination topology domain allocated for the IAB node by the non-F1 termination donor, thereby making the F1 termination donor request the IP address of the non-F1 termination topology domain, or can further send the IP address of the non-F1 termination topology domain for the IAB node when the non-F1 termination donor cannot send a message to the IAB node. In this way, for the routing ID of the non-F1 termination topology domain, the IAB node can use the IP address of the non-F1 termination topology domain.

[0090] FIG. 16 is a diagram showing another method for setting a transmission address under the dual connectivity scenario 1. As shown in FIG. 16, the method includes the following steps:

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

[0092] In some embodiments, the differences from FIG. 15 are as follows: after dual connectivity establishment is completed, if the SN does not establish SRB3, there is no need for the F1 terminated donor to proactively request an IP address for the non-F1 terminated topology domain, and the non-F1 terminated donor can proactively initiate IP address reconfiguration for the non-F1 terminated topology domain, and the IP address configuration information is carried by a second RRC container, and the second RRC container is carried by a secondary node change request message.

[0093] For example, in the process of modifying the secondary cell group, the non-F1 termination donor sends a secondary node modification request message (S-node Modification Required) to the F1 termination donor, and the secondary cell group configuration information (scg-CellGroupConfig field) in the RRC message CG-Config contained therein carries the entire RRC message RRCReconfiguration generated by the non-F1 termination donor, and the RRCReconfiguration is treated as a second RRC container and carries the IP address configuration information of the non-F1 termination topology domain, which is also referred to as 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 termination topology domain to be reconfigured for the boundary node.

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

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

[0097] As can be seen from the above embodiment, the F1 termination donor can receive the IP address configuration information of the non-F1 termination topology domain voluntarily transmitted by the non-F1 termination donor, and can transmit the IP address of the non-F1 termination topology domain for the IAB node when the non-F1 termination donor cannot transmit a message to the IAB node. In this way, for the routing ID of the non-F1 termination topology domain, the IAB node can use the IP address of the non-F1 termination topology domain.

[0098] III. Dual Connection Scenario 2 In some embodiments, Figure 17 is a diagram showing dual connection scenario 2. As shown in Figure 17, in dual connection scenario 2, the F1 termination donor is the secondary node SN CU of the IAB node, and the non-F1 termination donor is the main node MN CU of the IAB node. After the dual connection is established, some business of the border node can be migrated to the non-F1 termination topology domain, and some business is still in the F1 termination donor topology domain, and the IP address of the non-F1 termination topology domain refers to the IP address anchored to donor-DU1, and the IP address of the F1 termination 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 the dual connection scenario 1 is as follows: the IP address of the non-F1 termination topology domain cannot be requested during the dual connection establishment process, and the IP address of the non-F1 termination topology domain or the IP address of the F1 termination topology domain can only be requested / set after the dual connection is established, which will be described below respectively.

[0099] FIG. 18 is a diagram showing one method of transmission address configuration under the dual connectivity scenario 2. As shown in FIG. 18, the method includes the following steps:

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

[0101] In some embodiments, after the dual connection establishment is completed, an IP address of a non-F1 terminated topology domain is requested during the process of changing the secondary cell set, and the IP address request information is carried by a first RRC container, and the first RRC container is carried by a secondary node change request message. The F1 terminated donor sends a secondary node change request message to the non-F1 terminated donor, and for example, an RRC message CG-Config contained therein introduces IP address request information (IAB-TNLAddressInfo field), which carries the entire RRC message IABOtherInformation generated by the F1 terminated donor, and the IABOtherInformation is the first RRC container, carrying the IP address request information of the non-F1 terminated topology domain. The IP address configured by the non-F1 terminated donor can be directly sent by the non-F1 terminated donor to the boundary node through the SRB1. Therefore, the non-F1 terminated donor does not need to return the IP address configuration information to the F1 terminated donor, in other words, the F1 terminated donor does not receive the IP address configuration information sent by the non-F1 terminated donor.

[0102] The CG-Config can be described 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 the secondary node change request message to request an IP address of the non-F1 termination topology domain.

[0104] The above is an example in which the IP address request information is carried by the IABOtherInformation included in the first RRC container. In addition, the IP address request information may be further carried by the RRC reconfiguration message included in the first RRC container, but the embodiment of the present invention is not limited thereto.

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

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

[0107] As can be seen from the above embodiment, the F1 termination donor can request the non-F1 termination donor to allocate an IP address of the non-F1 termination topology domain, so that the F1 termination donor requests the IP address of the non-F1 termination topology domain, and the non-F1 termination donor sends the IP address of the non-F1 termination topology domain to the IAB node. In this way, for the routing ID of the non-F1 termination topology domain, the IAB node can use the IP address of the non-F1 termination topology domain.

[0108] FIG. 19 is a diagram showing another method for setting a transmission address under the dual connectivity scenario 2. As shown in FIG. 19, the method includes the following steps:

[0109] 1901: The F1 termination donor sends IP address configuration information of the F1 termination topology domain allocated for the IAB node to the non-F1 termination donor, and the second RRC container is carried by a secondary node change request message.

[0110] In some embodiments, after dual connectivity establishment is completed, if the SN does not establish SRB3, the F1 termination donor can autonomously initiate IP address reconfiguration for the F1 termination topology domain, and the IP address configuration information is carried by a second RRC container, and the second RRC container is carried by a secondary node change request message.

[0111] For example, in the process of modifying the secondary cell group, the F1 termination donor sends a secondary node modification request message (S-node Modification Required) to the non-F1 termination donor, and for example, the secondary cell configuration information (scg-CellGroupConfig field) in the RRC message CG-Config contained therein carries the entire RRC message RRCReconfiguration generated by the F1 termination donor, and the RRCReconfiguration is treated as a second RRC container and carries the IP address configuration information of the F1 termination topology domain, which is also referred to as IP address reconfiguration information.

[0112] The CG-Config can be described 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 to be reconfigured for the boundary node.

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

[0115] 1902: The non-F1 terminated donor forwards the IP address configuration information of the F1 terminated topology domain received to the IAB node, for example, the non-F1 terminated donor forwards an RRC Reconfiguration in a CG-Config generated by the F1 terminated donor, and the RRC Reconfiguration carries the IP address configuration information of the F1 terminated topology domain.

[0116] As can be seen from the above embodiment, the F1 termination donor can send the IP address configuration information of the F1 termination topology domain to the non-F1 termination donor, so that when the F1 termination donor cannot send a message to the IAB node, the non-F1 termination donor can send the IP address of the F1 termination topology domain to the IAB node. In this way, for the routing ID of the F1 termination topology domain, the IAB node can use the IP address of the F1 termination topology domain.

[0117] IV. RLF Recovery Scenarios In some embodiments, Figure 20 is a diagram showing an RLF recovery scenario. As shown in Figure 20, in the RLF recovery scenario, the F1 terminating donor is the donor (old donor CU) of the IAB node after RLF recovery, and the non-F1 terminating donor is the donor (new donor CU) of the IAB node before RLF recovery. The IP address of the non-F1 terminating topology domain refers to the IP address anchored to donor-DU2. Figure 21 is a diagram showing a transmission address setting method under the switching scenario. As shown in Figure 21, the method includes the following steps:

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

[0119] In some embodiments, an IP address of a non-F1 terminated topology domain is requested during a UE context acquisition process, and the IP address request information is carried by a first RRC container, and the first RRC container is carried by a UE context acquisition response message. Therefore, the non-F1 termination donor sends a UE context acquisition request message (RETRIEVE UE CONTEXT REQUEST) to the F1 termination donor, and the F1 termination donor returns a UE context acquisition response message (RETRIEVE UE CONTEXT RESPONSE) to the non-F1 termination donor. For example, the UE context acquisition response message includes an RRC message Handover Preparation Information, which can carry the entire RRC message IAB Other Information generated by the F1 termination donor, where the IAB Other Information is a first RRC container and carries IP address request information (IAB-TNL Address Info field) of the non-F1 termination topology domain, and the IAB Other Information may further include IP address configuration information in the F1 termination topology domain of the border node. After the boundary node is re-established to the non-F1 termination donor, the IP address configuration information can be sent only by the non-F1 termination donor, so the non-F1 termination donor does not need to send the IP address configuration information back to the F1 termination donor; in other words, the F1 termination donor does not receive the IP address configuration information sent by the non-F1 termination donor.

[0120] Therefore, a new RRC container IABOtherInformation can be introduced in the UE Context Get Response message to request an IP address of a non-F1 terminated topology domain.

[0121] The above is an example in which the IP address request information is carried by the IABOtherInformation included in the first RRC container. In addition, the IP address request information may be further carried by the RRC reconfiguration message included in the first RRC container, but the embodiment of the present invention is not limited thereto.

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

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

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

[0125] (2) IP address request information and / or IP address configuration information is carried by an IAB transport transition management request / response or an IAB transport transition change request. In some embodiments, the IP address request information is carried by an IAB transmission transition management request message, the 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., indicates the IP address request information for the boundary node; the IP address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message, the IP address configuration information includes a boundary node indicator, which is used to indicate that the IAB node is a boundary node, i.e., indicates the IP address configuration information configured for the boundary node.

[0126] Since the IAB transport transition management request / response or the IAB transport transition change request is dedicated to the IAB node and does not relate to AS layer configuration, requesting and configuring IP addresses of non-F1 termination topology domains through the IAB transport transition management request / response or the IAB transport transition change request can make the requesting and configuring of IP addresses simpler and more flexible.

[0127] I. Switching Scenarios In some embodiments, as shown in FIG. 11, in a switching scenario, all operations of the boundary node are migrated to a non-F1 terminating topology domain, the F1 terminating donor is the source donor of the switching of the IAB node, the non-F1 terminating donor is the target donor of the switching of the IAB node, and the IP address of the non-F1 terminating topology domain refers to the IP address anchored to donor-DU2. FIG. 22 is a diagram showing a transmission address configuration method under the switching scenario, and as shown in FIG. 22, the method includes the following steps:

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

[0129] In some embodiments, the IP address request information is carried by an IAB transport migration management request message. Thus, after switching preparation, the F1 terminating donor sends an IAB transport migration management request message to the non-F1 terminating donor, for example, the IAB transport migration management request message can carry the IP address request information IAB TNL ADDRESS REQUEST of the non-F1 terminating topology domain, and the 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, the IP address request information is the IP address request information of the non-F1 terminating 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] Among them, the IAB TNL ADDRESS REQUEST includes an IAB TNL Addresses Requested field, which is request information for an IPv4 or IPv6 address, and a Boundary Node field, which is a boundary node indicator.

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

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

[0134] Since RRC messages can be sent to the border node only by the target donor after switching, the non-F1 terminated donor does not need to send back IP address configuration information of the non-F1 terminated topology domain to the F1 terminated donor.

[0135] Therefore, a new information element, IAB TNL ADDRESS REQUEST, can be introduced in the IAB transport transition management request message to request the IP address of the non-F1 termination topology domain for the border node.

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

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

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

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

[0140] II. Dual Connection Scenario 1 In some embodiments, as shown in FIG. 13, in dual connection scenario 1, the F1 termination donor is the main node MN of the IAB node, and the non-F1 termination donor is the secondary node SN of the IAB node, and after the dual connection is established, some of the operations of the boundary node can be migrated to the non-F1 termination topology domain, and some of the operations are still in the F1 termination donor topology domain, and the IP address of the non-F1 termination topology domain refers to the IP address anchored to donor-DU2.

[0141] FIG. 23 is a diagram showing one method of transmission address configuration under the dual connectivity scenario 1. As shown in FIG. 23, the method includes the following steps:

[0142] 2301: The F1 termination donor sends to the non-F1 termination donor an IP address request information of the non-F1 termination topology domain for the IAB node; and 2302: The F1 termination donor receives IP address configuration information of the non-F1 termination topology domain assigned for the IAB node, sent by the non-F1 termination donor.

[0143] In some embodiments, after the process of adding a secondary cell set, an IP address of a non-F1 termination topology domain is requested, the IP address request information is carried by an IAB transit transition management request message, and the IP address configuration information is carried by an IAB transit transition management response message. For example, the IAB transmission transition management request message introduces IP address request information IAB TNL ADDRESS REQUEST of a non-F1 termination topology domain, the 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., indicates that the IP address request information is IP address request information of a non-F1 termination topology domain for a boundary node; when the SN does not establish an SRB3, the non-F1 termination donor returns an IAB transmission transition management response message to the F1 termination donor, which, for example, carries IP address configuration information of a non-F1 termination topology domain (information element structure IAB TNL Address Response), which may further include a boundary node indicator, which is used to indicate that the IAB node is a boundary node, i.e., indicates that the IP address configuration information is IP address configuration information of a non-F1 termination 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] It includes an IP address configuration IAB Allocated TNL Address List area and a boundary node indicator Boundary Node area of ​​at least one non-F1 termination topology domain to be assigned, and each IP address configuration includes a specific IP address IAB TNL Address and a corresponding donor-DU address Associated Donor DU Address.

[0146] Therefore, a new information element IP address request information IAB TNL ADDRESS REQUEST is introduced in the transmission transition management request message to request an IP address of a non-F1 termination topology domain, and by using the information element IAB TNL Address Response in the IAB transmission transition management response message, the IP address of the non-F1 termination topology domain to be configured for the border node (not a child node) can be indicated.

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

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

[0149] In 2303, optionally, when SN establishes SRB3, the non-F1 termination donor may further send the IP address configuration information to the IAB node, but the embodiment of the present invention is not limited thereto. As can be seen from the above embodiment, the F1 termination donor needs to request an IP address from the non-F1 termination donor, and the non-F1 termination donor configures and returns the IP address of the non-F1 termination topology domain to the F1 termination donor in response to the request, and the F1 termination donor forwards it to the border node, so that the IAB node can use the IP address of the non-F1 termination topology domain for the routing ID of the non-F1 termination topology domain.

[0150] FIG. 24 is a diagram showing another method for setting a transmission address under the dual connectivity scenario 1. As shown in FIG. 24, the method includes the following steps:

[0151] 2401: The F1 termination donor receives IP address configuration information of the non-F1 termination topology domain assigned for the IAB node, sent by the non-F1 termination donor.

[0152] In some embodiments, the differences from FIG. 23 are as follows: when the SN does not establish SRB3, the F1 termination donor does not need to proactively request an IP address for the non-F1 termination topology domain, and the non-F1 termination donor can proactively initiate IP address reconfiguration for the non-F1 termination topology domain, and the IP address configuration information is carried by the IAB TRANSPORT MODIFIATION REQUEST message.

[0153] For example, after the secondary node addition process, when the SN does not establish SRB3, the non-F1 termination donor sends an IAB transmission transition change request message to the F1 termination donor, for example, carrying the IP address configuration information of the non-F1 termination topology domain (information element structure IAB TNL Address Response, the specific data format is as mentioned above, and the detailed description is omitted here), which is also called IP address reconfiguration information, and the IP address configuration information may further include a boundary node indicator, which is used to indicate that the IAB node is a boundary node, that is, to indicate that the IP address configuration information is the IP address reconfiguration information of the non-F1 termination topology domain for the boundary node. Therefore, the information element IAB TNL Address Response in the IAB transmission transition change request message can indicate the IP address of the non-F1 termination topology domain to be reconfigured for the boundary node (not the child node).

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

[0155] 2402: The F1 terminated donor forwards the IP address configuration information received to the IAB node, for example, the F1 terminated donor forwards an RRC Reconfiguration generated by a non-F1 terminated donor, where the RRC Reconfiguration carries the IP address configuration information of the non-F1 terminated topology domain.

[0156] As can be seen from the above embodiment, the F1 termination donor can receive the IP address configuration information of the non-F1 termination topology domain voluntarily transmitted by the non-F1 termination donor, and can transmit the IP address of the non-F1 termination topology domain for the IAB node when the non-F1 termination donor cannot transmit a message to the IAB node. In this way, for the routing ID of the non-F1 termination topology domain, the IAB node can use the IP address of the non-F1 termination topology domain.

[0157] III. Dual Connection Scenario 2 In some embodiments, as shown in Figure 17, in dual connection scenario 2, the F1 termination donor is the secondary node SN CU of the IAB node, and the non-F1 termination donor is the main node MN CU of the IAB node, and after the dual connection is established, some business of the border node is migrated to the non-F1 termination topology domain, and some business is still in the F1 termination donor topology domain, and the IP address of the non-F1 termination topology domain is the IP address anchored to donor-DU1, and the IP address of the F1 termination topology domain is the IP address anchored to donor-DU2. After the dual connection is established, the IP address of the non-F1 termination topology domain or the IP address of the F1 termination topology domain can be requested / configured, which will be described below respectively.

[0158] FIG. 25 is a diagram showing one method of transmission address configuration under the dual connectivity scenario 2. As shown in FIG. 25, the method includes the following steps:

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

[0160] In some embodiments, after the dual connection establishment is completed, an IP address of the non-F1 terminating topology domain is requested, and the IP address request information is carried by an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. The F1 termination donor sends an IAB transmission transition management request message to the non-F1 termination donor, for example, introducing IP address request information of the non-F1 termination topology domain IAB TNL ADDRESS REQUEST (the specific data format is as described above, and detailed description thereof is omitted here), and the 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, indicates that the IP address request information is IP address request information of the non-F1 termination topology domain for a boundary node. Since the IP address configured by the non-F1 termination donor can be directly sent to the boundary node by the non-F1 termination donor through SRB1, the non-F1 termination donor does not need to return the IP address configuration information to the F1 termination donor, in other words, the F1 termination donor does not receive the IP address configuration information sent by the non-F1 termination donor.

[0161] Therefore, a new information element, IAB TNL ADDRESS REQUEST, can be introduced in the IAB transport transition management request message to request an IP address of a non-F1 termination topology domain.

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

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

[0164] As can be seen from the above embodiment, the F1 termination donor can request the non-F1 termination donor to allocate an IP address of the non-F1 termination topology domain, so that the F1 termination donor requests the IP address of the non-F1 termination topology domain, and the non-F1 termination donor sends the IP address of the non-F1 termination topology domain to the IAB node. In this way, for the routing ID of the non-F1 termination topology domain, the IAB node can use the IP address of the non-F1 termination topology domain.

[0165] FIG. 26 is a diagram showing another method for setting a transmission address under the dual connectivity scenario 2. As shown in FIG. 26, the method includes the following steps:

[0166] 2601: The F1 termination donor sends to the non-F1 termination donor IP address configuration information of the F1 termination topology domain allocated for the IAB node.

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

[0168] For example, an F1 termination donor sends an IAB transmission transition management request message to a non-F1 termination donor, for example, carrying IP address configuration information of an F1 termination topology domain (information element structure IAB TNL Address Response), the IP address configuration information further includes a boundary node indicator, the boundary node indicator is used to indicate that the IAB node is a boundary node, that is, the IP address configuration information indicates that the IP address configuration information is the IP address configuration information of a non-F1 termination topology domain for a boundary node, which 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 has been described above, and a detailed description thereof will be omitted here.

[0169] Therefore, a new information element, IAB TNL Address Response, can be introduced in the IAB Transmission Transition Management Request message to indicate the IP address of the F1 termination topology domain to be reconfigured for a border node (not a child node).

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

[0171] 2602: The non-F1 terminated donor forwards the IP address configuration information of the F1 terminated topology domain received to the IAB node, for example, the non-F1 terminated donor generates an RRC Reconfiguration, and the RRC Reconfiguration carries the IP address configuration information of the F1 terminated topology domain.

[0172] As can be seen from the above embodiment, the F1 termination donor can send the IP address configuration information of the F1 termination topology domain to the non-F1 termination donor, so that when the F1 termination donor cannot send a message to the IAB node, the non-F1 termination donor can send the IP address of the F1 termination topology domain to the IAB node. In this way, for the routing ID of the F1 termination topology domain, the IAB node can use the IP address of the F1 termination topology domain.

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

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

[0175] In some embodiments, after sending the UE context acquisition response message, the IP address of the non-F1 terminated topology domain is requested, and the IP address request information is carried by the IAB transmission transition management request message. Thus, the F1 terminated donor sends an IAB transmission transition management request message to the non-F1 terminated donor, for example, introducing the IP address request information of the non-F1 terminated topology domain IAB TNL ADDRESS REQUEST therein, and the 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, to indicate that the IP address request information is the IP address request information of the non-F1 terminated topology domain for the boundary node. After the boundary node is re-established to the non-F1 terminated donor, the non-F1 terminated donor does not need to return the IP address configuration information of the non-F1 terminated topology domain to the F1 terminated donor, since the IP address configuration information can be sent only by the non-F1 terminated donor, in other words, the F1 terminated donor does not receive the IP address configuration information sent by the non-F1 terminated donor.

[0176] Therefore, a new information element, IAB TNL ADDRESS REQUEST, can be introduced in the IAB transport transition management request message to request an IP address of a non-F1 termination topology domain.

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

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

[0179] As can be seen from the above embodiment, the F1 termination donor can request the non-F1 termination donor to allocate an IP address of the non-F1 termination topology domain, so that the F1 termination donor requests the IP address of the non-F1 termination topology domain, and the non-F1 termination donor sends the IP address of the non-F1 termination topology domain to the IAB node. In this way, for the routing ID of the non-F1 termination topology domain, the IAB node can use the IP address of the non-F1 termination topology domain.

[0180] The above signaling process is merely for illustrative purposes of the embodiment of the present invention, and the present invention is not limited thereto. For more specific details of the signaling, refer to the related art. For example, the execution order between operations 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 contents without being limited to the description of the above Figures 12, 14-16, 18-19, and 21.

[0181] The above-mentioned embodiments are provided to exemplify the embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications may be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a combination of the above-mentioned embodiments may be used.

[0182] As can be seen from the above embodiment, the F1 termination donor can request the non-F1 termination donor to allocate an IP address of the non-F1 termination topology domain, or can cause the F1 termination donor to request an IP address of the non-F1 termination topology domain by further receiving IP address configuration information of the non-F1 termination topology domain allocated for the IAB node by the non-F1 termination donor, or can further transmit an IP address of the non-F1 termination topology domain for the IAB node, for example, when the non-F1 termination donor cannot send a message to the IAB node. For example, when the non-F1 termination donor cannot send a message to the IAB node, the F1 termination donor can transmit an IP address of the non-F1 termination topology domain for the IAB node by receiving IP address configuration information of the non-F1 termination topology domain voluntarily transmitted by the non-F1 termination donor. Also, for example, when the F1 termination donor cannot send a message to the IAB node, the F1 termination donor can cause the non-F1 termination donor to send the IP address of the F1 termination topology domain to the IAB node by sending IP address configuration information of the F1 termination topology domain to the non-F1 termination donor. In this way, the IAB node can use the IP address of the non-F1 termination topology domain for the routing ID of the non-F1 termination topology domain, and can use the IP address of the F1 termination topology domain for the routing ID of the F1 termination topology domain.

[0183] <Example of the second aspect> In the embodiment of the present invention, a transmission address setting method is provided, and will be described from the perspective of a non-F1 terminal donor. Note that the description of the same contents as those in the embodiment of the first aspect will be omitted here.

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

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

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

[0187] The non-F1 termination donor sends 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 in the F1 termination topology domain of the IAB node, for example, the IP address request information is carried by another IAB information message (IABOtherInformation) or an RRC reconfiguration message (RRCReconfiguration) included 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 It is.

[0190] In some embodiments, the IP address configuration information is carried by a second RRC container, for example, the IP address configuration information is carried by an RRC Reconfiguration message included 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 It is.

[0192] In some embodiments, the F1 termination donor is a source donor of the IAB node switching, and the non-F1 termination donor is a target donor of the IAB node switching, and the method includes the following steps.

[0193] The non-F1 terminated donor receives IP address request information of the non-F1 terminated topology domain for the IAB node transmitted by the F1 terminated donor, the non-F1 terminated donor transmits IP address configuration information of the non-F1 terminated topology domain assigned for the IAB node to the F1 terminated donor, the first RRC container is carried by a switching request message, and the second RRC container is carried by a switching request response message.

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

[0195] The non-F1 terminated donor receives the F1 terminated donor-sent IP address request information of the non-F1 terminated topology domain for the IAB node, the first RRC container being carried by a secondary node addition request message or a secondary node modification request message, and the non-F1 terminated donor transmits to the F1 terminated donor IP address configuration information of the non-F1 terminated topology domain allocated for the IAB node, the second RRC container being carried by a secondary node addition response message or a secondary node modification response message. Optionally, the non-F1 terminated donor further transmits the IP address configuration information to the IAB node.

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

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

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

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

[0200] In some embodiments, the non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a 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 of the F1 termination donor sent by the F1 termination donor, the IP address configuration information being assigned to the boundary node in the F1 termination topology domain, and the second RRC container is carried by a secondary node change request message. Optionally, the non-F1 termination donor further sends the IP address configuration information to the IAB node.

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

[0203] The non-F1 termination donor receives the IP address request information of the non-F1 termination topology domain for the IAB node transmitted by the F1 termination donor, and the first RRC container is carried by a UE context acquisition response message. Optionally, the non-F1 termination 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, where 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.

[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 termination donor is a source donor of the IAB node switching, and the non-F1 termination donor is a target donor of the IAB node switching, and the method includes the following steps.

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

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

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

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

[0211] The non-F1 termination donor sends IP address configuration information of the non-F1 termination topology domain allocated for the IAB node to the F1 termination donor, and the IP address configuration information is carried by an IAB transmission transition change request message.

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

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

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

[0215] The non-F1 termination donor receives IP address configuration information of the F1 termination donor-sent F1 termination topology domain allocated for the boundary node, and the IP address configuration information is carried by an 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 a donor of the IAB node after RLF recovery and the non-F1-terminated donor is a donor of the IAB node before RLF recovery, and the method includes the steps of:

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

[0218] The above signaling process is for illustrative purposes only, but the present invention is not limited thereto, and more specific details of the signaling process can be found in the related art. 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 content, and the specific signaling process corresponds to the description of Figures 12, 14-16, 18-19, and 21 in the embodiment of the first aspect, and the detailed description thereof will be omitted here.

[0219] As can be seen from the above embodiment, the F1 termination donor can request the non-F1 termination donor to allocate an IP address of the non-F1 termination topology domain, or can cause the F1 termination donor to request an IP address of the non-F1 termination topology domain by further receiving IP address configuration information of the non-F1 termination topology domain allocated for the IAB node by the non-F1 termination donor, or can further transmit an IP address of the non-F1 termination topology domain for the IAB node, for example, when the non-F1 termination donor cannot send a message to the IAB node. For example, when the non-F1 termination donor cannot send a message to the IAB node, the F1 termination donor can transmit an IP address of the non-F1 termination topology domain for the IAB node by receiving IP address configuration information of the non-F1 termination topology domain voluntarily transmitted by the non-F1 termination donor. Also, for example, when the F1 termination donor cannot send a message to the IAB node, the F1 termination donor can cause the non-F1 termination donor to send the IP address of the F1 termination topology domain to the IAB node by sending IP address configuration information of the F1 termination topology domain to the non-F1 termination donor. In this way, the IAB node can use the IP address of the non-F1 termination topology domain for the routing ID of the non-F1 termination topology domain, and can use the IP address of the F1 termination topology domain for the routing ID of the F1 termination topology domain.

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

[0221] 29 is a diagram illustrating an IAB donor device according to an embodiment of the present invention. As shown in FIG. 29, an IAB donor device 2900 includes:

[0222] A first sending unit 2901: sending an IP address request information of a non-F1 termination topology domain for the IAB node to a non-F1 termination donor; and / or Sending IP address configuration information of the F1 termination topology domain assigned for the IAB node to a non-F1 termination donor; and / or A first receiving unit 2902: Receives IP address configuration information of a non-F1 termination topology domain assigned to the IAB node, transmitted by the non-F1 termination donor.

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

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

[0225] In some embodiments, the IP address request information is carried by an IABOtherInformation message or an RRCReconfiguration message included 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 It is.

[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 (RRCReconfiguration) included 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 It is.

[0230] In some embodiments, the F1 terminated donor is a source donor of the IAB node switching, the non-F1 terminated donor is a target donor of the IAB node switching, the first transmitter transmits IP address request information of the non-F1 terminated topology domain for the IAB node to the non-F1 terminated donor, the first receiver receives IP address configuration information of the non-F1 terminated topology domain assigned for the IAB node transmitted by the non-F1 terminated 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. Optionally, the first transmitter further transmits the IP address configuration information to the IAB node.

[0231] In some embodiments, the F1 termination donor is a main node MN of the IAB node, the non-F1 termination donor is a secondary node SN of the IAB node, the first transmitter transmits IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor, the first RRC container being carried by a secondary node addition request message or a secondary node change request message, and the first receiver receives IP address configuration information of a non-F1 termination topology domain assigned for the IAB node, transmitted by the non-F1 termination donor, and the second RRC container being 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 termination donor is a main node MN of the IAB node, the non-F1 termination donor is a secondary node SN of the IAB node, the first receiver receives IP address configuration information of a non-F1 termination topology domain assigned for the IAB node sent by the non-F1 termination 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 a main node MN of the IAB node, the F1 terminated donor is a secondary node SN of the IAB node, the first transmitter sends IP address request information of a non-F1 terminated topology domain for the IAB node to the non-F1 terminated donor, and the first RRC container is carried by a secondary node change request message.

[0234] In some embodiments, the non-F1 termination donor is a main node MN of the IAB node, the F1 termination donor is a secondary node SN of the IAB node, the first transmitter transmits IP address configuration information of an F1 termination topology domain assigned for a 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 a donor of the IAB node after RLF recovery, and the non-F1 terminated donor is a donor of the IAB node before RLF recovery, the first transmitter sends IP address request information of a 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 in an IAB transit transition management request message.

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

[0238] In some embodiments, the IP address configuration information is carried in an IAB Transport Transition Management Response message or an IAB Transport 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 a source donor of the IAB node switching, and the non-F1 termination donor is a target donor of the IAB node switching, and the first transmitter sends IP address request information of 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.

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

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

[0243] In some embodiments, the non-F1 termination donor is a main node MN of the IAB node, the F1 termination donor is a secondary node SN of the IAB node, and the first transmitter sends IP address request information of a 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 termination donor is a main node MN of the IAB node, the F1 termination donor is a secondary node SN of the IAB node, and the first transmitter transmits IP address configuration information of the F1 termination topology domain assigned for the boundary node to the non-F1 termination donor, and the IP address configuration information is carried by an IAB transmission transition management request message.

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

[0246] The above-mentioned embodiments are provided to exemplify the embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a combination of the above-mentioned embodiments may be used.

[0247] It should be noted that, although only the components or modules related to the present invention have been described above, the present invention is not limited thereto. The IAB donor device 2900 in the embodiment of the present invention may include other components or modules, and the specific contents of these components or modules can be referred to in the related art.

[0248] For convenience, Fig. 29 shows only the connection relationships or signal directions between each component or module, but as can be understood by those skilled in the art, various related technologies such as bus connection may be adopted. Furthermore, each of the above-mentioned components or modules may be realized by hardware such as a processor, a memory, a transmitter (device), and a receiver (device), and the implementation of the present invention is not limited thereto.

[0249] As can be seen from the above embodiment, the F1 termination donor can request the non-F1 termination donor to allocate an IP address of the non-F1 termination topology domain, or can cause the F1 termination donor to request an IP address of the non-F1 termination topology domain by further receiving IP address configuration information of the non-F1 termination topology domain allocated for the IAB node by the non-F1 termination donor, or can further transmit an IP address of the non-F1 termination topology domain for the IAB node, for example, when the non-F1 termination donor cannot send a message to the IAB node. For example, when the non-F1 termination donor cannot send a message to the IAB node, the F1 termination donor can transmit an IP address of the non-F1 termination topology domain for the IAB node by receiving IP address configuration information of the non-F1 termination topology domain voluntarily transmitted by the non-F1 termination donor. Also, for example, when the F1 termination donor cannot send a message to the IAB node, the F1 termination donor can cause the non-F1 termination donor to send the IP address of the F1 termination topology domain to the IAB node by sending IP address configuration information of the F1 termination topology domain to the non-F1 termination donor. In this way, the IAB node can use the IP address of the non-F1 termination topology domain for the routing ID of the non-F1 termination topology domain, and can use the IP address of the F1 termination topology domain for the routing ID of the F1 termination topology domain.

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

[0251] 30 is a diagram showing an IAB donor device in an embodiment of the present invention. As shown in FIG. 30, an IAB donor device 3000 includes:

[0252] A second receiving unit 3001: receiving IP address request information of a non-F1 termination topology domain for the IAB node transmitted by an F1 termination donor; and / or Receive IP address configuration information of the F1 termination donor transmission, the F1 termination topology domain assigned for the IAB node; and / or A second transmitting unit 3002: Transmits IP address configuration information of a non-F1 termination topology domain allocated for the IAB node to an F1 termination donor.

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

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

[0255] In some embodiments, the IP address request information is carried by an IABOtherInformation message or an RRCReconfiguration message included 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 It is.

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

[0258] In some embodiments, the IP address configuration 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: Switching request response message; Secondary node addition response message; Secondary Node Change Response message; and Secondary Node Change Request Message It is.

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

[0261] In some embodiments, the F1 termination donor is a main node MN of the IAB node, the non-F1 termination donor is a secondary node SN of the IAB node, the second receiver receives the F1 termination donor transmitted IP address request information of the non-F1 termination topology domain for the IAB node, the first RRC container is carried by a secondary node addition request message or a secondary node change request message, and the second transmitter transmits to the F1 termination donor IP address configuration information of the non-F1 termination topology domain allocated for the IAB node, 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 termination donor is a main node MN of the IAB node, the non-F1 termination donor is a secondary node SN of the IAB node, the second transmitter transmits IP address configuration information of a non-F1 termination topology domain assigned for the IAB node to the F1 termination donor, and the second RRC container is carried by a secondary node change request message.

[0263] In some embodiments, the non-F1 termination donor is a main node MN of the IAB node, the F1 termination donor is a secondary node SN of the IAB node, and the second receiver receives the F1 termination donor transmitted IP address request information of the non-F1 termination topology domain for the IAB node, and the first RRC container is carried by a 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 a main node MN of the IAB node, the F1 termination donor is a secondary node SN of the IAB node, the second receiver receives IP address configuration information of an F1 termination topology domain allocated for a boundary node of the F1 termination donor transmission, and the second RRC container is carried by a 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 a donor of the IAB node after RLF recovery, and the non-F1 terminated donor is a donor of the IAB node before RLF recovery, and the second receiver receives the F1 terminated donor sending IP address request information of the non-F1 terminated topology domain for the IAB node, and the first RRC container is carried by a UE context acquisition response message. Optionally, the second transmitter further sends the IP address configuration information to the IAB node.

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

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

[0268] In some embodiments, the IP address configuration information is carried in an IAB Transport Transition Management Response message or an IAB Transport 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 termination donor is a source donor of the IAB node switching, and the non-F1 termination donor is a target donor of the IAB node switching, and the second receiver receives the F1 termination donor-sent IP address request information of the non-F1 termination topology domain for the IAB node, and the IP address request information is carried by an IAB transmission transition management request message. Optionally, the second transmitter further sends the IP address configuration information to the IAB node.

[0271] In some embodiments, the F1 termination donor is a main node MN of the IAB node, the non-F1 termination donor is a secondary node SN of the IAB node, the second receiver receives IP address request information of the non-F1 termination topology domain for the IAB node from the F1 termination donor, the IP address request information is carried by an IAB transmission transition management request message, and the second transmitter transmits IP address configuration information of the non-F1 termination topology domain assigned for the IAB node to the F1 termination 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 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the second transmitter transmits IP address configuration information of a non-F1 termination topology domain assigned for the IAB node to the F1 termination donor, and the IP address configuration information is carried by an IAB transmission transition change request message.

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

[0274] In some embodiments, the non-F1 termination donor is a main node MN of the IAB node, the F1 termination donor is a secondary node SN of the IAB node, and the second receiver receives IP address configuration information of an F1 termination topology domain assigned for a boundary node from the F1 termination donor, 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 terminating donor is a donor of the IAB node after RLF recovery, and the non-F1 terminating donor is a donor of the IAB node before RLF recovery, and the second receiver receives the F1 terminating donor-sent IP address request information of the non-F1 terminating topology domain for the IAB node, and the IP address request information is carried by an IAB transmission transition management request message. Optionally, the second transmitter further sends the IP address configuration information to the IAB node.

[0276] The above-mentioned embodiments are merely for illustrative purposes, and the present invention is not limited thereto. Appropriate modifications may be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a combination of the above-mentioned embodiments may be used.

[0277] It should be noted that, although only the components or modules related to the present invention have been described above, the present invention is not limited thereto. The IAB donor device 3000 in the embodiment of the present invention may further include other components or modules, and the specific contents of these components or modules can be referred to in the related art.

[0278] For convenience, only the connection relationships or signal directions between each component or module are shown in Fig. 30, but various related technologies such as bus connection may be adopted as understood by those skilled in the art. Furthermore, each of the above-mentioned components or modules may be realized by hardware such as a processor, a memory, a transmitter (device), and a receiver (device), and the implementation of the present invention is not limited thereto.

[0279] As can be seen from the above embodiment, the F1 termination donor can request the non-F1 termination donor to allocate an IP address of the non-F1 termination topology domain, or can cause the F1 termination donor to request an IP address of the non-F1 termination topology domain by further receiving IP address configuration information of the non-F1 termination topology domain allocated for the IAB node by the non-F1 termination donor, or can further transmit an IP address of the non-F1 termination topology domain for the IAB node, for example, when the non-F1 termination donor cannot send a message to the IAB node. For example, when the non-F1 termination donor cannot send a message to the IAB node, the F1 termination donor can transmit an IP address of the non-F1 termination topology domain for the IAB node by receiving IP address configuration information of the non-F1 termination topology domain voluntarily transmitted by the non-F1 termination donor. Also, for example, when the F1 termination donor cannot send a message to the IAB node, the F1 termination donor can cause the non-F1 termination donor to send the IP address of the F1 termination topology domain to the IAB node by sending IP address configuration information of the F1 termination topology domain to the non-F1 termination donor. In this way, the IAB node can use the IP address of the non-F1 termination topology domain for the routing ID of the non-F1 termination topology domain, and can use the IP address of the F1 termination topology domain for the routing ID of the F1 termination topology domain.

[0280] <Example of the fifth aspect> In an embodiment of the present invention, a communication system is provided, which includes an IAB donor device 2900 in an embodiment of the third aspect and / or an IAB donor device 3000 in an embodiment of the fourth aspect, and also includes an IAB node (border node). For the network architecture of the donor device and the IAB node, reference may be made to related art, and detailed description thereof will be omitted here.

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

[0282] 9 is a diagram showing an IAB donor device according to an embodiment of the present invention. As shown in FIG. 9, the IAB device 900 may include a processor (e.g., a central processing unit CPU) 901 and a memory 902, and the memory 902 is connected to the processor 901. The memory 902 can store various data, and can also store a program 905 for information processing, and can execute the program 905 under the control of the central processing unit 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] Also, for example, the processor 901 may be configured to execute a program to implement the transmission address setting method in the embodiment of the second aspect.

[0285] In addition, as shown in Fig. 9, the IAB donor device 900 may further include a transceiver 903, an antenna 904, etc., among which the functions of these components are the same as those of the prior art, and detailed descriptions thereof will be omitted here. It is not necessary for the IAB device 900 to include all the components shown in Fig. 9. In addition, the IAB device 900 may include components not shown in Fig. 9, and the prior art can be referred to for this.

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

[0287] An embodiment of the present invention further provides a storage medium storing a computer readable program, wherein the computer readable program causes a computer to execute the transmission address setting method in the embodiment of the first or second aspect in an IAB donor device.

[0288] The above-mentioned devices and methods may be realized by software or hardware, or may be realized by a combination of hardware and software. The present invention further relates to a computer-readable program, which, when executed by a logic component, causes the logic component to realize the above-mentioned device or component, or causes the logic component to realize each of the above-mentioned methods or steps. The logic component may be, for example, a Field Programmable Gate Array (FPGA), a microprocessor, a processor for use in a computer, etc. The present invention also relates to a storage medium, such as a hard disk, a magnetic disk, an optical hard disk, a DVD, a flash memory, etc., storing the above-mentioned program.

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

[0290] Although the 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 fall within the technical scope of the present invention as long as they do not depart from the spirit of the present invention.

[0291] Furthermore, with respect to the above-mentioned embodiments, the following supplementary notes are disclosed.

[0292] <f1> (Appendix 1) A transport address configuration method, applied to an F1 termination donor device of an IAB node, the method comprising: the F1 termination donor sends to a non-F1 termination donor an IP address request information of a non-F1 termination topology domain for the IAB node; and / or the F1 termination donor receiving IP address configuration information of the non-F1 termination topology domain to be assigned for the IAB node, sent by the non-F1 termination donor; and / or The method includes the F1 termination donor transmitting IP address configuration information of an F1 termination topology domain allocated for the IAB node to a non-F1 termination donor.

[0293] (Appendix 2) 2. The method according to claim 1, comprising: The IP address request information is carried by a first RRC container.

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

[0295] (Appendix 4) The method according to claim 2 or 3, The method, wherein the IP address request information is carried by an other IAB information message (IABOtherInformation) or an RRC reconfiguration message (RRCReconfiguration) included in the first RRC container.

[0296] (Appendix 5) 5. The method according to any one of claims 2 to 4, comprising: 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 method.

[0297] (Appendix 6) 2. The method according to claim 1, comprising: The IP address configuration information is carried by a second RRC container.

[0298] (Appendix 7) 7. The method according to claim 6, comprising: The method, wherein the IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) included in the second RRC container.

[0299] (Appendix 8) 8. The method according to claim 6 or 7, 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 method.

[0300] (Appendix 9) 9. The method according to claim 5 or 8, The F1 terminal donor is a source donor for switching the IAB node, and the non-F1 terminal donor is a target donor for switching the IAB node, and the method further comprises: The F1 termination donor transmits IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor, and the F1 termination donor receives IP address configuration information of a non-F1 termination topology domain to be assigned for the IAB node, the IP address configuration information being transmitted by the non-F1 termination donor; Wherein, the first RRC container is carried by a switch request message, and the second RRC container is carried by a switch request response message.

[0301] (Appendix 9.1) 10. The method of claim 9, further comprising: the F1 termination donor sending the IP address configuration information to the IAB node.

[0302] (Appendix 10) 9. The method according to claim 5 or 8, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the method includes: the F1 termination donor sending to the non-F1 termination donor an IP address request information of a non-F1 termination topology domain for the IAB node; Wherein, the first RRC container is carried by a secondary node addition request message or a secondary node change request message.

[0303] (Appendix 10.1) 11. The method of claim 10, further comprising: The F1 termination donor receives IP address configuration information of a non-F1 termination topology domain assigned for the IAB node, the IP address configuration information being sent by the non-F1 termination donor; Wherein, the second RRC container is carried by a secondary node addition response message or a secondary node modification response message.

[0304] (Appendix 10.2) 10. The method of claim 10 or 10.1, further comprising: the F1 termination donor sending the IP address configuration information to the IAB node.

[0305] (Appendix 11) 9. The method according to claim 5 or 8, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the method includes: The F1 termination donor receives IP address configuration information of a non-F1 termination topology domain assigned for the IAB node, the IP address configuration information being sent by the non-F1 termination donor; Wherein, the second RRC container is carried by a secondary node change request message.

[0306] (Appendix 11.1) 12. The method of claim 11, further comprising: the F1 termination donor sending the IP address configuration information to the IAB node.

[0307] (Appendix 12) 9. The method according to claim 5 or 8, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the method includes: the F1 termination donor sending to the non-F1 termination donor an IP address request information of a non-F1 termination topology domain for the IAB node; Wherein, the first RRC container is carried by a secondary node change request message.

[0308] (Appendix 13) 9. The method according to claim 5 or 8, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the method includes: The F1 termination donor transmits to the non-F1 termination donor IP address configuration information of the F1 termination topology domain assigned for the IAB node; Wherein, the second RRC container is carried by a secondary node change request message.

[0309] (Appendix 14) 9. The method according to claim 5 or 8, the F1 terminated donor is a donor of the IAB node after RLF recovery, and the non-F1 terminated donor is a donor of the IAB node before RLF recovery, and the method further comprises: the F1 termination donor sending to the non-F1 termination donor an IP address request information of a non-F1 termination topology domain for the IAB node; Wherein, the first RRC container is carried by a UE context acquisition response message.

[0310] (Appendix 15) 2. The method according to claim 1, comprising: The IP address request information is carried by an IAB transit transition management request message.

[0311] (Appendix 16) 16. The method of claim 15, The method, wherein the IP address request information includes a boundary node indicator, the boundary node indicator being used to indicate that the IAB node is a boundary node.

[0312] (Appendix 17) 2. The method according to claim 1, comprising: The IP address configuration information is carried by an IAB transport transition management response message or an IAB transport transition change request message.

[0313] (Appendix 18) 18. The method according to claim 17, comprising: The 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] (Appendix 19) 18. The method according to claim 15 or 17, The F1 terminal donor is a source donor for switching the IAB node, and the non-F1 terminal donor is a target donor for switching the IAB node, and the method further comprises: the F1 termination donor sending to the non-F1 termination donor an IP address request information of a non-F1 termination topology domain for the IAB node; Wherein, the IP address request information is carried by an IAB transmission transition management request message.

[0315] (Appendix 20) 18. The method according to claim 15 or 17, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the method includes: the F1 termination donor sending to the non-F1 termination donor an IP address request information of a non-F1 termination topology domain for the IAB node; Wherein, the IP address request information is carried by an IAB transmission transition management request message.

[0316] (Appendix 20.1) 21. The method of claim 20, further comprising: The F1 termination donor receives IP address configuration information of a non-F1 termination topology domain assigned for the IAB node, the IP address configuration information being sent by the non-F1 termination donor; Wherein, the IP address configuration information is carried by an IAB transmission transition management response message.

[0317] (Appendix 20.2) 20. The method of claim 1, further comprising: the F1 termination donor sending the IP address configuration information to the IAB node.

[0318] (Appendix 21) 18. The method according to claim 15 or 17, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the method includes: The F1 termination donor receives IP address configuration information of a non-F1 termination topology domain assigned for the IAB node, the IP address configuration information being sent by the non-F1 termination donor; Wherein, the IP address configuration information is carried by an IAB transmission transition change request message.

[0319] (Appendix 21.1) 22. The method of claim 21, further comprising: the F1 termination donor sending the IP address configuration information to the IAB node.

[0320] (Appendix 22) 18. The method according to claim 15 or 17, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the method includes: the F1 termination donor sending to the non-F1 termination donor an IP address request information of a non-F1 termination topology domain for the IAB node; Wherein, the IP address request information is carried by an IAB transmission transition management request message.

[0321] (Appendix 23) 18. The method according to claim 15 or 17, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the method includes: The F1 termination donor transmits to the non-F1 termination donor IP address configuration information of the F1 termination topology domain assigned for the IAB node; Wherein, the IP address configuration information is carried by an IAB transmission transition management request message.

[0322] (Appendix 24) 18. The method according to claim 15 or 17, the F1 terminated donor is a donor of the IAB node after RLF recovery, and the non-F1 terminated donor is a donor of the IAB node before RLF recovery, and the method further comprises: the F1 termination donor sending to the non-F1 termination donor an IP address request information of a non-F1 termination topology domain for the IAB node; Wherein, the IP address request information is carried by an IAB transmission transition management request message.

[0323] (Appendix 25) An IAB donor device, A memory and a processor are included, The storage device stores a computer program, wherein the processor is configured to execute the computer program to perform the transmission address setting method described in any one of Supplementary Notes 1 to 25.

[0324] <Non-F1> (Appendix 1) A transport address configuration method is applied to a non-F1 terminating donor device of an IAB node, the method comprising: the non-F1 termination donor receiving IP address request information of the non-F1 termination topology domain for the IAB node sent by an F1 termination donor; and / or The non-F1 termination donor transmits to an F1 termination donor IP address configuration information of the non-F1 termination topology domain to be assigned for the IAB node; and / or The method includes the non-F1 termination donor receiving IP address configuration information of an F1 termination topology domain assigned for the IAB node, the IP address configuration information being sent by an F1 termination donor.

[0325] (Appendix 2) 2. The method according to claim 1, comprising: The IP address request information is carried by a first RRC container.

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

[0327] (Appendix 4) The method according to claim 2 or 3, The method, wherein the IP address request information is carried by an IABOtherInformation message or an RRCReconfiguration message included in the first RRC container.

[0328] (Appendix 5) 5. The method according to any one of claims 2 to 4, comprising: 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 method.

[0329] (Appendix 6) 2. The method according to claim 1, comprising: The IP address configuration information is carried by a second RRC container.

[0330] (Appendix 7) 7. The method according to claim 6, comprising: The method, wherein the IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) included in the second RRC container.

[0331] (Appendix 8) 8. The method according to claim 6 or 7, 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 method.

[0332] (Appendix 9) 9. The method according to claim 5 or 8, The F1 terminal donor is a source donor for switching the IAB node, and the non-F1 terminal donor is a target donor for switching the IAB node, and the method further comprises: The non-F1 termination donor receives the F1 termination donor-sent IP address request information of the non-F1 termination topology domain for the IAB node, and the non-F1 termination donor transmits to the F1 termination donor IP address configuration information of the non-F1 termination topology domain to be assigned for the IAB node; Wherein, the first RRC container is carried by a switch request message, and the second RRC container is carried by a switch request response message.

[0333] (Appendix 10) 9. The method according to claim 5 or 8, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the method includes: The non-F1 termination donor receives the F1 termination donor-transmitted IP address request information of the non-F1 termination topology domain for the IAB node; Wherein, the first RRC container is carried by a secondary node addition request message or a secondary node change request message.

[0334] (Appendix 10.1) 11. The method of claim 10, further comprising: the non-F1 termination donor transmitting to the F1 termination donor IP address configuration information of a non-F1 termination topology domain to be assigned for the IAB node; Wherein, the second RRC container is carried by a secondary node addition response message or a secondary node modification response message.

[0335] (Appendix 10.2) 10. The method of claim 10 or 10.1, further comprising: the non-F1 termination donor sending the IP address configuration information to the IAB node.

[0336] (Appendix 11) 9. The method according to claim 5 or 8, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the method includes: the non-F1 termination donor transmitting to the F1 termination donor IP address configuration information of a non-F1 termination topology domain to be assigned for the IAB node; Wherein, the second RRC container is carried by a secondary node change request message.

[0337] (Appendix 12) 9. The method according to claim 5 or 8, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the method includes: The non-F1 termination donor receives the F1 termination donor-transmitted IP address request information of the non-F1 termination topology domain for the IAB node; Wherein, the first RRC container is carried by a secondary node change request message.

[0338] (Appendix 12.1) 13. The method of claim 12, further comprising: the non-F1 termination donor sending the IP address configuration information to the IAB node.

[0339] (Appendix 13) 9. The method according to claim 5 or 8, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the method includes: The non-F1 termination donor receives, from the F1 termination donor transmission, IP address configuration information of an F1 termination topology domain assigned for the IAB node; Wherein, the second RRC container is carried by a secondary node change request message.

[0340] (Appendix 13.1) 14. The method of claim 13, further comprising: the non-F1 termination donor sending the IP address configuration information to the IAB node.

[0341] (Appendix 14) 9. The method according to claim 5 or 8, the F1 terminated donor is a donor of the IAB node after RLF recovery, and the non-F1 terminated donor is a donor of the IAB node before RLF recovery, and the method further comprises: The non-F1 termination donor receives the F1 termination donor-transmitted IP address request information of the non-F1 termination topology domain for the IAB node; Wherein, the first RRC container is carried by a UE context acquisition response message.

[0342] (Appendix 14.1) 15. The method of claim 14, further comprising: the non-F1 termination donor sending the IP address configuration information to the IAB node.

[0343] (Appendix 15) 2. The method according to claim 1, comprising: The IP address request information is carried by an IAB transit transition management request message.

[0344] (Appendix 16) 16. The method of claim 15, The method, wherein the IP address request information includes a boundary node indicator, the boundary node indicator being used to indicate that the IAB node is a boundary node.

[0345] (Appendix 17) 2. The method according to claim 1, comprising: The IP address configuration information is carried by an IAB transport transition management response message or an IAB transport transition change request message.

[0346] (Appendix 18) 18. The method according to claim 17, comprising: The 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] (Appendix 19) 18. The method according to claim 15 or 17, The F1 terminal donor is a source donor for switching the IAB node, and the non-F1 terminal donor is a target donor for switching the IAB node, and the method further comprises: The non-F1 termination donor receives the F1 termination donor-transmitted IP address request information of the non-F1 termination topology domain for the IAB node; Wherein, the IP address request information is carried by an IAB transmission transition management request message.

[0348] (Appendix 19.1) 20. The method of claim 19, further comprising: the non-F1 termination donor sending the IP address configuration information to the IAB node.

[0349] (Appendix 20) 18. The method according to claim 15 or 17, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the method includes: The non-F1 termination donor receives the F1 termination donor-transmitted IP address request information of the non-F1 termination topology domain for the IAB node; Wherein, the IP address request information is carried by an IAB transmission transition management request message.

[0350] (Appendix 20.1) 21. The method of claim 20, further comprising: the non-F1 termination donor transmitting to the F1 termination donor IP address configuration information of a non-F1 termination topology domain to be assigned for the IAB node; Wherein, the IP address configuration information is carried by an IAB transmission transition management response message.

[0351] (Appendix 20.2) 20. The method of claim 20, further comprising: the non-F1 termination donor sending the IP address configuration information to the IAB node.

[0352] (Appendix 21) 18. The method according to claim 15 or 17, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the method includes: the non-F1 termination donor transmitting to the F1 termination donor IP address configuration information of a non-F1 termination topology domain to be assigned for the IAB node; Wherein, the IP address configuration information is carried by an IAB transmission transition change request message.

[0353] (Appendix 22) 18. The method according to claim 15 or 17, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the method includes: The non-F1 termination donor receives the F1 termination donor-transmitted IP address request information of the non-F1 termination topology domain for the IAB node; Wherein, the IP address request information is carried by an IAB transmission transition management request message.

[0354] (Appendix 22.1) 23. The method of claim 22, further comprising: the non-F1 termination donor sending the IP address configuration information to the IAB node.

[0355] (Appendix 23) 18. The method according to claim 15 or 17, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the method includes: The non-F1 termination donor receives, from the F1 termination donor transmission, IP address configuration information of an F1 termination topology domain assigned for the IAB node; Wherein, the IP address configuration information is carried by an IAB transmission transition management request message.

[0356] (Appendix 23.1) 24. The method of claim 23, further comprising: the non-F1 termination donor sending the IP address configuration information to the IAB node.

[0357] (Appendix 24) 18. The method according to claim 15 or 17, the F1 terminated donor is a donor of the IAB node after RLF recovery, and the non-F1 terminated donor is a donor of the IAB node before RLF recovery, and the method further comprises: The non-F1 termination donor receives the F1 termination donor-transmitted IP address request information of the non-F1 termination topology domain for the IAB node; Wherein, the IP address request information is carried by an IAB transmission transition management request message.

[0358] (Appendix 24.1) 25. The method of claim 24, further comprising: the non-F1 termination donor sending the IP address configuration information to the IAB node.

[0359] (Appendix 25) An IAB donor device, A memory and a processor are included, The storage device stores a computer program, Wherein, the processor is configured to execute the computer program to implement the transmission address setting method described in any one of Supplementary Notes 1 to 25.

[0360] <f1> (Appendix 1) An IAB donor device, the IAB donor device is an F1 termination donor device of an IAB node; The device includes a first transmitting unit and / or a first receiving unit; The first transmission unit is Sending to a non-F1 termination donor a request for an IP address of the non-F1 termination topology domain for the IAB node; and / or Sending IP address configuration information of the F1 termination topology domain assigned for the IAB node to a non-F1 termination donor; The first receiving unit receives IP address configuration information of a non-F1 termination topology domain assigned to the IAB node, transmitted by the non-F1 termination donor.

[0361] (Appendix 2) 2. The device of claim 1, The IP address request information is carried by a first RRC container, the device.

[0362] (Appendix 3) 1. The device according to claim 2, The first RRC container further includes IP address configuration information in the F1 termination topology domain of the IAB node.

[0363] (Appendix 4) 5. The device according to claim 2 or 3, The IP address request information is carried by another IAB information message (IABOtherInformation) or an RRC reconfiguration message (RRCReconfiguration) included in the first RRC container, the device.

[0364] (Appendix 5) 5. The device according to claim 2, further comprising: 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 equipment.

[0365] (Appendix 6) 2. The device of claim 1, The IP address configuration information is carried by a second RRC container, the device.

[0366] (Appendix 7) 7. The device according to claim 6, The IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) included in the second RRC container, the device.

[0367] (Appendix 8) 8. The device according to claim 6 or 7, 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 equipment.

[0368] (Appendix 9) 11. The device according to claim 5 or 8, The F1 termination donor is a source donor of the IAB node switching, and the non-F1 termination donor is a target donor of the IAB node switching, the first sending unit sends IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor, and the first receiving unit receives IP address configuration information of a non-F1 termination topology domain to be assigned for the IAB node sent by the non-F1 termination donor; Wherein, the first RRC container is carried by a switch request message, and the second RRC container is carried by a switch request response message.

[0369] (Appendix 10) 11. The device according to claim 5 or 8, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the first sending unit sends IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor; Wherein, the first RRC container is carried by a secondary node addition request message or a secondary node change request message.

[0370] (Appendix 10.1) 11. The apparatus of claim 10, The first receiving unit further receives IP address configuration information of a non-F1 termination topology domain assigned to the IAB node, the IP address configuration information being sent by the non-F1 termination donor; Wherein, the second RRC container is carried by a secondary node addition response message or a secondary node modification response message.

[0371] (Appendix 11) 11. The device according to claim 5 or 8, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the first receiving unit receives IP address configuration information of a non-F1 termination topology domain assigned to the IAB node, transmitted by the non-F1 termination donor; Wherein, the second RRC container is carried by a secondary node change request message,

[0372] (Appendix 12) 11. The device according to claim 5 or 8, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the first sending unit sends IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor; Wherein, the first RRC container is carried by a secondary node change request message,

[0373] (Appendix 13) 11. The device according to claim 5 or 8, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the first transmission unit transmits IP address configuration information of an F1 termination topology domain assigned to the IAB node to the non-F1 termination donor; Wherein, the second RRC container is carried by a secondary node change request message,

[0374] (Appendix 14) 11. The device according to claim 5 or 8, The F1 terminating donor is a donor of the IAB node after RLF recovery, and the non-F1 terminating donor is a donor of the IAB node before RLF recovery, and the first sending unit sends IP address request information of a non-F1 terminating topology domain for the IAB node to the non-F1 terminating donor; Wherein, the first RRC container is carried by a UE context acquisition response message.

[0375] (Appendix 15) 2. The device of claim 1, The IP address request information is carried by an IAB transmission transition management request message, the device.

[0376] (Appendix 16) 16. The device of claim 15, The IP address request information includes a boundary node indicator, the boundary node indicator being used to indicate that the IAB node is a boundary node.

[0377] (Appendix 17) 2. The device of claim 1, The IP address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message.

[0378] (Appendix 18) 17. The device of claim 15, further comprising: The device, wherein the IP address configuration information includes a boundary node indicator, the boundary node indicator being used to indicate that the IAB node is a boundary node.

[0379] (Appendix 19) 18. The device according to claim 15 or 17, The F1 termination donor is a source donor of the switching of the IAB node, and the non-F1 termination donor is a target donor of the switching of the IAB node, and the first sending unit sends IP address request information of the non-F1 termination topology domain for the IAB node to the non-F1 termination donor; Wherein, the IP address request information is carried by an IAB transmission transition management request message;

[0380] (Appendix 20) 18. The device according to claim 15 or 17, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the first sending unit sends IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor; Wherein, the IP address request information is carried by an IAB transmission transition management request message;

[0381] (Appendix 20.1) 21. The apparatus of claim 20, The first receiving unit further receives IP address configuration information of a non-F1 termination topology domain assigned to the IAB node, the IP address configuration information being sent by the non-F1 termination donor; Wherein, the IP address configuration information is carried by an IAB transmission transition management response message;

[0382] (Appendix 21) 18. The device according to claim 15 or 17, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the first receiving unit receives IP address configuration information of a non-F1 termination topology domain assigned to the IAB node, transmitted by the non-F1 termination donor; Wherein, the IP address configuration information is carried by an IAB transmission transition change request message;

[0383] (Appendix 22) 18. The device according to claim 15 or 17, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the first sending unit sends IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor; Wherein, the IP address request information is carried by an IAB transmission transition management request message;

[0384] (Appendix 23) 18. The device according to claim 15 or 17, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the first transmission unit transmits IP address configuration information of an F1 termination topology domain assigned to the IAB node to the non-F1 termination donor; Wherein, the IP address configuration information is carried by an IAB transmission transition management request message;

[0385] (Appendix 24) 18. The device according to claim 15 or 17, The F1 terminating donor is a donor of the IAB node after RLF recovery, and the non-F1 terminating donor is a donor of the IAB node before RLF recovery, and the first sending unit sends IP address request information of a non-F1 terminating topology domain for the IAB node to the non-F1 terminating donor; Wherein, the IP address request information is carried by an IAB transmission transition management request message;

[0386] (Appendix 25) 22. The device of claim 9, 10, 10.1, 11, 20, 20.1, or 21, wherein the first transmitter is further configured to transmit the IP address configuration information to the IAB node.

[0387] <Non-F1> (Appendix 1) An IAB donor device, the IAB donor device is a non-F1 termination donor device of an IAB node; the device includes a second receiving unit and / or a second transmitting unit; The second receiving unit is receiving IP address request information of a non-F1 termination topology domain for said IAB node sent by an F1 termination donor; and / or Receive IP address configuration information of an F1 termination topology domain assigned for the IAB node sent by an F1 termination donor; The second transmission unit transmits IP address configuration information of a non-F1 termination topology domain assigned to the IAB node to an F1 termination donor.

[0388] (Appendix 2) 2. The device of claim 1, The IP address request information is carried by a first RRC container, the device.

[0389] (Appendix 3) 1. The device according to claim 2, The first RRC container further includes IP address configuration information in the F1 termination topology domain of the IAB node.

[0390] (Appendix 4) 5. The device according to claim 2 or 3, The IP address request information is carried by another IAB information message (IABOtherInformation) or an RRC reconfiguration message (RRCReconfiguration) included in the first RRC container, the device.

[0391] (Appendix 5) 5. The device according to claim 2, further comprising: 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 equipment.

[0392] (Appendix 6) 2. The device of claim 1, The IP address configuration information is carried by a second RRC container, the device.

[0393] (Appendix 7) 7. The device according to claim 6, The IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) included in the second RRC container, the device.

[0394] (Appendix 8) 8. The device according to claim 6 or 7, 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 equipment.

[0395] (Appendix 9) 11. The device according to claim 5 or 8, The F1 termination donor is a source donor of the IAB node switching, and the non-F1 termination donor is a target donor of the IAB node switching, the second receiving unit receives IP address request information of the non-F1 termination topology domain for the IAB node transmitted by the F1 termination donor, and the second transmitting unit transmits IP address configuration information of the non-F1 termination topology domain to be assigned for the IAB node to the F1 termination donor; Wherein, the first RRC container is carried by a switch request message, and the second RRC container is carried by a switch request response message.

[0396] (Appendix 10) 11. The device according to claim 5 or 8, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the second receiving unit receives IP address request information of a non-F1 termination topology domain for the IAB node transmitted by the F1 termination donor; Wherein, the first RRC container is carried by a secondary node addition request message or a secondary node change request message.

[0397] (Appendix 10.1) 11. The apparatus of claim 10, The second transmission unit further transmits IP address configuration information of a non-F1 termination topology domain assigned to the IAB node to the F1 termination donor; Wherein, the second RRC container is carried by a secondary node addition response message or a secondary node modification response message.

[0398] (Appendix 11) 11. The device according to claim 5 or 8, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the second transmission unit transmits IP address configuration information of a non-F1 termination topology domain assigned to the IAB node to the F1 termination donor; Wherein, the second RRC container is carried by a secondary node change request message,

[0399] (Appendix 12) 11. The device according to claim 5 or 8, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the second receiving unit receives IP address request information of a non-F1 termination topology domain for the IAB node transmitted by the F1 termination donor; Wherein, the first RRC container is carried by a secondary node change request message,

[0400] (Appendix 13) 11. The device according to claim 5 or 8, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the second receiving unit receives IP address configuration information of an F1 termination topology domain assigned to the IAB node, transmitted by the F1 termination donor; Wherein, the second RRC container is carried by a secondary node change request message,

[0401] (Appendix 14) 11. The device according to claim 5 or 8, The F1 terminating donor is a donor of the IAB node after RLF recovery, and the non-F1 terminating donor is a donor of the IAB node before RLF recovery, and the second receiving unit receives IP address request information of a non-F1 terminating topology domain for the IAB node transmitted by the F1 terminating donor; Wherein, the first RRC container is carried by a UE context acquisition response message.

[0402] (Appendix 15) 2. The device of claim 1, The IP address request information is carried by an IAB transmission transition management request message, the device.

[0403] (Appendix 16) 16. The device of claim 15, The IP address request information includes a boundary node indicator, the boundary node indicator being used to indicate that the IAB node is a boundary node.

[0404] (Appendix 17) 2. The device of claim 1, The IP address configuration information is carried by an IAB transmission transition management response message or an IAB transmission transition change request message.

[0405] (Appendix 18) 18. The device of claim 17, The device, wherein the IP address configuration information includes a boundary node indicator, the boundary node indicator being used to indicate that the IAB node is a boundary node.

[0406] (Appendix 19) 18. The device according to claim 15 or 17, The F1 termination donor is a source donor of the IAB node switching, and the non-F1 termination donor is a target donor of the IAB node switching, and the second receiving unit receives the F1 termination donor transmitted IP address request information of the non-F1 termination topology domain for the IAB node; Wherein, the IP address request information is carried by an IAB transmission transition management request message;

[0407] (Appendix 20) 18. The device according to claim 15 or 17, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the second receiving unit receives IP address request information of a non-F1 termination topology domain for the IAB node transmitted by the F1 termination donor; Wherein, the IP address request information is carried by an IAB transmission transition management request message;

[0408] (Appendix 20.1) 21. The apparatus of claim 20, The second transmission unit further transmits IP address configuration information of a non-F1 termination topology domain assigned to the IAB node to the F1 termination donor; Wherein, the IP address configuration information is carried by an IAB transmission transition management response message;

[0409] (Appendix 21) 18. The device according to claim 15 or 17, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node, and the second transmission unit transmits IP address configuration information of a non-F1 termination topology domain assigned to the IAB node to the F1 termination donor; Wherein, the IP address configuration information is carried by an IAB transmission transition change request message;

[0410] (Appendix 22) 18. The device according to claim 15 or 17, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the second receiving unit receives IP address request information of a non-F1 termination topology domain for the IAB node transmitted by the F1 termination donor; Wherein, the IP address request information is carried by an IAB transmission transition management request message;

[0411] (Appendix 23) 18. The device according to claim 15 or 17, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node, and the second receiving unit receives IP address configuration information of an F1 termination topology domain assigned to the IAB node, transmitted by the F1 termination donor; Wherein, the IP address configuration information is carried by an IAB transmission transition management request message;

[0412] (Appendix 24) 18. The device according to claim 15 or 17, The F1 terminating donor is a donor of the IAB node after RLF recovery, and the non-F1 terminating donor is a donor of the IAB node before RLF recovery, and the second receiving unit receives IP address request information of a non-F1 terminating topology domain for the IAB node transmitted by the F1 terminating donor; Wherein, the IP address request information is carried by an IAB transmission transition management request message;

[0413] (Appendix 25) A device as described in Annex 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 transmission unit further transmits the IP address setting information to the IAB node.

Claims

1. 1. An integrated access and backhaul IAB donor device, comprising: the IAB donor device is an F1 termination donor device of an IAB node; The device includes a first transmitting unit and / or a first receiving unit; The first transmission unit is Sending a request for an IP address of the non-F1 termination topology domain for the IAB node to a non-F1 termination donor; and / or Sending IP address configuration information of the F1 termination topology domain assigned for the IAB node to a non-F1 termination donor; The first receiving unit receives IP address configuration information of a non-F1 termination topology domain assigned for the IAB node, transmitted by the non-F1 termination donor.

2. 2. The device of claim 1, The IP address request information is carried by a first RRC container.

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

4. 4. The device according to claim 2 or 3, The IP address request information is carried by another IAB information message (IABOotherInformation) or an RRC reconfiguration message (RRCReconfiguration) included in the first RRC container.

5. 2. The device of claim 1, The IP address configuration information is carried by a second RRC container.

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

7. 7. The device according to claim 3 or 6, 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 and The second RRC container is carried by at least one of the following messages: Switch request response message; Secondary node addition response message; Secondary Node Change Response message; and Secondary Node Change Request Message That is, the equipment.

8. 8. The device of claim 7, the F1 terminal donor is a source donor for switching the IAB node, and the non-F1 terminal donor is a target donor for switching the IAB node; The first transmitting unit transmits IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor, and the first receiving unit receives IP address configuration information of a non-F1 termination topology domain to be assigned for the IAB node, transmitted by the non-F1 termination 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.

9. 8. The device of claim 7, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node; The first sending unit sends an IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor; The first RRC container is carried by a Secondary Node Addition Request message or a Secondary Node Change Request message; or The first receiving unit receives IP address configuration information of a non-F1 termination topology domain assigned to the IAB node, the IP address configuration information being sent by the non-F1 termination donor; The second RRC container is carried by a secondary node addition response message or a secondary node modification response message; or The first receiving unit receives IP address configuration information of a non-F1 termination topology domain assigned to the IAB node, the IP address configuration information being sent by the non-F1 termination donor; The second RRC container is carried by a secondary node change request message, the device.

10. 8. The device of claim 7, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node; The first sending unit sends an IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor; The first RRC container is carried by a secondary node change request message; or The first transmission unit transmits IP address configuration information of an F1 termination topology domain assigned for the IAB node to the non-F1 termination donor; The second RRC container is carried by a secondary node change request message, the device.

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

12. 2. The device of claim 1, The IP address request information is carried by an IAB transport transition management request message, and the IP address configuration information is carried by an IAB transport transition management response message or an IAB transport transition change request message.

13. 13. The apparatus of claim 12, The IP address request information includes a border node indicator, the border node indicator being used to indicate that the IAB node is a border node; or The IP address configuration information includes a boundary node indicator, the boundary node indicator being used to indicate that the IAB node is a boundary node.

14. 13. The apparatus of claim 12, the F1 terminal donor is a source donor for switching the IAB node, and the non-F1 terminal donor is a target donor for switching the IAB node; The first sending unit sends an IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor; The IP address request information is carried in an IAB Transition Management Request message.

15. 13. The apparatus of claim 12, The F1 termination donor is a main node MN of the IAB node, and the non-F1 termination donor is a secondary node SN of the IAB node; The first sending unit sends an IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor; the IP address request information is carried in an IAB Transit Transition Management Request message; or The first receiving unit receives IP address configuration information of a non-F1 termination topology domain assigned to the IAB node, the IP address configuration information being sent by the non-F1 termination donor; The IP address configuration information is carried in an IAB Transition Management Response message; or The first receiving unit receives IP address configuration information of a non-F1 termination topology domain assigned to the IAB node, the IP address configuration information being sent by the non-F1 termination donor; The IP address configuration information is carried by an IAB transport transition change request message.

16. 13. The apparatus of claim 12, The non-F1 termination donor is a main node MN of the IAB node, and the F1 termination donor is a secondary node SN of the IAB node; The first sending unit sends an IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor; the IP address request information is carried in an IAB Transit Transition Management Request message; or The first transmission unit transmits IP address configuration information of an F1 termination topology domain assigned for the IAB node to the non-F1 termination donor; The IP address configuration information is carried by an IAB transit transition management request message.

17. 13. The apparatus of claim 12, the F1-terminated donor is a donor of the IAB node after RLF recovery, and the non-F1-terminated donor is a donor of the IAB node before RLF recovery; The first sending unit sends an IP address request information of a non-F1 termination topology domain for the IAB node to the non-F1 termination donor; The IP address request information is carried in an IAB Transition Management Request message.

18. 2. The device of claim 1, The first transmission unit further transmits the IP address setting information to the IAB node.

19. 1. An integrated access and backhaul IAB donor device, comprising: the IAB donor device is a non-F1 termination donor device of an IAB node; the device includes a second receiving unit and / or a second transmitting unit; The second receiving unit is receiving IP address request information of a non-F1 termination topology domain for said IAB node sent by an F1 termination donor; and / or Receive IP address configuration information of an F1 termination topology domain assigned for the IAB node, sent by an F1 termination donor; The second transmission unit transmits, to an F1 termination donor, IP address configuration information of a non-F1 termination topology domain assigned to the IAB node.

20. 1. A communication system comprising: A communication system comprising a device according to claim 1 and / or a device according to claim 19.

Images