IAB node equipment, IAB donor equipment, 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 Art

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

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

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

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

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

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

[0008] Figure 5 shows the F1 user plane (F1-U) protocol stack between the IAB-DU and the IAB donor-CU. Figure 6 shows the F1 control plane (F1-C) protocol stack between the IAB-DU and the IAB donor-CU. As shown in Figures 5 and 6, F1-U and F1-C are established on top of the transmission (IP) layer between the IAB-DU and the IAB donor-CU, and Figures 5 and 6 include a two-hop wireless backhaul and a one-hop wired backhaul.

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

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

[0011] The inventors have discovered the following: When all or some of the operations of an IAB node need to be migrated or configured from an F1-terminating topology domain to a non-F1-terminating topology domain, the routing IDs of all or some of the operations of the IAB node must belong to the non-F1-terminating topology domain. That is, the IAB node must simultaneously transmit operations whose routing IDs belong to the F1-terminating topology domain and operations whose routing IDs belong to the non-F1-terminating topology domain. However, there is currently no corresponding scheme for how to ensure that each IAB node transmits operations whose transmitted routing IDs belong to the F1-terminating topology domain and operations whose routing IDs belong to the non-F1-terminating topology domain.

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

[0013] According to one aspect of the embodiment of the present invention, an integrated access and backhaul IAB node device is provided. The aforementioned device includes a first receiving unit, which receives a first RRC reset message, The first RRC reconfiguration message includes at least one IP address setting for the IAB node. The aforementioned at least one IP address setting includes IP address information for an F1-terminated topology domain, or includes IP address information for a non-F1-terminated topology domain.

[0014] According to another aspect of the embodiment of the present invention, an integrated access and backhaul IAB donor device is provided, which is applied to a first IAB donor. The device includes a first transmitting unit which transmits a first RRC reconfiguration message which includes at least one IP address setting for an IAB node; or transmits the IP address setting for at least one IAB node. The aforementioned at least one IP address setting includes IP address information for an F1-terminated topology domain, or includes IP address information for a non-F1-terminated topology domain. Of these, the F1 connection of the IAB node is terminated at the first IAB donor, and the IAB node has an RRC connection with the second IAB donor.

[0015] According to another aspect of the embodiment of the present invention, an integrated access and backhaul IAB donor device is provided, which is applied to a second IAB donor. The device includes a second transmitting unit which transmits a first RRC reconfiguration message which includes at least one IP address setting for an IAB node; or transmits at least one IP address setting for an IAB node, The aforementioned at least one IP address setting includes IP address information for an F1-terminated topology domain, or includes IP address information for a non-F1-terminated topology domain. Of these, the F1 connection of the IAB node is terminated at the first IAB donor, and the IAB node has an RRC connection with the second IAB donor. [Effects 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 set the IAB node to an IP address of a non-F1 terminating topology domain or an IP address of an F1 terminating topology domain. Thus, for the routing ID of a non-F1 terminating topology domain, the IAB node can use the IP address of the non-F1 terminating topology domain, and for the routing ID of an F1 terminating topology domain, it can use the IP address of the F1 terminating topology domain.

[0017] Specific embodiments of the present invention are disclosed in detail by referring to the following description and drawings, showing aspects in which the principles of the present invention can be adopted. It should be noted that the embodiments of the present invention are not limited in scope by these. Within the scope of the appended claims, the embodiments of the present invention may include various changes, modifications, and substitutions.

[0018] In addition, the features described and / or shown for one embodiment can be used in one or more other embodiments in the same or similar manner, combined with the features in other embodiments, or replace the features in other embodiments.

[0019] It should be noted that terms such as "comprising / including" when used in this specification refer to the presence of features, elements, steps, or assemblies, but also refer to not excluding the presence or addition of one or more other features, elements, steps, or assemblies.

Brief Description of the Drawings

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

[0021] The included drawings are used to provide a further understanding of the embodiments of the present invention. These drawings form a part of this specification, illustrate the embodiments of the present invention, and are used to explain the principles of the present invention together with the written description. Also, as is clear, the drawings described below are only for showing some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without creative labor. [Figure 1] It is a diagram showing an IAB system. [Figure 2] It is a diagram showing the IAB architecture in SA mode. [Figure 3]It is a diagram showing the IAB architecture in EN-DC mode. [Figure 4] It is a diagram showing a parent IAB-node and a child IAB-node. [Figure 5] It is a diagram showing the F1-U protocol stack of an IAB system. [Figure 6] It is a diagram showing the F1-C protocol stack of an IAB system. [Figure 7] It is a diagram showing the routing of an IAB system. [Figure 8] It is a diagram showing network topology adaptation. [Figure 9] It is a diagram showing an IAB device in an embodiment of the present invention. [Figure 10] It is a diagram showing a transmission address determination method in an embodiment of the present invention. [Figure 11] It is a diagram showing a switching scenario. [Figure 12] It is a diagram showing a dual connection scenario 1. [Figure 13] It is a diagram showing a dual connection scenario 2. [Figure 14] It is a diagram showing a transmission address determination method in an embodiment of the present invention. [Figure 15] It is a diagram showing a transmission address determination method in an embodiment of the present invention. [Figure 16] It is a diagram showing an IAB node device in an embodiment of the present invention. [Figure 17] It is a diagram showing an IAB donor device in an embodiment of the present invention. [Figure 18] It is a diagram showing an IAB donor device in an embodiment of the present invention.

Modes for Carrying Out the Invention

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0037] Access IAB nodes store uplink backhaul information (BH information), which includes the routing ID used by the service, the uplink backhaul RLC channel ID, and the next-hop node address. Based on the uplink BH information, the access IAB node sets the routing ID in the BAP layer data packet header for uplink services and selects the BH RLC channel and next-hop node for uplink service transmissions.

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

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

[0040] The path transition settings include updating the default backhaul RLC channel (default BH RLC channel) for uplink F1-C, F1-U, and non-F1 data, updating the default BAP routing ID, and updating the IP address to which the data is routed to the Donor-DU. When an IAB-node accesses a new parent node, it begins applying the aforementioned path transition settings, and similarly configures its child nodes for path transitions.

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

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

[0043] The routing IDs of all or some of the operations on a boundary node belong to the non-F1-terminating topology domain. That is, the boundary node needs to simultaneously transmit operations whose routing IDs belong to the F1-terminating topology domain and operations whose routing IDs belong to the non-F1-terminating topology domain. However, there is currently no corresponding scheme for how to ensure that each boundary node transmits operations whose routing IDs belong to the F1-terminating topology domain and operations whose routing IDs belong to the non-F1-terminating topology domain.

[0044] In the embodiments of the present invention, unless otherwise specified, the IAB node equipment includes a migration node or its child nodes. Furthermore, the phrase "resources for serving the IAB node's operations are already established in the donor-CU's topology domain" may also be expressed as "the IAB node's operations have been migrated to the donor-CU's topology domain," 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 side view> An embodiment of the present invention provides a method for determining a transmission address, which will be explained starting from an IAB node device.

[0046] Figure 10 shows a method for determining a transmission address in an embodiment of the present invention. As shown in Figure 10, the method includes the following steps.

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

[0048] Figure 10 above is merely illustrative to illustrate an embodiment of the present invention, and the present invention is not limited thereto. For example, the execution order between each operation (step) can be appropriately adjusted, or several other operations can be added or removed. Those skilled in the art can make appropriate modifications based on the above description, not limited to the description in Figure 10.

[0049] For routing IDs in non-F1-terminating topology domains, the boundary node must use the IP address of the non-F1-terminating topology domain, i.e., the IP address anchored to the donor-DU of the non-F1-terminating topology domain. Similarly, for F1-terminating topology domain routing IDs, the boundary node must use the IP address of the F1-terminating topology domain, i.e., the 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 set the IAB node to either the IP address of a non-F1-terminating topology domain or the IP address of an F1-terminating topology domain. In this way, the boundary node can 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.

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

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

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

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

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

[0055] In some embodiments, it may be implicitly indicated whether the configured IP address belongs to a non-F1 terminating topology domain, and in 1002, the IAB node can determine, based on the donor providing the IP address information, whether the IP address configuration includes IP address information from an F1 terminating topology domain or an IP address information from a non-F1 terminating topology domain. For example, when the donor providing the IP address information is an F1 terminating donor, it is determined that the IP address configuration includes IP address information from an F1 terminating topology domain, and when the donor providing the IP address information is a non-F1 terminating donor, it is determined that the IP address configuration includes IP address information from a non-F1 terminating topology domain.

[0056] In some embodiments, it may be explicitly indicated whether the IP address to be set belongs to a non-F1 terminating topology domain (for example, explicitly indicated based on first instruction information), and in 1002, the IAB node can determine, based on the first instruction information, that the IP address setting includes IP address information of an F1 terminating topology domain or an IP address information of a non-F1 terminating topology domain. For example, if the first instruction information is used to indicate that the IP address setting includes IP address information of a non-F1 terminating topology domain, the IAB node will determine that the IP address setting includes IP address information of a non-F1 terminating topology domain when it receives the first instruction information, and will determine that the IP address setting includes IP address information of an F1 terminating topology domain when it does not receive the first instruction information, but embodiments of the present invention are not limited to these. The method of carrying the first instruction information and specific examples will be described later. As can be seen from the embodiments described above, by implicit or explicit instruction, the IAB node can distinguish whether the IP address to be set belongs to a non-F1 terminating topology domain or to an F1 terminating topology domain.

[0057] The following will explain implicit and explicit instructions in conjunction with different scenarios.

[0058] (1) Regarding the switching scenario In some embodiments, Figure 11 illustrates a handover scenario, in which, as shown in Figure 11, all operations of the boundary node are migrated to a non-F1 terminating topology domain, the F1 terminating donor is the source donor for the handover of the IAB node, and the non-F1 terminating donor is the target donor for the handover of the IAB node. The IP address of the non-F1 terminating topology domain may be set during the handover process, or it may be set after the handover is complete. If the handover process is in progress, 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 of a failover 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 setting for the IAB node, the at least one IP address setting includes IP address information for a non-F1 terminated topology domain, the non-F1 terminated topology domain IP address refers to an IP address anchored to donor-DU2. The at least one IP address setting may be carried by a failover command RRC message, for example, in the RRC reconfiguration information of the reconfigurationWithSync information field in the master cell group information therein. The IAB node can determine that the at least one IP address setting set by the failover command RRC message includes IP address information for a non-F1 terminated topology domain, or the IAB node can determine that the at least one IP address setting in the RRC message sent by the target donor includes IP address information for 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 providing the IP address information is the target donor), and since the target donor is non-F1 terminated, the IAB node can determine after receiving the switching command RRC message that at least one IP address configuration carried by the switching command RRC message is IP address information for a non-F1 terminated topology domain.

