Method and apparatus for setting information and communication system

Abstract

In an embodiment of the present application, a method, an apparatus and a communication system for configuring information are provided, and the apparatus for configuring information is applied to an IAB node, and the apparatus includes a first receiving unit for receiving an RRC reconfiguration message, and the RRC reconfiguration message indicates relevant information of a topology to which a default uplink BAP routing ID configured for the IAB node belongs.

Description

[Technical field]

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

[0002] Integrated access and backhaul (IAB), also called access and backhaul integration, realizes the function of radio relay in next generation radio access networks (NG-RAN). An integrated access and backhaul node (IAB-node) supports New Radio (NR) access and backhaul. The network-side termination of the NR backhaul is called the IAB-donor, which represents one network device (e.g., gNB) that can support the IAB function.

[0003] An IAB-node can be connected to one IAB-donor by single or multi-hop. These multi-hop connections form a Directed Acyclic Graph (DAG) topology with the IAB-donor as the root node. The IAB-donor is responsible for performing centralized resource management, topology management, and routing management in the IAB network topology.

[0004] The IAB-node supports the function of gNB-DU (distributed unit), and the IAB-node DU is also called IAB-DU. The IAB-DU is the termination of the radio access (NR access) interface to the terminal equipment (UE) and the next hop IAB-node, and is also the termination of the F1 protocol to the gNB-CU (central unit) in the IAB-donor. The IAB-DU can serve normal UE and IAB child nodes. The IAB-DU realizes the function of a network side device, is connected to the downstream child IAB-node, provides NR air interface access to the UE and the downstream child IAB-node, and establishes an F1 connection with the IAB donor-CU.

[0005] In addition to the gNB-DU functions, the IAB-node also supports some UE functions and is called an IAB-MT (Mobile Termination), which is connected to a gNB-DU of another IAB-node or IAB-donor, connected to a gNB-CU in the IAB-donor, and connected to a core network, for example by including physical layer, layer 2, RRC, and NAS functions. The IAB-MT can support UE physical layer, access stratum (AS), radio resource control (RRC) layer, and non-access stratum (NAS) layer functions, for example, and can be connected to an IAB parent node.

[0006] The IAB-donor is an end node on the network side, and provides network access to the IAB-MT or UE through a backhaul or access link. The IAB-donor is further divided into the IAB-donor-CU (central unit) and the IAB-donor-DU. The IAB-DU and the IAB-donor-CU are connected by the F1 interface. In the case of an independent network construction scenario, the gNB and the IAB-donor-CU are connected by the Xn interface.

[0007] To support multi-hop routing forwarding of data packets, IAB introduces the Backhaul Adaptation Protocol (BAP) sublayer, which is located above the Radio Link Control (RLC) sublayer and below the IP layer and supports functions such as data packet destination node and route selection, data packet routing forwarding, bearer mapping, flow control feedback, and backhaul link failure notification.

[0008] Figure 1 is a diagram showing an IAB parent-child node relationship. As shown in Figure 1, in the IAB parent-child node relationship configuration 10, an IAB-node 100 includes an IAB-MT functional unit 101 and an IAB-DU functional unit 102, and adjacent nodes on the interface of the IAB-DU functional unit 102 are called child nodes, for example, child nodes 201, 202, and 203 shown in Figure 1, and communication can be performed between the IAB-DU functional unit 102 and the child nodes 201, 202, and 203 via an air interface (Uu), and adjacent nodes on the interface of the IAB-MT functional unit 101 are called parent nodes, and are parent nodes 301 and 302 shown in Figure 1, and communication can be performed between the IAB-MT functional unit 101 and the parent nodes 301 and 302 via an air interface (Uu).

[0009] 1, the direction from the IAB-node 100 to the child nodes 201, 202, 203 is called the downstream direction, and the direction from the IAB-node 100 to the parent nodes 301, 302 is called the upstream direction. An IAB-donor (not shown) performs centralized resource, topology, and routing management for the IAB topology 10.

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

[0011] In the case of a multi-hop scenario, to realize relay forwarding of a data packet, the IAB node needs to determine a destination node where the data packet arrives, and then determine a next-hop node corresponding to the destination node based on a routing table for transmission. The donor-CU configures, for the IAB node, a mapping of each uplink F1-U Tunnel initiated from the IAB node, a Non-UE associated F1AP message, a UE-associated F1AP message, and Non-F1 Traffic to a BAP routing indicator (ID) through F1AP (F1 application protocol) signaling.

[0012] The IAB node determines BAP routing indicators corresponding to different types of uplink IP packets initiated from the IAB node based on the routing indicator mapping information, and encapsulates BAP subheaders containing BAP routing indicator information for these uplink IP packets. The Donor-CU sets up mappings from different types of downlink data packets to BAP routing indicators for the Donor-DU through F1AP signaling. The Donor-DU determines BAP routing indicators corresponding to received downlink IP packets based on the routing indicator mapping information, and encapsulates downlink BAP subheaders containing BAP routing indicators for these downlink IP packets.

[0013] The BAP routing indicator contains the destination BAP address and the path identity between the IAB node and the donor-DU. The BAP address is also called DESTINATION in the BAP header. Every IAB node and donor-DU is configured with one BAP address.

[0014] At IAB node integration time, RRC can configure one default BH RLC channel and one default BAP routing indicator for non-F1-U traffic. These configurations can be updated under topology adaptation scenarios.

[0015] An IAB node may have redundant paths to different IAB-donor-CUs. For an IAB node working in Stand Alone (SA) mode, NR-DC can realize backhaul path redundancy by allowing the IAB-MT and two parent nodes to have backhaul links simultaneously. Two parent nodes can be connected to different IAB-donor-CUs, and these IAB-donor-CUs can control the establishment and release of redundant paths through the two parent nodes. The gNB-DU function of the parent node and the corresponding IAB-donor-CU together acquire the role of Master Node (MN) and / or Secondary Node (SN) of the IAB-MT. The NR-DC framework (e.g., processes related to MCG / SCG) is used to set up dual radio connections from the IAB node to the parent node.

[0016] Fig. 2 is a diagram showing an inter-donor topology redundancy (or inter-CU topology redundancy) network configuration, and Fig. 3 is a diagram showing partial migration between donors.

[0017] As shown in Figure 2, node 3 is called a boundary IAB node. A boundary IAB node refers to one whose RRC interface and F1 interface are terminated on different IAB-donor-CUs. Boundary IAB nodes are suitable for partial migration, inter-donor topology redundancy, and inter-donor RLF (radio link failure) recovery. As shown in Figure 2, node 3 meets the definition of a boundary IAB node because its DU is terminated on CU1 and its MT has interfaces to both CU1 and CU2. Descendant IAB nodes refer to nodes that access the network through a boundary IAB node, and each node is single-connected to its parent node, for example, IAB node 4 is a descendant node. An F1-terminating donor node refers to a donor-CU that terminates the F1 interfaces of a boundary IAB node and descendant nodes, for example, donor-CU1 is an F1 terminating node, i.e., the F1 interfaces of IAB-DU3 and IAB-DU4 in FIG. 2 are terminated in donor-CU1. A non-F1-terminating donor node refers to a CU that does not terminate the F1 interfaces of a boundary IAB node and descendant nodes and has a donor function, for example, donor-CU2 in FIG. 2. In the topology redundancy scenario shown in FIG. 2, the boundary node (i.e., node 3) is a dual-connection node. In the donor-to-donor topology redundancy scenario, the boundary IAB node (i.e., IAB node 3) and descendant nodes can communicate with CU1 via a first path and a second path, respectively.

[0018] In Figure 3, the IAB-MT of the border IAB node (i.e., IAB-MT3) can migrate under a parent node under one different IAB-donor-CU (e.g., migrate under a parent node under Donor-CU2). In such a case, the collocated IAB-DU (i.e., IAB-DU3) and the descendant IAB-DU (e.g., IAB-DU4) maintain F1 connectivity with the original IAB-donor-CU (e.g., Donor-CU1). Such migration is called inter-donor partial migration. After inter-donor partial migration, the F1 traffic of the IAB-DU of the border IAB node and the descendant nodes is routed through the BAP layer of the IAB topology to which the IAB-MT of the border IAB node has migrated. SA mode can support inter-donor partial migration.

[0019] When an IAB node in SA mode declares backhaul link RLF, it can perform RLF recovery with its parent node under a different IAB-donor-CU. Similar to partial migration between donors, the collocated IAB-DU and the IAB-DU of the descendant node can maintain F1 connectivity with the original IAB-donor-CU.

[0020] IABnode3 is a border IABnode, and IAB-MT3 changes from a single connection to parent node IABnode1 to a single connection to parent node IABnode2. IAB-DU3 and its child node IABnode4 still have F1 connections to donor-CU1, but the F1 connections take a path via IABnode2 to finally reach donor-CU1. In the donor-to-donor partial migration scenario shown in Figure 3, the border node (node3) is a transition node. The donor-to-donor partial migration scenario is also suitable for partial RLF recovery.

