IAB node device, IAB donor device and transmission address determination method

Abstract

In an embodiment of the present invention, an IAB node device, an IAB donor device and a transmission address determination method are provided, the IAB node device includes a first receiver, which receives a first RRC reconfiguration message, the first RRC reconfiguration message includes at least one IP address configuration for the IAB node, the at least one IP address configuration includes IP address information of an F1 terminated topology domain or includes IP address information of a non-F1 terminated topology domain.

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 (termination point) topology domain to a non-F1-terminating topology domain, the routing IDs of all or part of the services of the IAB node belong to a non-F1-terminating topology domain, that is, the IAB node needs to simultaneously transmit the services whose routing IDs belong to the F1-terminating topology domain and the services whose routing IDs belong to the non-F1-terminating topology domain. However, there is currently no corresponding scheme for how to allow the IAB node to transmit the services whose transmission routing IDs belong to the F1-terminating topology domain and the services whose routing IDs belong to the non-F1-terminating topology domain, respectively.

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

[0013] According to one aspect of an embodiment of the present invention, there is provided an integrated access and backhaul IAB node equipment, The device includes a first receiver that receives a first RRC reconfiguration message; the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain.

[0014] According to another aspect of an embodiment of the present invention, there is provided an integrated access and backhaul IAB donor device adapted for use with a first IAB donor; The device includes a first transmitter, which transmits a first RRC reconfiguration message, the first RRC reconfiguration message including at least one IP address configuration for an IAB node; or transmits an IP address configuration for at least one IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain; Wherein, the F1 connection of the IAB node is terminated with the first IAB donor, and the IAB node has an RRC connection with a second IAB donor.

[0015] According to another aspect of an embodiment of the present invention, there is provided an integrated access and backhaul IAB donor device adapted for use with a second IAB donor; The device includes a second transmitter, which transmits a first RRC reconfiguration message, the first RRC reconfiguration message including at least one IP address configuration for an IAB node; or transmits at least one IP address configuration for an IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain; Wherein, an F1 connection of the IAB node is terminated with a first IAB donor, and the IAB node has an RRC connection with the second IAB donor. Effect of the Invention

[0016] The advantageous effects of the embodiment of the present invention are at least as follows: the first RRC reconfiguration message can configure the IAB node with an IP address of a non-F1 terminated topology domain or an IP address of an F1 terminated topology domain; thus, for the routing ID of the non-F1 terminated topology domain, the IAB node can use the IP address of the non-F1 terminated topology domain, and for the routing ID of the F1 terminated topology domain, the IAB node can use the IP address of the F1 terminated topology domain.

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

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

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

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

[0021] 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. 2 illustrates an IAB device according to an embodiment of the present invention. [Figure 10] FIG. 2 is a diagram illustrating a method for determining a transmission address in an embodiment of the present invention. [Figure 11] FIG. 1 illustrates a switching scenario. [Figure 12] FIG. 1 illustrates a dual connection scenario 1. [Figure 13] FIG. 13 illustrates a dual connection scenario 2. [Figure 14] FIG. 2 is a diagram illustrating a method for determining a transmission address in an embodiment of the present invention. [Figure 15] FIG. 2 is a diagram illustrating a method for determining a transmission address in an embodiment of the present invention. [Figure 16] FIG. 2 illustrates an IAB node device in an embodiment of the present invention. [Figure 17] FIG. 1 illustrates an IAB donor device in accordance with an embodiment of the present invention. [Figure 18] FIG. 1 illustrates an IAB donor device in accordance with an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

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

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

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

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

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

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

[0030] Additionally, the term "network side" or "network equipment side" refers to the side of a network, or may be a base station, and 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, or may be a UE, and may include one or more terminal equipment as described above.

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

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

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

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

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

[0036] 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. In this way, after the next-hop node address is determined, the IAB-donor DU 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.

[0037] 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 uplink service transmission.

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

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

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

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

[0042] After the IAB-node switches / RLF recovers from donor-CU 1 (F1-terminating CU) to donor-CU 2 (non-F1-terminating CU), or after the RRC connection with donor-CU 2 increases, only the IAB-MT RRC is connected to donor-CU 2 and the F1 interface is still terminated on donor-CU 1, at which 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 F1-terminating topology domain.

[0043] The routing IDs of all or some of the services of a boundary node belong to a non-F1-terminating topological domain, that is, a boundary node needs to simultaneously transmit services whose routing IDs belong to an F1-terminating topological domain and services whose routing IDs belong to a non-F1-terminating topological domain. However, there is currently no corresponding scheme for how to allow a boundary node to transmit services whose routing IDs belong to an F1-terminating topological domain and services whose routing IDs belong to a non-F1-terminating topological domain, respectively.

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

[0045] <Example of the first aspect> In the embodiment of the present invention, a transmission address determination method is provided, and is described from the perspective of an IAB node device.

[0046] 10 is a diagram showing a method for determining a transmission address in an embodiment of the present invention. As shown in FIG. 10, the method includes the following steps:

[0047] 1001: The IAB node receives a first RRC reconfiguration message, the first RRC reconfiguration message including at least one IP address configuration for the IAB node, the at least one IP address configuration including IP address information of an F1 terminated topology domain or including IP address information of a non-F1 terminated topology domain.

[0048] Note 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 (step) can be appropriately adjusted, or some other operations can be increased or decreased. 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.

[0049] For the routing ID of the non-F1-terminating topology domain, the boundary node needs to use an IP address of the non-F1-terminating topology domain, i.e., an IP address anchored to the donor-DU of the non-F1-terminating topology domain, and for the routing ID of the F1-terminating topology domain, the boundary node needs to use an IP address of the F1-terminating topology domain, i.e., an IP address anchored to the donor-DU of the F1-terminating topology domain. As can be seen from the above embodiment, the first RRC reconfiguration message can configure the IAB node with an IP address of the non-F1-terminating topology domain or an IP address of the F1-terminating topology domain, so that the boundary node can respectively transmit the service whose routing ID belongs to the F1-terminating topology domain and the service whose routing ID belongs to the non-F1-terminating topology domain.

[0050] In some embodiments, the IAB node includes a transition node or its child node, for example, when the IAB node is a transition node (also referred to as a border node), the F1 connection of the IAB node is terminated at a first IAB donor (e.g., a first IAB donor-CU), and there is an RRC connection between the IAB node and the second IAB donor (e.g., a second IAB donor-CU). For example, the IAB-MT of the IAB node maintains an RRC connection with the second IAB donor, hereinafter, the first IAB donor is also referred to as an F1 terminating donor (e.g., an F1 terminating donor-CU), and the second IAB donor is also referred to as a non-F1 terminating donor (e.g., a non-F1 terminating donor-CU), where the F1 terminating donor refers to an IAB donor that terminates the F1 interface of the border IAB node and its child IAB node, i.e., the first IAB donor. A non-F1 terminating donor refers to a donor with donor functionality that does not terminate the F1 interface of a border IAB node and its child IAB nodes, such as a secondary IAB donor.

[0051] In some embodiments, the IP address refers to an IP address configured for an IAB node and anchored to a donor-DU, and the at least one IP address configuration in the first RRC reconfiguration message may be IP address configurations of at least two donor-DUs, or may be at least one IP address configuration of one donor-DU, and each IP address configuration may include an IP address index and a corresponding IP address, but the embodiments of the present invention are not limited thereto.

[0052] 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 a "TNL address(es) that is (are) routable via the IAB-donor-DU", and these terms may be used interchangeably, and the present invention is not limited thereto. For example, an IP address of a donor-DU of a non-F1 terminating topology domain configured for the IAB node refers to a TNL address that is routable via a donor-DU of a non-F1 terminating topology domain configured for the IAB node.

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

[0054] 1002: The IAB node determines that the IP address configuration includes IP address information of an F1 termination topology domain or IP address information of a non-F1 termination topology domain.

[0055] In some embodiments, the IAB node may implicitly indicate whether the configured IP address belongs to a non-F1 terminated topology domain, and in 1002, the IAB node may determine that the IP address configuration includes IP address information of the F1 terminated topology domain or IP address information of the non-F1 terminated topology domain based on the donor providing the IP address information. For example, when the donor providing the IP address information is an F1 terminated donor, the IAB node determines that the IP address configuration includes IP address information of the F1 terminated topology domain, and when the donor providing the IP address information is a non-F1 terminated donor, the IAB node determines that the IP address configuration includes IP address information of the non-F1 terminated topology domain.

[0056] In some embodiments, the IP address to be configured may be explicitly indicated to belong to a non-F1 termination topology domain (for example, explicitly indicated based on the first indication information), and in 1002, the IAB node can determine that the IP address configuration includes IP address information of the F1 termination topology domain or IP address information of the non-F1 termination topology domain based on the first indication information. For example, if the first indication information is used to indicate that the IP address configuration includes IP address information of the non-F1 termination topology domain, the IAB node determines that the IP address configuration includes IP address information of the non-F1 termination topology domain when receiving the first indication information, and determines that the IP address configuration includes IP address information of the F1 termination topology domain when not receiving the first indication information, but the embodiments of the present invention are not limited thereto. In addition, the conveying manner and specific examples of the first indication information will be described later. As can be seen from the above embodiments, the IAB node can distinguish whether the IP address to be configured belongs to a non-F1 termination topology domain or an F1 termination topology domain by implicit or explicit indication.

[0057] Implicit and explicit instructions are each explained below along with different scenarios.

[0058] (1) Switching scenario In some embodiments, FIG. 11 is a diagram illustrating a handover scenario, in which all the operations of the border node are transferred to a non-F1 terminating topology domain, the F1 terminating donor is the source donor of the IAB node's handover, and the non-F1 terminating donor is the target donor of the IAB node's handover. The IP address of the non-F1 terminating topology domain may be configured during the handover process, or the IP address of the non-F1 terminating topology domain may be configured after the handover is completed. During the handover process, the first RRC reconfiguration message is a handover command RRC message generated by the second IAB donor and forwarded by the first IAB donor. In the case after the switching process, the first RRC reconfiguration message is an RRC message sent directly by the second IAB donor to the IAB node, and the first RRC reconfiguration message includes at least one IP address configuration for the IAB node, the at least one IP address configuration includes IP address information of a non-F1 terminated topology domain, and the IP address of the non-F1 terminated topology domain refers to an IP address anchored to donor-DU2. The at least one IP address configuration may be carried by a switching command RRC message, for example, may be carried in the RRC reconfiguration information of a reconfigurationWithSync information field in the master cell group information therein. The IAB node can determine that the at least one IP address configuration configured by the switching command RRC message includes IP address information of a non-F1 terminated topology domain, or the IAB node can determine that the at least one IP address configuration in the RRC message sent by the target donor includes IP address information of a non-F1 terminated topology domain.

[0059] (i) Implicit indication For example, during the switching process, a switching command RRC message is generated by the target donor (i.e., the donor that provides the IP address information is the target donor), and since the target donor is a non-F1 termination, after receiving the switching command RRC message, the IAB node can determine that at least one IP address setting carried by the switching command RRC message is IP address information of a non-F1 termination topology domain.

[0060] For example, after the switching is completed, the target donor can directly send an RRC message to the IAB node, so that after receiving the RRC message, the IAB node can determine that at least one IP address configuration carried by the RRC message is IP address information of a non-F1 termination topology domain.

[0061] (ii) Explicit indication For example, during the switching process, when the target donor generates a switching command RRC message, it may introduce a new information element therein, i.e., first indication information non-F1-terminating, so that after receiving the switching command RRC message, i.e., when the switching command RRC message includes the first indication information, the IAB node can determine that at least one IP address configuration carried by the switching command RRC message is IP address information of a non-F1-terminating topology domain.