[0060] For example, after the switchover is complete, 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 for a non-F1 terminated 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, namely the first instruction information non-F1-terminating. Therefore, after receiving the switching command RRC message, i.e., when the switching command RRC message contains the first instruction information, the IAB node can determine that at least one IP address configuration carried by the switching command RRC message is IP address information for a non-F1-terminating topology domain.

[0062] For example, after the switchover is complete, the target donor can directly send an RRC message to the IAB node and introduce a new information element, namely the first non-F1-terminating indication, so that the IAB node can determine after receiving the RRC message, i.e., when the switchover instruction RRC message contains the first indication, that at least one IP address configuration carried by the RRC message is IP address information for a non-F1-terminating topology domain.

[0063] In some embodiments, the first instruction information may be included in a newly added information element of the RRC reset message, or in an IP address setting list information element of the RRC reset message, or in an IP address setting information element of the RRC reset message, or in an IP address index information element of the RRC reset message. Each of these will be explained below with examples.

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

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

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

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

[0068] [Table 2] The instruction methods described in 1) and 2) above allow for a unified instruction that all configured IP address information belongs to a non-F1 terminated topology domain, thus saving information bits.

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

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

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

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

[0073] [Table 4] The instruction methods described in 3) and 4) above allow for greater flexibility in the instruction method, as the granularity of the instruction may be limited to the IP address information being set for each individual instruction.

[0074] (ii) Dual connection scenario 1 In some embodiments, Figure 12 shows a dual connection scenario 1, where, as shown in Figure 12, the first IAB donor (F1-terminated donor) is the main node (also called the master node) MN of the IAB node, and the second IAB donor (non-F1-terminated donor) is the secondary node SN of the IAB node. After the dual connection is established, some operations of the boundary node can be moved to the non-F1-terminated topology domain, while some operations remain in the F1-terminated donor topology domain. The IP address of the non-F1-terminated topology domain refers to the IP address anchored to donor-DU2. The IP address of the non-F1-terminated topology domain may be set during the dual connection establishment process, or it may be set after the dual connection is established. In the case of an implicit instruction, the IAB node can determine that the at least one IP address setting in the RRC message received by SRB3 includes IP address information for a non-F1 terminated topology domain, or that the at least one IP address setting in the secondary cell group configuration information received by SRB1 includes IP address information for a non-F1 terminated topology domain, or that the at least one IP address setting in the RRC message received by SRB1 includes IP address information for an F1 terminated topology domain. In the case of an explicit instruction, the IAB node can determine that the at least one IP address setting in the secondary cell group configuration information received by SRB1 includes IP address information for a non-F1 terminated topology domain when it receives first instruction information, and can determine that the at least one IP address setting in the secondary cell group configuration information received by SRB1 includes IP address information for an F1 terminated topology domain when it does not receive first instruction information. Each of these will be explained below.

[0075] In some embodiments, the IP address of a non-F1 terminated topology domain is configured during the secondary cell group addition process, and the first RRC reconfiguration message is an RRC reconfiguration message carried by the secondary cell group configuration (mrdc-SecondaryCellGroupConfig area (field)) of the RRC reconfiguration message, is entirely generated by the second donor and carried by the second RRC reconfiguration message transmitted by the first IAB donor, and the IAB node receives the second RRC reconfiguration message transmitted by the first 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 for a non-F1 terminated topology domain, where the IP address of the non-F1 terminated topology domain refers to an IP address anchored to donor-DU2.

[0076] The ASN.1 structure of the RRC reconfiguration message is as follows, and it includes the Secondary Cell Group setting (mrdc-SecondaryCellGroupConfig area).

[0077] [Table 5] (i) Implicit instructions For example, SN can generate a Secondary Cell Group Configuration RRC message and send it to MN in a Secondary Cell Group Addition Response message. After MN receives the Secondary Cell Group Configuration RRC message sent by SN, it generates a Secondary RRC Reconfiguration message, places the Secondary Cell Group Configuration RRC message in the mrdc-SecondaryCellGroupConfig area of ​​the Secondary RRC Reconfiguration message, and forwards it to the IAB node. Therefore, after the IAB node receives the second RRC reconfiguration message from SRB1, it can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area carried therein, and the IAB node knows that the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area is generated by SN (i.e., at least one IP address setting is provided by SN), and since SN is non-F1 terminated, the IAB node can determine that the at least one IP address setting carried by the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area is IP address information for a non-F1 terminated topology domain. In other words, the IAB node can determine that at least one IP address setting in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area received by SRB1 contains IP address information for a non-F1 terminated topology domain.

[0078] (ii) explicit instructions For example, when SN generates a Secondary Cell Group Configuration RRC message, it can introduce a new information element, namely the first instruction information non-F1-terminating, and send it to MN in the Secondary Cell Group Addition Response message. After MN receives the Secondary Cell Group Configuration RRC message sent by SN, it generates a second RRC reconfiguration message and forwards the Secondary Cell Group Configuration RRC message to the IAB node by placing it in the mrdc-SecondaryCellGroupConfig area. Therefore, after the IAB node receives the second RRC reconfiguration message from SRB1, it can obtain the RRC reconfiguration message in the mrdc-SecondaryCellGroupConfig area and the first instruction information contained therein, so the IAB node can determine that at least one IP address configuration carried by the RRC reconfiguration message in the mrdc-SecondaryCellGroupConfig area is IP address information for a non-F1 terminated topology domain. The example of introducing first instruction information into the secondary recell group setting RRC message is the same as described in 1)-4) above, so a detailed explanation is omitted here.

[0079] For example, SN generates a Secondary Cell Group Configuration RRC message and sends it to MN in a Secondary Cell Group Addition Response message. After MN receives the Secondary Cell Group Configuration RRC message sent by SN, it generates a Secondary RRC Reconfiguration message. The Secondary RRC Reconfiguration message introduces a new information element, namely the first instruction information non-F1-terminating, and the Secondary Cell Group Configuration RRC message is included in the Secondary RRC Reconfiguration message and forwarded to the IAB node. Thus, after the IAB node receives the Secondary RRC Reconfiguration message from SRB1, it can obtain the RRC Reconfiguration message and the first instruction information carried therein in the mrdc-SecondaryCellGroupConfig area. The IAB node can then determine that at least one IP address configuration carried by the RRC Reconfiguration message in the mrdc-SecondaryCellGroupConfig area is IP address information for a non-F1-terminating topology domain. The example of introducing the first instruction information into the second RRC reconfiguration message is the same as in 1) above, but the difference is that when generating the second RRC reconfiguration message, it is not necessary to include the iab-IP-AddressConfigurationList-r16 information element regarding its own IP address configuration.

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

[0081] (i) Implicit instructions For example, the IAB node receives the first RRC reconfiguration message by SRB3, and the IAB node knows that the first RRC reconfiguration message is generated by SN (i.e., at least one IP address setting is provided by SN), and since SN is non-F1 terminated, the IAB node can determine that the at least one IP address setting carried by the first RRC reconfiguration message is IP address information for a non-F1 terminated topology domain. In other words, the IAB node can determine that the at least one IP address setting in the first RRC reconfiguration message received by SRB1 contains IP address information for a non-F1 terminated topology domain.

[0082] (ii) explicit instructions For example, when SN generates the first RRC reconfiguration message, a new information element, namely the first instruction information "non-F1-terminating," can be introduced into it. The IAB node can then obtain the first RRC reconfiguration message and the first instruction information within it via SRB3, and thus determine that at least one IP address configuration carried by the first RRC reconfiguration message is IP address information for a non-F1-terminating topology domain. The example of introducing the first instruction information into the first RRC reconfiguration message is the same as described in 1)-4) above, so a detailed explanation is omitted here.

[0083] In some embodiments, after dual connection establishment is complete, the IP address of a non-F1 terminated topology domain can be set (changed) during the secondary cell group change process. The first RRC reconfiguration message is an RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area 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 SRB1. The first RRC reconfiguration message includes at least one IP address setting for the IAB node, and the at least one IP address setting includes IP address information for a non-F1 terminated topology domain, where the IP address of the non-F1 terminated topology domain refers to an IP address anchored to donor-DU2.

[0084] (i) Implicit instructions For example, SN generates a Secondary Cell Group Configuration RRC message, includes it in a Secondary Cell Group Change Request message, and sends it to MN. After MN sends the Secondary Cell Group Configuration RRC message sent by SN, it generates a second RRC reconfiguration message, includes the Secondary Cell Group Configuration RRC message in the mrdc-SecondaryCellGroupConfig area of ​​the second RRC reconfiguration message, and forwards it to the IAB node. Thus, after the IAB node receives the second RRC reconfiguration message from SRB1, it can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area carried therein. The IAB node knows that the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area is generated by SN (i.e., at least one IP address configuration is provided by SN), and since SN is non-F1 terminated, the IAB node can determine that the at least one IP address configuration carried by the Secondary Cell Group Configuration RRC message is IP address information for a non-F1 terminated topology domain. In other words, the IAB node can determine that at least one IP address setting in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area received by SRB1 contains IP address information for a non-F1 terminated topology domain.

[0085] (ii) explicit instructions For example, when an SN generates a Secondary Cell Group Configuration RRC message, it can introduce a new information element, namely the first instruction information non-F1-terminating, and send it to the MN in a Secondary Cell Group Change Request message. After the MN sends the Secondary Cell Group Configuration RRC message sent by the SN, it generates a second RRC reconfiguration message, places the Secondary Cell Group Configuration RRC message in the mrdc-SecondaryCellGroupConfig area of ​​the second RRC reconfiguration message, and forwards it to the IAB node. As a result, after the IAB node receives the second RRC reconfiguration message by the SRB1, it can obtain the RRC reconfiguration message and the first instruction information carried in the mrdc-SecondaryCellGroupConfig area. Therefore, the IAB node can determine that at least one IP address configuration carried by the RRC reconfiguration message in the mrdc-SecondaryCellGroupConfig area is IP address information for a non-F1-terminating topology domain. The example of introducing first instruction information into the secondary recell group setting RRC message is the same as described in 1)-4) above, and a detailed explanation is omitted here.