[0021] The inventor of the present application has found that a border IAB node belongs to two IAB topologies, and the prior art does not indicate which topology it belongs to when configuring a default uplink BAP routing ID and / or a default uplink BH RLC channel for the border IAB node, for example, does not consider the case where an SN is an F1 termination donor when configuring a default uplink BH RLC channel, and does not consider the case where the BAP address of the corresponding donor-DU is pseudo when configuring an IP address for the border IAB node or its descendant node.

[0022] The embodiments of the present application provide a method and apparatus and a communication system for configuring information, and indicate related information of a topology to which a default uplink BH RLC channel and / or a default uplink BAP routing ID configured for an IAB node belongs by an RRC reconfiguration message, thereby indicating which topology a default uplink BAP routing ID and / or a default uplink BH RLC channel configured for an IAB node belongs to. [Means for solving the problem]

[0023] According to one aspect of an embodiment of the present application, an apparatus for setting information is provided, which is applied to an IAB node, and the apparatus includes: A first receiving unit for receiving an RRC reconfiguration message, Wherein, the RRC reconfiguration message indicates relevant information of the topology to which the default uplink BAP routing ID configured for the IAB node belongs.

[0024] According to another aspect of an embodiment of the present application, an apparatus for setting information is provided, which is applied to an IAB node, and the apparatus includes: A second receiving unit for receiving an RRC reconfiguration message, Wherein, the RRC reconfiguration message indicates relevant information of a topology to which a default uplink BH RLC channel to be configured for the IAB node belongs.

[0025] According to another aspect of an embodiment of the present application, an apparatus for setting information is provided, which is applied to an IAB node, and the apparatus includes: A third receiving unit for receiving an RRC reconfiguration message, Wherein, the RRC reconfiguration message configures a first donor-DU BAP address for the IAB node, and the first donor-DU BAP address refers to a donor distribution unit (DU2) in the second topology. Effect of the Invention

[0026] The advantageous effects of the embodiment of the present invention are at least as follows: the default uplink BAP routing ID and / or the default uplink BH RLC channel configured for an IAB node can indicate which topology it belongs to.

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

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

[0029] It should be noted that terms such as "comprise / have" when used in this specification refer to the presence of a feature, element, step, or assembly, but do not exclude the presence or addition of one or more other features, elements, steps, or assemblies. [Brief description of the drawings]

[0030] Elements and features described in one drawing or one embodiment of the invention may be combined with elements and features shown in one or more other drawings or embodiments, and in the drawings, like reference numerals are used to indicate corresponding parts in the several drawings and to indicate corresponding parts used in several embodiments. [Figure 1] FIG. 2 illustrates an IAB parent-child node relationship. [Diagram 2] FIG. 1 is a diagram showing a donor-to-donor topology redundant network configuration. [Diagram 3] FIG. 1 shows partial transfer between donors. [Figure 4] FIG. 11 is a diagram showing a method for setting information in an embodiment of the first aspect. [Diagram 5] FIG. 11 is a diagram showing a method for setting information in an embodiment of the second aspect. [Figure 6] FIG. 11 is a diagram showing a method for setting information in an embodiment of the third aspect. [Figure 7] FIG. 11 is a diagram showing a method for setting information in an embodiment of the fourth aspect. [Figure 8] FIG. 13 is a diagram showing a method for setting information in an embodiment of the fifth aspect. [Figure 9] FIG. 13 is a diagram showing a method for setting information in an embodiment of the sixth aspect. [Figure 10] FIG. 13 is a diagram showing an apparatus for setting information in an embodiment of the seventh aspect. [Figure 11] FIG. 13 is a diagram showing an apparatus for setting information in an embodiment of the eighth aspect. [Figure 12] FIG. 13 is a diagram showing an apparatus for setting information in an embodiment of the ninth aspect. [Figure 13] FIG. 13 is a diagram showing an apparatus for setting information in an embodiment of the tenth aspect. [Figure 14] FIG. 13 is a diagram showing an apparatus for setting information in an embodiment of the eleventh aspect. [Figure 15] FIG. 23 is a diagram showing a method for setting information in an embodiment of the twelfth aspect. [Figure 16] FIG. 1 is a diagram showing a configuration of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

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

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

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

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

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

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

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

[0040] In the prior art (eg, TS38.331), the field description for the default BAP routing ID and BH RLC channel configuration in the RRC reconfiguration message is shown in Table 1 below.

[0041] [Table 1] In the prior art (eg, TS38.331), the contents of the IAB-IP-AddressConfiguration field in the RRC reconfiguration message and the description of the iab-donor-DU-BAP-Address field therein are as shown in Table 2 below.

[0042] [Table 2] In the embodiments of the present application, the higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, for example, referred to as an RRC message, including, for example, MIB, system information, dedicated RRC messages, or referred to as an RRC information element (IE). The higher layer signaling may be, for example, further F1-C signaling, or referred to as an F1AP protocol, but the present application is not limited thereto.

[0043] In this application, the embodiments are described taking a multi-hop IAB network deployment scenario as an example, in which multiple terminal devices (e.g., UEs) are connected to an IAB-donor through multi-hop IAB nodes, and finally access a network, such as a 5G network. Note that the embodiments of this application are not limited to such a scenario.

[0044] In each embodiment of the present application, the IAB topology refers to a combination of all IAB nodes and IAB-donor-DUs that are connected to each other by backhaul links and whose F1 interfaces and / or RRCs are terminated in the same IAB-donor-CU. For example, in Figures 2 and 3, Donor-DU1, IAB node 1, IAB node 3, and IAB node 4 are nodes managed by Donor-CU1, and the IAB topology network that they configure with Donor-CU1 is called the first topology, and Donor-DU2, IAB node 2, and IAB node 3 are nodes managed by Donor-CU2, and the IAB topology network that they configure with Donor-CU2 is called the second topology. The border node (i.e., IAB node 3) belongs to both the first topology and the second topology.

[0045] <Example of the first aspect> In the IAB node's guided process, transition process, or the IAB-MT's RRC recovery and IAB-MT's RRC re-establishment processes, the RRC reconfiguration message can configure a default uplink BAP routing ID (defaultUL-BAP-RoutingID) for the IAB node's F1-C and non-F1 traffic. This default uplink BAP routing ID can be configured or reconfigured when the IP address corresponding to the IAB node's F1-C related traffic changes.

[0046] However, in the scenarios of Figures 2 and 3, the border node is connected to different IAB topologies, and the uplink BAP routing indicators used by the border node may have BAP routing indicators to two IAB topologies (i.e., to donor-DUs under two different donor-CUs). Since the BAP routing indicators of different IAB topologies are configured and managed by each donor-CU, the BAP routing indicators belonging to different IAB topologies may collide. Therefore, the default uplink BAP routing ID has ambiguity, and it is necessary to further clarify the related information of the topology.

[0047] To solve the above problem or similar problems, an embodiment of the first aspect of the present application provides a method for configuring information, which is applied to an IAB node.

[0048] 4 is a diagram showing a method for setting information in an embodiment of the first aspect. As shown in FIG. 4, the method includes the following operations (steps):

[0049] Operation 401: Receive an RRC reconfiguration message, in which the RRC reconfiguration message indicates relevant information of a topology to which a default uplink BAP routing ID configured for an IAB node belongs.

[0050] In an embodiment of the first aspect, the IAB node may be a border IAB node, such as the IAB node 3 shown in Figure 2 or Figure 3. Moreover, the IAB node of the present application is not limited thereto, and the IAB node may be of other types.

[0051] In operation 401, the topology-related information may refer to topology information and / or cell group (CG) information, where the topology includes F1-terminated topology or non-F1-terminated topology, and the cell group information includes master cell group / secondary cell group (MCG / SCG) information.

[0052] In at least some embodiments, in operation 401, the RRC reconfiguration message may include first indication information, and the first indication information is used to indicate the topology to which the default uplink BAP routing ID belongs. For example, the first indication information is used to indicate that the topology to which the default uplink BAP routing ID belongs belongs to an F1 terminated topology or a non-F1 terminated topology. The first indication information may be mandatory only for border IAB nodes.

[0053] In at least some other embodiments, in operation 401, the donor central unit (donor-CU) may set a default uplink BAP routing ID (defaultUL-BAP-RoutingID) field or set a backhaul adaptation protocol configuration (bap-Config) that includes the default uplink BAP routing ID field to indicate the topology to which the default uplink BAP routing ID belongs, thereby allowing an implicit method to be used to indicate which topology the default uplink BAP routing ID belongs to.

[0054] Wherein, when an F1 termination donor sets the default uplink BAP routing ID field or sets a bap-Config including the default uplink BAP routing ID field, the default uplink BAP routing ID belongs to the F1 termination topology; when a non-F1 termination donor sets the default uplink BAP routing ID field or sets a bap-Config including the default uplink BAP routing ID field, the default uplink BAP routing ID belongs to the non-F1 termination topology.

[0055] For example, the RRC standard can be enhanced in TS 38.331. Specifically, the defaultUL-BAP-RoutingID field in the bap-Config IE of the RRC reconfiguration information may be changed to a format as shown in Table 3 below.

[0056] [Table 3] Regarding the scheme of indicating which topology the default uplink BAP routing ID belongs to by an implicit method, in one specific implementation manner, when the MN or SN is an F1 termination donor, it may be determined that the F1 termination donor or a non-F1 termination donor sets the default uplink BAP routing ID field or a bap-Config including the default uplink BAP routing ID field.