[0062] For example, after switching is completed, the target donor can directly send an RRC message to the IAB node, and introduce a new information element therein, i.e., first indication information non-F1-terminating-Indication, so that the IAB node can determine after receiving the RRC message, i.e., when the first indication information is included in the switching command RRC message, that at least one IP address configuration carried by the RRC message is IP address information of a non-F1 terminating topology domain.

[0063] In some embodiments, the first indication information may be included in a newly added information element of the RRC reconfiguration message, or may be included in an IP address configuration list information element of the RRC reconfiguration message, or may be included in an IP address configuration information element of the RRC reconfiguration message, or may be included in an IP address index information element of the RRC reconfiguration message, as described below with reference to examples.

[0064] 1) A new information element, non-F1-terminating-Indication, is added to the first RRC reconfiguration message to indicate that at least one IP address configuration carried by the RRC message is IP address information of a non-F1 terminating topology domain or to indicate that the at least one IP address configuration is generated by a non-F1 terminating donor.

[0065] The first RRC reconfiguration message can be described using Abstract Syntax Notation One (ASN.1) data format as follows:

[0066] [Table 1] 2) A new information element, non-F1-terminating-Indication, is added to the IP address configuration list information element IAB-IP-AddressConfigurationList of the first RRC reconfiguration message to indicate that at least one IP address configuration carried by the RRC message is IP address information of a non-F1 terminating topology domain or to indicate that the at least one IP address configuration is generated by a non-F1 terminating donor.

[0067] The IP address configuration list information element can be written using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0068] [Table 2] The indication methods in 1) and 2) above allow all IP address information to be uniformly indicated as IP address information of a non-F1 termination topology domain, thereby saving information bits.

[0069] 3) A new information element, non-F1-terminating-Indication, is added to the IP address configuration information element IAB-IP-AddressConfiguration of the first RRC reconfiguration message to indicate that a certain IP address configuration carried by the RRC message is IP address information of a non-F1 terminating topology domain or to indicate that the IP address configuration is generated by a non-F1 terminating donor.

[0070] The IP address configuration information element can be written using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0071] [Table 3] 4) A new information element, non-F1-terminating-Indication, is added to the IP address index information element IAB-IP-AddressIndexInfo of the first RRC reconfiguration message to indicate that a certain IP address configuration carried by the RRC message is IP address information of a non-F1 terminating topology domain or to indicate that the IP address configuration is generated by a non-F1 terminating donor.

[0072] The IP address index information element can be written using the Abstract Syntax Notation One (ASN.1) data format as follows:

[0073] [Table 4] According to the instruction methods in 3) and 4) above, the granularity of the instruction may be for each set IP address information, so that the instruction method may be more flexible.

[0074] (2) Dual Connection Scenario 1 In some embodiments, FIG. 12 is a diagram showing a dual connection scenario 1. As shown in FIG. 12, in the dual connection scenario 1, the first IAB donor (F1 termination donor) is the main node (also called the master node) MN of the IAB node, and the second IAB donor (non-F1 termination donor) is the secondary node SN of the IAB node. After the dual connection is established, some of the border node's business can be migrated to the non-F1 termination topology domain, and some of the business can still be located 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 set 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 set after the dual connection is established. When the indication is implicit, the IAB node can determine that the at least one IP address configuration in the RRC message received by SRB3 includes IP address information of a non-F1 terminated topology domain, or can determine that the at least one IP address configuration in the secondary cell group configuration information received by SRB1 includes IP address information of a non-F1 terminated topology domain, or can determine that the at least one IP address configuration in the RRC message received by SRB1 includes IP address information of a F1 terminated topology domain. When the indication is explicit, the IAB node can determine that the at least one IP address configuration in the secondary cell group configuration information received by SRB1 includes IP address information of a non-F1 terminated topology domain when receiving the first indication information, and can determine that the at least one IP address configuration in the secondary cell group configuration information received by SRB1 includes IP address information of a F1 terminated topology domain when not receiving the first indication information. Each will be described below.

[0075] In some embodiments, an IP address of a non-F1 terminated topology domain is configured during a secondary cell group addition process, and the first RRC reconfiguration message is an RRC reconfiguration message carried by a secondary cell group configuration (mrdc-SecondaryCellGroupConfig field) of an RRC reconfiguration message, which is entirely generated by a second donor and carried by a second RRC reconfiguration message sent by the first IAB donor, and the IAB node receives the second RRC reconfiguration message sent by the first IAB donor via an SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of a non-F1 terminated topology domain, and the IP address of a non-F1 terminated topology domain refers to an IP address anchored to a donor-DU2.

[0076] The ASN.1 structure of the RRC reconfiguration message is shown below, and includes a secondary cell group configuration (mrdc-SecondaryCellGroupConfig field).

[0077] [Table 5] (i) Implied Instructions For example, the SN can generate a secondary cell group configuration RRC message and send it to the MN in a secondary cell group addition response message, and after receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message and forwards the secondary cell group configuration RRC message to the IAB node in the mrdc-SecondaryCellGroupConfig field of the second RRC reconfiguration message. Therefore, after receiving the second RRC reconfiguration message by SRB1, the IAB node can obtain the RRC reconfiguration message carried therein by the mrdc-SecondaryCellGroupConfig field, and the IAB node knows that the RRC reconfiguration message carried in the mrdc-SecondaryCellGroupConfig field is generated by an SN (i.e., at least one IP address configuration is provided by an SN), and since the SN is a non-F1 terminated, the IAB node can determine that the at least one IP address configuration carried by the RRC reconfiguration message carried in the mrdc-SecondaryCellGroupConfig field is IP address information of a non-F1 terminated topology domain. That is, the IAB node can determine that the at least one IP address configuration in the RRC reconfiguration message carried in the mrdc-SecondaryCellGroupConfig field received by SRB1 includes IP address information of a non-F1 terminated topology domain.

[0078] (ii) Explicit instructions For example, when the SN generates a secondary cell group configuration RRC message, it can introduce a new information element therein, i.e., first indication information non-F1-terminating, and send it to the MN in a secondary cell group addition response message, and the MN generates a second RRC reconfiguration message after receiving the secondary cell group configuration RRC message sent by the SN, and puts the secondary cell group configuration RRC message into the mrdc-SecondaryCellGroupConfig field in the second RRC reconfiguration message and forwards it to the IAB node. Thus, after the IAB node receives the second RRC reconfiguration message through the SRB1, it can obtain the RRC reconfiguration message in the mrdc-SecondaryCellGroupConfig field carried therein and the first indication information contained therein, so that the IAB node can determine that at least one IP address configuration carried by the RRC reconfiguration message in the mrdc-SecondaryCellGroupConfig field is IP address information of a non-F1 terminating topology domain. Incidentally, an example of introducing the first indication information into the secondary cell group configuration RRC message is similar to 1)-4) above, and therefore a detailed description thereof will be omitted here.

[0079] For example, the SN generates a secondary cell group configuration RRC message and sends it to the MN in a secondary cell group addition response message, and the MN generates a second RRC reconfiguration message after receiving the secondary cell group configuration RRC message sent by the SN, introduces a new information element, i.e., first indication information non-F1-terminating, into the second RRC reconfiguration message, and transmits the secondary cell group configuration RRC message to the IAB node in the second RRC reconfiguration message. Thus, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message and the first indication information carried therein in the mrdc-SecondaryCellGroupConfig field, so that the IAB node can determine that at least one IP address configuration carried by the RRC reconfiguration message in the mrdc-SecondaryCellGroupConfig field is IP address information of a non-F1 terminating topology domain. An example of introducing first instruction information into the second RRC reconfiguration message is similar to that of 1) above, but the difference is that when the second RRC reconfiguration message is generated, it is not necessary to include the information element iab-IP-AddressConfigurationList-r16 regarding its own IP address configuration.

[0080] In some embodiments, an IP address of a non-F1 terminated topology domain can be configured (changed) after dual connectivity establishment is completed. The first RRC reconfiguration message is directly sent by the second IAB donor to an IAB node, and the IAB node receives the first RRC reconfiguration message sent by the second IAB donor via an SRB3. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, the at least one IP address configuration includes IP address information of a non-F1 terminated topology domain, and the IP address of the non-F1 terminated topology domain refers to an IP address anchored to donor-DU2.

[0081] (i) Implied Instructions For example, the IAB node receives the first RRC reconfiguration message via SRB3, the IAB node knows that the first RRC reconfiguration message is generated by an SN (i.e., at least one IP address configuration is provided by an SN), and since the SN is a non-F1 terminated, the IAB node can determine that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 terminated topology domain. That is, the IAB node can determine that the at least one IP address configuration in the first RRC reconfiguration message received by SRB1 includes IP address information of a non-F1 terminated topology domain.

[0082] (ii) Explicit instructions For example, when SN generates a first RRC reconfiguration message, it can introduce a new information element therein, namely, first indication information non-F1-terminating, and the IAB node can obtain the first RRC reconfiguration message and the first indication information therein through SRB3, so that the IAB node can determine that at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 terminating topology domain. Note that, the example of introducing the first indication information into the first RRC reconfiguration message is the same as the above 1)-4), and thus the detailed description thereof is omitted here.

[0083] In some embodiments, after the dual connection establishment is completed, an IP address of a non-F1 terminated topology domain can be configured (changed) during a secondary cell group change process. The first RRC reconfiguration message is an RRC reconfiguration message included in an mrdc-SecondaryCellGroupConfig field and is carried by a second RRC reconfiguration message sent by the first IAB donor, and the IAB node receives the second RRC reconfiguration message sent by the first IAB donor via an SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of a non-F1 terminated topology domain, and the IP address of the non-F1 terminated topology domain refers to an IP address anchored to donor-DU2.

[0084] (i) Implied Instructions For example, the SN generates a secondary cell group configuration RRC message and sends it to the MN in a secondary cell group change request message, and the MN generates a second RRC reconfiguration message after sending the secondary cell group configuration RRC message sent by the SN, and sends the secondary cell group configuration RRC message in the mrdc-SecondaryCellGroupConfig field in the second RRC reconfiguration message to the IAB node. Thus, after the IAB node receives the second RRC reconfiguration message through SRB1, it can obtain the RRC reconfiguration message carried therein in the mrdc-SecondaryCellGroupConfig field, and the IAB node knows that the RRC reconfiguration message carried in the mrdc-SecondaryCellGroupConfig field is generated by the SN (i.e., at least one IP address configuration is provided by the SN), and since the SN is a non-F1 termination, the IAB node can determine that the at least one IP address configuration carried by the secondary cell group configuration RRC message is the IP address information of a non-F1 termination topology domain. That is, the IAB node can determine that at least one IP address configuration in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field received by SRB1 includes IP address information of a non-F1 termination topology domain.

[0085] (ii) Explicit instructions For example, when the SN generates a secondary cell group configuration RRC message, it can introduce a new information element therein, i.e., the first indication information non-F1-terminating, and send it in a secondary cell group change request message to the MN. After the MN sends the secondary cell group configuration RRC message sent by the SN, it generates a second RRC reconfiguration message, and sends the secondary cell group configuration RRC message in the mrdc-SecondaryCellGroupConfig field in the second RRC reconfiguration message to the IAB node, so that the IAB node can obtain the RRC reconfiguration message and the first indication information carried therein carried in the mrdc-SecondaryCellGroupConfig field after receiving the second RRC reconfiguration message by SRB1. Therefore, the IAB node can determine that at least one IP address configuration carried by the RRC reconfiguration message carried in the mrdc-SecondaryCellGroupConfig field is the IP address information of the non-F1 terminating topology domain. Incidentally, an example of introducing the first indication information into the secondary cell group configuration RRC message is similar to 1)-4) above, and therefore a detailed description thereof will be omitted here.