[0086] For example, SN generates a Secondary Cell Group Configuration RRC message, includes it in a Secondary Cell Group Change Request message, and sends it to MN. After MN sends the Secondary Cell Group Configuration RRC message sent by SN, it generates a second RRC reconfiguration message, introduces a new information element, namely the first instruction information non-F1-terminating, into the second RRC reconfiguration message, and forwards the Secondary Cell Group Configuration RRC message to an IAB node that has placed it in the mrdc-SecondaryCellGroupConfig area of ​​the second RRC reconfiguration message. Therefore, after the IAB node receives the second RRC reconfiguration message by SRB1, it can obtain the RRC reconfiguration message and the first instruction information contained in the mrdc-SecondaryCellGroupConfig area, and thus the IAB node can determine that at least one IP address configuration carried by the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area is IP address information for a non-F1-terminating topology domain. The example of introducing the first instruction information into the second RRC reconfiguration message is the same as in 1) above, the difference being that when generating the second RRC reconfiguration message, it is not necessary to include the iab-IP-AddressConfigurationList-r16 information element regarding its own IP address configuration.

[0087] In some embodiments, after dual connection establishment is complete, the IP addresses of non-F1 terminated topology domains may be reconfigured during the IAB transmission transition management process and sent to the IAB node by the MN.

[0088] (i) Implicit instructions The first RRC reconfiguration message is an RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area, and since the IAB transmission transition management process does not support the SN generating secondary cell group configuration RRC messages, the first RRC reconfiguration message is generated by the first IAB donor on behalf of the second IAB donor and carried by the second RRC reconfiguration message transmitted by the first IAB donor. The IAB node receives the second RRC reconfiguration message transmitted by the first IAB donor via SRB1. The first RRC reconfiguration message includes at least one IP address setting for the IAB node, the at least one IP address setting includes IP address information for a non-F1 terminated topology domain, where the IP address for the non-F1 terminated topology domain refers to an IP address anchored to donor-DU2.

[0089] For example, SN provides at least one IP address configuration and sends it to MN in an IAB transmission transition management response message. After 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 to the IAB node in a second RRC reconfiguration message. Thus, after the IAB node receives the second RRC reconfiguration message by SRB1, it can obtain the RRC reconfiguration message contained within the mrdc-SecondaryCellGroupConfig area. The IAB node knows that at least one IP address configuration in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area is provided by SN. Furthermore, since SN is non-F1 terminated, the IAB node can determine that the at least one IP address configuration carried by the second cell group configuration RRC message is IP address information for a non-F1 terminated topology domain. In other words, the IAB node can determine that at least one IP address setting in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area received by SRB1 contains IP address information for a non-F1 terminated topology domain.

[0090] (ii) explicit instructions The SN provides the MN with at least one IP address configuration, 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 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 for a non-F1 terminated topology domain, where the IP address for the non-F1 terminated topology domain refers to an IP address anchored to donor-DU2.

[0091] For example, SN can provide at least one IP address configuration and send it to MN in an IAB transmission transition management response message. After receiving at least one IP address configuration, MN can generate a first RRC reconfiguration message, introducing a new information element, namely the first instruction information "non-F1-terminating," and send the first RRC reconfiguration message to the IAB node. After the IAB node receives the first RRC reconfiguration message via SRB1, it can obtain at least one IP address information and the first instruction information carried within it. Therefore, the IAB node can determine that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information for a non-F1-terminating topology domain. The example of introducing the first instruction information into the first RRC reconfiguration message is the same as described in 1)-4) above, and a detailed explanation is omitted here.

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

[0093] (i) Implicit instructions For example, the IAB node receives the first RRC reconfiguration message by SRB3, and the IAB node knows that the first RRC reconfiguration message is generated by SN (i.e., at least one IP address configuration is provided by SN), and since SN 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 for a non-F1 terminated topology domain. In other words, the IAB node can determine that the at least one IP address configuration in the first RRC reconfiguration message received by SRB1 contains IP address information for a non-F1 terminated topology domain.

[0094] (ii) explicit instructions For example, when the SN generates the first RRC reconfiguration message, it introduces a new information element, namely the first instruction information "non-F1-terminating," and the IAB node can receive the first RRC reconfiguration message and the first instruction information within it via the SRB3. Thus, the IAB node can determine that at least one IP address configuration carried by the first RRC reconfiguration message is IP address information for a non-F1 terminated topology domain. The example of the first RRC reconfiguration message is the same as described in 1)-4) above, and a detailed explanation is omitted here.

[0095] In some embodiments, after dual connection establishment is complete, the IP address of the F1 termination topology domain can be set (changed) during the secondary recell group change process. The first RRC reconfiguration message is generated by 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 setting for the IAB node, which includes IP address information for the F1 termination topology domain, where the IP address of the F1 termination topology domain refers to the IP address anchored to donor-DU1.

[0096] (i) Implicit instructions For example, the IAB node receives the first RRC reconfiguration message from SRB1, and the IAB node knows that the first RRC reconfiguration message is generated by MN (i.e., at least one IP address configuration is provided by MN), and since MN is 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 for an F1 termination topology domain. In other words, the IAB node can determine that the at least one IP address configuration in the first RRC reconfiguration message received by SRB1 contains IP address information for an F1 termination topology domain.

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

[0098] (3) Dual Connection Scenario 2 In some embodiments, Figure 13 shows a dual connection scenario 2. As shown in Figure 13, in dual connection scenario 2, the first IAB donor (F1-terminated donor) is the secondary node SN of the IAB node, and the second IAB donor (non-F1-terminated donor) is the main node MN of the IAB node. After the dual connection is established, some operations of the boundary node can be moved to the non-F1-terminated topology domain, while some operations remain in the F1-terminated donor topology domain. The IP address of the non-F1-terminated topology domain refers to the IP address anchored to donor-DU1, and the IP address of the F1-terminated topology domain refers to the IP address anchored to donor-DU2. The difference from dual connection scenario 1 is that the IP address of the non-F1-terminated topology domain cannot be set during the dual connection establishment process, and the IP address of the non-F1-terminated topology domain or the IP address of the F1-terminated topology domain can only be set after the dual connection is established. In the case of an implicit instruction, the IAB node can determine that the at least one IP address setting in the RRC message received by SRB1 includes IP address information for a non-F1 terminating topology domain, or that the at least one IP address setting in the secondary recell group setting information received by SRB1 includes IP address information for an F1 terminating topology domain, or that the at least one IP address setting in the RRC message received by SRB3 includes IP address information for an F1 terminating topology domain. In the case of an explicit instruction, the IAB node can determine that the at least one IP address setting in the first RRC reconfiguration message includes IP address information for a non-F1 terminating topology domain when it receives first instruction information, and can determine that the at least one IP address setting in the first RRC reconfiguration message includes IP address information for an F1 terminating topology domain when it does not receive first instruction information. Each of these will be explained below.

[0099] In some embodiments, the IP address of a non-F1 terminated topology domain can be set (changed) after the dual connection is established. The first RRC reconfiguration message is sent by the second IAB donor to the IAB node, which 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 setting for the IAB node, which includes IP address information for a non-F1 terminated topology domain, where the IP address of the non-F1 terminated topology domain refers to an IP address anchored to donor-DU1.

[0100] (i) Implicit 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 MN (i.e., 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 for a non-F1 terminated topology domain. In other words, the IAB node can determine that the at least one IP address configuration in the first RRC reconfiguration message received by SRB1 contains IP address information for a non-F1 terminated topology domain.

[0101] (ii) explicit instructions For example, when the MN generates the first RRC reconfiguration message, it introduces a new information element, namely the first instruction information "non-F1-terminating," and the IAB node can receive the first RRC reconfiguration message and the first instruction information within it via the SRB1. As a result, the IAB node can determine that at least one IP address configuration carried by the first RRC reconfiguration message is IP address information for a non-F1 terminated topology domain. The example of introducing the first instruction information into the first RRC reconfiguration message is the same as described in 1)-4) above, and a detailed explanation is omitted here.

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

[0103] (i) Implicit instructions For example, the IAB node receives the first RRC reconfiguration message from SRB3, and the IAB node knows that the first RRC reconfiguration message is generated by SN (i.e., at least one IP address setting is provided by SN), and since SN is F1 termination, the IAB node can determine that the at least one IP address setting carried by the first RRC reconfiguration message is IP address information for an F1 termination topology domain. In other words, the IAB node can determine that the at least one IP address setting in the first RRC reconfiguration message received by SRB3 contains IP address information for an F1 termination topology domain.

[0104] (ii) explicit instructions For example, when the SN generates the first RRC reconfiguration message, there is no need to introduce a new information element, namely the first instruction information non-F1-terminating, and the IAB node receives the first RRC reconfiguration message by the SRB3, and the IAB node does not receive the first instruction information, so it can be determined that at least one IP address setting in the first RRC reconfiguration message received by the SRB3 contains IP address information for an F1-terminating topology domain.

[0105] In some embodiments, after dual connection establishment is complete, the IP address of the F1 termination topology domain can be set (changed) during the secondary cell group change process. The first RRC reconfiguration message is an RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area of ​​the RRC reconfiguration message, is entirely generated by the 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 SRB1. The first RRC reconfiguration message includes at least one IP address setting for the IAB node, and the at least one IP address setting includes IP address information for the F1 termination topology domain, where the IP address of the F1 termination topology domain refers to the IP address anchored to donor-DU2.

[0106] (i) Implicit instructions For example, SN generates a Secondary Cell Group Configuration RRC message, includes it in a Secondary Cell Group Change Request message, and sends it to MN. After MN sends the Secondary Cell Group Configuration RRC message sent by SN, it generates a third RRC reconfiguration message, includes the Secondary Cell Group Configuration RRC message in the mrdc-SecondaryCellGroupConfig area of ​​the third RRC reconfiguration message, and forwards it to the IAB node. Thus, after the IAB node receives the third RRC reconfiguration message from SRB1, it can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area carried therein. The IAB node knows that the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area is generated by SN (i.e., at least one IP address configuration is provided by SN), and since SN is F1 terminated, the IAB node can determine that the at least one IP address configuration carried by the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area is IP address information for an F1 terminated topology domain. In other words, the IAB node can determine that at least one IP address setting in the secondary cell group configuration RRC message received by SRB1 contains IP address information for an F1 termination topology domain.