[0057] For example, if an IAB node establishes an NR-DC after establishing an F1 connection, then the MN is the F1 termination donor, and if an IAB node establishes an NR-DC before establishing an F1-C, then the IAB node selects an MN or an SN as the F1 termination donor.

[0058] If the default uplink BAP routing ID field or bap-Config is included in the RRC reconfiguration message transmitted by SRB3, or if the default uplink BAP routing ID field or bap-Config is included in the multi-radio access technology dual connectivity secondary cell group information element (mrdc-SecondaryCellGroup IE), the default uplink BAP routing ID field or bap-Config is configured by the secondary node (SN). If the default uplink BAP routing ID field or bap-Config is included in the RRC reconfiguration message transmitted by SRB1 and is not included in the mrdc-SecondaryCellGroup IE, the default uplink BAP routing ID field or bap-Config is configured by the master node (MN).

[0059] According to an embodiment of the first aspect, the default uplink BAP routing ID configured for an IAB node can indicate which topology it belongs to.

[0060] <Example of the second aspect> In the IAB node's guiding process, transition process, or IAB-MT's RRC recovery and IAB-MT's RRC re-establishment process, the RRC reconfiguration message can configure a default uplink BH RLC channel (defaultUL-BH-RLC-Channel) for the IAB node's F1-C and non-F1 traffic. This default uplink BH RLC channel can be configured or reconfigured when the IAB node's IP address corresponding to the F1-C related traffic changes and when the new IP address is anchored to a different IAB-donor-DU. Since the BH RLC channel indicator is only unique on each link, in the case of dual connectivity, it is necessary to further indicate the link of the BH RLC channel (i.e., the link of the uplink parent node, which is also equivalent to the cell group). In Rel-16, if the IAB-MT works in an EN-DC scenario, the default uplink BH RLC channel points to the RLC channel on the SCG (secondary cell group), otherwise it points to the RLC (Radio Link Control) channel on the MCG (master cell group).

[0061] In the Rel-17 NR-DC scenario, the parent nodes of an IAB node may belong to different IAB-donor-CUs, i.e., a border IAB node may have two IAB-donor-CUs. The MN (master node) and the SN (secondary node) can all be F1 terminating donor nodes. When an IAB node determines NR-DC before F1-C connection establishment, the IAB node can implicitly obtain that the MN or SN is an F1 terminating donor, for example, based on the entity that provides the default BAP configuration. In such a case, the Rel-16 designation method cannot be used, because in the Rel-17 NR-DC scenario, the default uplink BH RLC channel can also point to the SCG. That is, when the IAB-MT works in a scenario other than the EN-DC scenario, the default uplink BH RLC channel can point to the RLC channel of the MCG or SCG.

[0062] When routing is performed at the BAP sublayer, if the backhaul routing configuration has not been configured or reconfigured by the F1AP after the defaultUL-BH-RLC-Channel was last configured or reconfigured by the RRC, it is necessary to select an egress link based on the configured defaultUL-BH-RLC-Channel. Therefore, since the default uplink BH RLC channel has ambiguity, the selection of the egress link also has ambiguity, which requires further indication of topology information or cell group information.

[0063] To solve the above problem or similar problems, an embodiment of the second aspect of the present application provides a method for configuring information, which is applied to an IAB node.

[0064] 5 is a diagram illustrating a method for setting information in an embodiment of the second aspect. As shown in FIG. 5, the method includes the following operations:

[0065] Operation 501: Receive an RRC reconfiguration message, in which the RRC reconfiguration message indicates relevant information of a topology to which a default uplink BH RLC channel to be configured for an IAB node belongs.

[0066] In an embodiment of the second aspect, the IAB node does not work in an EN-DC scenario, and may be a border IAB node, such as the IAB node 3 shown in Figure 2 or Figure 3. Also, the IAB node of the present application is not limited thereto, and the IAB node may be of other types.

[0067] In operation 501, the topology-related information may refer to topology information and / or cell group information, where the topology includes F1-terminated topology or non-F1-terminated topology, and the cell group information includes master cell group / secondary cell group (MCG / SCG) information.

[0068] In some embodiments of the operation 501, the RRC reconfiguration message may include second indication information, which is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or the second indication information is used to indicate that the default uplink BH RLC channel is directed to an RLC channel on a master cell group (MCG) or an RLC channel on a secondary cell group (SCG). The second indication information may be mandatory for a dual access node, or a node of an NR-DC, or a border IAB node.

[0069] In at least some other embodiments of the operation 501, the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) may point to an RLC channel of an MCG or point to an RLC channel of an SCG, and a donor central unit (donor-CU) that configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config that includes the default uplink BH RLC channel field can indicate the cell group to which the default uplink BH RLC channel points, thereby indicating the relevant information of the topology to which the default uplink BH RLC channel belongs in an implicit manner.

[0070] In at least some other embodiments, when an MN configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field, the default uplink BH RLC channel points to an RLC channel on an MCG, and when an SN configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field, the default uplink BH RLC channel points to an RLC channel on an SCG. That is, for an IAB node (e.g., a border IAB node), the default uplink BH RLC channel points to an RLC channel on a backhaul link configured by a donor-CU that configures the field.

[0071] For example, the RRC standard can be enhanced in TS 38.331. Specifically, the defaultUL-BH-RLC-Channel field in the bap-Config IE of the RRC reconfiguration information can be enhanced as shown in Table 4 below.

[0072] [Table 4] In at least some other embodiments, if the default uplink BH RLC channel field or bap-Config is included in an RRC reconfiguration message transmitted by SRB1 and is not included in a multi-radio access technology dual connectivity secondary cell group information element (mrdc-SecondaryCellGroup IE), the default uplink BH RLC channel field or bap-Config is configured by a master node (MN), and if the default uplink BH RLC channel field or bap-Config is included in an RRC reconfiguration message transmitted by SRB3 or the default uplink BH RLC channel field or bap-Config is included in the mrdc-SecondaryCellGroup IE, the default uplink BH RLC channel field or bap-Config is configured by a secondary node (SN).

[0073] When performing routing at the BAP sublayer, if the backhaul routing configuration has not been configured or reconfigured by the F1AP since the default uplink BH RLC channel was last configured or reconfigured by the RRC, an exit link is selected based on the cell group corresponding to the default uplink BH RLC channel.

[0074] In at least one embodiment, when routing at the BAP sublayer, if the backhaul routing configuration has not been configured or reconfigured by the F1 Application Protocol (F1AP) since the default uplink BH RLC channel was last configured or reconfigured by the RRC, the IAB node selects an exit link based on a cell group corresponding to the default uplink BH RLC channel.

[0075] According to an embodiment of the second aspect, it is possible to indicate information related to the topology to which the default uplink BH RLC channel configured for the IAB node belongs.

[0076] <Example of the third aspect> In the case of inter-donor routing shown in Figures 2 and 3, the descendant nodes of the boundary node can use the same inter-donor (or inter-CU) topology adaptation process. For example, after the IAB-MT of the boundary node migrates to donor-CU2 or establishes RRC with donor-CU2, the IAB-DU of the boundary node still maintains F1 connection with donor-CU1, and the descendant node (e.g., IAB node 4) still maintains RRC connection and F1 connection with donor-CU1.

[0077] Because the descendant node of the boundary node needs to migrate the transmission path of the F1 connection to a non-F1 terminated topology, donor-CU2 needs to provide the descendant node with a new TNL (transport network layer) address, i.e., an IP address, in response to the request of donor-CU1. These one or more new TNL addresses are anchored to a donor-DU, e.g., donor-DU2, in the topology of donor-CU2. Donor-CU2 sends these new TNL addresses to donor-CU1 by an XnAP message, e.g., an IAB Transport Migration Management Response message. Donor-CU2 further provides layer 2 information in the topology to donor-CU1, e.g., an uplink BAP routing indicator, including the BAP address of a donor-DU, e.g., donor-DU2, in the topology. Donor-CU1 configures IP addresses for the descendant node by an RRCReconfiguration message. The IP address is configured using the IAB-IP-AddressConfiguration IE in the RRC reconfiguration, which includes fields such as the IP address, the purpose of the IP address, and the BAP address of the donor-DU corresponding to the IP address (iab-donor-DU-BAP-Address). When a descendant node transmits its own uplink data, it obtains the BAP address included in the routing ID according to the BAP routing ID configured for the data traffic, which is the BAP address of the destination donor-DU, and then finds the IP address corresponding to the BAP address of the donor-DU from the IAB-IP-AddressConfiguration setting, and selects the IP address as the IP address used by the traffic to perform uplink transmission.

[0078] Since the BAP address of donor-DU2 is within the topology of CU2, there is a possibility that it may collide with the BAP address within the topology of CU1.

[0079] To solve the above problem, an embodiment of the third aspect provides a method for configuring information, which is applied to an IAB node.

[0080] 6 is a diagram illustrating a method for setting information in an embodiment of the third aspect. As shown in FIG. 6, the method includes the following operations.

[0081] Operation 601: Receive an RRC reconfiguration message, in which the RRC reconfiguration message configures a first donor-DU BAP address for an IAB node, and the first donor-DU BAP address points to a donor distribution unit (donor-DU2) in a second topology.