[0086] For example, the SN generates a secondary cell group configuration RRC message and sends it to the MN in a secondary cell group change request message, and the MN generates a second RRC reconfiguration message after sending the secondary cell group configuration RRC message sent by the SN, introduces a new information element, i.e., first indication information non-F1-terminating, into the second RRC reconfiguration message, and forwards the secondary cell group configuration RRC message to the IAB node in the mrdc-SecondaryCellGroupConfig field of the second RRC reconfiguration message. Thus, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message and the first indication information contained in the mrdc-SecondaryCellGroupConfig field therein, so that the IAB node can determine that at least one IP address configuration carried by the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is IP address information of a non-F1 terminating topology domain. An example of introducing first instruction information into the second RRC reconfiguration message is the same as that in 1) above, and the difference is that when the second RRC reconfiguration message is generated, it is not necessary to include the information element iab-IP-AddressConfigurationList-r16 regarding its own IP address configuration.

[0087] In some embodiments, after the dual connection establishment is completed, the IP address of the non-F1 terminating topology domain may be reconfigured during the IAB transport transition management process and sent by the MN to the IAB node.

[0088] (i) Implied Instructions The first RRC reconfiguration message is an RRC reconfiguration message included in an mrdc-SecondaryCellGroupConfig field, and since the IAB transmission transition management process does not support SN to generate a secondary cell group configuration RRC message, the first RRC reconfiguration message is generated by the first IAB donor instead of the second IAB donor, and is carried by a second RRC reconfiguration message sent by the first IAB donor. The IAB node receives the second RRC reconfiguration message sent by the first IAB donor via an SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of a non-F1 terminated topology domain, and the IP address of the non-F1 terminated topology domain refers to an IP address anchored to donor-DU2.

[0089] For example, the SN provides at least one IP address configuration and sends it to the MN in an IAB transmission transition management response message, and after the MN receives the at least one IP address configuration, it generates a first RRC reconfiguration message on behalf of the second IAB donor and forwards the first RRC reconfiguration message in a second RRC reconfiguration message to the IAB node. Thus, after the IAB node receives the second RRC reconfiguration message by SRB1, it can obtain the RRC reconfiguration message carried therein in the mrdc-SecondaryCellGroupConfig field, and the IAB node knows that the at least one IP address configuration in the RRC reconfiguration message carried in the mrdc-SecondaryCellGroupConfig field is provided by the SN, and since the SN is a non-F1 termination, the IAB node can determine that the at least one IP address configuration carried by the secondary cell group configuration RRC message is the IP address information of a non-F1 termination topology domain. That is, the IAB node can determine that at least one IP address configuration in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field received by SRB1 includes IP address information of a non-F1 termination topology domain.

[0090] (ii) Explicit instructions The SN provides at least one IP address configuration to the MN, the first RRC reconfiguration message is generated by the MN, and the IAB node receives the second RRC reconfiguration message sent by the first IAB donor via an SRB1, the first RRC reconfiguration message includes at least one IP address configuration for the IAB node, the at least one IP address configuration includes IP address information of a non-F1 terminating topology domain, and the IP address of the non-F1 terminating topology domain refers to an IP address anchored to a donor-DU2.

[0091] For example, the SN provides at least one IP address configuration and sends it to the MN in an IAB transmission transition management response message, and the MN can generate a first RRC reconfiguration message after receiving the at least one IP address configuration, introduce a new information element therein, i.e., first indication information non-F1-terminating, and send the first RRC reconfiguration message to the IAB node, so that the IAB node can obtain the at least one IP address information and the first indication information carried therein after receiving the first RRC reconfiguration message by SRB1. Therefore, the IAB node can determine that the at least one IP address configuration carried by the first RRC reconfiguration message is the IP address information of the non-F1 terminating topology domain. Note that the example of introducing the first indication information into the first RRC reconfiguration message is the same as the above 1)-4), and the detailed description thereof will be omitted here.

[0092] In some embodiments, after the dual connection establishment is completed, an IP address of a non-F1 terminated topology domain can be reconfigured during an IAB transmission transition management process, where the first RRC reconfiguration message is generated by an SN and directly sent by the second IAB donor to the IAB node, and the IAB node receives the first RRC reconfiguration message sent by the second IAB donor via an SRB3. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, where the at least one IP address configuration includes IP address information of a non-F1 terminated topology domain, and the IP address of the non-F1 terminated topology domain refers to an IP address anchored to donor-DU2.

[0093] (i) Implied Instructions For example, the IAB node receives the first RRC reconfiguration message via SRB3, and the IAB node knows that the first RRC reconfiguration message is generated by an SN (i.e., at least one IP address configuration is provided by an SN), and the SN is a non-F1 terminated, so the IAB node can determine that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 terminated topology domain. That is, the IAB node can determine that the at least one IP address configuration in the first RRC reconfiguration message received by SRB1 includes IP address information of a non-F1 terminated topology domain.

[0094] (ii) Explicit instructions For example, when SN generates a first RRC reconfiguration message, it introduces a new information element therein, namely, first indication information non-F1-terminating, and the IAB node can receive the first RRC reconfiguration message and the first indication information therein through SRB3, so that the IAB node can determine that at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 terminating topology domain. Note that, examples of the first RRC reconfiguration message are the same as those in 1)-4) above, and detailed description thereof is omitted here.

[0095] In some embodiments, after the dual connection establishment is completed, an IP address of an F1 terminated topology domain can be configured (changed) during a secondary cell group change process. The first RRC reconfiguration message is generated by the MN and sent directly to the IAB node by the first IAB donor, and the IAB node receives the first RRC reconfiguration message sent by the first IAB donor via SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, the at least one IP address configuration includes IP address information of an F1 terminated topology domain, and the IP address of the F1 terminated topology domain refers to an IP address anchored to donor-DU1.

[0096] (i) Implied Instructions For example, the IAB node receives the first RRC reconfiguration message via SRB1, the IAB node knows that the first RRC reconfiguration message is generated by the MN (i.e., at least one IP address configuration is provided by the MN), and the MN is F1 terminated, so the IAB node can determine that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of the F1 terminated topology domain, that is, the IAB node can determine that the at least one IP address configuration in the first RRC reconfiguration message received by SRB1 includes IP address information of the F1 terminated topology domain.

[0097] (ii) Explicit instructions For example, when the MN generates a first RRC reconfiguration message, there is no need to introduce a new information element therein, i.e., the first indication information non-F1-terminating, and the IAB node receives the first RRC reconfiguration message via SRB1, and the first indication information is not included therein, i.e., the IAB node does not receive the first indication information, so the IAB node can determine that at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of the F1-terminating topology domain.

[0098] (3) Dual Connection Scenario 2 In some embodiments, FIG. 13 is a diagram showing dual connection scenario 2. As shown in FIG. 13, in dual connection scenario 2, the first IAB donor (F1 termination donor) is the secondary node SN of the IAB node, and the second IAB donor (the non-F1 termination donor) is the main node MN of the IAB node. After the dual connection is established, some of the border node's business can be migrated to the non-F1 termination topology domain, and some of the business can still be located in the F1 termination donor topology domain. 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 dual connection scenario 1 is that the IP address of the non-F1 termination topology domain cannot be set 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 set after the dual connection is established. When the indication is implicit, the IAB node can determine that the at least one IP address configuration in the RRC message received by SRB1 includes IP address information of a non-F1 terminated topology domain, or can determine that the at least one IP address configuration in the secondary cell group configuration information received by SRB1 includes IP address information of an F1 terminated topology domain, or can determine that the at least one IP address configuration in the RRC message received by SRB3 includes IP address information of an F1 terminated topology domain. When the indication is explicit, the IAB node can determine that the at least one IP address configuration in the first RRC reconfiguration message includes IP address information of a non-F1 terminated topology domain when receiving the first indication information, and can determine that the at least one IP address configuration in the first RRC reconfiguration message includes IP address information of an F1 terminated topology domain when not receiving the first indication information. Each will be described below.

[0099] In some embodiments, an IP address of a non-F1 terminated topology domain can be configured (changed) after dual connectivity establishment is completed. The first RRC reconfiguration message is sent by the second IAB donor to an IAB node, and the IAB node receives the first RRC reconfiguration message sent by the second IAB donor via SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, the at least one IP address configuration includes IP address information of a non-F1 terminated topology domain, and the IP address of the non-F1 terminated topology domain refers to an IP address anchored to donor-DU1.

[0100] (i) Implied Instructions For example, the IAB node receives the first RRC reconfiguration message by SRB1, and the IAB node knows that the first RRC reconfiguration message is generated by the MN (i.e., at least one IP address configuration is provided by the MN), and the MN is a non-F1 terminated, so the IAB node can determine that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 terminated topology domain. That is, the IAB node can determine that the at least one IP address configuration in the first RRC reconfiguration message received by SRB1 includes IP address information of a non-F1 terminated topology domain.

[0101] (ii) Explicit instructions For example, when the MN generates a first RRC reconfiguration message, it introduces a new information element therein, namely, first indication information non-F1-terminating, and the IAB node can receive the first RRC reconfiguration message and the first indication information therein through SRB1, so that the IAB node can determine that at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 terminating topology domain. Note that the example of introducing the first indication information into the first RRC reconfiguration message is the same as the above 1)-4), and the detailed description thereof is omitted here.

[0102] In some embodiments, after the dual connection establishment is completed, an IP address of an F1 terminated topology domain can be configured (changed) during a secondary cell group change process. The first RRC reconfiguration message is generated by a first IAB donor, and the IAB node receives the first RRC reconfiguration message sent by the first IAB donor via an SRB3. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, the at least one IP address configuration includes IP address information of an F1 terminated topology domain, and the IP address of the F1 terminated topology domain refers to an IP address anchored to a donor-DU2.

[0103] (i) Implied Instructions For example, the IAB node receives the first RRC reconfiguration message via SRB3, the IAB node knows that the first RRC reconfiguration message is generated by an SN (i.e., at least one IP address configuration is provided by an SN), and since the SN is an F1 termination, the IAB node can determine that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of an F1 terminated topology domain, that is, the IAB node can determine that the at least one IP address configuration in the first RRC reconfiguration message received by SRB3 includes IP address information of an F1 terminated topology domain.

[0104] (ii) Explicit instructions For example, when an SN generates a first RRC reconfiguration message, there is no need to introduce a new information element therein, i.e., the first indication information non-F1-terminating, and the IAB node receives the first RRC reconfiguration message through SRB3, and since the IAB node does not receive the first indication information, it can be determined that at least one IP address configuration in the first RRC reconfiguration message received by SRB3 includes IP address information of the F1-terminating topology domain.

[0105] In some embodiments, after the dual connectivity establishment is completed, an IP address of the F1 terminated topology domain can be configured (changed) during the secondary cell group change process. The first RRC reconfiguration message is an RRC reconfiguration message included in an mrdc-SecondaryCellGroupConfig field of an RRC reconfiguration message, which is entirely generated by a first IAB donor and carried by a third RRC reconfiguration message sent by the second IAB donor, and the IAB node receives the third RRC reconfiguration message sent by the second IAB donor via an SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, the at least one IP address configuration includes IP address information of an F1 terminated topology domain, and the IP address of the F1 terminated topology domain refers to an IP address anchored to donor-DU2.