[0107] (ii) explicit instructions For example, when SN generates a Secondary Cell Group Configuration RRC message, it does not need to introduce a new information element, namely the first instruction information non-F1-terminating, and instead includes the Secondary Cell Group Configuration RRC message in a Secondary Cell Group Change Request message and sends it to MN. After MN sends the Secondary Cell Group Configuration RRC message transmitted by SN, it generates a third RRC reconfiguration message and forwards the Secondary Cell Group Configuration RRC message to the IAB node by including it in the mrdc-SecondaryCellGroupConfig area of ​​the third RRC reconfiguration message. Therefore, after the IAB node receives the third RRC reconfiguration message from SRB1, it can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area carried therein. However, neither the first RRC reconfiguration message nor the third RRC reconfiguration message contains the first instruction information; that is, the IAB node does not receive the first instruction information. Thus, 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 for an F1 termination topology domain.

[0108] In some embodiments, after dual connection establishment is complete, the IP address of a non-F1 terminated topology domain can be set (changed) during the 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 the 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 setting for the IAB node, and the at least one IP address setting includes IP address information for a non-F1 terminated topology domain, where the IP address of the non-F1 terminated topology domain refers to an IP address anchored to donor-DU1.

[0109] (i) Implicit instructions For example, SN sends an IAB transmission transition management request message to MN, and MN (second IAB donor, non-F1 terminating donor) generates a first RRC reconfiguration message after receiving the request message, in which at least one IP address setting includes IP address information for a non-F1 terminating topology domain, and then sends the first RRC reconfiguration message to the IAB node. Thus, after the IAB node receives the first RRC reconfiguration message by SRB1, it can obtain at least one IP address setting carried therein, the IAB node knows that at least one IP address setting is provided by MN, and since MN is non-F1 terminating, the IAB node can determine that at least one IP address setting carried by the first RRC reconfiguration message is IP address information for a non-F1 terminating topology domain. In other words, the IAB node can determine that at least one IP address setting in the first RRC reconfiguration message received by SRB1 includes IP address information for a non-F1 terminating topology domain.

[0110] (ii) explicit instructions For example, SN can send an IAB transmission transition management request message to MN, and MN (second IAB donor, non-F1-terminating donor) can generate a first RRC reconfiguration message after receiving the request message, introducing a new information element, namely the first instruction information non-F1-terminating, and send the first RRC reconfiguration message to the IAB node. As a result, after the IAB node receives the first RRC reconfiguration message via SRB1, it can obtain at least one IP address information and the first instruction information carried within it, and thus the IAB node can determine that the at least one IP address setting carried by the first RRC reconfiguration message is IP address information for a non-F1-terminating topology domain. The example of introducing the first instruction information into the first RRC reconfiguration message is the same as described in 1)-4) above, and a detailed explanation is omitted here.

[0111] In some embodiments, after dual connection establishment is complete, the IP address of the F1 termination topology domain can be set (changed) during the 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 the 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 setting for the IAB node, and the at least one IP address setting includes IP address information for the F1 termination topology domain, where the IP address of the F1 termination topology domain refers to the IP address anchored to donor-DU2.

[0112] (i) Implicit instructions For example, SN provides at least one IP address configuration (including IP address information for an F1 termination topology domain) and sends it to MN (second IAB donor, non-F1 termination donor) in an IAB transmission transition change request message. After receiving the request message, MN generates a Secondary Cell Configuration RRC message on behalf of SN, in which at least one IP address configuration includes IP address information for an F1 termination topology domain. It also generates a third RRC reconfiguration message, places the first RRC reconfiguration message in the mrdc-SecondaryCellGroupConfig area of ​​the third RRC reconfiguration message, and forwards it to the IAB node. Therefore, after the IAB node receives the third RRC reconfiguration message by SRB1, it can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area carried therein, and the IAB node knows that at least one IP address setting in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area is provided by SN, and since SN is an F1 termination donor, the IAB node can determine that at least one IP address setting carried by the first RRC reconfiguration message is IP address information for an F1 termination topology domain. In other words, the IAB node can determine that at least one IP address setting in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig area of ​​the first RRC reconfiguration message received by SRB1 contains IP address information for an F1 termination topology domain.

[0113] (ii) explicit instructions SN provides at least one IP address configuration (including IP address information for an F1-terminated topology domain) and sends it to MN (second IAB donor, non-F1-terminated donor) in an IAB transmission transition change request message. After receiving the request message, MN generates a first RRC reconfiguration message in which at least one IP address configuration includes IP address information for an F1-terminated topology domain. However, it is not necessary to introduce first instruction information into the first RRC reconfiguration message, and the first RRC reconfiguration message does not contain first instruction information, i.e., the IAB node does not receive first instruction information. Therefore, the IAB node can determine that the at least one IP address configuration carried by the RRC message is IP address information for an F1-terminated topology domain.

[0114] The above explains how to configure and specify IP addresses for non-F1 terminated topology domains or F1 terminated topology domains, and how an IAB node can distinguish whether the configured IP address is for a non-F1 terminated topology domain or an F1 terminated topology domain. In the above embodiment, the IAB node can know whether MN or SN is an F1 terminated donor or a non-F1 terminated donor. For example, the IAB node can determine that MN or SN is an F1 terminated donor based on which donor provides the received BAP configuration information (bap-config-r16 area).

[0115] The explicit instructions described above illustrate how to determine whether the configured IP address is in a non-F1 terminating topology domain or an F1 terminating topology domain, using the reception of the first instruction information as an example. However, the present invention is not limited thereto. For example, the first instruction information may be used to indicate whether the IP address configuration includes IP address information in a non-F1 terminating topology domain, or to indicate whether the IP address configuration includes IP address information in a non-F1 terminating topology domain or IP address information in an F1 terminating 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), it may determine that the IP address configuration includes IP address information in a non-F1 terminating topology domain, and when the value of the first instruction information is a second value (false or 0), it may determine that the IP address configuration includes IP address information in an F1 terminating topology domain. However, the specific flow is the same as described above, and a detailed explanation is omitted here.

[0116] The signaling process described above is for illustrative purposes to illustrate embodiments of the present invention, but the present invention is not limited thereto, and further reference to related technologies can be made for more specific details of signaling. Furthermore, for example, the execution order between each operation can be appropriately adjusted, or several other operations can be added or removed. Those skilled in the art can make appropriate modifications based on the above description, not limited to those shown in the drawings.

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

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

[0119] <Example of the second aspect> An embodiment of the present invention provides a method for determining a transmission address, and this will be explained from the perspective of the first IAB donor. Note that the same information as in the embodiment described in the first aspect will be omitted here.

[0120] Figure 14 shows another transmission address determination method in an embodiment of the present invention. As shown in Figure 14, the method includes the following steps.

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

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

[0123] In some embodiments, it may be implicitly indicated whether the configured IP address belongs to a non-F1 terminating topology domain, or it may be explicitly indicated whether the configured IP address belongs to a non-F1 terminating topology domain. For example, the first IAB donor indicates by first instruction information that the IP address configuration includes IP address information for an F1 terminating topology domain or includes IP address information for a non-F1 terminating topology domain.

[0124] In some embodiments, the IP address configuration includes IP address information for non-F1 terminated topology domains.

[0125] In some embodiments, the first IAB donor is the source donor for the IAB node switchover, the second IAB donor is the target donor for the IAB node switchover, the first RRC reset message is a switchover command RRC message, and the method may further include the first IAB donor receiving the first RRC reset message transmitted by the second IAB donor, and in 1401, the first IAB donor forwards the first RRC reset message generated by the second IAB donor to the IAB node.

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

[0127] For example, the first RRC reset message is an RRC reset message included in the secondary recell group setting area of ​​the RRC reset message, and is carried by a second RRC reset message sent by the first IAB donor, and the first IAB donor sends the second RRC reset message to the IAB node via SRB1.

[0128] The method further includes the following: the first IAB donor receives the first RRC reconfiguration message transmitted by the second IAB donor (the first RRC reconfiguration message is generated by the second IAB donor). Also, at 1401, the first IAB donor transmits the second RRC reconfiguration message (the second RRC reconfiguration message is generated by the first IAB donor) to the IAB node via SRB1, and the second RRC reconfiguration message carries the first RRC reconfiguration message.

[0129] Alternatively, the method may further include the following: the first IAB donor receives the IP address configuration provided by the second IAB donor, 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 (which is also generated by the first IAB donor) to the IAB node via SRB1, with the second RRC reconfiguration message carrying the first RRC reconfiguration message.

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

[0131] In the embodiment described above, the IP address setting includes IP address information for a non-F1 termination topology domain, and in the case of an explicit instruction, the first IAB donor indicates that the IP address setting includes IP address information for a non-F1 termination topology domain by including the first instruction information in the first RRC reconfiguration message or the second RRC reconfiguration message. 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 in the IP address setting list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or in the IP address setting 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 for the F1 termination topology domain.

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

[0134] For example, in 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 reset message to the second IAB donor, and the first RRC reset message is a second recell group setting RRC message.

[0136] For example, in 1401, the first IAB donor transmits the IP address configuration to the second IAB donor, and the IP address configuration is carried by an IAB transmission transition change request message.

[0137] In some embodiments, the first IAB donor is the main node MN of the IAB node, and the second IAB donor is the 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 embodiment described above, the IP address setting includes IP address information for the F1 termination topology domain. When an explicit instruction is given, the first IAB donor indicates that the IP address setting includes IP address information for the F1 termination topology domain by not including the first instruction information in the first RRC reconfiguration message.

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

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

[0142] <Example of the third side> An embodiment of the present invention provides a method for determining a transmission address, which will be explained from the perspective of the second IAB donor.

[0143] Figure 15 shows a method for determining a transmission address in an embodiment of the present invention. As shown in Figure 15, the method includes the following steps.

[0144] 1501: The second IAB donor sends a first RRC reconfiguration message, which includes at least one IP address setting for an IAB node; or sends at least one IP address setting for an IAB node; The at least one IP address configuration includes IP address information for an F1-terminated topology domain, or includes IP address information for a non-F1-terminated 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 F1 connection of the IAB node is terminated at the first IAB donor, and the IAB node has an RRC connection with the second IAB donor.

[0146] In some embodiments, it may be implicitly indicated whether the configured IP address belongs to a non-F1 terminating topology domain, or it may be explicitly indicated whether the configured IP address belongs to a non-F1 terminating topology domain. For example, the second IAB donor indicates by the first instruction information that the IP address configuration includes IP address information for an F1 terminating topology domain or includes IP address information for a non-F1 terminating topology domain.

[0147] In some embodiments, the IP address configuration includes IP address information for non-F1 terminated topology domains.