[0082] In an embodiment of the third aspect, the IAB node may be a descendant node of a boundary IAB node, for example, IAB node 4 shown in Figure 2 or Figure 3. Also, the IAB node of the present application is not limited thereto, and the IAB node may be of other types.

[0083] In at least one embodiment, the second topology refers to a topology different from the topology to which the IAB node belongs, for example, the IAB node belongs to an F1 terminating topology of a boundary node, i.e., a first topology, and the second topology is a non-F1 terminating topology of a boundary node.

[0084] In at least one embodiment of operation 601, the IP address configuration of the RRC reconfiguration message may include the first donor-DU BAP address.

[0085] In at least one embodiment, the IAB node is configured with an uplink BAP routing ID, and the uplink BAP routing ID includes the first donor-DU BAP address.

[0086] In at least one embodiment, as shown in FIG. 6, the method further includes the following operations.

[0087] Operation 602: The IAB node selects an IP address based on the first donor-DU BAP address; and Operation 603: The IAB node performs uplink transmission via the second topology using the selected IP address.

[0088] 2 and 3, in an embodiment of the third aspect, CU1 can assign a first donor-DU BAP address to donor-DU2 in the topology of CU1, which may be referred to as a pseudo BAP address or an alias address. CU1 can configure an uplink BAP routing ID for a descendant node, including an indication of the first donor-DU BAP address of donor-DU2.

[0089] Because the descendant node makes the corresponding selection based on the donor-DU BAP address in the uplink BAP routing ID during IP address selection, the BAP address for donor-DU2 in IAB-IP-AddressConfiguration is also the first donor-DU BAP address of donor-DU2, not the actual BAP address in CU2 topology of donor-DU2. Specifically, for the descendant node of the border IAB node, the BAP address of IAB-donor-DU in IP address configuration may be the first donor-DU BAP address, which points to a certain IAB-donor-DU (e.g., donor-DU2 in Figures 2 and 3) under the non-F1 terminating donor CU of the border IAB node.

[0090] For example, the RRC standard can be enhanced in TS 38.331. Specifically, the iab-donor-DU-BAP-Address field in the IAB-IP-AddressConfiguration IE of the RRC reconfiguration information can be enhanced as shown in Table 5 below.

[0091] [Table 5] In at least one embodiment, when an IAB node receives an IAB IP address add / modify list (iab-IP-AddressToAddModList) included in an RRC reconfiguration message, the IAB node stores the IP addresses in the list and the first donor-DU BAP addresses corresponding to the IP addresses. The IP addresses may be IPv4 or IPv6 addresses. The usage of the IP addresses may be F1-C, F1-U, non-F1 traffic, etc.

[0092] According to an embodiment of the third aspect, when setting an IP address for a border IAB node or a descendant node, it is possible to handle the case where the BAP address of a donor-DU is pseudo.

[0093] <Example of the fourth aspect> In an embodiment of the fourth aspect of the present application, a method for setting information is provided, which corresponds to the method for setting information in the embodiment of the first aspect, which is applied to a donor central unit (CU), for example donor-CU1 or donor-CU2 in FIG.

[0094] 7 is a diagram illustrating a method for setting information in an embodiment of the fourth aspect. As shown in FIG. 7, the method includes the following operations:

[0095] Operation 701: Send an RRC reconfiguration message, in which the RRC reconfiguration message indicates relevant information of a topology to which a default uplink BAP routing ID configured for an IAB node belongs.

[0096] In an embodiment of the fourth aspect, the IAB node may be a border IAB node, such as the IAB node 3 shown in Figure 2 or Figure 3. Moreover, the IAB node of the present application is not limited thereto, and the IAB node may be of other types.

[0097] In operation 701, the topology-related information may refer to topology information and / or cell group information, where the topology includes F1-terminated topology or non-F1-terminated topology, and the cell group information includes master cell group / secondary cell group (MCG / SCG) information.

[0098] In at least some embodiments, in operation 701, the RRC reconfiguration message may include first indication information, and the first indication information is used to indicate the topology to which the default uplink BAP routing ID belongs. For example, the first indication information is used to indicate that the topology to which the default uplink BAP routing ID belongs belongs to an F1 terminated topology or a non-F1 terminated topology. The first indication information may be mandatory only for border IAB nodes.

[0099] In at least some other embodiments, in operation 701, a donor central unit (donor-CU) that sets a default uplink BAP routing ID (defaultUL-BAP-RoutingID) field or sets a backhaul adaptation protocol configuration (bap-Config) that includes the default uplink BAP routing ID field can indicate the topology to which the default uplink BAP routing ID belongs, thereby using an implicit method to indicate which topology the default uplink BAP routing ID belongs to.

[0100] Wherein, when an F1 termination donor sets the default uplink BAP routing ID field or sets a bap-Config including the default uplink BAP routing ID field, the default uplink BAP routing ID belongs to the F1 termination topology; when a non-F1 termination donor sets the default uplink BAP routing ID field or sets a bap-Config including the default uplink BAP routing ID field, the default uplink BAP routing ID belongs to the non-F1 termination topology.

[0101] According to an embodiment of the fourth aspect, the default uplink BAP routing ID configured for an IAB node can indicate which topology it belongs to.

[0102] <Example of the fifth aspect> In an embodiment of the fifth aspect of the present application, a method for setting information is provided, which corresponds to the method for setting information in the embodiment of the second aspect, which is applied to a donor central unit (CU), for example donor-CU1 or donor-CU2 as shown in FIG.

[0103] 8 is a diagram illustrating a method for setting information in an embodiment of the fifth aspect. As shown in FIG. 8, the method includes the following operations:

[0104] Operation 801: Send an RRC reconfiguration message, where the RRC reconfiguration message indicates relevant information of a topology to which a default uplink BH RLC channel to be configured for an IAB node belongs.

[0105] In an embodiment of the fifth aspect, the IAB node does not work in an EN-DC scenario, and may be a border IAB node, such as the IAB node 3 shown in Figure 2 or Figure 3. Also, the IAB node of the present application is not limited thereto, and the IAB node may be of other types.

[0106] In operation 801, the topology-related information may refer to topology information and / or cell group information, where the topology includes F1-terminated topology or non-F1-terminated topology, and the cell group information includes master cell group / secondary cell group (MCG / SCG) information.

[0107] In some embodiments of operation 801, the RRC reconfiguration message may include second indication information, which is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or the second indication information is used to indicate that the default uplink BH RLC channel is directed to an RLC channel on a master cell group (MCG) or an RLC channel on a secondary cell group (SCG). The second indication information may be mandatory for a dual access node, or a node of an NR-DC, or a border IAB node.

[0108] In at least some other embodiments of operation 801, the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) may point to an RLC channel of an MCG or point to an RLC channel of an SCG, and a donor central unit (donor-CU) that configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config that includes the default uplink BH RLC channel field can indicate the cell group to which the default uplink BH RLC channel points, thereby indicating the relevant information of the topology to which the default uplink BH RLC channel belongs in an implicit manner.

[0109] In at least some other embodiments, if the donor that configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures the bap-Config including the default uplink BH RLC channel field is an MN, the default uplink BH RLC channel points to an RLC channel on an MCG, and if the donor that configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures the bap-Config including the default uplink BH RLC channel field is an SN, the default uplink BH RLC channel points to an RLC channel on an SCG. In other words, for an IAB node (e.g., a border IAB node), the default uplink BH RLC channel points to an RLC channel on a backhaul link configured by the donor-CU that configures the field.

[0110] In at least one embodiment, when routing at the BAP sublayer, if the backhaul routing configuration has not been configured or reconfigured by the F1 Application Protocol (F1AP) since the default uplink BH RLC channel was last configured or reconfigured by the RRC, the IAB node selects an exit link based on a cell group corresponding to the default uplink BH RLC channel.

[0111] According to an embodiment of the fifth aspect, it is possible to indicate information related to the topology to which the default uplink BH RLC channel configured for the IAB node belongs.

[0112] <Example of the sixth aspect> In an embodiment of the sixth aspect, a method for setting information is provided, which corresponds to the method for setting information in the embodiment of the third aspect, the method being applied to a donor central unit (CU), for example donor-CU1 as shown in FIG.

[0113] 9 is a diagram illustrating a method for setting information in an embodiment of the sixth aspect. As shown in FIG. 9, the method includes the following operations:

[0114] Operation 901: Send an RRC reconfiguration message, in which the RRC reconfiguration message configures a first donor-DU BAP address for the IAB node, and the first donor-DU BAP address points to a donor distribution unit (donor-DU2) in the second topology.

[0115] In an embodiment of the sixth aspect, the IAB node may be a descendant node of a boundary IAB node, for example, IAB node 4 shown in Figure 2 or Figure 3. Moreover, the IAB node of the present application is not limited thereto, and the IAB node may be of other types.

[0116] In at least one embodiment, the second topology refers to a topology different from the topology to which the IAB node belongs, for example, the IAB node belongs to an F1 terminating topology of a boundary node, and the second topology is a non-F1 terminating topology of a boundary node.

[0117] In at least one embodiment of operation 901, the IP address configuration of the RRC reconfiguration message may include the first donor-DU BAP address.