[0106] (i) Implied Instructions For example, the SN generates a secondary cell group configuration RRC message and sends it to the MN in a secondary cell group change request message, and the MN generates a third RRC reconfiguration message after sending the secondary cell group configuration RRC message sent by the SN, and sends the secondary cell group configuration RRC message in the mrdc-SecondaryCellGroupConfig field in the third RRC reconfiguration message to the IAB node. Thus, after the IAB node receives the third RRC reconfiguration message through SRB1, it can obtain the RRC reconfiguration message carried therein in the mrdc-SecondaryCellGroupConfig field, and the IAB node knows that the RRC reconfiguration message carried in the mrdc-SecondaryCellGroupConfig field is generated by the SN (i.e., at least one IP address configuration is provided by the SN), and since the SN is an F1 termination, the IAB node can determine that the at least one IP address configuration carried by the RRC reconfiguration message carried in the mrdc-SecondaryCellGroupConfig field is the IP address information of the F1 termination topology domain. That is, the IAB node can determine that at least one IP address configuration in the secondary cell group configuration RRC message received by SRB1 includes IP address information of the F1 terminated topology domain.

[0107] (ii) Explicit instructions For example, when the SN generates a secondary cell group configuration RRC message, there is no need to introduce a new information element therein, i.e., the first indication information non-F1-terminating, and the secondary cell group configuration RRC message is put into a secondary cell group change request message and sent to the MN. After sending the secondary cell group configuration RRC message sent by the SN, the MN generates a third RRC reconfiguration message, and puts the secondary cell group configuration RRC message into the mrdc-SecondaryCellGroupConfig field in the third RRC reconfiguration message and forwards it to the IAB node. Therefore, after receiving the third RRC reconfiguration message by SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried therein, but both the first RRC reconfiguration message and the third RRC reconfiguration message do not contain the first indication information, that is, the IAB node does not receive the first indication information, so the IAB node can determine that at least one IP address configuration carried by the secondary cell group configuration RRC message is IP address information of the F1 termination topology domain.

[0108] In some embodiments, after the dual connection establishment is completed, an IP address of a non-F1 terminated topology domain can be configured (changed) during an IAB transmission transition management process, and the first RRC reconfiguration message is generated by the second IAB donor and sent by the second IAB donor to an IAB node. The IAB node receives the first RRC reconfiguration message sent by the second IAB donor via SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of a non-F1 terminated topology domain, and the IP address of the non-F1 terminated topology domain refers to an IP address anchored to donor-DU1.

[0109] (i) Implied Instructions For example, SN sends an IAB transmission transition management request message to MN, and MN (second IAB donor, non-F1 terminated donor) generates a first RRC reconfiguration message after receiving the request message, in which the at least one IP address configuration includes IP address information of a non-F1 terminated topology domain, and sends the first RRC reconfiguration message to an IAB node. Thus, after receiving the first RRC reconfiguration message by SRB1, the IAB node can obtain the at least one IP address configuration carried therein, and the IAB node knows that the at least one IP address configuration is provided by MN, and since MN is non-F1 terminated, the IAB node can determine that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 terminated topology domain. That is, the IAB node can determine that the at least one IP address configuration in the first RRC reconfiguration message received by SRB1 includes IP address information of a non-F1 terminated topology domain.

[0110] (ii) Explicit instructions For example, an SN sends an IAB transmission transition management request message to an MN, and the MN (second IAB donor, non-F1 terminating donor) can generate a first RRC reconfiguration message after receiving the request message, introduce a new information element therein, i.e., first indication information non-F1-terminating, and send the first RRC reconfiguration message to an IAB node, so that the IAB node can obtain at least one IP address information and first indication information carried therein after receiving the first RRC reconfiguration message through SRB1, so that the IAB node can determine that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 terminating topology domain. Note that the example of introducing the first indication information into the first RRC reconfiguration message is the same as the above 1)-4), and a detailed description thereof will be omitted here.

[0111] In some embodiments, after the dual connection establishment is completed, an IP address of an F1-terminated topology domain can be configured (changed) during an IAB transmission transition management process, and the first RRC reconfiguration message may be generated by the second IAB donor instead of the first IAB donor and sent by the second IAB donor to an IAB node. The IAB node receives the first RRC reconfiguration message sent by the second IAB donor via an SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of an F1-terminated topology domain, and the IP address of the F1-terminated topology domain refers to an IP address anchored to donor-DU2.

[0112] (i) Implied Instructions For example, the SN provides at least one IP address configuration (including IP address information of the F1 termination topology domain) and sends it in an IAB transmission transition change request message to the MN (second IAB donor, non-F1 termination donor); after receiving the request message, the MN generates a secondary cell configuration RRC message on behalf of the SN, in which the at least one IP address configuration includes the IP address information of the F1 termination topology domain, and generates a third RRC reconfiguration message, and forwards the first RRC reconfiguration message to the IAB node in the mrdc-SecondaryCellGroupConfig field in the third RRC reconfiguration message. Therefore, after receiving the third RRC Reconfiguration message by SRB1, the IAB node can obtain the RRC Reconfiguration message carried therein by the mrdc-SecondaryCellGroupConfig field, and the IAB node knows that the at least one IP address configuration in the RRC Reconfiguration message carried in the mrdc-SecondaryCellGroupConfig field is provided by an SN, and since the SN is an F1 termination donor, the IAB node can determine that the at least one IP address configuration carried by the first RRC Reconfiguration message is IP address information of the F1 termination topology domain, that is, the IAB node can determine that the at least one IP address configuration in the RRC Reconfiguration message carried in the mrdc-SecondaryCellGroupConfig field in the first RRC Reconfiguration message received by SRB1 includes IP address information of the F1 termination topology domain.

[0113] (ii) Explicit instructions The SN provides at least one IP address configuration (including IP address information of the F1 terminated topology domain) and sends it to the MN (second IAB donor, non-F1 terminated donor) in an IAB transmission transition change request message, and the MN generates a first RRC reconfiguration message after receiving the request message, in which the at least one IP address configuration includes the IP address information of the F1 terminated topology domain. However, there is no need to introduce first indication information into the first RRC reconfiguration message, and the first indication information is not included in the first RRC reconfiguration message, that is, the IAB node does not receive the first indication information, so the IAB node can determine that the at least one IP address configuration carried by the RRC message is the IP address information of the F1 terminated topology domain.

[0114] The above describes how to configure and indicate an IP address of a non-F1 terminated topology domain or an F1 terminated topology domain, and how an IAB node distinguishes whether the configured IP address is a non-F1 terminated topology domain or an F1 terminated topology domain. In the above embodiment, an IAB node can know whether an MN or an SN is an F1 terminated donor or a non-F1 terminated donor, for example, an IAB node can determine that an MN or an SN is an F1 terminated donor based on which donor provides the BAP configuration information (bap-config-r16 field) it receives.

[0115] In the above-mentioned explicit instruction, the first instruction information is received as an example to explain how to determine that the IP address to be set is a non-F1 termination topology domain or an F1 termination topology domain, but the present invention is not limited thereto, and for example, the first instruction information can be used to indicate whether the IP address setting includes IP address information of a non-F1 termination topology domain, or the first instruction information can be used to indicate whether the IP address setting includes IP address information of a non-F1 termination topology domain or IP address information of an F1 termination topology domain. In this case, for example, the IAB may receive the first instruction information, and when the value of the first instruction information is a first value (true or 1), determine that the IP address setting includes IP address information of a non-F1 termination topology domain, and when the value of the first instruction information is a second value (false or 0), determine that the IP address setting includes IP address information of an F1 termination topology domain, but the specific flow is the same as that described above, and the detailed description thereof is omitted here.

[0116] The above signaling process is for illustrative purposes only to describe the embodiments of the present invention, but the present invention is not limited thereto, and more specific content of the signaling can be further referred to the related art. In addition, for example, the execution order between each operation can be appropriately adjusted, or some other operations can be increased or decreased. Those skilled in the art can make appropriate modifications based on the above content without being limited to the description of the above drawings.

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

[0118] As can be seen from the above embodiment, the first RRC reconfiguration message can configure the IAB node with an IP address of a non-F1-terminating topology domain or an IP address of an F1-terminating topology domain, thus enabling the boundary node to transmit services whose routing IDs belong to the F1-terminating topology domain and services whose routing IDs belong to the non-F1-terminating topology domain, respectively.

[0119] <Example of the second aspect> In the embodiment of the present invention, a method for determining a transmission address is provided, which is described from the first IAB donor side, and the description of the same contents as those in the embodiment of the first aspect will be omitted.

[0120] 14 is a diagram showing another method for determining a transmission address in an embodiment of the present invention. As shown in FIG. 14, the method includes the following steps:

[0121] 1401: The first IAB donor sends a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; or sends at least one IP address configuration for the IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain.

[0122] In some embodiments, the first IAB donor can send the first RRC reconfiguration message to the IAB node or a second IAB donor, the IAB node's F1 connection is terminated at the first IAB donor, and the IAB node has an RRC connection with the second IAB donor.

[0123] In some embodiments, the first IAB donor may implicitly indicate whether the IP address to be configured belongs to a non-F1 terminated topology domain, or may explicitly indicate whether the IP address to be configured belongs to a non-F1 terminated topology domain, for example, the first IAB donor may indicate through first indication information that the IP address configuration includes IP address information of an F1 terminated topology domain or includes IP address information of a non-F1 terminated topology domain.

[0124] In some embodiments, the IP address configuration includes IP address information of a non-F1 termination topology domain.

[0125] In some embodiments, the first IAB donor is a source donor of the IAB node switching, the second IAB donor is a target donor of the IAB node switching, and the first RRC reconfiguration message is a switching command RRC message, and the method may further include: the first IAB donor receives a first RRC reconfiguration message sent by the second IAB donor, and at 1401, the first IAB donor forwards the first RRC reconfiguration message generated by the second IAB donor to the IAB node.

[0126] In some embodiments, the first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node.

[0127] For example, the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration area in an RRC reconfiguration message, and is carried by a second RRC reconfiguration message sent by the first IAB donor, and the first IAB donor sends the second RRC reconfiguration message to the IAB node via SRB1.

[0128] The method further includes: the first IAB donor receives the first RRC reconfiguration message sent by the second IAB donor, where the first RRC reconfiguration message is generated by the second IAB donor; and in 1401, the first IAB donor sends the second RRC reconfiguration message, where the second RRC reconfiguration message is generated by the first IAB donor, to the IAB node via SRB1, where the second RRC reconfiguration message carries the first RRC reconfiguration message.

[0129] Alternatively, the method may further include: the first IAB donor receives the IP address configuration provided by the second IAB donor and generates the first RRC reconfiguration message on behalf of the second IAB donor; and in 1401, the first IAB donor sends the second RRC reconfiguration message (the second RRC reconfiguration message is also generated by the first IAB donor) to the IAB node via SRB1, carrying the first RRC reconfiguration message in the second RRC reconfiguration message.

[0130] For example, the method may further include: the first IAB donor receives the IP address configuration provided by the second IAB donor and generates a first RRC reconfiguration message, and at 1401, the first IAB donor sends the first RRC reconfiguration message to the IAB node via SRB1.

[0131] In the above embodiment, the IP address configuration includes IP address information of a non-F1 terminated topology domain, and when explicitly indicated, the first IAB donor indicates that the IP address configuration includes IP address information of a non-F1 terminated topology domain by the first RRC reconfiguration message or the second RRC reconfiguration message including the first indication information, which is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

[0132] In some embodiments, the IP address configuration includes IP address information of an F1 termination topology domain.

[0133] In some embodiments, the first IAB donor is an SN of the IAB node and the second IAB donor is an MN of the IAB node.