[0148] In some embodiments, the first IAB donor is the source donor for the IAB node switchover, the second IAB donor is the target donor for the IAB node switchover, the first RRC reset message is a switchover command RRC message, and in 1501, the second IAB donor sends the first RRC reset message to the first IAB donor.

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

[0150] For example, in 1501, the second IAB donor sends the first RRC reset message to the first IAB donor; or For example, in 1501, the second IAB donor sends the IP address setting to the first IAB donor.

[0151] For example, in 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 the main node MN of the IAB node, and the first IAB donor is the secondary node SN of the IAB node.

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

[0154] In the embodiment described above, when the IP address setting includes IP address information for a non-F1 terminating topology domain and is explicitly indicated, the second IAB donor indicates that the IP address setting includes IP address information for a non-F1 terminating topology domain by including the first instruction information in the first RRC reconfiguration message. The first instruction information is included in the newly added information element of the first RRC reconfiguration message, or in the IP address setting list information element of the first RRC reconfiguration message, or in the IP address setting information element of the first RRC reconfiguration message, or in the IP address index information element of the first RRC reconfiguration message.

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

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

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

[0158] The method further includes the following: the second IAB donor receives the first RRC reset message transmitted by the first IAB donor.

[0159] For example, in 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 following: the second IAB donor receives the IP address configuration sent by the first IAB donor, and in 1501, the second IAB donor sends the first RRC reconfiguration message to the IAB node via SRB1.

[0161] In the embodiment described above, the IP address setting includes IP address information for the F1 termination topology domain. When an explicit instruction is given, the first IAB donor indicates that the IP address setting includes IP address information for the F1 termination topology domain by not including the first instruction information in the first RRC reconfiguration message or the third RRC reconfiguration message.

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

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

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

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

[0166] Figure 16 shows an IAB node device in an embodiment of the present invention. As shown in Figure 16, the IAB node device 1600 includes the following:

[0167] First receiving unit 1601: Receives a first RRC reconfiguration message, which includes at least one IP address setting for the IAB node.

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

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

[0170] In some embodiments, the apparatus further includes the following:

[0171] First processing unit 1602: Determines that the IP address setting includes IP address information for an F1-terminated topology domain or IP address information for a non-F1-terminated topology domain.

[0172] In some embodiments, the first processing unit determines, based on the first instruction information, that the IP address setting includes IP address information for an F1-terminated topology domain or IP address information for a non-F1-terminated topology domain.

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

[0174] In some embodiments, the first IAB donor is the source donor for the IAB node switchover, the second IAB donor is the target donor for the IAB node switchover, and the first RRC reset message is a switchover 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 the main node MN of the IAB node, and the second IAB donor is the secondary node SN of the IAB node.

[0176] For example, the first RRC reset message is an RRC reset message included in the secondary recell group setting area of ​​the RRC reset message and is carried by a second RRC reset message transmitted by the first IAB donor, and the first receiver receives the second RRC reset message transmitted by the first IAB donor via SRB1. Optionally, the first RRC reset message may be generated by the first IAB donor on behalf of the second IAB donor.

[0177] For example, the first receiving unit receives the first RRC reconfiguration message transmitted by the second IAB donor via SRB3.

[0178] For example, the first receiving unit receives the first RRC reconfiguration message transmitted by the first IAB donor via SRB1.

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

[0180] In some embodiments, the first processing unit determines that the IP address setting includes IP address information for a non-F1 termination topology domain when the first instruction information is included in the first RRC reconfiguration message or the second RRC reconfiguration message. 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 in the IP address setting list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or in the IP address setting information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or in the 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 setting includes IP address information for an F1-terminating topology domain.

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

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

[0184] For example, the first RRC reset message is an RRC reset message included in the secondary recell group setting area of ​​the RRC reset message and is carried by a third RRC reset message transmitted by the second IAB donor, and the first receiver receives the third RRC reset message transmitted by the second IAB donor via SRB1. Optionally, the first RRC reset message is generated by the second IAB donor on behalf of the first IAB donor.

[0185] For example, the first receiving unit receives the first RRC reconfiguration message transmitted by the first IAB donor via SRB3.

[0186] For example, the first receiving unit receives the first RRC reconfiguration message transmitted by the second IAB donor via SRB1.

[0187] In some embodiments, the first processing unit determines that the IP address setting includes IP address information for an F1 termination topology domain when the first RRC reconfiguration message or the third RRC reconfiguration message does not contain the first instruction information.

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

[0189] Although the various components or modules relating to the present invention have been described above, the present invention is not limited to these. The IAB node device 1600 in the embodiments of the present invention may include other components or modules, and the specific details of these components or modules should be referred to related technologies.

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

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

[0192] <Example of the fifth side> In embodiments of the present invention, an IAB donor device is provided, and the same description as in the embodiments of the second aspect is 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] Figure 17 shows an IAB donor device in an embodiment of the present invention. As shown in Figure 17, the IAB donor device 1700 includes the following:

[0194] First transmission unit 1701: Sends a first RRC reconfiguration message, which includes at least one IP address setting for an IAB node; or sends at least one IP address setting for an IAB node.

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

[0196] In some embodiments, the IAB donor device indicates by first instruction information whether the IP address setting includes IP address information for an F1-terminated topology domain or IP address information for a non-F1-terminated topology domain.

[0197] In some embodiments, the IP address configuration includes IP address information for non-F1 terminated topology domains.

[0198] In some embodiments, the first IAB donor is the source donor for the IAB node switchover, the second IAB donor is the target donor for the IAB node switchover, and the first RRC reset message is a switchover command RRC message.

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

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

[0201] For example, the first RRC reset message is an RRC reset message included in the secondary recell group setting area of ​​the RRC reset message, and is carried by the second RRC reset message sent by the first IAB donor, and the first transmitter sends the second RRC reset message to the IAB node via SRB1.

[0202] In some embodiments, the apparatus further includes the following (not shown), namely, Third receiving unit: Receives the first RRC reconfiguration message transmitted by the second IAB donor.

[0203] In some embodiments, the apparatus further includes the following (not shown), namely, Fourth receiving unit: receives the IP address settings provided by the second IAB donor; and Second processing unit: Generates the first RRC reconfiguration message in place of the second IAB donor.

[0204] In some embodiments, the apparatus further includes the following (not shown), namely, Fifth receiving unit: receives the IP address configuration provided by the second IAB donor, and the first transmitting unit transmits 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 for a non-F1 terminated topology domain by including the first RRC reconfiguration message or the second RRC reconfiguration message in the first instruction information.

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

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

[0208] For example, the first transmitting unit sends the first RRC reconfiguration message to the IAB node using SRB3.

[0209] For example, the first transmitting unit sends the first RRC reset message to the second IAB donor, of which the first RRC reset message is a secondary recell group setting RRC message; or The first transmission unit transmits the IP address settings to the second IAB donor.

[0210] In some embodiments, the first IAB donor is the main node MN of the IAB node, the second IAB donor is the secondary node SN of the IAB node, and the first transmitter transmits 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 for an F1 termination topology domain by not including the first RRC reconfiguration message.

[0212] In some embodiments, the first instruction information is included in a newly added information element of the first RRC reset message or the second RRC reset message, or in the IP address setting list information element of the first RRC reset message or the second RRC reset message, or in the IP address setting information element of the first RRC reset message or the second RRC reset message, or in the IP address index information element of the first RRC reset message or the second RRC reset message.

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

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

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

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

[0217] <Example of the sixth side view> In embodiments of the present invention, an IAB donor device is provided, and the same description as in the embodiment of the third aspect is 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 one or more parts, assemblies, or modules provided in the IAB donor-CU.

[0218] Figure 18 shows an IAB donor device in an embodiment of the present invention. As shown in Figure 18, the IAB donor device 1800 includes the following:

[0219] Second transmission unit 1801: Sends a first RRC reconfiguration message, which includes at least one IP address setting for an IAB node; or sends at least one IP address setting for an IAB node.

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

[0221] Of these, 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 by first instruction information whether the IP address setting includes IP address information for an F1-terminated topology domain or IP address information for a non-F1-terminated topology domain.

[0223] In some embodiments, the IP address configuration includes IP address information for non-F1 terminated topology domains.

[0224] In some embodiments, the first IAB donor is the source donor for the IAB node switching, the second IAB donor is the target donor for the IAB node switching, the first RRC reset message is a switching command RRC message, and the second transmission unit transmits the first RRC reset message to the first IAB donor.

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

[0226] For example, the second transmitting 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 transmitting unit sends the first RRC reconfiguration message to the IAB node via SRB3.

[0228] In some embodiments, the first IAB donor is the SN of the IAB node, the second IAB donor is the MN of the IAB node, and the second transmitter transmits 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 for a non-F1 terminated topology domain by including the first RRC reconfiguration message in the first instruction information.

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

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

[0232] For example, the first RRC reset message is an RRC reset message included in the secondary recell group setting area of ​​the RRC reset message, and is carried by the third RRC reset message sent by the second IAB donor, and the second transmitter sends the third RRC reset message to the IAB node via SRB1.

[0233] In some embodiments, the apparatus further includes the following (not shown), namely, Sixth receiver: Receives the first RRC reset message transmitted by the first IAB donor.

[0234] In some embodiments, the apparatus further includes the following (not shown), namely, Seventh receiving unit: receives the IP address settings provided by the first IAB donor; and Second processing unit: Generates the first RRC reconfiguration message on behalf of the first IAB donor.

[0235] In some embodiments, the apparatus further includes the following (not shown), namely, Eighth receiving unit: Receives the IP address configuration transmitted by the first IAB donor, and the second transmitting unit transmits 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 for an F1 termination topology domain by not including the first RRC reconfiguration message or the third RRC reconfiguration message.

[0237] In some embodiments, the first instruction information is included in a newly added information element of the first RRC reset message or the second RRC reset message, or in the IP address setting list information element of the first RRC reset message or the second RRC reset message, or in the IP address setting information element of the first RRC reset message or the second RRC reset message, or in the IP address index information element of the first RRC reset message or the second RRC reset message.

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

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

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

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

[0242] <Example of the seventh side view> Embodiments of the present invention provide a communication system which includes a first IAB donor device in the fourth embodiment, a second IAB donor device in the fifth embodiment, and an IAB node device in the third embodiment. Further references can be made to related technologies regarding the network architecture of the donor and IAB node devices, and a detailed description thereof is omitted here.

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

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

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