[0118] In at least one embodiment, the CU may configure an uplink BAP routing ID for the IAB node, where the uplink BAP routing ID includes the first donor-DU BAP address.

[0119] 2 and 3, in an embodiment of the third aspect, donor-CU1 can assign a first donor-DU BAP address to donor-DU2 in the topology of CU1, which may be referred to as a pseudo BAP address or an alias address. CU1 can configure an uplink BAP routing ID for a descendant node, including an indication of the first donor-DU BAP address of donor-DU2.

[0120] Because the descendant node makes the corresponding selection based on the donor-DU BAP address in the uplink BAP routing ID during IP address selection, the BAP address for donor-DU2 in IAB-IP-AddressConfiguration is also the first donor-DU BAP address of donor-DU2, not the actual BAP address in CU2 topology of donor-DU2. Specifically, for the descendant node of the border IAB node, the BAP address of IAB-donor-DU in IP address configuration may be the first donor-DU BAP address, which points to a certain IAB-donor-DU (e.g., donor-DU2 in Figures 2 and 3) under the non-F1 terminating donor CU of the border IAB node.

[0121] In at least one embodiment, the RRC reconfiguration message sent by the CU may include an IAB IP address add / modify list (iab-IP-AddressToAddModList), which includes an IP address and a first donor-DU BAP address corresponding to the IP address. The IP address may be an IPv4 address or an IPv6 address. The usage of the IP address may be F1-C, F1-U, non-F1 traffic, etc.

[0122] According to an embodiment of the sixth aspect, when setting an IP address for a border IAB node or a descendant node, it is possible to deal with the case where the BAP address of a donor-DU is pseudo.

[0123] <Example of the seventh aspect> In an embodiment of the seventh aspect of the present application, an apparatus for setting information is provided, which corresponds to the method for setting information described in the embodiment of the first aspect, wherein the apparatus is applied to an IAB node.

[0124] 10 is a diagram showing an apparatus for setting information in an embodiment of the seventh aspect. As shown in FIG. 10, an apparatus 1000 for setting information includes:

[0125] A first receiving unit 1001: receives an RRC reconfiguration message, in which the RRC reconfiguration message indicates relevant information of a topology to which a default uplink BAP routing ID configured for an IAB node belongs.

[0126] In an embodiment of the seventh aspect, the IAB node may be a border IAB node, such as the IAB node 3 shown in Figure 2 or Figure 3. Moreover, the IAB node of the present application is not limited thereto, and the IAB node may be of other types.

[0127] The topology-related information may refer to topology information and / or cell group information, where the topology includes F1-terminated topology or non-F1-terminated topology, and the cell group information includes master cell group / secondary cell group (MCG / SCG) information.

[0128] In at least some embodiments, the RRC reconfiguration message may include first indication information, and the first indication information is used to indicate the topology to which the default uplink BAP routing ID belongs. For example, the first indication information is used to indicate that the topology to which the default uplink BAP routing ID belongs belongs to an F1 terminated topology or a non-F1 terminated topology. The first indication information may be mandatory only for border IAB nodes.

[0129] In at least some other embodiments, a donor central unit (donor-CU) that configures a default uplink BAP routing ID (defaultUL-BAP-RoutingID) field or configures a backhaul adaptation protocol configuration (bap-Config) that includes the default uplink BAP routing ID field can indicate the topology to which the default uplink BAP routing ID belongs, thereby using an implicit method to indicate which topology the default uplink BAP routing ID belongs to.

[0130] Wherein, when an F1 termination donor sets the default uplink BAP routing ID field or sets a bap-Config including the default uplink BAP routing ID field, the default uplink BAP routing ID belongs to the F1 termination topology; when a non-F1 termination donor sets the default uplink BAP routing ID field or sets a bap-Config including the default uplink BAP routing ID field, the default uplink BAP routing ID belongs to the non-F1 termination topology.

[0131] As a scheme for indicating which topology the default uplink BAP routing ID belongs to in an implicit manner, in one specific implementation manner, when the MN or SN is an F1 termination donor, it can be determined that the F1 termination donor or a non-F1 termination donor sets the default uplink BAP routing ID field or a bap-Config including the default uplink BAP routing ID field.

[0132] For example, when an IAB node establishes an NR-DC after establishing an F1 connection, the MN is the F1 termination donor, and when an IAB node establishes an NR-DC before establishing an F1-C, the IAB node selects an MN or an SN as the F1 termination donor.

[0133] If the default uplink BAP routing ID field or bap-Config is included in the RRC reconfiguration message transmitted by SRB3, or if the default uplink BAP routing ID field or bap-Config is included in the multi-radio access technology dual connectivity secondary cell group information element (mrdc-SecondaryCellGroup IE), the default uplink BAP routing ID field or bap-Config is configured by the secondary node (SN). If the default uplink BAP routing ID field or bap-Config is included in the RRC reconfiguration message transmitted by SRB1 and is not included in the mrdc-SecondaryCellGroup IE, the default uplink BAP routing ID field or bap-Config is configured by the master node (MN).

[0134] According to an embodiment of the seventh aspect, the default uplink BAP routing ID configured for an IAB node can indicate which topology it belongs to.

[0135] <Example of the eighth aspect> In an embodiment of the eighth aspect of the present application, an apparatus for setting information is provided, which corresponds to the method for setting information in the embodiment of the second aspect. The apparatus is applied to an IAB node.

[0136] 11 is a diagram showing an apparatus 1100 for setting information in an embodiment of the eighth aspect. As shown in FIG. 11, the apparatus 1100 for setting information includes:

[0137] A second receiving unit 1101: receives an RRC reconfiguration message, in which the RRC reconfiguration message indicates relevant information of a topology to which a default uplink BH RLC channel configured for an IAB node belongs.

[0138] In an embodiment of the eighth aspect, the IAB node does not work in an EN-DC scenario, and may be a border IAB node, such as the IAB node 3 shown in Figure 2 or Figure 3. Also, the IAB node of the present application is not limited thereto, and the IAB node may be of other types.

[0139] The topology-related information may refer to topology information and / or cell group information, where the topology includes F1-terminated topology or non-F1-terminated topology, and the cell group information includes master cell group / secondary cell group (MCG / SCG) information.

[0140] In some embodiments, the RRC reconfiguration message may include second indication information, which is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or the second indication information is used to indicate that the default uplink BH RLC channel is directed to an RLC channel on a master cell group (MCG) or an RLC channel on a secondary cell group (SCG). The second indication information may be mandatory for a dual access node, or a node of an NR-DC, or a border IAB node.

[0141] In at least some other embodiments, the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) may point to an RLC channel of an MCG or point to an RLC channel of an SCG, and a donor central unit (donor-CU) that configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config that includes the default uplink BH RLC channel field can indicate the cell group to which the default uplink BH RLC channel points, thereby indicating related information of the topology to which the default uplink BH RLC channel belongs in an implicit manner.

[0142] In at least some other embodiments, when an MN configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field, the default uplink BH RLC channel points to an RLC channel on an MCG, and when an SN configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field, the default uplink BH RLC channel points to an RLC channel on an SCG. That is, for an IAB node (e.g., a border IAB node), the default uplink BH RLC channel points to an RLC channel on a backhaul link configured by a donor-CU that configures the field.

[0143] In at least some other embodiments, if the default BH RLC channel field or bap-Config is included in an RRC reconfiguration message transmitted by SRB1 and is not included in a multi-radio access technology dual connectivity secondary cell group information element (mrdc-SecondaryCellGroup IE), the default BH RLC channel field or bap-Config is configured by a master node (MN), and if the default uplink BH RLC channel field or bap-Config is included in an RRC reconfiguration message transmitted by SRB3 or the default uplink BH RLC channel field or bap-Config is included in the mrdc-SecondaryCellGroup IE, the default uplink BH RLC channel field or bap-Config is configured by a secondary node (SN).

[0144] When routing at the BAP sublayer, if the backhaul routing configuration has not been configured or reconfigured by the F1AP since the default uplink BH RLC channel was last configured or reconfigured by the RRC, an exit link is selected based on the cell group corresponding to the default uplink BH RLC channel.

[0145] In at least one embodiment, when routing at the BAP sublayer, if the backhaul routing configuration has not been configured or reconfigured by the F1 Application Protocol (F1AP) since the default uplink BH RLC channel was last configured or reconfigured by the RRC, the IAB node selects an exit link based on a cell group corresponding to the default uplink BH RLC channel.

[0146] According to an embodiment of the eighth aspect, it is possible to indicate information related to the topology to which the default uplink BH RLC channel configured for the IAB node belongs.

[0147] <Example of the ninth aspect> In an embodiment of the ninth aspect, an apparatus for setting information is provided, which corresponds to the method for setting information in the embodiment of the third aspect. The apparatus is applied to an IAB node.

[0148] 12 is a diagram showing an apparatus for setting information in an embodiment of the ninth aspect. As shown in FIG. 12, the apparatus 1200 for setting information includes:

[0149] A third receiving unit 1201: receives an RRC reconfiguration message, in which the RRC reconfiguration message configures a first donor-DU BAP address for the IAB node, and the first donor-DU BAP address points to a donor distribution unit (donor-DU2) in the second topology.