[0134] For example, at 1401, the first IAB donor sends the first RRC reconfiguration message to the IAB node via SRB3.

[0135] For example, in 1401, the first IAB donor sends the first RRC reconfiguration message to the second IAB donor, where the first RRC reconfiguration message is a secondary cell group configuration RRC message.

[0136] For example, at 1401, the first IAB donor sends the IP address configuration to the second IAB donor, where the IP address configuration is carried in an IAB transport transition change request message.

[0137] In some embodiments, the first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node.

[0138] For example, the first IAB donor sends the first RRC reconfiguration message to the IAB node via SRB1.

[0139] In the above embodiment, the IP address configuration includes IP address information of an F1 terminated topology domain. When explicitly indicating, the first IAB donor indicates that the IP address configuration includes IP address information of an F1 terminated topology domain by causing the first RRC reconfiguration message to not include the first indication information.

[0140] It should be noted that the above-mentioned FIG. 14 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 adjusted, or some other 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. 14.

[0141] As can be seen from the above embodiment, the first RRC reconfiguration message can configure the IAB node with an IP address of a non-F1-terminating topology domain or an IP address of an F1-terminating topology domain, thus enabling the boundary node to transmit services whose routing IDs belong to the F1-terminating topology domain and services whose routing IDs belong to the non-F1-terminating topology domain, respectively.

[0142] <Example of the third aspect> In an embodiment of the present invention, a method for determining a transmission address is provided, which is described from the side of a second IAB donor.

[0143] 15 is a diagram showing a method for determining a transmission address in an embodiment of the present invention. As shown in FIG. 15, the method includes the following steps:

[0144] 1501: The second IAB donor sends a first RRC reconfiguration message, the first RRC reconfiguration message including at least one IP address configuration for an IAB node; or sends at least one IP address configuration for an IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain.

[0145] In some embodiments, the second IAB donor can send the first RRC reconfiguration message to the IAB node or the first IAB donor, the IAB node's F1 connection is terminated at the first IAB donor, and the IAB node has an RRC connection with the second IAB donor.

[0146] In some embodiments, the second IAB donor may implicitly indicate whether the IP address to be configured belongs to a non-F1 terminated topology domain, or may explicitly indicate whether the IP address to be configured belongs to a non-F1 terminated topology domain, for example, the second IAB donor may indicate through first indication information that the IP address configuration includes IP address information of an F1 terminated topology domain or includes IP address information of a non-F1 terminated topology domain.

[0147] In some embodiments, the IP address configuration includes IP address information of a non-F1 termination topology domain.

[0148] In some embodiments, the first IAB donor is a source donor of the IAB node switching, the second IAB donor is a target donor of the IAB node switching, the first RRC reconfiguration message is a switching command RRC message, and at 1501, the second IAB donor sends the first RRC reconfiguration message to the first IAB donor.

[0149] In some embodiments, the first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node.

[0150] For example, in 1501, the second IAB donor sends a first RRC reconfiguration message to the first IAB donor; or For example, at 1501, the second IAB donor sends the IP address configuration to the first IAB donor.

[0151] For example, at 1501, the second IAB donor sends the first RRC reconfiguration message to the IAB node via SRB3.

[0152] In some embodiments, the second IAB donor is a main node MN of the IAB node, and the first IAB donor is a secondary node SN of the IAB node.

[0153] For example, at 1501, the second IAB donor sends the first RRC reconfiguration message to the IAB node via SRB1.

[0154] In the above embodiment, the IP address configuration includes IP address information of a non-F1 terminated topology domain, and when there is an explicit indication, the second IAB donor indicates that the IP address configuration includes IP address information of a non-F1 terminated topology domain by including the first indication information in the first RRC reconfiguration message, which is included in a newly added information element of the first RRC reconfiguration message, or included in an IP address configuration list information element of the first RRC reconfiguration message, or included in an IP address configuration information element of the first RRC reconfiguration message, or included in an IP address index information element of the first RRC reconfiguration message.

[0155] In some embodiments, the IP address configuration includes IP address information of an F1 termination topology domain.

[0156] In some embodiments, the first IAB donor is an SN of the IAB node and the second IAB donor is an MN of the IAB node.

[0157] For example, the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration area in an RRC reconfiguration message, and is carried by a third RRC reconfiguration message sent by the second IAB donor, and in 1501, the second IAB donor sends the third RRC reconfiguration message to the IAB node via SRB1.

[0158] The method further includes: the second IAB donor receiving a first RRC reconfiguration message sent by the first IAB donor.

[0159] For example, at 1501, the second IAB donor receives the IP address configuration provided by the first IAB donor and generates the first RRC reconfiguration message on behalf of the first IAB donor.

[0160] For example, the method may further include: the second IAB donor receives the IP address configuration sent by the first IAB donor, and at 1501, the second IAB donor sends the first RRC reconfiguration message to the IAB node via SRB1.

[0161] In the above embodiment, the IP address configuration includes IP address information of an F1 terminated topology domain. When explicitly indicating, the first IAB donor indicates that the IP address configuration includes IP address information of an F1 terminated topology domain by causing the first RRC reconfiguration message or the third RRC reconfiguration message not to include the first indication information.

[0162] It should be noted that the above-mentioned FIG. 15 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 adjusted, or some other operations can be increased or decreased. 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. 15.

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

[0164] As can be seen from the above embodiment, the first RRC reconfiguration message can configure the IAB node with an IP address of a non-F1-terminating topology domain or an IP address of an F1-terminating topology domain, thus enabling the boundary node to transmit services whose routing IDs belong to the F1-terminating topology domain and services whose routing IDs belong to the non-F1-terminating topology domain, respectively.

[0165] <Example of the fourth aspect> In the embodiment of the present invention, an IAB node device is provided, and the description of the same contents as those in the embodiment of the first aspect will be omitted. The device may be, for example, an IAB node in an IAB system (e.g., a border node in the embodiment of the first aspect), or may be one or more parts, assemblies, or modules provided in the IAB node.

[0166] 16 is a diagram illustrating an IAB node device in an embodiment of the present invention. As shown in FIG. 16, an IAB node device 1600 includes:

[0167] A first receiving unit 1601: receives a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.

[0168] The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain.

[0169] In some embodiments, the IAB node's F1 connection is terminated with a first IAB donor, and the IAB node has an RRC connection with a second IAB donor.

[0170] In some embodiments, the device further comprises:

[0171] A first processing unit 1602: determines that the IP address configuration includes IP address information of an F1 termination topology domain or IP address information of a non-F1 termination topology domain.

[0172] In some embodiments, the first processing unit determines, based on the first indication information, that the IP address configuration includes IP address information of an F1 termination topology domain or IP address information of a non-F1 termination topology domain.

[0173] In some embodiments, the first processing unit determines that the IP address configuration includes IP address information of a non-F1-terminating topology domain.

[0174] In some embodiments, the first IAB donor is a source donor of the IAB node switching, the second IAB donor is a target donor of the IAB node switching, and the first RRC reconfiguration message is a switching command RRC message generated by the second IAB donor and forwarded by the first IAB donor.

[0175] In some embodiments, the first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node.

[0176] For example, the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in an RRC reconfiguration message and is carried by a second RRC reconfiguration message sent by the first IAB donor, and the first receiver receives the second RRC reconfiguration message sent by the first IAB donor via SRB1. Optionally, the first RRC reconfiguration message may be generated by the first IAB donor on behalf of the second IAB donor.

[0177] For example, the first receiver receives the first RRC reconfiguration message sent by the second IAB donor via SRB3.

[0178] For example, the first receiver receives the first RRC reconfiguration message sent by the first IAB donor via SRB1.

[0179] In some embodiments, the first IAB donor is an SN of the IAB node, the second IAB donor is an MN of the IAB node, and the first receiver receives the first RRC reconfiguration message sent by the second IAB donor via SRB1.

[0180] In some embodiments, the first processing unit determines that the IP address configuration includes IP address information of a non-F1 terminated topology domain when the first indication information is included in the first RRC reconfiguration message or the second RRC reconfiguration message, and the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

[0181] In some embodiments, the first processing unit determines that the IP address configuration includes IP address information of an F1-terminating topology domain.

[0182] In some embodiments, the first IAB donor is a main node MN of the IAB node, the second IAB donor is a secondary node SN of the IAB node, and the first receiver receives the first RRC reconfiguration message sent by the first IAB donor via SRB1.

[0183] In some embodiments, the first IAB donor is an SN of the IAB node and the second IAB donor is an MN of the IAB node.

[0184] For example, the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in an RRC reconfiguration message and is carried by a third RRC reconfiguration message sent by the second IAB donor, and the first receiver receives the third RRC reconfiguration message sent by the second IAB donor via SRB1. Optionally, the first RRC reconfiguration message is generated by the second IAB donor on behalf of the first IAB donor.

[0185] For example, the first receiver receives the first RRC reconfiguration message sent by the first IAB donor via SRB3.

[0186] For example, the first receiver receives the first RRC reconfiguration message sent by the second IAB donor via SRB1.

[0187] In some embodiments, the first processing unit determines that the IP address configuration includes IP address information of an F1 termination topology domain when the first indication information is not included in the first RRC reconfiguration message or the third RRC reconfiguration message.

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

[0189] Although the above describes each component or module related to the present invention, the present invention is not limited thereto. The IAB node device 1600 in the embodiment of the present invention may include other components or modules, and the specific contents of these components or modules are referred to in the related art.

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

[0191] As can be seen from the above embodiment, the first RRC reconfiguration message can configure the IAB node with an IP address of a non-F1-terminating topology domain or an IP address of an F1-terminating topology domain, thus enabling the boundary node to transmit services whose routing IDs belong to the F1-terminating topology domain and services whose routing IDs belong to the non-F1-terminating topology domain, respectively.

[0192] <Example of the fifth 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. The device may be, for example, an IAB donor-CU in an IAB system (e.g., the first IAB donor in the embodiments of the first, second, and third aspects), or one or more parts, assemblies, or modules provided in the IAB donor-CU.

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

[0194] A first sending unit 1701: Send a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or send at least one IP address configuration for the IAB node.

[0195] The at least one IP address configuration includes IP address information of an F1 terminated topology domain, or includes IP address information of a non-F1 terminated topology domain, in which the F1 connection of the IAB node is terminated at the first IAB donor, and the IAB node has an RRC connection with a second IAB donor.

[0196] In some embodiments, the IAB donor device indicates through the first indication information that the IP address configuration includes IP address information of an F1 termination topology domain or includes IP address information of a non-F1 termination topology domain.

[0197] In some embodiments, the IP address configuration includes IP address information of a non-F1 termination topology domain.

[0198] In some embodiments, the first IAB donor is a source donor of a switching of the IAB node, the second IAB donor is a target donor of a switching of the IAB node, and the first RRC reconfiguration message is a switching command RRC message.

[0199] Among them, the device further includes the following (not shown): a second receiving unit, which receives a first RRC reconfiguration message sent by the second IAB donor, and the first transmitting unit, which forwards the first RRC reconfiguration message generated by the second IAB donor to the IAB node.

[0200] In some embodiments, the first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node.

[0201] For example, the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration area in an RRC reconfiguration message, and is carried by a second RRC reconfiguration message sent by the first IAB donor, and the first transmitter sends the second RRC reconfiguration message to the IAB node via SRB1.

[0202] In some embodiments, the device further comprises (not shown): A third receiving unit: receives the first RRC reconfiguration message sent by the second IAB donor.

[0203] In some embodiments, the device further comprises (not shown): A fourth receiving unit: receiving the IP address configuration provided by the second IAB donor; and A second processing unit: generates the first RRC reconfiguration message on behalf of the second IAB donor.