[0248] Furthermore, as shown in Figure 9, the IAB device 900 may also include a transceiver 903, an antenna 904, etc., and since the functions of the above-mentioned components are the same as in the prior art, a detailed explanation of them is omitted here. Note that the IAB device 900 does not need to include all the components shown in Figure 9. Also, the IAB device 900 may include components not shown in Figure 9, but for these, the prior art can be referred to.

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

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

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

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

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

[0254] Also, regarding the above-described embodiments, etc., the following additional remarks are disclosed.

[0255] <Boundary Node> (Appendix 1) A transmission address determination method, applied to access and backhaul IAB node devices, the method includes: the IAB node receiving a first RRC reconfiguration message, the first RRC reconfiguration message including at least one IP address setting for the IAB node, the at least one IP address setting including IP address information of an F1 terminated topology domain or IP address information of a non-F1 terminated topology domain. [[ID=Z17]]

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

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

[0258] (Appendix 4) The method according to Appendix 3, the IAB node determining, based on first indication information, that the IP address setting includes IP address information of an F1 terminated topology domain or IP address information of a non-F1 terminated topology domain.

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

[0260] (Note 6) The method described in Appendix 5, The first IAB donor is the source donor for the IAB node switchover, and the second IAB donor is the target donor for the IAB node switchover. The first RRC reset message is a switching command RRC message generated by the second IAB donor and forwarded by the first IAB donor, in this method.

[0261] (Note 7) The method described in Appendix 5, The first IAB donor is the main node MN of the IAB node, and the second IAB donor is the secondary node SN of the IAB node, in this method.

[0262] (Note 8) The method described in Appendix 7, The first RRC reset message is an RRC reset message included in the secondary recell group setting area within the RRC reset message, and is carried by the second RRC reset message transmitted by the first IAB donor. A method in which the IAB node receives the second RRC reconfiguration message transmitted by the first IAB donor via SRB1.

[0263] (Note 9) The method described in Appendix 8, The first RRC reset message is generated by the first IAB donor instead of the second IAB donor, in a manner that is appropriate.

[0264] (Note 10) The method described in Appendix 7, A method by which the IAB node receives the first RRC reconfiguration message transmitted by the second IAB donor via SRB3.

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

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

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

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

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

[0270] (Appendix 16) The method described in Appendix 11, A method wherein the first IAB donor is the SN of the IAB node, and the second IAB donor is the MN of the IAB node.

[0271] (Note 17) The method described in Appendix 16, The first RRC reset message is an RRC reset message included in the secondary recell setting area within the RRC reset message, and is carried by the third RRC reset message transmitted by the second IAB donor. A method by which the IAB node receives the third RRC reconfiguration message transmitted by the second IAB donor via SRB1.

[0272] (Note 18) The method described in Appendix 17, The first RRC reset message is generated by the second IAB donor instead of the first IAB donor, in a manner that is appropriate.

[0273] (Note 19) The method described in Appendix 16, A method in which the IAB node receives the first RRC reconfiguration message transmitted by the first IAB donor via SRB3.

[0274] (Note 20) The method described in Appendix 16, A method in which the IAB node receives the first RRC reconfiguration message transmitted by the second IAB donor via SRB1.

[0275] (Note 21) A method described in any one of the appendices 14 to 20, A method for determining that the IP address setting includes IP address information for an F1 termination topology domain when the IAB node does not include the first instruction information in the first RRC reconfiguration message or the third RRC reconfiguration message.

[0276] (Note 22) The method described in Appendix 13, A method wherein the first instruction information is included in the newly added information element of the first RRC reset message or the second RRC reset message, or is included in the IP address setting list information element of the first RRC reset message or the second RRC reset message, or is included in the IP address setting information element of the first RRC reset message or the second RRC reset message, or is included in the IP address index information element of the first RRC reset message or the second RRC reset message.

[0277] (Note 23) IAB node (donor) equipment, Including memory and processing units, The device wherein a computer program is stored in the memory, and the processing unit is configured to execute the computer program to realize the transmission address determination method described in any one of the appendices 1 to 22.

[0278] <First donor CU node side> (Note 1) A method for determining a transmission address, Applicable to the first IAB donor, the method described above is The first IAB donor sends a first RRC reconfiguration message, which includes at least one IP address setting for the IAB node; or This includes sending the IP address configuration of at least one of the aforementioned IAB nodes, The aforementioned at least one IP address setting includes IP address information for an F1-terminated topology domain, or includes IP address information for a non-F1-terminated topology domain. In this method, the F1 connection of the IAB node is terminated at the first IAB donor, and the IAB node has an RRC connection with the second IAB donor.

[0279] (Note 2) The method described in Appendix 1, A method by which the first IAB donor instructs, by first instruction information, that the IP address setting includes IP address information for an F1-terminated topology domain or includes IP address information for a non-F1-terminated topology domain.

[0280] (Note 3) The method described in Appendix 1 or 2, The aforementioned IP address configuration method includes IP address information for a non-F1 terminated topology domain.

[0281] (Note 4) The method described in Appendix 3, The first IAB donor is the source donor for the IAB node switchover, the second IAB donor is the target donor for the IAB node switchover, and the first RRC reset message is a switchover command RRC message. A method comprising the first IAB donor receiving a first RRC reconfiguration message transmitted by the second IAB donor, and forwarding the first RRC reconfiguration message generated by the second IAB donor to the IAB node.

[0282] (Note 5) The method described in Appendix 3, The first IAB donor is the main node MN of the IAB node, and the second IAB donor is the secondary node SN of the IAB node, in this method.

[0283] (Note 6) The method described in Appendix 5, The first RRC reset message is an RRC reset message included in the secondary recell group setting area within the RRC reset message, and is carried by the second RRC reset message transmitted by the first IAB donor. A method in which the first IAB donor sends the second RRC reconfiguration message to the IAB node via SRB1.

[0284] (Note 7) The method described in Appendix 6, The above method further, A method comprising the first IAB donor receiving the first RRC reconfiguration message transmitted by the second IAB donor.

[0285] (Note 8) The method described in Appendix 6, The above method further, A method comprising 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] (Note 9) The method described in Appendix 5, The above method further, A method comprising 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] (Note 10) A method described in any one of the appendices 3 to 9, A method by which the first IAB donor indicates that the IP address configuration includes IP address information for a non-F1 terminated topology domain, by including the first RRC reconfiguration message or the second RRC reconfiguration message in the first instruction information.

[0288] (Note 11) The method described in Appendix 1 or 2, The aforementioned IP address configuration is a method that includes IP address information for an F1 termination topology domain.

[0289] (Note 12) The method described in Appendix 11, A method wherein the first IAB donor is the SN of the IAB node, and the second IAB donor is the MN of the IAB node.

[0290] (Note 13) The method described in Appendix 12, A method in which the first IAB donor sends the first RRC reconfiguration message to the IAB node via SRB3.

[0291] (Note 14) The method described in Appendix 12, The first IAB donor sends the first RRC reset message to the second IAB donor, of which the first RRC reset message is a secondary recell group setting RRC message; or A method by which the first IAB donor transmits the IP address settings to the second IAB donor.

[0292] (Note 15) The method described in Appendix 11, The first IAB donor is the main node MN of the IAB node, and the second IAB donor is the secondary node SN of the IAB node. A method in which the first IAB donor sends the first RRC reconfiguration message to the IAB node via SRB1.

[0293] (Note 17) A method described in any one of the appendices 11 to 15, A method by which the first IAB donor indicates that the IP address configuration includes IP address information for an F1 termination topology domain by the first RRC reconfiguration message not including the first instruction information.

[0294] (Note 18) The method described in Appendix 10, A method wherein the first instruction information is included in the newly added information element of the first RRC reset message or the second RRC reset message, or is included in the IP address setting list information element of the first RRC reset message or the second RRC reset message, or is included in the IP address setting information element of the first RRC reset message or the second RRC reset message, or is included in the IP address index information element of the first RRC reset message or the second RRC reset message.

[0295] (Note 19) IAB donor device, Including memory and processing units, A device wherein a computer program is stored in the memory, and the processing unit is configured to execute the computer program to realize the transmission address determination method described in any one of the appendices 1 to 17.

[0296] <Second donor CU node side> (Note 1) A method for determining a transmission address, Applicable to the second IAB donor, the method is: The second IAB donor sends a first RRC reconfiguration message, which includes at least one IP address setting for the IAB node; or This includes sending at least one IP address configuration for the IAB node, The aforementioned at least one IP address setting includes IP address information for an F1-terminated topology domain, or includes IP address information for a non-F1-terminated topology domain. In this method, the F1 connection of the IAB node is terminated at the first IAB donor, and the IAB node has an RRC connection with the second IAB donor.

[0297] (Note 2) The method described in Appendix 1, A method by which the second IAB donor indicates, based on the first instruction information, that the IP address setting includes IP address information for an F1-terminated topology domain or includes IP address information for a non-F1-terminated topology domain.

[0298] (Note 3) The method described in Appendix 1 or 2, The aforementioned IP address configuration method includes IP address information for a non-F1 terminated topology domain.

[0299] (Note 4) The method described in Appendix 3, The first IAB donor is the source donor for the IAB node switchover, the second IAB donor is the target donor for the IAB node switchover, and the first RRC reset message is a switchover command RRC message. A method by which the second IAB donor sends the first RRC reset message to the first IAB donor.

[0300] (Note 5) The method described in Appendix 3, The first IAB donor is the main node MN of the IAB node, and the second IAB donor is the secondary node SN of the IAB node, in this method.

[0301] (Note 6) The method described in Appendix 5, A method in which 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] (Note 7) The method described in Appendix 5, A method in which the second IAB donor sends the first RRC reconfiguration message to the IAB node via SRB3.

[0303] (Note 8) The method described in Appendix 3, The first IAB donor is the SN of the IAB node, and the second IAB donor is the MN of the IAB node. A method in which the second IAB donor sends the first RRC reconfiguration message to the IAB node via SRB1.

[0304] (Note 9) A method described in any one of the appendices 3 to 8, A method by which the second IAB donor indicates that the IP address configuration includes IP address information for a non-F1 terminated topology domain, by including the first instruction information in the first RRC reconfiguration message.

[0305] (Note 10) The method described in Appendix 1 or 2, The aforementioned IP address configuration is a method that includes IP address information for an F1 termination topology domain.

[0306] (Note 11) The method described in Appendix 10, A method wherein the first IAB donor is the SN of the IAB node, and the second IAB donor is the MN of the IAB node.