[0150] In an embodiment of the ninth aspect, the IAB node may be a descendant node of a boundary IAB node, for example, IAB node 4 shown in Figure 2 or Figure 3. Moreover, the IAB node of the present application is not limited to this, and the IAB node may be of other types.

[0151] In at least one embodiment, the second topology refers to a topology different from the topology to which the IAB node belongs, for example, the IAB node belongs to an F1 terminating topology of a boundary node, and the second topology is a non-F1 terminating topology of a boundary node.

[0152] In at least one embodiment, the IP address configuration of the RRC reconfiguration message may include the first donor-DU BAP address.

[0153] In at least one embodiment, the IAB node is configured with an uplink BAP routing ID, and the uplink BAP routing ID includes the first donor-DU BAP address.

[0154] In at least one embodiment, the third receiving unit 1201 may further perform the following operations: First, select an IP address based on the donor-DU BAP address; and The selected IP address is used to perform uplink transmission via the second topology.

[0155] 2 and 3, in an embodiment of the ninth aspect, CU1 can assign a first donor-DU BAP address to donor-DU2 in the topology of CU1, where the first donor-DU BAP address may be referred to as a pseudo BAP address or an alias address. CU1 can configure an uplink BAP routing ID for a descendant node, including an indication of the first donor-DU BAP address of donor-DU2.

[0156] Because the descendant node makes the corresponding selection based on the donor-DU BAP address in the uplink BAP routing ID during IP address selection, the BAP address for donor-DU2 in IAB-IP-AddressConfiguration is also the first donor-DU BAP address of donor-DU2, not the actual BAP address in CU2 topology of donor-DU2. Specifically, for the descendant node of the border IAB node, the BAP address of IAB-donor-DU in IP address configuration may be the first donor-DU BAP address, which points to a certain IAB-donor-DU (e.g., donor-DU2 in Figures 2 and 3) under the non-F1 terminating donor CU of the border IAB node.

[0157] In at least one embodiment, when an IAB node receives an IAB IP address add / modify list (iab-IP-AddressToAddModList) included in an RRC reconfiguration message, it stores an IP address in the list and a first donor-DU BAP address corresponding to the IP address. The IP address may be an IPv4 address or an IPv6 address. The usage of the IP address may be F1-C, F1-U, non-F1 traffic, etc.

[0158] According to an embodiment of the ninth aspect, when setting an IP address for a border IAB node or a descendant node, it is possible to handle the case where the BAP address of a donor-DU is pseudo.

[0159] <Example of the tenth aspect> In an embodiment of the tenth aspect of the present application, an apparatus for setting information is provided, which corresponds to the method for setting information in the embodiment of the fourth aspect, the apparatus being applied in a donor central unit (CU), for example donor-CU1 or donor-CU2 in FIG.

[0160] 13 is a diagram showing an apparatus for setting information in an embodiment of the tenth aspect. As shown in FIG. 13, the apparatus 1300 includes:

[0161] A first sending unit 1301: Sends an RRC reconfiguration message, in which the RRC reconfiguration message indicates relevant information of a topology to which a default uplink BAP routing ID configured for an IAB node belongs.

[0162] In an embodiment of the tenth aspect, the IAB node may be a border IAB node, such as the IAB node 3 shown in Figure 2 or Figure 3. Moreover, the IAB node of the present application is not limited thereto, and the IAB node may be of other types.

[0163] The topology-related information may refer to topology information and / or cell group information, where the topology includes F1-terminated topology or non-F1-terminated topology, and the cell group information includes master cell group / secondary cell group (MCG / SCG) information.

[0164] In at least some embodiments, the RRC reconfiguration message may include first indication information, and the first indication information is used to indicate the topology to which the default uplink BAP routing ID belongs. For example, the first indication information is used to indicate that the topology to which the default uplink BAP routing ID belongs belongs to an F1 terminated topology or a non-F1 terminated topology. The first indication information may be mandatory only for border IAB nodes.

[0165] In at least some other embodiments, a donor central unit (donor-CU) that configures a default uplink BAP routing ID (defaultUL-BAP-RoutingID) field or configures a backhaul adaptation protocol configuration (bap-Config) that includes the default uplink BAP routing ID field can indicate the topology to which the default uplink BAP routing ID belongs, thereby using an implicit method to indicate which topology the default uplink BAP routing ID belongs to.

[0166] Wherein, when an F1 termination donor sets the default uplink BAP routing ID field or sets a bap-Config including the default uplink BAP routing ID field, the default uplink BAP routing ID belongs to the F1 termination topology; when a non-F1 termination donor sets the default uplink BAP routing ID field or sets a bap-Config including the default uplink BAP routing ID field, the default uplink BAP routing ID belongs to the non-F1 termination topology.

[0167] According to an embodiment of the tenth aspect, it is possible to indicate which topology a default uplink BAP routing ID configured for an IAB node belongs to.

[0168] <Example of the eleventh aspect> In an embodiment of the eleventh aspect of the present application, an information setting device is provided, which corresponds to the information setting method in the embodiment of the fifth aspect, which is applied to a donor central unit (CU), for example donor-CU1 or donor-CU2 as shown in FIG.

[0169] 14 is a diagram showing an apparatus for setting information in an embodiment of the eleventh aspect. As shown in FIG. 14, the apparatus 1400 includes:

[0170] A second sending unit 1401: Sends an RRC reconfiguration message, in which the RRC reconfiguration message indicates relevant information of a topology to which a default uplink BH RLC channel configured for an IAB node belongs.

[0171] In an embodiment of the eleventh aspect, the IAB node does not work in an EN-DC scenario, and may be a border IAB node, such as the IAB node 3 shown in Figure 2 or Figure 3. Also, the IAB node of the present application is not limited thereto, and the IAB node may be of other types.

[0172] The topology-related information may refer to topology information and / or cell group information, where the topology includes F1-terminated topology or non-F1-terminated topology, and the cell group information includes master cell group / secondary cell group (MCG / SCG) information.

[0173] In some embodiments, the RRC reconfiguration message may include second indication information, which is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or the second indication information is used to indicate that the default uplink BH RLC channel is directed to an RLC channel on a master cell group (MCG) or an RLC channel on a secondary cell group (SCG). The second indication information may be mandatory for a dual access node, or a node of an NR-DC, or a border IAB node.

[0174] In at least some other embodiments, the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) may point to an RLC channel of an MCG or point to an RLC channel of an SCG, and a donor central unit (donor-CU) that configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config that includes the default uplink BH RLC channel field can indicate the cell group to which the default uplink BH RLC channel points, thereby indicating related information of the topology to which the default uplink BH RLC channel belongs in an implicit manner.

[0175] In at least some other embodiments, when a donor that configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field is an MN, the default uplink BH RLC channel points to an RLC channel on an MCG, and when a donor that configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field is an SN, the default uplink BH RLC channel points to an RLC channel on an SCG. That is, for an IAB node (e.g., a border IAB node), the default uplink BH RLC channel points to an RLC channel on a backhaul link configured by a donor-CU that configures the field.

[0176] In at least one embodiment, when routing at the BAP sublayer, if the backhaul routing configuration has not been configured or reconfigured by the F1 Application Protocol (F1AP) since the default uplink BH RLC channel was last configured or reconfigured by the RRC, the IAB node selects an exit link based on a cell group corresponding to the default uplink BH RLC channel.

[0177] According to an embodiment of the eleventh aspect, it is possible to indicate information related to the topology to which the default uplink BH RLC channel configured for the IAB node belongs.

[0178] <Example of the twelfth aspect> In an embodiment of the twelfth aspect, an apparatus for setting information is provided, which corresponds to the method for setting information in the embodiment of the sixth aspect, the apparatus being applied in a donor central unit (CU), for example donor-CU1 as shown in FIG.

[0179] 15 is a diagram showing an apparatus for setting information in an embodiment of the twelfth aspect. As shown in FIG. 15, the apparatus 1500 includes:

[0180] A third sending unit 1501: sends an RRC reconfiguration message, in which the RRC reconfiguration message configures a first donor-DU BAP address for the IAB node, and the first donor-DU BAP address points to a donor distribution unit (donor-DU2) in the second topology.

[0181] In an embodiment of the twelfth aspect, the IAB node may be a descendant node of a boundary IAB node, for example, IAB node 4 shown in Figure 2 or Figure 3. Moreover, the IAB node of the present application is not limited thereto, and the IAB node may be of other types.

[0182] In at least one embodiment, the second topology refers to a topology different from the topology to which the IAB node belongs, for example, the IAB node belongs to an F1 terminating topology of a boundary node, and the second topology is a non-F1 terminating topology of a boundary node.

[0183] In at least one embodiment, the IP address configuration of the RRC reconfiguration message may include the first donor-DU BAP address.

[0184] In at least one embodiment, the CU may configure an uplink BAP routing ID for the IAB node, where the uplink BAP routing ID includes the first donor-DU BAP address.

[0185] 2 and 3, in an embodiment of the twelfth aspect, donor-CU1 can assign a first donor-DU BAP address to donor-DU2 in the topology of CU1, and the first donor-DU BAP address may be referred to as a pseudo BAP address or an alias address. CU1 can configure an uplink BAP routing ID for a descendant node, including an indication of the first donor-DU BAP address of donor-DU2.