[0204] In some embodiments, the device further comprises (not shown): A fifth receiving unit: receives the IP address configuration provided by the second IAB donor, and the first sending unit sends the first RRC reconfiguration message via SRB1.

[0205] In some embodiments, the IAB donor device indicates that the IP address configuration includes IP address information of a non-F1 terminated topology domain by the first RRC reconfiguration message or the second RRC reconfiguration message including the first indication information.

[0206] In some embodiments, the IP address configuration includes IP address information of an F1 termination topology domain.

[0207] In some embodiments, the first IAB donor is an SN of the IAB node and the second IAB donor is an MN of the IAB node.

[0208] For example, the first transmitter sends the first RRC reconfiguration message to the IAB node via SRB3.

[0209] For example, the first transmitter sends the first RRC reconfiguration message to the second IAB donor, where the first RRC reconfiguration message is a secondary cell group configuration RRC message; or The first sender sends the IP address configuration to the second IAB donor.

[0210] In some embodiments, the first IAB donor is a main node MN of the IAB node, the second IAB donor is a secondary node SN of the IAB node, and the first transmitter sends the first RRC reconfiguration message to the IAB node via SRB1.

[0211] In some embodiments, the IAB donor device indicates that the IP address configuration includes IP address information of an F1 terminated topology domain by the first RRC reconfiguration message not including the first indication information.

[0212] In some embodiments, the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

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

[0214] Although the above describes each component or module related to the present invention, the present invention is not limited thereto. The IAB donor device 1700 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.

[0215] For convenience, Fig. 17 shows only the connection relationships or signal directions between each component or module, but various related technologies such as bus connection may be adopted as understood by those skilled in the art. 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), but the implementation of the present invention is not limited thereto.

[0216] As can be seen from the above embodiment, the first RRC reconfiguration message can configure the IAB node with an IP address of a non-F1-terminating topology domain or an IP address of an F1-terminating topology domain, thus enabling the boundary node to transmit services whose routing IDs belong to the F1-terminating topology domain and services whose routing IDs belong to the non-F1-terminating topology domain, respectively.

[0217] <Example of the sixth 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 third aspect will be omitted. The device may be, for example, an IAB donor-CU in an IAB system (e.g., the second IAB donor in the embodiments of the first, second, and third aspects), or may be one or more parts, assemblies, or modules provided in the IAB donor-CU.

[0218] 18 is a diagram illustrating an IAB donor device in accordance with an embodiment of the present invention. As shown in FIG. 18, an IAB donor device 1800 includes:

[0219] A second sending unit 1801: Sends a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or sends at least one IP address configuration for an IAB node.

[0220] The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain.

[0221] Wherein, the F1 connection of the IAB node is terminated at the first IAB donor, and the IAB node and the second IAB donor have an RRC connection.

[0222] In some embodiments, the IAB donor device indicates through the first indication information that the IP address configuration includes IP address information of an F1 termination topology domain or includes IP address information of a non-F1 termination topology domain.

[0223] In some embodiments, the IP address configuration includes IP address information of a non-F1 termination topology domain.

[0224] In some embodiments, the first IAB donor is a source donor of the IAB node switching, the second IAB donor is a target donor of the IAB node switching, the first RRC reconfiguration message is a switching command RRC message, and the second transmitter transmits the first RRC reconfiguration message to the first IAB donor.

[0225] In some embodiments, the first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node.

[0226] For example, the second sending unit sends a first RRC reconfiguration message to the first IAB donor; or sends the IP address configuration to the first IAB donor.

[0227] For example, the second transmitter sends the first RRC reconfiguration message to the IAB node via SRB3.

[0228] In some embodiments, the first IAB donor is an SN of the IAB node, the second IAB donor is an MN of the IAB node, and the second transmitter sends the first RRC reconfiguration message to the IAB node via SRB1.

[0229] In some embodiments, the IAB donor device indicates that the IP address configuration includes IP address information of a non-F1 terminated topology domain by including the first indication information pointer in the first RRC reconfiguration message.

[0230] In some embodiments, the IP address configuration includes IP address information of an F1 termination topology domain.

[0231] In some embodiments, the first IAB donor is an SN of the IAB node and the second IAB donor is an MN of the IAB node.

[0232] For example, the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration area in an RRC reconfiguration message, and is carried by a third RRC reconfiguration message sent by the second IAB donor, and the second transmitter sends the third RRC reconfiguration message to the IAB node via SRB1.

[0233] In some embodiments, the device further comprises (not shown): A sixth receiving unit: receives a first RRC reconfiguration message sent by the first IAB donor.

[0234] In some embodiments, the device further comprises (not shown): A seventh receiving unit: receiving the IP address configuration provided by the first IAB donor; and A second processing unit: generates the first RRC reconfiguration message on behalf of the first IAB donor.

[0235] In some embodiments, the device further comprises (not shown): An eighth receiving unit: receives the IP address configuration sent by the first IAB donor, and the second sending unit sends the first RRC reconfiguration message to the IAB node via SRB1.

[0236] In some embodiments, the IAB donor device indicates that the IP address configuration includes IP address information of the F1 termination topology domain by the first RRC reconfiguration message or the third RRC reconfiguration message not including the first indication information.

[0237] In some embodiments, the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

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

[0239] Although the above describes each component or module related to the present invention, the present invention is not limited thereto. The IAB donor device 1800 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.

[0240] For convenience, only the connection relationships or signal directions between each component or module are shown in Fig. 18, but various related technologies such as bus connection may be adopted as understood by those skilled in the art. 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), but the implementation of the present invention is not limited thereto.

[0241] As can be seen from the above embodiment, the first RRC reconfiguration message can configure the IAB node with an IP address of a non-F1-terminating topology domain or an IP address of an F1-terminating topology domain, thus enabling the boundary node to transmit services whose routing IDs belong to the F1-terminating topology domain and services whose routing IDs belong to the non-F1-terminating topology domain, respectively.

[0242] <Example of the seventh aspect> In an embodiment of the present invention, a communication system is provided, which includes a first IAB donor device of an embodiment of the fourth aspect, a second IAB donor device of an embodiment of the fifth aspect, and an IAB-node device of an embodiment of the third aspect, and the network architecture of the donor device and the IAB-node device can further be referred to the related art, and detailed description thereof will be omitted here.

[0243] In an embodiment of the present invention, an IAB device is further provided, which may be an IAB donor device or an IAB node device (a transition node or a child node).

[0244] 9 is a diagram showing an IAB 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.

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

[0246] Also, for example, the processor 901 may be configured to execute a program to implement the transmission address determination method in the embodiment of the second aspect.

[0247] Also, for example, the processor 901 may be configured to execute a program to implement the transmission address determination method in the embodiment of the third aspect.

[0248] 9, the IAB device 900 may further include a transceiver 903, an antenna 904, etc., among which the functions of the above-mentioned components are the same as those of the prior art, and therefore detailed description thereof will be omitted here. Note that the IAB device 900 does not need to include all the components shown in Fig. 9. The IAB device 900 may also include components not shown in Fig. 9, but the prior art can be referred to for this information.

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

[0250] An embodiment of the present invention further provides a storage medium storing a computer readable program, in which the computer readable program causes a computer to perform the transmission address determination method according to the embodiment of the first to third aspects in an IAB device.

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

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

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

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

[0255] <Border node> (Appendix 1) A method for determining a transmission address, comprising: and applying the method to access and backhaul IAB node equipment, the method comprising: receiving a first RRC reconfiguration message from the IAB node; the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; The method, wherein the at least one IP address configuration includes IP address information of an F1 termination topology domain or includes IP address information of a non-F1 termination topology domain.

[0256] (Appendix 2) 2. The method according to claim 1, comprising: A method, wherein an F1 connection of the IAB node is terminated with a first IAB donor, and the IAB node has an RRC connection with a second IAB donor.

[0257] (Appendix 3) 3. The method according to claim 2, comprising: The method further comprises: The method includes the IAB node determining that the IP address configuration includes IP address information of an F1 termination topology domain or IP address information of a non-F1 termination topology domain.

[0258] (Appendix 4) 4. The method according to claim 3, comprising: The IAB node determines, based on first indication information, that the IP address configuration includes IP address information of an F1 termination topology domain or IP address information of a non-F1 termination topology domain.

[0259] (Appendix 5) 5. The method according to claim 3 or 4, The IAB node determines that the IP address configuration includes IP address information of a non-F1-terminating topology domain.

[0260] (Appendix 6) 6. The method according to claim 5, the first IAB donor is a source donor for the IAB node switching, and the second IAB donor is a target donor for the IAB node switching; The method, wherein the first RRC reconfiguration message is a switch command RRC message forwarded by a first IAB donor and generated by a second IAB donor.

[0261] (Appendix 7) 6. The method according to claim 5, The method, wherein the first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node.

[0262] (Appendix 8) 8. The method according to claim 7, The first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in the RRC reconfiguration message, and is carried by a second RRC reconfiguration message sent by the first IAB donor; A method in which the IAB node receives the second RRC reconfiguration message sent by the first IAB donor via SRB1.

[0263] (Appendix 9) 9. The method according to claim 8, comprising: The method of claim 1, wherein the first RRC reconfiguration message is generated by the first IAB donor on behalf of the second IAB donor.

[0264] (Appendix 10) 8. The method according to claim 7, A method in which the IAB node receives the first RRC reconfiguration message sent by the second IAB donor via SRB3.

[0265] (Appendix 11) 8. The method according to claim 7, A method in which the IAB node receives the first RRC reconfiguration message sent by the first IAB donor via SRB1.

[0266] (Appendix 12) 6. The method according to claim 5, the first IAB donor is an SN of the IAB node, and the second IAB donor is an MN of the IAB node; The method comprises receiving the first RRC reconfiguration message sent by the second IAB donor via SRB1, wherein the IAB node receives the first RRC reconfiguration message sent by the second IAB donor via SRB1.

[0267] (Appendix 13) 13. The method according to any one of claims 5 to 12, comprising: A method in which the IAB node determines that the IP address configuration includes IP address information of a non-F1 terminated topology domain when the first indication information is included in the first RRC reconfiguration message or the second RRC reconfiguration message.

[0268] (Appendix 14) 5. The method according to claim 3 or 4, The IAB node determines that the IP address configuration includes IP address information of an F1-terminating topology domain.

[0269] (Appendix 15) 15. The method according to claim 14, The first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node; A method in which the IAB node receives the first RRC reconfiguration message sent by the first IAB donor via SRB1.

[0270] (Appendix 16) 12. The method according to claim 11, The method, wherein the first IAB donor is an SN of the IAB node and the second IAB donor is an MN of the IAB node.

[0271] (Appendix 17) 17. The method of claim 16, comprising: The first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell configuration field in the RRC reconfiguration message, and is carried by a third RRC reconfiguration message sent by the second IAB donor; The IAB node receives the third RRC reconfiguration message sent by the second IAB donor via SRB1.

[0272] (Appendix 18) 18. The method according to claim 17, comprising: The method of claim 1, wherein the first RRC reconfiguration message is generated by the second IAB donor on behalf of the first IAB donor.

[0273] (Appendix 19) 17. The method of claim 16, comprising: A method in which the IAB node receives the first RRC reconfiguration message sent by the first IAB donor via SRB3.

[0274] (Appendix 20) 17. The method of claim 16, comprising: The method comprises receiving the first RRC reconfiguration message sent by the second IAB donor via SRB1, wherein the IAB node receives the first RRC reconfiguration message sent by the second IAB donor via SRB1.