[0307] (Note 12) The method described in Appendix 11, The first RRC reset message is an RRC reset message included in the secondary recell group setting area within the RRC reset message, and is carried by the third RRC reset message sent by the second IAB donor. A method in which the second IAB donor sends the third RRC reconfiguration message to the IAB node via SRB1.

[0308] (Note 13) The method described in Appendix 12, The above method further, A method by which the second IAB donor receives the first RRC reconfiguration message transmitted by the first IAB donor.

[0309] (Note 14) The method described in Appendix 12, A method comprising the second IAB donor receiving the IP address configuration provided by the first IAB donor and generating the first RRC reconfiguration message on behalf of the first IAB donor.

[0310] (Note 15) The method described in Appendix 11, The above method further, A method comprising the second IAB donor receiving the IP address configuration transmitted by the first IAB donor and sending the first RRC reconfiguration message to the IAB node via SRB1.

[0311] (Note 16) A method described in any one of the appendices 11 to 15, A method by which the second IAB donor indicates that the IP address configuration includes IP address information for an F1 termination topology domain by the first RRC reconfiguration message or the third RRC reconfiguration message not including the first instruction information.

[0312] (Note 17) The method described in Appendix 9, The first instruction information is included in the newly added information element of the first RRC reset message or the second RRC reset message, or included in the IP address setting list information element of the first RRC reset message or the second RRC reset message, or included in the IP address setting information element of the first RRC reset message or the second RRC reset message, or included in the IP address index information element of the first RRC reset message or the second RRC reset message.

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

[0314] <Boundary Node> (Note 1) IAB node equipment, The aforementioned device includes a first receiving unit, The first receiving unit receives the first RRC reset message, The first RRC reconfiguration message includes at least one IP address setting for the IAB node. A device in which the aforementioned at least one IP address configuration includes IP address information for an F1-terminated topology domain or includes IP address information for a non-F1-terminated topology domain.

[0315] (Note 2) The equipment described in Appendix 1, The F1 connection of the aforementioned IAB node is terminated at the first IAB donor, and the aforementioned IAB node has an RRC connection with the second IAB donor.

[0316] (Note 3) The equipment described in Appendix 2, The apparatus further includes a first processing unit, The first processing unit determines that the IP address setting includes IP address information for an F1-terminated topology domain or IP address information for a non-F1-terminated topology domain.

[0317] (Note 4) The equipment described in Appendix 3, The first processing unit determines, based on the first instruction information, that the IP address setting includes IP address information for an F1-terminated topology domain or IP address information for a non-F1-terminated topology domain.

[0318] (Note 5) The equipment described in Appendix 3 or 4, The first processing unit determines that the IP address setting includes IP address information for a non-F1-terminating topology domain.

[0319] (Note 6) The equipment described in Appendix 5, The first IAB donor is the source donor for the IAB node switchover, and the second IAB donor is the target donor for the IAB node switchover. The aforementioned first RRC reset message is a switching command RRC message generated by the second IAB donor and forwarded by the first IAB donor, according to the equipment.

[0320] (Note 7) The equipment described in Appendix 5, The equipment wherein the first IAB donor is the main node MN of the IAB node, and the second IAB donor is the secondary node SN of the IAB node.

[0321] (Note 8) The equipment described in Appendix 7, The first RRC reset message is an RRC reset message included in the secondary recell group setting area within the RRC reset message, and is carried by the second RRC reset message transmitted by the first IAB donor. The first receiving unit is a device that receives the second RRC reset message transmitted by the first IAB donor via SRB1.

[0322] (Note 9) The equipment described in Appendix 8, The first RRC reset message is generated by the first IAB donor instead of the second IAB donor, on the device.

[0323] (Note 10) The equipment described in Appendix 7, The first receiving unit is a device that receives the first RRC reset message transmitted by the second IAB donor via SRB3.

[0324] (Note 11) The equipment described in Appendix 7, The first receiving unit is a device that receives the first RRC reset message transmitted by the first IAB donor via SRB1.

[0325] (Note 12) The equipment described in Appendix 5, The first IAB donor is the SN of the IAB node, and the second IAB donor is the MN of the IAB node. The first receiving unit is a device that receives the first RRC reset message transmitted by the second IAB donor via SRB1.

[0326] (Note 13) The equipment described in any one of the appendices 5 to 12, The first processing unit determines that the IP address setting includes IP address information for a non-F1 termination topology domain when the first RRC reset message or the second RRC reset message includes the first instruction information.

[0327] (Note 14) The equipment described in Appendix 3 or 4, The first processing unit determines that the IP address setting includes IP address information for an F1-terminating topology domain.

[0328] (Note 15) The equipment described in Appendix 14, The first IAB donor is the main node MN of the IAB node, and the second IAB donor is the secondary node SN of the IAB node. The first receiving unit is a device that receives the first RRC reset message transmitted by the first IAB donor via SRB1.

[0329] (Note 16) The equipment described in Appendix 11, The first IAB donor is the SN of the IAB node, and the second IAB donor is the MN of the IAB node, in this device.

[0330] (Note 17) The equipment described in Appendix 16, The first RRC reset message is an RRC reset message included in the secondary recell setting area within the RRC reset message, and is carried by the third RRC reset message transmitted by the second IAB donor. The first receiving unit is a device that receives the third RRC reset message transmitted by the second IAB donor via SRB1.

[0331] (Note 18) The equipment described in Appendix 17, The first RRC reset message is generated by the second IAB donor instead of the first IAB donor.

[0332] (Note 19) The equipment described in Appendix 16, The first receiving unit is a device that receives the first RRC reset message transmitted by the first IAB donor via SRB3.

[0333] (Note 20) The equipment described in Appendix 16, The first receiving unit is a device that receives the first RRC reset message transmitted by the second IAB donor via SRB1.

[0334] (Note 21) The equipment described in any one of the appendices 14 to 20, The first processing unit determines that the IP address setting includes IP address information of an F1 termination topology domain when the first RRC reset message or the third RRC reset message does not include the first instruction information.

[0335] (Note 22) The equipment described in Appendix 13, The first instruction information is included in the newly added information element of the first RRC reset message or the second RRC reset message, or is included in the IP address setting list information element of the first RRC reset message or the second RRC reset message, or is included in the IP address setting information element of the first RRC reset message or the second RRC reset message, or is included in the IP address index information element of the first RRC reset message or the second RRC reset message, and is included in the device.

[0336] <First donor CU node side> (Note 1) IAB donor device, Applicable to the first IAB donor, the equipment includes a first transmitting unit, The first transmission unit transmits a first RRC reconfiguration message, the first RRC reconfiguration message includes at least one IP address setting for the IAB node; or transmits at least one IP address setting for the IAB node. The aforementioned at least one IP address setting includes IP address information for an F1-terminated topology domain, or includes IP address information for a non-F1-terminated topology domain. Among these, the F1 connection of the IAB node is terminated at the first IAB donor, and the IAB node has an RRC connection with the second IAB donor.

[0337] (Note 2) The equipment described in Appendix 1, The IAB donor device is a device that, by first instruction information, instructs that the IP address setting includes IP address information for an F1-terminated topology domain or includes IP address information for a non-F1-terminated topology domain.

[0338] (Note 3) The equipment described in Appendix 1 or 2, The aforementioned IP address configuration includes IP address information for a non-F1 terminated topology domain of the device.

[0339] (Note 4) The equipment described in Appendix 3, The first IAB donor is the source donor for the IAB node switchover, the second IAB donor is the target donor for the IAB node switchover, and the first RRC reset message is a switchover command RRC message. The device further includes a second receiving unit which receives a first RRC reset message transmitted by the second IAB donor, and the first transmitting unit which forwards the first RRC reset message generated by the second IAB donor to the IAB node.

[0340] (Note 5) The equipment described in Appendix 3, The equipment wherein the first IAB donor is the main node MN of the IAB node, and the second IAB donor is the secondary node SN of the IAB node.

[0341] (Note 6) The equipment described in Appendix 5, The first RRC reset message is an RRC reset message included in the secondary recell setting area within the RRC reset message, and is carried by the second RRC reset message transmitted by the first IAB donor. The first transmitting unit is a device that transmits the second RRC reset message to the IAB node using SRB1.

[0342] (Note 7) The equipment described in Appendix 6, The device further includes a third receiving unit which receives the first RRC reset message transmitted by the second IAB donor.

[0343] (Note 8) The equipment described in Appendix 6, The aforementioned device further, A fourth receiving unit that receives the IP address settings provided by the second IAB donor; and A device including a second processing unit that generates the first RRC reset message in place of the second IAB donor.

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

[0345] (Note 10) Any equipment described in any one of the appendices 3 to 9, The IAB donor device is a device that indicates that the IP address configuration includes IP address information for a non-F1 terminated topology domain, by including the first RRC reconfiguration message or the second RRC reconfiguration message in the first instruction information.

[0346] (Note 11) The equipment described in Appendix 1 or 2, The aforementioned IP address configuration is a method that includes IP address information for an F1 termination topology domain.

[0347] (Note 12) The equipment described in Appendix 11, The first IAB donor is the SN of the IAB node, and the second IAB donor is the MN of the IAB node, in this device.

[0348] (Note 13) The equipment described in Appendix 12, The first transmitting unit is a device that transmits the first RRC reset message to the IAB node using SRB3.

[0349] (Note 14) The equipment described in Appendix 12, The first transmitting unit transmits the first RRC reset message to the second IAB donor, of which the first RRC reset message is a secondary reset RRC message; or The first transmitting unit is a device that transmits the IP address settings to the second IAB donor.

[0350] (Note 15) The equipment described in Appendix 11, The first IAB donor is the main node MN of the IAB node, and the second IAB donor is the secondary node SN of the IAB node. The first transmitting unit is a device that transmits the first RRC reset message to the IAB node using SRB1.

[0351] (Note 17) Any equipment described in any one of the appendices 11 to 15, The IAB donor device is a device that indicates that the IP address setting includes IP address information for an F1 termination topology domain, by the absence of the first RRC reconfiguration message from the first instruction information.

[0352] (Note 18) The equipment described in Appendix 10, The first instruction information is included in the newly added information element of the first RRC reset message or the second RRC reset message, or is included in the IP address setting list information element of the first RRC reset message or the second RRC reset message, or is included in the IP address setting information element of the first RRC reset message or the second RRC reset message, or is included in the IP address index information element of the first RRC reset message or the second RRC reset message, and is included in the device.