[0186] Because the descendant node makes the corresponding selection based on the donor-DU BAP address in the uplink BAP routing ID during IP address selection, the BAP address for donor-DU2 in IAB-IP-AddressConfiguration is also the first donor-DU BAP address of donor-DU2, not the actual BAP address in CU2 topology of donor-DU2. Specifically, for the descendant node of the border IAB node, the BAP address of IAB-donor-DU in IP address configuration may be the first donor-DU BAP address, which points to a certain IAB-donor-DU (e.g., donor-DU2 in Figures 2 and 3) under the non-F1 terminating donor CU of the border IAB node.

[0187] In at least one embodiment, the RRC reconfiguration message sent by the CU may include an IAB IP address add / modify list (iab-IP-AddressToAddModList), which includes an IP address and a first donor-DU BAP address corresponding to the IP address. The IP address may be an IPv4 address or an IPv6 address. The usage of the IP address may be F1-C, F1-U, non-F1 traffic, etc.

[0188] According to an embodiment of the twelfth aspect, when setting an IP address for a border IAB node or a descendant node, it is possible to handle the case where the BAP address of a donor-DU is pseudo.

[0189] <Example of the thirteenth aspect> In an embodiment of the present application, a communication system is further provided, and the communication system may include an IAB node and a base station CU. At least one of the MT of the IAB node, the DU of the IAB node, and the base station CU may have the electronic device configuration shown in FIG.

[0190] Fig. 16 is a diagram showing the configuration of an electronic device (network device) in an embodiment of the present application. As shown in Fig. 16, an electronic device 1600 may include a processor 1610 (e.g., a central processing unit CPU) and a memory 1620, and the memory 1620 is connected to the processor 1610. The memory 1620 can store various data, and can further store a program 1630 for information processing, and can execute the program 1630 under the control of the processor 1610.

[0191] For example, the processor 1610 may be configured to execute a program to implement the methods in the embodiments of the first aspect to the embodiments of the sixth aspect.

[0192] 16, the electronic device 1600 may further include a transceiver (transmitter / receiver) 1640, an antenna 1650, etc., among which the functions of these components are the same as those of the prior art, and detailed description thereof will be omitted here. Note that the electronic device 1600 does not need to include all the components shown in Fig. 16, and the electronic device 1600 may further include components not shown in Fig. 16, and for this, reference can be made to the prior art.

[0193] In an embodiment of the present application, a computer program is further provided, which, when executed in an IAB node, causes the IAB node to perform the method described in the embodiments of the first to third aspects.

[0194] An embodiment of the present application further provides a computer program, where, when the program is executed in a CU node, the program causes the CU to perform the methods described in the embodiments of the fourth to sixth aspects.

[0195] In an embodiment of the present application, a storage medium storing a computer program is further provided, wherein the computer program causes an electronic device to perform the methods described in the embodiments of the first to sixth aspects.

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

[0197] Furthermore, one or more combinations of the functional blocks described in the drawings and / or one or more combinations of the functional blocks may be implemented as a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic component, 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 described in the drawings and / or one or more combinations of the 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 communicatively to a DSP, or any other configuration combination.

[0198] The preferred embodiments of the present invention have been described above. However, the present invention is not limited to such embodiments, and any changes to the present invention belong to the technical scope of the present invention as long as they do not depart from the spirit of the present invention.

[0199] Also, the following supplementary notes are disclosed regarding the above-described embodiments and the like.

[0200] <Method on the IAB Node Side> (Supplementary Note 1) A method for setting information applied to an IAB node, comprising: receiving an RRC reconfiguration message, wherein the RRC reconfiguration message instructs related information of a topology to which a default uplink BAP routing ID set for the IAB node belongs.

[0201] (Supplementary Note 2) The method according to Supplementary Note 1, comprising: the topology includes an F1 termination topology or a non-F1 termination topology.

[0202] (Supplementary Note 3) The method according to Supplementary Note 1, comprising: The method, wherein the RRC reconfiguration message includes first indication information, and the first indication information is used to indicate a topology to which the default uplink BAP routing ID belongs.

[0203] (Appendix 4) 2. The method according to claim 1, comprising: A method for indicating a topology to which a default uplink BAP routing ID belongs by a donor central unit (donor-CU) setting a default uplink BAP routing ID field (defaultUL-BAP-RoutingID) or setting a bap-Config including the default uplink BAP routing ID field.

[0204] (Appendix 5) 5. The method according to claim 4, A method according to the present invention, wherein when the default uplink BAP routing ID field is configured by an F1 termination donor, or a bap-Config including the default uplink BAP routing ID field is configured, the default uplink BAP routing ID belongs to an F1 termination topology.

[0205] (Appendix 6) 5. The method according to claim 4, A method according to the present invention, wherein when the default uplink BAP routing ID field is configured by a non-F1 termination donor, or a bap-Config including the default uplink BAP routing ID field is configured, the default uplink BAP routing ID belongs to a non-F1 termination topology.

[0206] (Appendix 7) 7. The method according to claim 5 or 6, A method for determining that an MN or SN is an F1 termination donor, and therefore an F1 termination donor or a non-F1 termination donor sets the default uplink BAP routing ID field or a bap-Config including the default uplink BAP routing ID field.

[0207] (Appendix 8) 8. The method according to claim 7, A method in which, if the IAB node establishes an NR-DC after establishing an F1 connection, the MN is an F1 termination donor, and, if the IAB node establishes an NR-DC before establishing an F1-C, the IAB node selects an MN or an SN as an F1 termination donor.

[0208] (Appendix 9) 8. The method according to claim 7, A method in which the default uplink BAP routing ID field or bap-Config is included in an RRC reconfiguration message transmitted by an SRB3, or when the default uplink BAP routing ID field or bap-Config is included in an mrdc-SecondaryCellGroup IE, the default uplink BAP routing ID field or bap-Config is configured by a secondary node (SN).

[0209] (Appendix 10) 8. The method according to claim 7, A method in which, when the default uplink BAP routing ID field or bap-Config is included in an RRC reconfiguration message transmitted by SRB1 and is not included in mrdc-SecondaryCellGroup IE, the default uplink BAP routing ID field or bap-Config is set by a master node (MN).

[0210] (Appendix 11) 2. The method according to claim 1, comprising: The method, wherein the IAB node is a border IAB node.

[0211] (Appendix 12) A method for configuring information, applied to an IAB node, comprising: A method comprising: receiving an RRC reconfiguration message, wherein the RRC reconfiguration message indicates relevant information of a topology to which a default uplink BH RLC channel configured for the IAB node belongs.

[0212] (Appendix 13) 13. The method of claim 12, further comprising: the RRC reconfiguration message comprises second indication information; The method, wherein the second indication information is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or the second indication information is used to indicate that the default uplink BH RLC channel is directed to an RLC channel on a master cell group or an RLC channel on a secondary cell group.

[0213] (Appendix 14) 13. The method of claim 12, further comprising: The method, wherein the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) that is set points to an RLC channel of an MCG or an RLC channel of an SCG.

[0214] (Appendix 15) 15. The method according to claim 14, A method for indicating a cell group to which a default uplink BH RLC channel is directed by a donor central unit (donor-CU) configuring a default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configuring a bap-Config including the default uplink BH RLC channel field.

[0215] (Appendix 16) 16. The method according to claim 15, A method in which, when an MN configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field, the default uplink BH RLC channel points to an RLC channel on an MCG.

[0216] (Appendix 17) 16. The method according to claim 15, When an SN configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field, the default uplink BH RLC channel points to an RLC channel on an SCG.

[0217] (Appendix 18) 18. The method according to claim 17, comprising: A method in which, when the default uplink BH RLC channel field or bap-Config is included in an RRC reconfiguration message transmitted by an SRB3, or the default uplink BH RLC channel field or bap-Config is included in an mrdc-SecondaryCellGroup IE, the default uplink BH RLC channel field or bap-Config is configured by a secondary node (SN).

[0218] (Appendix 19) 17. The method of claim 16, comprising: A method in which, when the default BH RLC channel field or bap-Config is included in an RRC reconfiguration message transmitted by SRB1 and is not included in an mrdc-SecondaryCellGroup IE, the default BH RLC channel field or bap-Config is configured by a master node (MN).

[0219] (Appendix 20) 20. The method according to any one of claims 12-19, comprising: A method, wherein the IAB node does not work in an EN-DC scenario.

[0220] (Appendix 21) 13. The method of claim 12, further comprising: A method for selecting an exit link based on a cell group corresponding to a default uplink BH RLC channel when routing at a BAP sublayer and a backhaul routing configuration has not been configured or reconfigured by an F1AP after the default uplink BH RLC channel was last configured or reconfigured by an RRC.

[0221] (Appendix 22) 13. The method of claim 12, further comprising: The method, wherein the IAB node is a border IAB node.

[0222] (Appendix 23) A method for configuring information, applied to an IAB node, comprising: A method comprising: receiving an RRC reconfiguration message, wherein the RRC reconfiguration message configures a first donor-DU BAP address for the IAB node, and the first donor-DU BAP address points to a donor distribution unit (DU2) in a second topology.