[0275] (Appendix 21) 21. The method according to any one of claims 14 to 20, comprising: A method in which the IAB node determines that the IP address configuration includes IP address information of an F1 terminated topology domain when the first RRC reconfiguration message or the third RRC reconfiguration message does not include the first indication information.

[0276] (Appendix 22) 14. The method according to claim 13, comprising: The method according to claim 1, wherein the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

[0277] (Appendix 23) An IAB node (donor) device, A memory and a processor are included, The device, wherein the memory stores a computer program, and the processor is configured to execute the computer program to realize the transmission address determination method described in any one of Supplementary Notes 1 to 22.

[0278] <First donor CU node side> (Appendix 1) A method for determining a transmission address, comprising: and applying to a first IAB donor, the method comprising: the first IAB donor sends a first RRC reconfiguration message, the first RRC reconfiguration message including at least one IP address configuration for an IAB node; or transmitting an IP address configuration of at least one of the IAB nodes; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain; wherein an F1 connection of the IAB node is terminated at the first IAB donor, and the IAB node has an RRC connection with a second IAB donor.

[0279] (Appendix 2) 2. The method according to claim 1, comprising: The first IAB donor indicates through first indication information that the IP address configuration includes IP address information of an F1 termination topology domain or includes IP address information of a non-F1 termination topology domain.

[0280] (Appendix 3) 3. The method according to claim 1 or 2, The method, wherein the IP address configuration includes IP address information of a non-F1 termination topology domain.

[0281] (Appendix 4) 4. The method according to claim 3, comprising: the first IAB donor is a source donor of the IAB node switching, the second IAB donor is a target donor of the IAB node switching, and the first RRC reconfiguration message is a switching command RRC message; wherein the first IAB donor receives a first RRC reconfiguration message sent by the second IAB donor, and forwards the first RRC reconfiguration message generated by the second IAB donor to the IAB node.

[0282] (Appendix 5) 4. The method according to claim 3, comprising: The method, wherein the first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node.

[0283] (Appendix 6) 6. The method according to claim 5, The first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in the RRC reconfiguration message, and is carried by a second RRC reconfiguration message sent by the first IAB donor; The first IAB donor sends the second RRC reconfiguration message to the IAB node via SRB1.

[0284] (Appendix 7) 7. The method according to claim 6, comprising: The method further comprises: The method includes the first IAB donor receiving the first RRC reconfiguration message transmitted by the second IAB donor.

[0285] (Appendix 8) 7. The method according to claim 6, comprising: The method further comprises: The method includes the first IAB donor receiving the IP address configuration provided by the second IAB donor and generating the first RRC reconfiguration message on behalf of the second IAB donor.

[0286] (Appendix 9) 6. The method according to claim 5, The method further comprises: The method includes the first IAB donor receiving the IP address configuration provided by the second IAB donor and sending the first RRC reconfiguration message via SRB1.

[0287] (Appendix 10) 10. The method according to any one of claims 3 to 9, comprising: The first IAB donor indicates that the IP address configuration includes IP address information of a non-F1 terminated topology domain by including the first indication information in the first RRC reconfiguration message or the second RRC reconfiguration message.

[0288] (Appendix 11) 3. The method according to claim 1 or 2, The method, wherein the IP address configuration includes IP address information of an F1 termination topology domain.

[0289] (Appendix 12) 12. The method according to claim 11, The method, wherein the first IAB donor is an SN of the IAB node and the second IAB donor is an MN of the IAB node.

[0290] (Appendix 13) 13. The method of claim 12, The first IAB donor sends the first RRC reconfiguration message to the IAB node via SRB3.

[0291] (Appendix 14) 13. The method of claim 12, the first IAB donor sends the first RRC reconfiguration message to the second IAB donor, where the first RRC reconfiguration message is a secondary cell group configuration RRC message; or The first IAB donor transmits the IP address configuration to the second IAB donor.

[0292] (Appendix 15) 12. The method according to claim 11, The first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node; The first IAB donor sends the first RRC reconfiguration message to the IAB node via SRB1.

[0293] (Appendix 17) 16. The method according to any one of claims 11 to 15, comprising: The first IAB donor indicates that the IP address configuration includes IP address information of an F1 termination topology domain by the first RRC reconfiguration message not including the first indication information.

[0294] (Appendix 18) 11. The method of claim 10, further comprising: The method according to claim 1, wherein the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

[0295] (Appendix 19) An IAB donor device, A memory and a processor are included, The device, wherein the memory stores a computer program, and the processor is configured to execute the computer program to realize the transmission address determination method described in any one of Supplementary Notes 1 to 17.

[0296] <Second donor CU node side> (Appendix 1) A method for determining a transmission address, comprising: and applying to a second IAB donor, said method comprising: the second IAB donor sends a first RRC reconfiguration message, the first RRC reconfiguration message including at least one IP address configuration for an IAB node; or transmitting at least one IP address configuration for the IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain; wherein an F1 connection of the IAB node is terminated with a first IAB donor, and the IAB node has an RRC connection with the second IAB donor.

[0297] (Appendix 2) 2. The method according to claim 1, comprising: The second IAB donor indicates through first indication information that the IP address configuration includes IP address information of an F1 termination topology domain or includes IP address information of a non-F1 termination topology domain.

[0298] (Appendix 3) 3. The method according to claim 1 or 2, The method, wherein the IP address configuration includes IP address information of a non-F1 termination topology domain.

[0299] (Appendix 4) 4. The method according to claim 3, comprising: the first IAB donor is a source donor of the IAB node switching, the second IAB donor is a target donor of the IAB node switching, and the first RRC reconfiguration message is a switching command RRC message; The second IAB donor sends the first RRC reconfiguration message to the first IAB donor.

[0300] (Appendix 5) 4. The method according to claim 3, comprising: The method, wherein the first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node.

[0301] (Appendix 6) 6. The method according to claim 5, The second IAB donor sends a first RRC reconfiguration message to the first IAB donor; or sends the IP address configuration to the first IAB donor.

[0302] (Appendix 7) 6. The method according to claim 5, The second IAB donor sends the first RRC reconfiguration message to the IAB node via SRB3.

[0303] (Appendix 8) 4. The method according to claim 3, comprising: the first IAB donor is an SN of the IAB node, and the second IAB donor is an MN of the IAB node; The second IAB donor sends the first RRC reconfiguration message to the IAB node via SRB1.

[0304] (Appendix 9) 9. The method according to any one of claims 3 to 8, comprising: The second IAB donor indicates that the IP address configuration includes IP address information of a non-F1 terminated topology domain by including the first indication information in the first RRC reconfiguration message.

[0305] (Appendix 10) 3. The method according to claim 1 or 2, The method, wherein the IP address configuration includes IP address information of an F1 termination topology domain.

[0306] (Appendix 11) 11. The method of claim 10, further comprising: The method, wherein the first IAB donor is an SN of the IAB node and the second IAB donor is an MN of the IAB node.

[0307] (Appendix 12) 12. The method according to claim 11, The first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in the RRC reconfiguration message, and is carried by a third RRC reconfiguration message sent by the second IAB donor; The second IAB donor sends the third RRC reconfiguration message to the IAB node via SRB1.

[0308] (Appendix 13) 13. The method of claim 12, The method further comprises: The second IAB donor receives a first RRC reconfiguration message sent by the first IAB donor.

[0309] (Appendix 14) 13. The method of claim 12, further comprising: The second IAB donor receives the IP address configuration provided by the first IAB donor and generates the first RRC reconfiguration message on behalf of the first IAB donor.

[0310] (Appendix 15) 12. The method according to claim 11, The method further comprises: The method includes: the second IAB donor receiving the IP address configuration sent by the first IAB donor; and sending the first RRC reconfiguration message to the IAB node via SRB1.

[0311] (Appendix 16) 16. The method according to any one of claims 11 to 15, comprising: The second IAB donor indicates that the IP address configuration includes IP address information of an F1 termination topology domain by the first RRC reconfiguration message or the third RRC reconfiguration message not including the first indication information.

[0312] (Appendix 17) 10. The method according to claim 9, The first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

[0313] (Appendix 18) 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 determination method according to any one of Supplementary Notes 1 to 17.

[0314] <Border node> (Appendix 1) An IAB node device, the device includes a first receiver; The first receiving unit receives a first RRC reconfiguration message; the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain.

[0315] (Appendix 2) 2. The device of claim 1, An apparatus, wherein an F1 connection of the IAB node is terminated with a first IAB donor, and the IAB node has an RRC connection with a second IAB donor.

[0316] (Appendix 3) 1. The device according to claim 2, The device further includes a first processing section; The first processing unit determines that the IP address configuration includes IP address information of an F1 termination topology domain or IP address information of a non-F1 termination topology domain.

[0317] (Appendix 4) 3. The device according to claim 3, The first processing unit determines, based on the first indication information, that the IP address configuration includes IP address information of an F1 termination topology domain or IP address information of a non-F1 termination topology domain, the device.

[0318] (Appendix 5) 5. The device according to claim 3 or 4, The first processing unit determines that the IP address configuration includes IP address information of a non-F1-terminating topology domain.

[0319] (Appendix 6) 5. The device according to claim 5, the first IAB donor is a source donor for the IAB node switching, and the second IAB donor is a target donor for the IAB node switching; The first RRC reconfiguration message is a switch command RRC message generated by a second IAB donor and forwarded by a first IAB donor.

[0320] (Appendix 7) 5. The device according to claim 5, The first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node,

[0321] (Appendix 8) 8. The device according to claim 7, The first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in the RRC reconfiguration message, and is carried by a second RRC reconfiguration message sent by the first IAB donor; The first receiving unit receives the second RRC reconfiguration message transmitted by the first IAB donor via SRB1, the device.

[0322] (Appendix 9) 10. The device according to claim 8, The first RRC reconfiguration message is generated by the first IAB donor on behalf of the second IAB donor.

[0323] (Appendix 10) 8. The device according to claim 7, The first receiving unit receives the first RRC reconfiguration message transmitted by the second IAB donor via SRB3, the device.

[0324] (Appendix 11) 8. The device according to claim 7, The first receiving unit receives the first RRC reconfiguration message transmitted by the first IAB donor via SRB1, the device.

[0325] (Appendix 12) 5. The device according to claim 5, the first IAB donor is an SN of the IAB node, and the second IAB donor is an MN of the IAB node; The first receiving unit receives the first RRC reconfiguration message transmitted by the second IAB donor via SRB1, the device.

[0326] (Appendix 13) 13. A device according to any one of claims 5 to 12, comprising: The first processing unit determines that the IP address configuration includes IP address information of a non-F1 terminated topology domain when the first RRC reconfiguration message or the second RRC reconfiguration message includes the first indication information.

[0327] (Appendix 14) 5. The device according to claim 3 or 4, The first processing unit determines that the IP address configuration includes IP address information of an F1-terminating topology domain.

[0328] (Appendix 15) 15. The device of claim 14, The first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node; The first receiving unit receives the first RRC reconfiguration message transmitted by the first IAB donor via SRB1, the device.

[0329] (Appendix 16) 12. The device of claim 11, The first IAB donor is an SN of the IAB node, and the second IAB donor is an MN of the IAB node.

[0330] (Appendix 17) 17. The device of claim 16, The first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell configuration field in the RRC reconfiguration message, and is carried by a third RRC reconfiguration message sent by the second IAB donor; The first receiving unit receives the third RRC reconfiguration message transmitted by the second IAB donor via SRB1, the device.

[0331] (Appendix 18) 18. The device of claim 17, The first RRC reconfiguration message is generated by the second IAB donor on behalf of the first IAB donor.