[0353] <Second donor CU node side> (Note 1) IAB donor device, Applicable to the second IAB donor, The device includes a second transmitting unit which transmits a first RRC reconfiguration message which includes at least one IP address setting for an IAB node; or transmits at least one IP address setting for an IAB node, The aforementioned at least one IP address setting includes IP address information for an F1-terminated topology domain, or includes IP address information for a non-F1-terminated topology domain. Among these, the F1 connection of the IAB node is terminated at the first IAB donor, and the IAB node has an RRC connection with the second IAB donor.

[0354] (Note 2) The equipment described in Appendix 1, The IAB donor device is a device that, by first instruction information, instructs that the IP address setting includes IP address information for an F1-terminated topology domain or includes IP address information for a non-F1-terminated topology domain.

[0355] (Note 3) The equipment described in Appendix 1 or 2, The aforementioned IP address configuration includes IP address information for a non-F1 terminated topology domain of the device.

[0356] (Note 4) The equipment described in Appendix 3, The first IAB donor is the source donor for the IAB node switchover, the second IAB donor is the target donor for the IAB node switchover, and the first RRC reset message is a switchover command RRC message. The second transmitting unit is a device that transmits the first RRC reset message to the first IAB donor.

[0357] (Note 5) The equipment described in Appendix 3, The equipment wherein the first IAB donor is the main node MN of the IAB node, and the second IAB donor is the secondary node SN of the IAB node.

[0358] (Note 6) The equipment described in Appendix 5, The device wherein the second transmitting unit transmits a first RRC reconfiguration message to the first IAB donor; or transmits the IP address setting to the first IAB donor.

[0359] (Note 7) The equipment described in Appendix 5, The second transmitting unit is a device that transmits the first RRC reconfiguration message to the IAB node using SRB3.

[0360] (Note 8) The equipment described in Appendix 3, The first IAB donor is the SN of the IAB node, and the second IAB donor is the MN of the IAB node. The second transmitting unit is a device that transmits the first RRC reconfiguration message to the IAB node using SRB1.

[0361] (Note 9) Any equipment described in any one of the appendices 3 to 8, The IAB donor device is a device that, by including the first RRC reconfiguration message, indicates that the IP address configuration includes IP address information for a non-F1 terminated topology domain.

[0362] (Note 10) The equipment described in Appendix 1 or 2, The aforementioned IP address configuration includes IP address information for the F1 termination topology domain of the device.

[0363] (Note 11) The equipment described in Appendix 10, The first IAB donor is the SN of the IAB node, and the second IAB donor is the MN of the IAB node, in this device.

[0364] (Note 12) The equipment described in Appendix 11, The first RRC reset message is an RRC reset message included in the secondary recell setting area within the RRC reset message, and is carried by the third RRC reset message transmitted by the second IAB donor. The second transmitting unit is a device that transmits the third RRC reset message to the IAB node using SRB1.

[0365] (Note 13) The equipment described in Appendix 12, The apparatus further includes a sixth receiving unit which receives a first RRC reconfiguration message transmitted by the first IAB donor.

[0366] (Note 14) The equipment described in Appendix 12, The device further includes a seventh receiving unit, which receives the IP address configuration provided by the first IAB donor. The device further includes a third processing unit which generates the first RRC reset message on behalf of the first IAB donor.

[0367] (Note 15) The equipment described in Appendix 11, The device further includes an eighth receiving unit which receives the IP address configuration transmitted by the first IAB donor, and the second transmitting unit which transmits the first RRC reconfiguration message to the IAB node via SRB1.

[0368] (Note 16) Any equipment described in any one of the appendices 11 to 15, A method by which the IAB donor device indicates that the IP address setting includes IP address information for an F1 termination topology domain by the first RRC reconfiguration message or the third RRC reconfiguration message not including the first instruction information.

[0369] (Note 17) The equipment described in Appendix 9, The first instruction information is included in the newly added information element of the first RRC reset message or the second RRC reset message, or included in the IP address setting list information element of the first RRC reset message or the second RRC reset message, or included in the IP address setting information element of the first RRC reset message or the second RRC reset message, or included in the IP address index information element of the first RRC reset message or the second RRC reset message.

Claims

1. It is an IAB (integrated access and backhaul) node, Including the receiver, The receiver receives the first RRC reset message. The first RRC reconfiguration message includes IP address information for the F1 termination topology domain for the IAB node. The IP address information for the F1 termination topology domain of the aforementioned IAB node is: The IAB node includes a TNL address anchored to a donor DU (donor-DU) under an F1-terminated donor CU; or This includes IP address information for non-F1 terminated topology domains for the aforementioned IAB node, The IP address information for the non-F1 terminated topology domain for the IAB node includes the TNL address of the IAB node that is anchored to the donor DU (donor-DU) under the non-F1 terminated donor CU. The F1 connection of the IAB node is terminated at the first IAB donor CU, and the IAB node has an RRC connection with the second IAB donor CU. The first IAB donor CU is the MN of the IAB node, and the second IAB donor CU is the SN of the IAB node. The first RRC reset message is an RRC reset message included in the secondary recell group setting area of ​​the RRC reset message, and is carried by the second RRC reset message. The receiver is an IAB node that receives the second RRC reset message via SRB1.

2. It is an IAB (integrated access and backhaul) node, Including the receiver, The receiver receives the first RRC reset message. The first RRC reconfiguration message includes IP address information for the F1 termination topology domain for the IAB node. The IP address information for the F1 termination topology domain of the aforementioned IAB node is: The IAB node includes a TNL address anchored to a donor DU (donor-DU) under an F1-terminated donor CU; or This includes IP address information for non-F1 terminated topology domains for the aforementioned IAB node, The IP address information for the non-F1 terminated topology domain for the IAB node includes the TNL address of the IAB node that is anchored to the donor DU (donor-DU) under the non-F1 terminated donor CU. The F1 connection of the IAB node is terminated at the first IAB donor CU, and the IAB node has an RRC connection with the second IAB donor CU. The first IAB donor CU is the MN of the IAB node, and the second IAB donor CU is the SN of the IAB node. The receiver is an IAB node that receives the first RRC reconfiguration message transmitted by the second IAB donor CU via SRB3.

3. It is an IAB (integrated access and backhaul) node, Including the receiver, The receiver receives the first RRC reset message. The first RRC reconfiguration message includes IP address information for the F1 termination topology domain for the IAB node. The IP address information for the F1 termination topology domain of the aforementioned IAB node is: The IAB node includes a TNL address anchored to a donor DU (donor-DU) under an F1-terminated donor CU; or This includes IP address information for non-F1 terminated topology domains for the aforementioned IAB node, The IP address information for the non-F1 terminated topology domain for the IAB node includes the TNL address of the IAB node that is anchored to the donor DU (donor-DU) under the non-F1 terminated donor CU. The F1 connection of the IAB node is terminated at the first IAB donor CU, and the IAB node has an RRC connection with the second IAB donor CU. The first IAB donor CU is the SN of the IAB node, and the second IAB donor CU is the MN of the IAB node. The receiver is an IAB node that receives the first RRC reconfiguration message transmitted by the second IAB donor CU via SRB1.

4. An IAB node according to claim 1, 2, or 3, Further including a processor, The processor is an IAB node that determines that the first RRC reset message includes IP address information for an F1-terminated topology domain or IP address information for a non-F1-terminated topology domain.

5. IAB (integrated access and backhaul) donor device applicable to the first IAB donor CU, Including the transmitter, The transmitter sends the first RRC reset message, The aforementioned first RRC reconfiguration message includes IP address information for the F1 termination topology domain for the IAB node. The IP address information for the F1 termination topology domain of the aforementioned IAB node is: The IAB node includes a TNL address anchored to a donor DU (donor-DU) under an F1-terminated donor CU; or This includes IP address information for non-F1 terminated topology domains for the aforementioned IAB node, The IP address information for the non-F1 terminated topology domain for the IAB node includes the TNL address of the IAB node that is anchored to the donor DU (donor-DU) under the non-F1 terminated donor CU. The F1 connection of the IAB node is terminated at the first IAB donor CU. The first IAB donor CU is the MN of the IAB node, the IAB node has an RRC connection with the second IAB donor CU, and the second IAB donor CU is the SN of the IAB node. The first RRC reset message is an RRC reset message included in the secondary recell group setting area of ​​the RRC reset message, and is carried by the second RRC reset message transmitted by the first IAB donor CU. The transmitter is an IAB donor device that transmits the second RRC reset message via SRB1.

6. IAB (integrated access and backhaul) donor devices applicable to the second IAB donor CU, Including the transmitter, The transmitter sends the first RRC reset message, The aforementioned first RRC reconfiguration message includes IP address information for the F1 termination topology domain for the IAB node. The IP address information for the F1 termination topology domain of the aforementioned IAB node is: The IAB node includes a TNL address anchored to a donor DU (donor-DU) under an F1-terminated donor CU; or This includes IP address information for non-F1 terminated topology domains for the aforementioned IAB node, The IP address information for the non-F1 terminated topology domain for the IAB node includes the TNL address of the IAB node that is anchored to the donor DU (donor-DU) under the non-F1 terminated donor CU. The F1 connection of the aforementioned IAB node is terminated at the first IAB donor CU. The first IAB donor CU is the SN of the IAB node, the IAB node has an RRC connection with the second IAB donor CU, and the second IAB donor CU is the MN of the IAB node. The transmitter is an IAB donor device that transmits the first RRC reset message via SRB1.

7. IAB (integrated access and backhaul) donor devices applicable to the second IAB donor CU, Including the transmitter, The transmitter sends the first RRC reset message, The aforementioned first RRC reconfiguration message includes IP address information for the F1 termination topology domain for the IAB node. The IP address information for the F1 termination topology domain of the aforementioned IAB node is: The IAB node includes a TNL address anchored to a donor DU (donor-DU) under an F1-terminated donor CU; or This includes IP address information for non-F1 terminated topology domains for the aforementioned IAB node, The IP address information for the non-F1 terminated topology domain for the IAB node includes the TNL address of the IAB node that is anchored to the donor DU (donor-DU) under the non-F1 terminated donor CU. The F1 connection of the aforementioned IAB node is terminated at the first IAB donor CU. The first IAB donor CU is the MN of the IAB node, the IAB node has an RRC connection with the second IAB donor CU, and the second IAB donor CU is the SN of the IAB node. The transmitter is an IAB donor device that transmits the first RRC reset message via SRB3.

Images