[0223] (Appendix 24) 24. The method according to claim 23, comprising: The IP address configuration of the RRC reconfiguration message includes the first donor-DU BAP address.

[0224] (Appendix 25) 24. The method according to claim 23, comprising: The method in which, when the IAB node receives an IAB IP address addition / change list (iab-IP-AddressToAddModList) included in the RRC reconfiguration message, the IAB node saves the IP addresses in the list and the first donor-DU BAP address corresponding to the IP addresses.

[0225] (Appendix 26) The method according to Appendix 23, wherein the uplink BAP routing ID is set for the IAB node, and the first donor-DU BAP address is included in the uplink BAP routing ID.

[0226] (Appendix 27) The method according to Appendix 24, further comprising the IAB node selects an IP address based on the first donor-DU BAP address; and performing uplink transmission via a second topology using the selected IP address.

[0227] (Appendix 28) The method according to Appendix 23, wherein the IAB node is a descendant node of a border IAB node.

[0228] (Appendix 29) The method according to Appendix 28, wherein the second topology is a non-F1 termination topology of the border IAB node.

[0229] <Method on the CU side> (Appendix 30) A method for setting information applied to a donor central unit (CU), comprising transmitting an RRC reconfiguration message, wherein the RRC reconfiguration message includes instructing related information of a topology to which a default uplink BAP routing ID set for an IAB node belongs.

[0230] (Appendix 31) 31. The method of claim 30, The method, wherein the topology comprises an F1 terminated topology or a non-F1 terminated topology.

[0231] (Appendix 32) 31. The method of claim 30, The method, wherein the RRC reconfiguration message includes first indication information, and the first indication information is used to indicate a topology to which the default uplink BAP routing ID belongs.

[0232] (Appendix 33) 31. The method of claim 30, A method for indicating a topology to which a default uplink BAP routing ID belongs by a donor central unit (donor-CU) setting a default uplink BAP routing ID field (defaultUL-BAP-RoutingID) or setting a bap-Config including the default uplink BAP routing ID field.

[0233] (Appendix 34) 34. The method of claim 33, A method in which, when the default uplink BAP routing ID field is configured or a bap-Config including the default uplink BAP routing ID field is configured by the CU as an F1 termination donor, the default uplink BAP routing ID belongs to an F1 termination topology.

[0234] (Appendix 35) 34. The method of claim 33, A method in which, when the default uplink BAP routing ID field is set or a bap-Config including the default uplink BAP routing ID field is set by the CU as a non-F1 termination donor, the default uplink BAP routing ID belongs to a non-F1 termination topology.

[0235] (Appendix 36) 31. The method of claim 30, The method, wherein the IAB node is a border IAB node.

[0236] (Appendix 37) A method for setting information, applied to a donor central unit (CU), comprising: A method comprising: sending an RRC reconfiguration message, wherein the RRC reconfiguration message indicates related information of a topology to which a default uplink BH RLC channel configured for an IAB node belongs.

[0237] (Appendix 38) 38. The method according to claim 37, comprising: the RRC reconfiguration message comprises second indication information; The method, wherein the second indication information is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or the second indication information is used to indicate that the default uplink BH RLC channel is directed to an RLC channel on a master cell group or an RLC channel on a secondary cell group.

[0238] (Appendix 39) 38. The method according to claim 37, comprising: The method, wherein the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) that is set points to an RLC channel of an MCG or an RLC channel of an SCG.

[0239] (Appendix 40) 39. The method of claim 39, A method for indicating a cell group to which a default uplink BH RLC channel is directed by a donor central unit (donor-CU) configuring a default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configuring a bap-Config including the default uplink BH RLC channel field.

[0240] (Appendix 41) 41. The method of claim 40, A method in which, when the CU as an MN configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field, the default uplink BH RLC channel points to an RLC channel on an MCG.

[0241] (Appendix 42) 41. The method of claim 40, The method, wherein when the CU as an SN configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field, the default uplink BH RLC channel points to an RLC channel on an SCG.

[0242] (Appendix 43) 37-42. The method according to claim 37, further comprising: A method, wherein the IAB node does not work in an EN-DC scenario.

[0243] (Appendix 44) 38. The method according to claim 37, comprising: A method for selecting an exit link based on a cell group corresponding to a default uplink BH RLC channel when routing at a BAP sublayer of the IAB node and a backhaul routing configuration has not been configured or reconfigured by an F1AP after the default uplink BH RLC channel was last configured or reconfigured by the RRC.

[0244] (Appendix 45) 38. The method according to claim 37, comprising: The method, wherein the IAB node is a border IAB node.

[0245] (Appendix 46) A method for setting information applied to a donor central unit (CU), comprising: A method comprising: sending an RRC reconfiguration message, wherein the RRC reconfiguration message configures a first donor-DU BAP address for an IAB node, and the first donor-DU BAP address points to a donor distribution unit (DU2) in a second topology.

[0246] (Appendix 47) 47. The method of claim 46, The IP address configuration of the RRC reconfiguration message includes the first donor-DU BAP address.

[0247] (Appendix 48) 47. The method of claim 46, further comprising: The method includes the CU sending an IAB IP address add / modify list (iab-IP-AddressToAddModList), the list including an IP address and the first donor-DU BAP address corresponding to the IP address.

[0248] (Appendix 49) 47. The method of claim 46, further comprising: The method includes the CU configuring an uplink BAP routing ID for the IAB node, and the uplink BAP routing ID includes the first donor-DU BAP address.

[0249] (Appendix 50) 47. The method of claim 46, The IAB node is a descendant node of a boundary IAB node.

[0250] (Appendix 51) 51. The method of claim 50, The second topology is a non-F1 terminated topology of the border IAB node.

Claims

1. An information setting device, applied to an IAB node, comprising: A first receiving unit for receiving an RRC reconfiguration message, The RRC reconfiguration message indicates relevant information of a topology to which a default uplink BAP routing ID configured for the IAB node belongs.

2. 2. The apparatus of claim 1, The topology includes an F1 terminated topology or a non-F1 terminated topology.

3. 2. The apparatus of claim 1, An apparatus for indicating a topology to which a default uplink BAP routing ID belongs by a donor central unit (donor-CU) that sets a default uplink BAP routing ID field (defaultUL-BAP-RoutingID) or sets a bap-Config that includes the default uplink BAP routing ID field.

4. 4. The apparatus of claim 3, When the default uplink BAP routing ID field is configured by an F1 termination donor, or a bap-Config including the default uplink BAP routing ID field is configured, the default uplink BAP routing ID belongs to an F1 termination topology.

5. 4. The apparatus of claim 3, A device, wherein when the default uplink BAP routing ID field is configured by a non-F1 termination donor, or a bap-Config including the default uplink BAP routing ID field is configured, the default uplink BAP routing ID belongs to a non-F1 termination topology.

6. 2. The apparatus of claim 1, The IAB node is a border IAB node.

7. An information setting device, applied to an IAB node, comprising: A second receiving unit for receiving an RRC reconfiguration message, The RRC reconfiguration message indicates relevant information of a topology to which a default uplink BH RLC channel to be configured for the IAB node belongs.

8. 8. The apparatus of claim 7, The default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) that is set points to an RLC channel of an MCG or an RLC channel of an SCG.

9. 9. The apparatus of claim 8, An apparatus for indicating a cell group to which a default uplink BH RLC channel is directed by a donor central unit (donor-CU) that sets a default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or sets a bap-Config that includes the default uplink BH RLC channel field.

10. 10. The apparatus of claim 9, When an MN configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field, the default uplink BH RLC channel points to an RLC channel on an MCG.

11. 10. The apparatus of claim 9, When an SN configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures a bap-Config including the default uplink BH RLC channel field, the default uplink BH RLC channel points to an RLC channel on an SCG.

12. 8. The apparatus of claim 7, The IAB node does not work in an EN-DC scenario.

13. 8. The apparatus of claim 7, An apparatus for selecting an exit link based on a cell group corresponding to a default uplink BH RLC channel when routing at a BAP sublayer and a backhaul routing configuration has not been configured or reconfigured by an F1AP after the default uplink BH RLC channel was last configured or reconfigured by an RRC.

14. 8. The apparatus of claim 7, The IAB node is a border IAB node.

15. An information setting device, applied to an IAB node, comprising: A third receiving unit for receiving an RRC reconfiguration message, The RRC reconfiguration message configures a first donor-DU BAP address for the IAB node, the first donor-DU BAP address pointing to a donor distribution unit (DU2) in a second topology.

16. 16. The apparatus of claim 15, The IP address configuration of the RRC reconfiguration message includes the first donor-DU BAP address.

17. 16. The apparatus of claim 15, When the IAB node receives an IAB IP address addition / modification list (iab-IP-AddressToAddModList) included in the RRC reconfiguration message, the IAB node stores an IP address in the list and the first donor-DU BAP address corresponding to the IP address.

18. 17. The apparatus of claim 16, The third receiving unit further comprises: Selecting an IP address based on the first donor-DU BAP address; and The apparatus performs uplink transmission via a second topology using the selected IP address.

19. 16. The apparatus of claim 15, The IAB node is a descendant node of a boundary IAB node.

20. 20. The apparatus of claim 19, The second topology is a non-F1 terminated topology of the border IAB node.

Images