[0332] (Appendix 19) 17. The device of claim 16, The first receiving unit receives the first RRC reconfiguration message transmitted by the first IAB donor via SRB3, the device.

[0333] (Appendix 20) 17. The device of claim 16, The first receiving unit receives the first RRC reconfiguration message transmitted by the second IAB donor via SRB1, the device.

[0334] (Appendix 21) 21. A device according to any one of claims 14 to 20, comprising: The first processing unit determines that the IP address configuration includes IP address information of an F1 termination topology domain when the first indication information is not included in the first RRC reconfiguration message or the third RRC reconfiguration message.

[0335] (Appendix 22) 14. The device of claim 13, The device, wherein the first instruction information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

[0336] <First donor CU node side> (Appendix 1) An IAB donor device, a first IAB donor, the device including a first transmitter; The first transmitter transmits a first RRC reconfiguration message, and the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or transmits at least one IP address configuration for the IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain; Wherein, an F1 connection of the IAB node is terminated at the first IAB donor, and the IAB node has an RRC connection with a second IAB donor.

[0337] (Appendix 2) 2. The device of claim 1, The IAB donor device indicates through first indication information that the IP address configuration includes IP address information of an F1 termination topology domain or includes IP address information of a non-F1 termination topology domain.

[0338] (Appendix 3) 3. The device according to claim 1 or 2, The IP address configuration includes IP address information of a non-F1 termination topology domain.

[0339] (Appendix 4) 3. The device according to claim 3, the first IAB donor is a source donor of the IAB node switching, the second IAB donor is a target donor of the IAB node switching, and the first RRC reconfiguration message is a switching command RRC message; Among them, the device further includes a second receiving unit, which receives a first RRC reconfiguration message sent by the second IAB donor, and the first transmitting unit forwards the first RRC reconfiguration message generated by the second IAB donor to the IAB node.

[0340] (Appendix 5) 3. The device according to claim 3, The first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node,

[0341] (Appendix 6) 5. The device according to claim 5, The first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell configuration field in an RRC reconfiguration message, and is carried by a second RRC reconfiguration message sent by the first IAB donor; The first transmitting unit transmits the second RRC reconfiguration message to the IAB node via SRB1.

[0342] (Appendix 7) 7. The device according to claim 6, The device further includes a third receiver, which receives the first RRC reconfiguration message transmitted by the second IAB donor.

[0343] (Appendix 8) 7. The device according to claim 6, The device further comprises: a fourth receiving unit for receiving the IP address configuration provided by the second IAB donor; and A second processing unit that generates the first RRC reconfiguration message on behalf of the second IAB donor.

[0344] (Appendix 9) 5. The device according to claim 5, The device further includes a fifth receiving unit that receives the IP address configuration provided by the second IAB donor, and the first transmitting unit transmits the first RRC reconfiguration message via SRB1.

[0345] (Appendix 10) 10. A device according to any one of claims 3 to 9, comprising: The IAB donor equipment indicates that the IP address configuration includes IP address information of a non-F1 terminated topology domain by the first RRC reconfiguration message or the second RRC reconfiguration message including the first indication information.

[0346] (Appendix 11) 3. The device according to claim 1 or 2, The method, wherein the IP address configuration includes IP address information of an F1 termination topology domain.

[0347] (Appendix 12) 12. The device of claim 11, The first IAB donor is an SN of the IAB node, and the second IAB donor is an MN of the IAB node.

[0348] (Appendix 13) 13. The device of claim 12, The first transmitting unit transmits the first RRC reconfiguration message to the IAB node via SRB3.

[0349] (Appendix 14) 13. The device of claim 12, the first transmitter sends the first RRC reconfiguration message to the second IAB donor, where the first RRC reconfiguration message is a secondary cell configuration RRC message; or The first sending unit sends the IP address configuration to the second IAB donor.

[0350] (Appendix 15) 12. The device according to claim 11, The first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node; The first transmitting unit transmits the first RRC reconfiguration message to the IAB node via SRB1.

[0351] (Appendix 17) 16. A device according to any one of claims 11 to 15, comprising: The IAB donor equipment indicates that the IP address configuration includes IP address information of an F1 termination topology domain by the first RRC reconfiguration message not including the first indication information.

[0352] (Appendix 18) 11. The apparatus of claim 10, The device, wherein the first instruction information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

[0353] <Second donor CU node side> (Appendix 1) An IAB donor device, Applied to the second IAB donor, The device includes a second transmitter, which transmits a first RRC reconfiguration message, the first RRC reconfiguration message including at least one IP address configuration for an IAB node; or transmits at least one IP address configuration for an IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain; Wherein, an F1 connection of the IAB node is terminated with a first IAB donor, and the IAB node has an RRC connection with the second IAB donor.

[0354] (Appendix 2) 2. The device of claim 1, The IAB donor device indicates through first indication information that the IP address configuration includes IP address information of an F1 termination topology domain or includes IP address information of a non-F1 termination topology domain.

[0355] (Appendix 3) 3. The device according to claim 1 or 2, The IP address configuration includes IP address information of a non-F1 termination topology domain.

[0356] (Appendix 4) 3. The device according to claim 3, the first IAB donor is a source donor of the IAB node switching, the second IAB donor is a target donor of the IAB node switching, and the first RRC reconfiguration message is a switching command RRC message; The second transmitter transmits the first RRC reconfiguration message to the first IAB donor.

[0357] (Appendix 5) 3. The device according to claim 3, The first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node,

[0358] (Appendix 6) 5. The device according to claim 5, The second transmitting unit transmits a first RRC reconfiguration message to the first IAB donor; or transmits the IP address configuration to the first IAB donor.

[0359] (Appendix 7) 5. The device according to claim 5, The second transmission unit transmits the first RRC reconfiguration message to the IAB node via SRB3.

[0360] (Appendix 8) 3. The device according to claim 3, the first IAB donor is an SN of the IAB node, and the second IAB donor is an MN of the IAB node; The second transmission unit transmits the first RRC reconfiguration message to the IAB node via SRB1.

[0361] (Appendix 9) 9. A device according to any one of claims 3 to 8, comprising: The IAB donor equipment indicates that the IP address configuration includes IP address information of a non-F1 terminated topology domain by including the first indication information in the first RRC reconfiguration message.

[0362] (Appendix 10) 3. The device according to claim 1 or 2, The IP address configuration includes IP address information of an F1 termination topology domain.

[0363] (Appendix 11) 11. The apparatus of claim 10, The first IAB donor is an SN of the IAB node, and the second IAB donor is an MN of the IAB node.

[0364] (Appendix 12) 12. The device of claim 11, The first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell configuration field in the RRC reconfiguration message, and is carried by a third RRC reconfiguration message sent by the second IAB donor; The second transmission unit transmits the third RRC reconfiguration message to the IAB node via SRB1.

[0365] (Appendix 13) 13. The device of claim 12, The device further includes a sixth receiver, which receives a first RRC reconfiguration message sent by the first IAB donor.

[0366] (Appendix 14) 13. The device of claim 12, The device further includes a seventh receiver that receives the IP address configuration provided by the first IAB donor; The device further includes a third processing unit that generates the first RRC reconfiguration message on behalf of the first IAB donor.

[0367] (Appendix 15) 12. The device according to claim 11, The device further includes an eighth receiving unit that receives the IP address configuration sent by the first IAB donor, and the second transmitting unit transmits the first RRC reconfiguration message to the IAB node via SRB1.

[0368] (Appendix 16) 16. A device according to any one of claims 11 to 15, comprising: The IAB donor device indicates that the IP address configuration includes IP address information of an F1 termination topology domain by the first RRC reconfiguration message or the third RRC reconfiguration message not including the first indication information.

[0369] (Appendix 17) 10. The device according to claim 9, The first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

Claims

1. 1. An integrated access and backhaul IAB node device, comprising: A first receiving unit, which receives a first RRC reconfiguration message; the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain.

2. 2. The device of claim 1, The IAB node's F1 connection is terminated with a first IAB donor, and the IAB node has an RRC connection with a second IAB donor.

3. 3. The device of claim 2, The device further includes a first processing unit, which determines that the IP address configuration includes IP address information of an F1 termination topology domain or IP address information of a non-F1 termination topology domain.

4. 4. The device of claim 3, The first processing unit determines, based on the first indication information, that the IP address configuration includes IP address information of an F1 termination topology domain or IP address information of a non-F1 termination topology domain.

5. 5. The device according to claim 3 or 4, The first processing unit determines that the IP address configuration includes IP address information of a non-F1-terminating topology domain.

6. 6. The device of claim 5, The first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node.

7. 7. The device of claim 6, The first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in the RRC reconfiguration message, and is carried by a second RRC reconfiguration message sent by the first IAB donor; The first receiving unit receives the second RRC reconfiguration message transmitted by the first IAB donor via SRB1, the device.

8. 6. The device of claim 5, the first IAB donor is an SN of the IAB node, and the second IAB donor is an MN of the IAB node; The first receiving unit receives the first RRC reconfiguration message transmitted by the second IAB donor via SRB1.

9. 6. The device of claim 5, The first processing unit determines that the IP address configuration includes IP address information of a non-F1 termination topology domain when the first indication information is included in the first RRC reconfiguration message or the second RRC reconfiguration message.

10. 5. The device according to claim 3 or 4, The first processing unit determines that the IP address configuration includes IP address information of an F1-terminating topology domain, the device.

11. 11. The apparatus of claim 10, The first IAB donor is an SN of the IAB node and the second IAB donor is an MN of the IAB node.

12. 12. The apparatus of claim 11, The first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell configuration field in the RRC reconfiguration message, and is carried by a third RRC reconfiguration message sent by the second IAB donor; The first receiving unit receives the third RRC reconfiguration message transmitted by the second IAB donor via SRB1.

13. 13. The apparatus of claim 12, The first processing unit determines that the IP address configuration includes IP address information of an F1 termination topology domain when the first indication information is not included in the first RRC reconfiguration message or the third RRC reconfiguration message.

14. 6. The device of claim 5, the first IAB donor is a source donor for the IAB node switching, and the second IAB donor is a target donor for the IAB node switching; The first RRC reconfiguration message is a switch command RRC message generated by a second IAB donor and forwarded by the first IAB donor.

15. 8. The device of claim 7, The first RRC reconfiguration message is generated by the first IAB donor on behalf of the second IAB donor.

16. 13. The apparatus of claim 12, The first RRC reconfiguration message is generated by the second IAB donor on behalf of the first IAB donor.

17. 10. The device of claim 9, The device, wherein the first instruction information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

18. 11. The apparatus of claim 10, The first IAB donor is a main node MN of the IAB node, and the second IAB donor is a secondary node SN of the IAB node; The first receiving unit receives the first RRC reconfiguration message transmitted by the first IAB donor via SRB1, the device.

19. 1. An integrated access and backhaul IAB donor device applied to a first IAB donor, comprising: A first transmitter, which transmits a first RRC reconfiguration message, the first RRC reconfiguration message including at least one IP address configuration for an IAB node; or transmits at least one IP address configuration for the IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain; The F1 connection of the IAB node is terminated at the first IAB donor.

20. 1. An integrated access and backhaul IAB donor device adapted for a second IAB donor, comprising: a second transmitter, which transmits a first RRC reconfiguration message, the first RRC reconfiguration message including at least one IP address configuration for the IAB node; or transmits at least one IP address configuration for the IAB node; The at least one IP address configuration includes IP address information of an F1 termination topology domain, or includes IP address information of a non-F1 termination topology domain; The F1 connection of the IAB node is terminated at a first IAB donor.

Images