Information configuration method, device and communication system

Abstract

An embodiment of the present invention provides an information configuration method, an apparatus and a communication system, the information configuration apparatus being applied to an IAB node, and including a first processing unit, the first processing unit being configured to match a topology in a backhaul routing configuration indicated by a first type indicator with a topology to which a BAP data protocol data unit (PDU) belongs.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE The present invention relates to the field of communications technology. [Background technology]

[0002] Integrated access and backhaul (IAB) realizes the function of radio relay in next generation radio access network (NG-RAN). Integrated access and backhaul node (IAB-node) supports access and backhaul via new radio (NR). The network side termination point of NR backhaul is called IAB-donor, which represents a network device (e.g., gNB) that supports IAB function.

[0003] An IAB node can be connected to one IAB-donor via single or multi-hop connections. These multi-hop connections form a topological structure of a Directed Acyclic Graph (DAG) with the IAB-donor as the root node. The IAB-donor performs centralized resource management, topology management, and routing management of the IAB network topology.

[0004] The IAB-node supports the function of a gNB-DU (distributed unit). The IAB-node DU is also called the IAB-DU, which is the endpoint of the radio access (NR access) interface between the user equipment (UE) and the next hop IAB-node, and is the endpoint of the F1 protocol to the gNB-CU (IAB-node: aggregation unit) at the IAB-donor. The IAB-DU can provide services to normal UEs and IAB child nodes. The IAB-DU realizes the function of a network side device, connects to a downstream child IAB-node, provides an NR air interface to the UE and the downstream child IAB-node, and establishes an F1 connection between the IAB donor-CU.

[0005] In addition to the gNB-DU functions, the IAB-node supports a part of the UE functions called IAB-MT (mobile termination). The IAB-MT includes, for example, physical layer, layer 2, RRC, and NAS functions for connecting to a gNB-DU of another IAB-node or IAB-donor, connecting to a gNB-CU at the IAB-donor, and connecting to the core network. The IAB-MT can support functions such as UE physical layer, access stratum (AS), radio resource control (RRC) layer, and non-access stratum (NAS) layer, and can connect to an IAB parent node.

[0006] The IAB-donor is a network-side end node that provides network access for the IAB-MT or UE via a backhaul or access link. The IAB-donor is further divided into an IAB-donor-CU (central unit) and an IAB-donor-DU. The IAB-DU and the IAB-donor-CU are connected via an F1 interface. In a network-only deployment scenario, the gNB and the IAB-donor-CU are connected via an Xn interface.

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

[0008] FIG. 1 is a schematic diagram of an example of an IAB parent-child node relationship. As shown in FIG. 1, in the IAB parent-child node relationship structure 10, an IAB-node 100 includes an IAB-MT functional unit 101 and an IAB-DU functional unit 102, and adjacent nodes at the interface of the IAB-DU functional unit 102 are called child nodes, and include, for example, child nodes 201, 202, and 203 shown in FIG. 1. The IAB-DU functional unit 102 and the child nodes 201, 202, and 203 can communicate with each other via an air interface (Uu). The adjacent nodes at the interface of the IAB-MT functional unit 101 are called parent nodes, and include, for example, parent nodes 301 and 302 shown in FIG. 1. The IAB-MT functional unit 101 and the parent nodes 301 and 302 can communicate with each other via an air interface (Uu).

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

[0010] The above description of the background art is merely for the purpose of more clearly and completely explaining the configurations of the present invention and for the understanding of those skilled in the art, and should not be construed as meaning that these configurations are well known to those skilled in the art just because they are described in the background art of the present invention. Summary of the Invention [Problem to be solved by the invention]

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

[0012] The IAB node determines BAP routing identifiers corresponding to different types of uplink IP packets initiated from the IAB node based on the routing identifier mapping information, and encapsulates BAP subheaders including the BAP routing identifier information for these uplink IP packets. The Donor-CU configures mappings from different types of downlink data packets to BAP routing identifiers for the donor-DU via F1AP signaling. The Donor-DU determines BAP routing identifiers corresponding to received downlink IP packets based on the routing identifier mapping information, and encapsulates BAP subheaders including the BAP routing identifiers for these downlink IP packets.

[0013] The BAP routing identifier includes a destination BAP address and a path identity from the IAB node to the donor-DU. The BAP address is also referred to as DESTINATION in the BAP header. One BAP address is configured for each IAB node and donor-DU.

[0014] At IAB node integration, the RRC may configure a default backhaul (BH) RLC channel and a default BAP routing identifier for non-F1-U traffic. These configurations may be updated in topology adaptation scenarios.

[0015] In the upstream direction, the IAB-donor-CU configures for the IAB node a mapping relationship between upstream F1 and non-F1 traffic from the IAB node and the appropriate BAP routing ID, next-hop BAP address, and BH RLC channel. A specific mapping relationship is configured for each F1-U GTP-U tunnel, non-UE-related F1AP message, UE-related F1AP message, and non-F1 traffic.

[0016] An IAB node can have redundant paths to different IAB-donor-CUs. When an IAB node operates in Stand Alone (SA) mode, it may allow the IAB-MT and two parent nodes to have backhaul links simultaneously via NR-NR Dual Connectivity (NR-DC) to achieve backhaul path redundancy. Two parent nodes can be connected to different IAB-donor-CUs, which can control the establishment and release of redundant paths through the two parent nodes. The gNB-DU function of the parent node, together with the corresponding IAB-donor-CU, plays the role of the master node (MN) and / or secondary node (SN) of the IAB-MT. The NR-DC framework, e.g., procedures related to the master cell group (MCG) / secondary cell group (SCG), are used to configure dual radio connectivity from the IAB node to the parent node.

[0017] 2 is a schematic diagram of an example of a network structure of inter-donor topology redundancy (or inter-CU topology redundancy). FIG. 3 is a schematic diagram of an example of inter-donor partial migration.

[0018] As shown in FIG. 2, node 3 is referred to as a boundary IAB node. A boundary IAB node means that its RRC interface and F1 interface terminate on different IAB-donor-CUs. A boundary IAB node applies to partial migration, inter-donor topology redundancy, and inter-donor RLF (radio link failure) recovery. As shown in FIG. 2, the DU of node 3 terminates on CU1, and the MT of node 3 has interfaces on both CU1 and CU2, so it falls under the definition of a boundary IAB node. A descendant IAB node means a node connected to the network via 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 means a donor-CU that terminates the F1 interfaces of a boundary IAB node and a descendant node, for example, donor-CU1 is an F1 terminating node, i.e., the F1 interfaces of IAB-DU3 and IAB-DU4 in FIG. 2 terminate on donor-CU1. A non-F1-terminating donor node means a CU that does not terminate the F1 interface of a border IAB node and a descendant node and functions as a donor, such as donor-CU2 in FIG. 2. In the topology redundancy scenario shown in FIG. 2, a border node (i.e., node 3) is a dual-connected node. In the donor-to-donor topology redundancy scenario, a border IAB node (i.e., IAB node 3) and a descendant node can communicate with CU1 via a first path and a second path, respectively.

[0019] In FIG. 3, the IAB-MT of the border IAB node (i.e., IAB-MT3) can migrate to a parent node under a different IAB-donor-CU (e.g., migrate to a parent node under Donor-CU2). In this 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. The SA mode can support inter-donor partial migration.

[0020] When an IAB node in SA mode declares backhaul link RLF, RLF recovery can be done at the parent node under a different IAB-donor-CU. Similar to inter-donor partial migration, the collocated IAB-DU and the IAB-DU of the descendant node can maintain F1 connectivity with the original IAB-donor-CU.

[0021] As shown in Figure 3, IAB node 3 is a border IAB node, and IAB-MT3 is changed from a single connection to parent node IAB node 1 to a single connection to parent node IAB node 2. IAB-DU3 and its child node IAB node 4 still have an F1 connection with donor-CU1, but the path taken by this F1 connection goes through IAB node 2 and finally to donor-CU1. In the donor-to-donor partial migration scenario shown in Figure 3, the border node (node ​​3) is a transition node. The donor-to-donor partial migration scenario is similarly applicable to partial RLF recovery.

[0022] The inventors of the present invention have found that a border IAB node belongs to two IAB topologies, and in the prior art, when configuring uplink traffic mapping for an IAB node or performing BAP routing, the routing ID does not indicate which topology it belongs to, which leads to collision or ambiguity of the routing ID. Also, when performing BH RLC channel mapping, the topology is not taken into account, which makes the link indicator unclear and makes it impossible to perform BH RLC channel mapping correctly.

[0023] The embodiments of the present invention provide an information configuration method, an apparatus and a communication system for matching a topology in a backhaul routing configuration indicated by a first type indicator with a topology to which a BAP data protocol data unit (PDU) belongs, so as to select an appropriate routing entry for the BAP data PDU. [Means for solving the problem]

[0024] In one aspect of an embodiment of the present invention, there is provided an information configuring device, applied to an IAB node, comprising a first processing unit, the first processing unit being configured to match a topology in a backhaul routing configuration indicated by a first type indicator with a topology to which a BAP data protocol data unit (PDU) belongs.

[0025] Another aspect of an embodiment of the present invention provides an information configuring apparatus, applied to an IAB node, comprising: a second processing unit, the second processing unit configured to receive Uplink Traffic to Routing ID Mapping Configuration information, the configuration information comprising a second type indicator, the second type indicator being used to indicate whether an entry or a BAP Routing ID in the entry belongs to a topology of a non-F1 termination donor.

[0026] Another aspect of an embodiment of the present invention provides an information configuring device, applied to an IAB node, comprising a third processing unit, the third processing unit configured to perform BH RLC channel mapping for BAP data packets from a collocated BAP entity or perform BH RLC channel mapping for BAP SDUs from an upper layer based on topology information of a link to which a BH RLC channel belongs.

[0027] The advantageous effects of the embodiment of the present invention are as follows: A suitable routing entry can be selected for the BAP data PDU.

[0028] As shown in the following description and drawings, certain embodiments of the present invention are disclosed in detail to show the manner in which the principles of the present invention can be employed. However, the scope of the embodiments of the present invention is not limited to these. The embodiments of the present invention include modifications, alterations and equivalents within the spirit and scope of the appended claims.

[0029] Features described and / or shown 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 replaced by features in the other embodiments.

[0030] It should be noted that in this text, the term "including / having" means the presence of a feature, element, step or component, and does not exclude the presence or addition of one or more other features, elements, steps or components. [Brief description of the drawings]

[0031] Elements and features depicted in one drawing and one embodiment of the present invention may be combined with elements and features shown in one or more drawings or embodiments, and in the drawings, like reference numerals may designate corresponding elements in multiple drawings and may designate corresponding elements used in more than one embodiment. [Figure 1] FIG. 2 is a schematic diagram of an example of an IAB parent-child node relationship. [Diagram 2] FIG. 1 is a schematic diagram of an example of a network structure with inter-donor topology redundancy. [Diagram 3] FIG. 1 is a schematic diagram of an example of donor-to-donor moiety transfer. [Figure 4] FIG. 2 is a schematic diagram of an example of an information configuration method according to the first embodiment; [Diagram 5] FIG. 11 is a schematic diagram of an example of an information configuration method according to a second embodiment. [Figure 6] FIG. 13 is a schematic diagram of an example of an information configuration method according to a third embodiment. [Figure 7] FIG. 13 is a schematic diagram of an example of an information configuration method according to a fourth embodiment. [Figure 8] FIG. 13 is a schematic diagram of an example of an information configuration device according to a fifth embodiment. [Figure 9] FIG. 23 is a schematic diagram of an example of an information configuration device according to a sixth embodiment. [Figure 10] FIG. 23 is a schematic diagram of an example of an information configuration device according to a seventh embodiment. [Figure 11] 1 is a schematic diagram illustrating an example of a configuration of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0032] The above and other features of the present invention will become apparent from the following description. In the specification and drawings, specific embodiments of the present invention are disclosed in detail, and some of the embodiments in which the principles of the present invention can be employed are shown. However, the present invention is not limited to the described embodiments. The present invention includes all modifications, variations, and equivalents within the scope of the appended claims.

[0033] In embodiments of the present invention, the terms "first", "second", etc. are used in the title to distinguish different elements, but do not represent the spatial arrangement or temporal order of these elements, and these elements are not limited to these terms. The term "and / or" includes any and all combinations of one or more of the terms listed in the associated list. The terms "including", "comprising", "having", etc. refer to the presence of listed features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.

[0034] In the embodiments of the present invention, the singular forms "a", "the", etc., include the plural forms and should be understood broadly as "one kind" or "a class", and are not limited to "one". In addition, the term "said" should be understood to include both the singular and the plural forms, unless the context clearly indicates otherwise. In addition, the term "described in" should be understood to mean "described at least in part", and the term "based on" should be understood to mean "based at least in part on", unless the context clearly indicates otherwise.

[0035] 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, for example, new radio (NR), Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0036] Additionally, communications between devices in a communication system may occur according to any generation of communication protocols, including, but not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, and new radio (NR), and / or other currently known or future developed communication protocols.

[0037] In the embodiment of the present invention, the term "network device" refers to a device in a communication system, for example, allowing a terminal device to access the communication system and providing a service to the terminal device. The network device may include, but is not limited to, an access backhaul integration node (IAB-node), a relay device (relay), a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobility management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0038] Here, the base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), and a 5G base station (gNB), etc., as well as a Remote Radio Head (RRH), a Remote Radio Unit (RRU), a relay, or a low power node (e.g., femto, pico, etc.). Also, the term "base station" may include some or all of these functions, and each base station may provide communication coverage for a particular geographic area. The term "cell" may refer to a base station and / or its coverage area depending on the context in which the term is used.

[0039] In the embodiment of the present invention, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to an apparatus that accesses a communication network and receives a network service via, for example, a network device. The terminal apparatus may be fixed or mobile, and may be called a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a mobile termination (MT), a station, etc.

[0040] Here, the terminal device may include, but is not limited to, a cellular phone, a personal digital assistant (PDA), a wireless modulation / demodulation device, a wireless communication device, a handheld device, a machine-type communication device, a laptop computer, a cordless phone, a smartphone, a smart watch, a digital camera, and the like.

[0041] Also, for example, in a scenario such as the Internet of Things (IoT), the terminal device may be an instrument or device that performs monitoring or measurement, and may include, but is 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.

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

[0043] In the embodiment of the present invention, 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 message, or referred to as an RRC information element (RRC IE). The higher layer signaling may be, for example, F1-C signaling, or referred to as an F1AP protocol. However, the present invention is not limited thereto.

[0044] In the present invention, the deployment scenario of a multi-hop IAB network is taken as an example to describe each embodiment. Here, multiple terminal devices (e.g., UEs) are connected to an IAB-donor through a multi-hop IAB node, and finally access a network. The network is, for example, a 5G network. Note that each embodiment of the present invention is not limited to the above scenario.

[0045] In each embodiment of the present invention, the IAB topology refers to a combination of all IAB nodes and IAB-donor-DUs that are connected to each other via backhaul links and whose F1 interfaces and / or RRCs are terminated in the same IAB-donor-CU. For example, in Fig. 2 and Fig. 3, Donor-DU1, IAB node 1, IAB node 3, and IAB node 4 are nodes managed by Donor-CU1, and the IAB topology configured by these nodes and Donor-CU1 is referred to as a first topology. Donor-DU2, IAB node 2, and IAB node 3 are nodes managed by Donor-CU2, and the IAB topology configured by these nodes and Donor-CU2 is referred to as a second topology. A border node (i.e., IAB node 3) belongs to both the first topology and the second topology.

[0046] <Example 1> In the backhaul routing configuration (BH Routing Configuration, i.e., BAP routing table) of the BAP sublayer, each entry includes a BAP routing identifier, a next-hop BAP address, and a first type indicator, which indicates whether the entry belongs to a topology of a non-F1 terminating donor. The first type indicator is configured by a Non-F1-terminating Topology Indicator IE in the F1AP signaling.

[0047] The first type indicator may be a Boolean variable. For example, if a non-F1 terminated topology indicator is configured in F1AP signaling for the entry, the first type indicator is a first value. For example, the first value is true. On the other hand, if a non-F1 terminated topology indicator is not configured in F1AP signaling for the entry, the first type indicator is a second value. For example, the second value is false.

[0048] The first type indicator may be an enumerated variable and indicate a specific topology type, for example, if a non-F1 terminated topology indicator is configured in F1AP signaling for the entry, the first type indicator indicates "non-F1 terminated topology", while if a non-F1 terminated topology indicator is not configured in F1AP signaling for the entry, the first type indicator indicates "F1 terminated topology".

[0049] In the scenario of Fig. 2, a border node (e.g., IAB node 3) is connected to different IAB topologies, and the uplink BAP routing identifier used by the border node may have BAP routing identifiers leading to two IAB topologies respectively (i.e., leading to donor-DUs under two different donor-CUs). Since the BAP routing identifiers of different IAB topologies are configured and managed by the respective donor-CUs, the BAP routing identifiers belonging to different IAB topologies may conflict. Similarly, in the scenario of Fig. 3, the border node may have conflicts between the uplink BAP routing identifier of the non-F1-terminated topology and the downlink BAP routing identifier of the F1-terminated topology.

[0050] To solve the above or similar problems, a first embodiment of the present invention provides an information configuration method, which is applied to an IAB node.

[0051] 4 is a schematic diagram of an example of an information configuration method according to Example 1. As shown in FIG. 4, the method includes the following steps:

[0052] Step 401: Match a topology in a backhaul routing configuration indicated by a first type indicator with a topology to which a BAP data protocol data unit (PDU) belongs.

[0053] In the first embodiment, the IAB node may be a border IAB node, for example, the IAB node 3 shown in Fig. 2 or Fig. 3. However, the IAB node of the present invention is not limited thereto, and may be another type of IAB node.

[0054] In step 401, when BAP routing is performed at the border IAB node, it is necessary to match the topology in the backhaul routing configuration indicated by the first type indicator with the topology to which the BAP data PDU (protocol data unit) belongs, so as to select a suitable routing entry for the BAP data PDU to perform routing. The topology to which the BAP data PDU belongs means the topology to which the PDU needs to be routed or to select an egress link, and may be regarded as an egress topology.

[0055] In at least some embodiments, when a BAP entity needs to transmit a BAP data PDU, if the BAP address of an entry in the backhaul routing configuration matches the DESTINATION field, the path identifier of the BAP address of the entry is the same as the PATH field of the BAP address, the topology obtained by the first type indicator of the entry is the same as the topology of the BAP data PDU, and the egress link corresponding to the next hop BAP address is available, then the egress link corresponding to the next hop BAP address of the entry is selected.

[0056] In at least some other embodiments, when the above conditions are not met, i.e., when there is no entry in the backhaul routing configuration that matches any of the destination field, the path field, and the topology, or when the egress link corresponding to the matching entry is unavailable, select an entry from the at least one entry when there is at least one entry in the backhaul routing configuration that has a BAP address that matches the "destination" field, the topology acquired by the first type indicator of the entry is the same as the topology of the BAP data PDU, and the egress link corresponding to the next-hop BAP address is available. The BAP address of the selected entry matches the "destination" field, the topology acquired by the first type indicator of the entry is the same as the topology of the BAP data PDU, and the egress link corresponding to the next-hop BAP address is available. Then, select the egress link corresponding to the next-hop BAP address of the entry.

[0057] For example, the standard routing procedure part of the BAP sublayer in TS 38.340 may be extended, for example as shown in Table 1.

[0058] [Table 1] Because the border IAB nodes belong to multiple topologies and the BAP routing identifier, path identifier, BAP address, etc. are unique only within a topology, for the uniqueness of the selected routing, in the backhaul routing configuration, for the same topology, i.e., for the same first type indicator, each combination of BAP address and BAP path indicator can have at most one entry. In order to perform local rerouting, in the backhaul routing configuration, for the same first type indicator, the same BAP address may have multiple entries.

[0059] For example, the standard routing procedure part of the BAP sublayer in TS 38.340 may be extended, for example as shown in Table 2.

[0060] [Table 2] Example 1 illustrates the case where the IAB node is an intermediate node of traffic (i.e., the IAB node receives and forwards data from other nodes). According to example 1, an appropriate routing entry and egress link can be selected for the BAP data PDU.

[0061] <Example 2> In the upstream direction, the IAB-donor-CU configures for the IAB node a mapping relationship between upstream F1 and non-F1 traffic from the IAB node (i.e., the IAB node is the initial node of the uplink traffic), the appropriate BAP routing ID, the next-hop BAP address, and the BH RLC channel. A specific mapping relationship is configured for each F1-U GTP-U tunnel, non-UE related F1AP message, UE related F1AP message, and non-F1 traffic. Since the border IAB node belongs to multiple topologies, the uplink mapping configuration of the border IAB node needs to indicate which specific topology it belongs to in the backhaul information (BH Information) IE in the F1AP signaling. For example, if a non-F1 terminated topology indicator is configured, it indicates that the next-hop BAP address and the egress BH RLC channel identifier in the IE belong to the non-F1 terminated topology of the border IAB node.

[0062] In the Uplink Traffic to Routing ID Mapping Configuration of the BAP sublayer, each entry contains a traffic type designator and a BAP routing identifier (ID). Because a border node belongs to multiple topologies, the BAP routing identifier can be ambiguous.

[0063] To solve the above problem or similar problems, embodiment 2 provides an information configuration method, which is applied to an IAB node.

[0064] 5 is a schematic diagram of an example of an information configuration method according to Example 2. As shown in FIG. 5, the method includes the following steps:

[0065] Step 501: Receive uplink traffic to routing ID mapping configuration information, the configuration information including a second type indicator, the second type indicator is used to indicate whether an entry or a BAP routing ID in the entry belongs to a topology of a non-F1 termination donor.

[0066] In the second embodiment, the IAB node may be a border IAB node, for example, the IAB node 3 shown in Fig. 2 or Fig. 3. However, the IAB node of the present invention is not limited thereto and may be another type of node.

[0067] In step 501, a second type indicator may be added to each mapping relationship (i.e., each entry), and the second type indicator is used to indicate whether the BAP routing ID (in other words, the entry) belongs to a topology of a non-F1 terminated donor. The second type indicator may be indicated (or configured) by a non-F1 terminated topology indicator IE in F1 application protocol (AP) signaling.

[0068] In at least some embodiments, the second type indicator may be a Boolean variable, e.g., if a non-F1 terminated topology indicator is configured in F1AP signaling for the entry, the second type indicator has a first value, e.g., the second type indicator is true, whereas if a non-F1 terminated topology indicator is not configured in F1AP signaling for the entry, the second type indicator has a second value, e.g., the second type indicator is false.

[0069] In at least some other embodiments, the second type indicator may be an enumerated variable and used to indicate a specific topology type, for example, if a non-F1 terminated topology indicator is configured in F1AP signaling for the entry, the second type indicator is "non-F1 terminated topology", whereas if no non-F1 terminated topology indication is configured in F1AP signaling for the entry, the second type indicator is "F1 terminated topology".

[0070] For example, the BAP sublayer standard may be extended in TS 38.340. As shown in Table 3, an extension may be made in the selection procedure of the BAP routing ID of an IAB node.

[0071] [Table 3] In at least some embodiments, when an IAB node receives a service data unit (BAP SDU) from upper layers and needs to transmit the BAP SDU in an upstream direction, the BAP entity may explicitly determine the topology over which the data needs to be transmitted based on a mapping configuration of uplink traffic to routing IDs, and perform routing on the corresponding topology.

[0072] In at least one specific embodiment, when an IAB node receives a BAP SDU (service data unit) from an upper layer and needs to transmit it in an upstream direction, the BAP entity selects an entry from a mapping configuration of uplink traffic to routing IDs based on a traffic type designator corresponding to the BAP SDU, and then determines a topology of a BAP data PDU corresponding to the BAP SDU based on a second type indicator in the entry. That is, if the second type indicator corresponding to the selected entry or the BAP routing ID (i.e., the BAP address and the BAP path ID) indicates a non-F1 terminated topology, the BAP data PDU corresponding to the BAP SDU is data belonging to a non-F1 terminated donor topology, while if the second type indicator corresponding to the selected BAP routing ID indicates an F1 terminated topology, the BAP data PDU corresponding to the BAP SDU is data belonging to an F1 terminated donor topology.

[0073] For example, the BAP sublayer standard may be extended in TS 38.340. As shown in Table 4, an extension may be made in the selection procedure of the BAP routing ID of an IAB node.

[0074] [Table 4] In the second embodiment, the BAP entity obtains the BAP routing ID and topology information of the BAP data PDU through the BAP routing ID selection procedure, and then can perform BAP routing according to the method according to the first embodiment.

[0075] <Example 3> For BAP data packets received from a collocated BAP entity, i.e., BAP data packets requiring forwarding, the transmitter of the BAP entity performs mapping to an Egress BH RLC channel based on a BH RLC Channel Mapping Configuration, whose entries include an ingress link identifier, an egress link identifier, an ingress BH RLC channel identifier, and an egress BH RLC channel identifier.

[0076] In the donor-to-donor routing scenario of Figures 2 and 3, when a border IAB node performs BH RLC channel mapping for BAP data packets from collocated BAP entities, if the border IAB node does not take into account the topology information of the link to which the BH RLC channel belongs, link selection and BH RLC channel mapping become unclear.

[0077] To solve the above problem or similar problems, embodiment 3 provides an information configuration method, which is applied to an IAB node.

[0078] 6 is a schematic diagram of an example of an information configuration method according to Example 3. As shown in FIG. 6, the method includes the following steps:

[0079] Step 601: The IAB node performs BH RLC channel mapping for a BAP data packet from a collocated BAP entity based on the topology information of the link to which the BH RLC channel belongs. In step 601, when the IAB node performs BH RLC channel mapping, it needs to select a suitable mapping entry and egress BH RLC channel for the BAP data PDU by matching the topology to which the ingress link in the backhaul RLC channel mapping configuration belongs with the topology to which the ingress link of the BAP data PDU belongs, and matching the topology to which the egress link in the backhaul RLC channel mapping configuration belongs with the topology to which the selected egress link belongs.

[0080] In the third embodiment, the IAB node may be a border IAB node, for example, the IAB node 3 shown in Fig. 2 or Fig. 3. However, the IAB node of the present invention is not limited thereto and may be other types of nodes.

[0081] In step 601, for a BAP data PDU received from an ingress BH RLC channel on an ingress link, after an egress link is selected according to a BAP sublayer routing method, if there is an entry in the BH RLC channel mapping configuration, and the ingress BH RLC channel identifier of the entry matches the ingress BH RLC channel of the BAP data PDU, the ingress link identifier of the entry matches the ingress link of the BAP data PDU, the topology to which the ingress link identifier of the entry belongs is the same as the topology to which the ingress link of the BAP data PDU belongs, the egress link identifier of the entry corresponds to the selected egress link, and the topology to which the egress link identifier of the entry belongs is the same as the topology to which the selected egress link belongs, select an egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry.

[0082] For example, the BAP sublayer standard may be extended in TS 38.340. In an IAB node, the extension shown in Table 5 may be performed for BH RLC channel mapping for BAP data packets from a collocated BAP entity.

[0083] [Table 5] In Example 3, the IAB node may be an intermediate node of traffic, and when performing BH RLC channel mapping for BAP data packets from collocated BAP entities, it can avoid ambiguity in link selection and BH RLC channel mapping by taking into account topology information of the link to which the BH RLC channel belongs.

[0084] <Example 4> When an IAB node receives a BAP SDU from upper layers, the BAP entity may perform mapping to an egress BH RLC channel based on an Uplink Traffic to BH RLC Channel Mapping Configuration, where an entry in the Uplink Traffic to BH RLC Channel Mapping Configuration includes a traffic type designator, an egress link identifier, and an egress BH RLC channel identifier.

[0085] In the donor-to-donor routing scenario of Figures 2 and 3, when a border IAB node performs BH RLC channel mapping for a BAP SDU from an upper layer, if the border IAB node does not take into account the topology information of the link to which the BH RLC channel belongs, link selection and BH RLC channel mapping will be unclear.

[0086] To solve the above problem or similar problems, in embodiment 4, an information configuration method is provided, which is applied to an IAB node.

[0087] 7 is a schematic diagram of an example of an information configuration method according to Example 4. As shown in FIG. 7, the method includes the following steps:

[0088] Step 701: The IAB node performs BH RLC channel mapping for the BAP SDU from the upper layer based on the topology information of the link to which the BH RLC channel belongs. In step 701, when the IAB node performs BH RLC channel mapping, it needs to select a suitable mapping entry and egress BH RLC channel for the BAP SDU by matching the topology to which the egress link in the mapping configuration of the uplink traffic to the backhaul RLC channel belongs and the topology to which the selected egress link belongs.

[0089] In the fourth embodiment, the IAB node may be a border IAB node, for example, the IAB node 3 shown in Fig. 2 or Fig. 3. However, the IAB node of the present invention is not limited thereto and may be other types of nodes.

[0090] In step 701, when the IAB node receives a BAP SDU from an upper layer and transmits it in the upstream direction, after the BAP entity selects an egress link according to the BAP sublayer routing method, for the BAP SDU in which the F1-U data packet is encapsulated, if there is an entry in the mapping configuration of uplink traffic to a BH RLC channel, the traffic type designator of the entry corresponds to the destination IP address and TEID (Tunnel Endpoint Identifier) ​​of the BAP SDU, the egress link identifier of the entry corresponds to the selected egress link, and the topology to which the egress link identifier of the entry belongs is the same as the topology to which the selected egress link belongs, then select an egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry. Similarly, for a BAP SDU in which a non-F1-U data packet is encapsulated, if an entry exists in the mapping configuration of uplink traffic to BH RLC channels, the traffic type specifier of the entry corresponds to the traffic type of the BAP SDU, the egress link identifier of the entry corresponds to the selected egress link, and the topology to which the egress link identifier of the entry belongs is the same as the topology to which the selected egress link belongs, select the egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry.

[0091] For example, the BAP sublayer standard may be extended in TS 38.340. In the IAB node, the extension shown in Table 6 may be performed for the BH RLC channel mapping procedure for the BAP SDU from the upper layer.

[0092] [Table 6] In embodiment 4, the IAB node may be the initial node of uplink traffic, and when performing BH RLC channel mapping for the BAP SDU from the upper layer, the IAB node can avoid ambiguity in link selection and BH RLC channel mapping by considering the topology information of the link to which the BH RLC channel belongs.

[0093] <Example 5> A fifth embodiment of the present invention provides an information configuration apparatus, which corresponds to the information configuration method of the first embodiment. The apparatus is applied to an IAB node.

[0094] 8 is a schematic diagram of an example of an information configuration device according to Example 5. As shown in FIG. 8, an information configuration device 800 includes a first processing unit 801.

[0095] The first processing unit 801 is configured to match a topology in a backhaul routing configuration indicated by the first type indicator with a topology to which a BAP data protocol data unit (PDU) belongs.

[0096] In the fifth embodiment, the IAB node may be a border IAB node, for example, the IAB node 3 shown in Fig. 2 or Fig. 3. However, the IAB node of the present invention is not limited thereto and may be other types of nodes.

[0097] In Example 5, when performing BAP routing, an appropriate routing entry can be selected for routing the BAP data PDU (protocol data unit) by matching the topology in the backhaul routing configuration indicated by the first type indicator with the topology to which the BAP data PDU belongs.

[0098] In at least some embodiments, when a BAP entity needs to transmit a BAP data PDU, if the BAP address of an entry in the backhaul routing configuration matches the DESTINATION field, the path identifier of the BAP address of the entry is the same as the PATH field of the BAP address, the topology obtained by the first type indicator of the BAP address of the entry is the same as the topology of the BAP data PDU, and the egress link corresponding to the next hop BAP address of the BAP address of the entry is available, then the egress link corresponding to the next hop BAP address is selected.

[0099] In at least some other embodiments, when the above conditions are not met, i.e., there is no BAP address of an entry in the backhaul routing configuration that matches the destination field, path field, and topology, or the egress link corresponding to the matching entry is unavailable, select an entry from the at least one entry when there is at least one entry in the backhaul routing configuration that has a BAP address that matches the "destination" field, the topology acquired by the first type indicator of the entry is the same as the topology of the BAP data PDU, and the egress link corresponding to the next hop BAP address is available. Then, select an egress link corresponding to the next hop BAP address of the entry.

[0100] Because the border IAB nodes belong to multiple topologies and the BAP routing identifier, path identifier, BAP address, etc. are unique only within a topology, for the uniqueness of the selected path, in the backhaul routing configuration, for the same topology, i.e., for the same first type indicator, each combination of BAP address and BAP path indicator can have at most one entry. For local rerouting, in the backhaul routing configuration, for the same first type indicator, the same BAP address can have multiple entries.

[0101] Example 5 illustrates a scenario in which the IAB node is an intermediate node of traffic (i.e., the IAB node receives and forwards data from another node), and according to example 5, a suitable routing entry can be selected for the BAP data PDU.

[0102] <Example 6> A sixth embodiment of the present invention provides an information configuration device, which is applied to an IAB node and corresponds to the information configuration method of the second embodiment.

[0103] 9 is a schematic diagram of an example of an information configuration device according to Example 6. As shown in FIG.

[0104] The second processing unit 901 is configured to receive Uplink Traffic to Routing ID Mapping Configuration information, the configuration information including a second type indicator, the second type indicator being used to indicate whether an entry or a BAP Routing ID in the entry belongs to a topology of a non-F1 termination donor.

[0105] In the sixth embodiment, the IAB node may be a border IAB node, for example, the IAB node 3 shown in Fig. 2 or Fig. 3. However, the IAB node of the present invention is not limited thereto and may be other types of nodes.

[0106] In at least one embodiment, a second type indicator may be added to each mapping relationship (i.e., each entry), and the second type indicator is used to indicate whether the BAP routing ID (in other words, the entry) belongs to a topology of a non-F1 terminated donor. The second type indicator may be indicated (or configured) by a non-F1 terminated topology indicator IE in F1 application protocol (AP) signaling.

[0107] In at least some embodiments, the second type indicator may be a Boolean variable, e.g., if a non-F1 terminated topology indicator is configured in F1AP signaling for the entry, the second type indicator has a first value, e.g., the second type indicator is true, whereas if a non-F1 terminated topology indicator is not configured in F1AP signaling for the entry, the second type indicator has a second value, e.g., the second type indicator is false.

[0108] In at least some other embodiments, the second type indicator may be an enumerated variable and used to indicate a specific topology type, for example, if a non-F1 terminated topology indicator is configured in F1AP signaling for the entry, the second type indicator is "non-F1 terminated topology", whereas if no non-F1 terminated topology indication is configured in F1AP signaling for the entry, the second type indicator is "F1 terminated topology".

[0109] In at least some embodiments, when an IAB node receives a service data unit (BAP SDU) from upper layers and needs to transmit the BAP SDU in an upstream direction, the BAP entity may explicitly determine the topology over which the data needs to be transmitted based on a mapping configuration of uplink traffic to routing IDs, and perform routing on the corresponding topology.

[0110] In at least one specific embodiment, when an IAB node receives a BAP SDU (service data unit) from an upper layer and needs to transmit it in an upstream direction, the BAP entity selects an entry from a mapping configuration of uplink traffic to routing IDs based on a traffic type designator corresponding to the BAP SDU, and then determines a topology of a BAP data PDU corresponding to the BAP SDU based on a second type indicator in the entry. That is, if the second type indicator corresponding to the selected entry or the BAP routing ID (i.e., the BAP address and the BAP path ID) indicates a non-F1 terminated topology, the BAP data PDU corresponding to the BAP SDU is data belonging to a non-F1 terminated donor topology, while if the second type indicator corresponding to the selected BAP routing ID indicates an F1 terminated topology, the BAP data PDU corresponding to the BAP SDU is data belonging to an F1 terminated donor topology.

[0111] In the sixth embodiment, the BAP entity obtains the BAP routing ID and topology information of the BAP data PDU through the BAP routing ID selection procedure, and then can perform BAP routing according to the method according to the first embodiment.

[0112] <Example 7> Example 7 provides a configuration information device, which is applied to an IAB node and corresponds to the configuration information method of Example 3 or Example 4.

[0113] 10 is a schematic diagram of an example of an information configuration device according to Example 7. As shown in FIG.

[0114] The third processing unit 1001 is configured to perform BH RLC channel mapping for BAP data packets from a collocated BAP entity, or perform BH RLC channel mapping for BAP SDUs from an upper layer, based on topology information of the link to which the BH RLC channel belongs.

[0115] In the seventh embodiment, the IAB node may be a border IAB node, such as the IAB node 3 shown in Fig. 2 or Fig. 3. However, the IAB node of the present invention is not limited thereto and may be other types of nodes.

[0116] In at least one embodiment, after an egress link is selected according to the BAP sublayer routing device for a BAP data PDU received from an ingress BH RLC channel on an ingress link, if an entry exists in the BH RLC channel mapping configuration, the ingress BH RLC channel identifier of the entry matches the ingress BH RLC channel of the BAP data PDU, the ingress link identifier of the entry matches the ingress link of the BAP data PDU, the topology to which the ingress link identifier of the entry belongs is the same as the topology to which the ingress link of the BAP data PDU belongs, the egress link identifier of the entry corresponds to the selected egress link, and the topology to which the egress link identifier of the entry belongs is the same as the topology to which the selected egress link belongs, then select an egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry.

[0117] In at least another embodiment, when an IAB node receives a BAP SDU from an upper layer and transmits it in the upstream direction, after the BAP entity selects an egress link according to the BAP sublayer routing method, if there is an entry in the mapping configuration of uplink traffic to BH RLC channel for the BAP SDU in which the F1-U data packet is encapsulated, the traffic type designator of the entry corresponds to the destination IP address and TEID (Tunnel Endpoint Identifier) ​​of the BAP SDU, the egress link identifier of the entry corresponds to the selected egress link, and the topology to which the egress link identifier of the entry belongs is the same as the topology to which the selected egress link belongs, then the IAB node selects an egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry. Similarly, for a BAP SDU in which a non-F1-U data packet is encapsulated, if an entry exists in the mapping configuration of uplink traffic to BH RLC channels, the traffic type specifier of the entry corresponds to the traffic type of the BAP SDU, the egress link identifier of the entry corresponds to the selected egress link, and the topology to which the egress link identifier of the entry belongs is the same as the topology to which the selected egress link belongs, select the egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry.

[0118] In the seventh embodiment, the IAB node may be an intermediate node of traffic, and when performing BH RLC channel mapping for BAP data packets from a collocated BAP entity, the IAB node may consider topology information of the link to which the BH RLC channel belongs, thereby avoiding ambiguity in link selection and BH RLC channel mapping. Alternatively, the IAB node may be an initial node of uplink traffic, and when performing BH RLC channel mapping for BAP SDUs from an upper layer, the IAB node may consider topology information of the link to which the BH RLC channel belongs, thereby avoiding ambiguity in link selection and BH RLC channel mapping.

[0119] <Example 8> The eighth embodiment of the present invention further provides a communication system. 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.

[0120] Fig. 11 is a schematic diagram of an example of the configuration of an electronic device according to an embodiment of the present invention. As shown in Fig. 11, the electronic device 1100 may include a processor 1110 (e.g., a central processing unit CPU) and a memory 1120. The memory 1120 is connected to the processor 1110. The memory 1120 may store various data, and may further store an information processing program 1130 and execute the program 1130 under the control of the processor 1110.

[0121] For example, the processor 1110 may be configured to execute a program to realize the methods in the first to fourth embodiments.

[0122] 11, the electronic device 1100 may further include a transceiver 1140 and an antenna 1150. Here, the functions of the above units are similar to those of the prior art, and the description thereof will be omitted here. Note that the electronic device 1100 does not need to include all the units shown in FIG. 11. The electronic device 1100 may further include units not shown in FIG. 11, and may refer to the prior art.

[0123] In an embodiment of the present invention, there is further provided a computer program, which, when executed in an IAB node, causes the IAB node to perform the method according to any one of the first to fourth embodiments.

[0124] An embodiment of the present invention further provides a storage medium having a computer program stored thereon, the computer program, when executed, causing an IAB node to perform a method according to any one of embodiments 1 to 4.

[0125] The above-mentioned apparatus and method of the present invention may be realized by hardware or by a combination of hardware and software.The present invention relates to a computer readable program which, when executed by a logic unit, causes the logic unit to realize the above-mentioned apparatus or components, or to realize the above-mentioned various methods or steps.The present invention relates to a storage medium for storing the above-mentioned program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0126] Each processing method in each device described with reference to the embodiments of the present invention may be implemented by hardware, a software module executed by a processor, or a combination of both. For example, one or more of the functional block diagrams shown in the drawings, or one or more combinations of the functional block diagrams, may correspond to each software module of a process of a computer program, or each hardware module. These software modules may correspond to each step shown in the drawings. These hardware modules may be realized by implementing these software modules in hardware, for example, using a field programmable gate array (FPGA).

[0127] The software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of storage medium known to those skilled in the art. The storage medium may be connected to the processor such that the processor reads information from and / or writes information to the storage medium, or the storage medium may be a component of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal, or in a memory card inserted in the mobile terminal. For example, if the device (e.g., a mobile terminal) uses a MEGA-SIM card or a large capacity flash memory device with a relatively large capacity, the software module may be stored in the MEGA-SIM card or the large capacity flash memory device.

[0128] One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings may be implemented with 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 device, a discrete gate or transistor logic device, a discrete hardware component, or any suitable combination thereof to perform the functions described herein. One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings may be implemented with, for example, a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP communication, or any other configuration.

[0129] Although the present invention has been described above with reference to specific embodiments, the above description is merely illustrative and does not limit the scope of protection of the present invention. Various modifications and changes may be made to the present invention without departing from the spirit and principles of the present invention, and these modifications and changes are also within the scope of the present invention.

[0130] Furthermore, the following supplementary notes are disclosed regarding the embodiments including the above-mentioned examples. (Appendix 1) A method for configuring information applied to an IAB node, comprising: A method comprising: matching a topology in a backhaul routing configuration indicated by a first type indicator with a topology to which a BAP data protocol data unit (PDU) belongs. (Appendix 2) The method described in Supplementary Note 1, in which when a BAP entity needs to send a BAP data PDU, if the BAP address of an entry in a backhaul routing configuration matches the destination field, the path identifier of the entry is identical to the PATH field of the BAP address, the topology obtained by the first type indicator of the BAP address of the entry is identical to the topology of the BAP data PDU, and the egress link corresponding to the next hop BAP address of the entry is available, the egress link corresponding to the next hop BAP address of the entry is selected. (Appendix 3) If there is no entry in the backhaul routing configuration that matches the destination field, path field, and topology, or if the egress link corresponding to the matching entry is unavailable, The method according to claim 1 or 2, wherein when there is at least one entry in the backhaul routing configuration having a BAP address that matches the destination field, the topology obtained by the first type indicator of the entry is identical to the topology of the BAP data PDU, and an egress link corresponding to the next hop BAP address of the entry is available, an entry is selected from the at least one entry, and an egress link corresponding to the next hop BAP address of the entry is selected. (Appendix 4) The method of claim 1, wherein in the backhaul routing configuration, for the same first type indicator, each combination of a BAP address and a BAP path indicator corresponds to at most one entry. (Appendix 5) 2. The method of claim 1, wherein in a backhaul routing configuration, for a same first type indicator, each BAP address corresponds to at least one entry. (Appendix 6) A method for configuring information applied to an IAB node, comprising: receiving Uplink Traffic to Routing ID Mapping Configuration information, the configuration information including a second type indicator, the second type indicator being used to indicate whether an entry or a BAP Routing ID in an entry belongs to a topology of a non-F1 termination donor. (Appendix 7) The method of claim 6, wherein the second type indicator is indicated or configured by a non-F1 terminated topology indicator IE in F1 application protocol (F1AP) signaling. (Appendix 8) 7. The method of claim 6, wherein the second type indicator is a Boolean variable. (Appendix 9) if a non-F1 terminated topology indicator is configured in F1AP signaling for the entry, the second type indicator is a first value; 9. The method of claim 8, wherein if a non-F1 terminated topology indicator is not configured in F1AP signaling for the entry, the second type indicator is a second value. (Appendix 10) 7. The method of claim 6, wherein the second type indicator is an enumeration variable and is used to indicate a topology type. (Appendix 11) 11. The method of claim 10, wherein if a non-F1 terminated topology indicator is configured in F1AP signaling for the entry, the second type indicator is a value corresponding to a non-F1 terminated topology. (Appendix 12) 11. The method of claim 10, wherein if a non-F1 terminated topology indicator is not configured in F1AP signaling for the entry, the second type indicator is a value corresponding to an F1 terminated topology. (Appendix 13) The method described in Supplementary Note 6, wherein when a BAP service data unit (SDU) is received by the IAB node from an upper layer and needs to be transmitted in the upstream direction, the BAP entity determines the topology over which the data needs to be transmitted based on a mapping configuration to a routing ID for uplink traffic. (Appendix 14) The method of claim 13, wherein when a BAP service data unit (SDU) is received by the IAB node from an upper layer and needs to be transmitted in an upstream direction, the BAP entity selects an entry from a mapping configuration to uplink traffic routing IDs based on a traffic type designator corresponding to the BAP SDU, and then determines a topology of a BAP data PDU corresponding to the BAP SDU based on the second type indicator in the entry. (Appendix 15) If the second type indicator corresponding to the selected entry indicates a non-F1 terminated topology, the BAP data PDU corresponding to the BAP SDU is data belonging to a non-F1 terminated donor topology; or 15. The method of claim 14, wherein if the second type indicator corresponding to the selected entry indicates an F1 terminated topology, then the BAP data PDU corresponding to the BAP SDU is data belonging to an F1 terminated donor topology. (Appendix 16) A method for configuring information applied to an IAB node, comprising: A method comprising a step of performing BH RLC channel mapping for a BAP data packet from a collocated BAP entity, or performing BH RLC channel mapping for a BAP SDU from an upper layer, based on topology information of a link to which the BH RLC channel belongs. (Appendix 17) 17. The method of claim 16, further comprising: for a BAP data PDU received from an ingress BH RLC channel at an ingress link, after an egress link is selected, if an entry exists in a BH RLC channel mapping configuration, an ingress BH RLC channel identifier of the entry matches the ingress BH RLC channel of the BAP data PDU, an ingress link identifier of the entry matches the ingress link of the BAP data PDU, a topology to which the ingress link identifier of the entry belongs is the same as a topology to which the ingress link of the BAP data PDU belongs, an egress link identifier of the entry corresponds to the selected egress link, and a topology to which the egress link identifier of the entry belongs is the same as a topology to which the selected egress link belongs, the method of claim 16, further comprising: selecting an egress BH RLC channel corresponding to an egress BH RLC channel identifier in the entry. (Appendix 18) When the IAB node receives a BAP SDU from an upper layer and transmits it in the upstream direction, the BAP entity selects an egress link according to the BAP sublayer routing device, and then: The method according to claim 16, further comprising: selecting an egress BH RLC channel corresponding to an egress BH RLC channel identifier in an entry when, for a BAP SDU in which an F1-U data packet is encapsulated, an entry exists in a mapping configuration of uplink traffic to a BH RLC channel, a traffic type specifier of the entry corresponds to a destination IP address and a TEID (Tunnel Endpoint Identifier) ​​of the BAP SDU, an egress link identifier of the entry corresponds to a selected egress link, and a topology to which the egress link identifier of the entry belongs is the same as a topology to which the selected egress link belongs. (Appendix 19) When the IAB node receives a BAP SDU from an upper layer and transmits it in the upstream direction, the BAP entity selects an egress link according to the BAP sublayer routing device, and then: 17. The method of claim 16, further comprising: selecting an egress BH RLC channel corresponding to an egress BH RLC channel identifier in an entry for a BAP SDU encapsulated with a non-F1-U data packet, if an entry exists in a mapping configuration of uplink traffic to a BH RLC channel, a traffic type specifier of the entry corresponds to the traffic type of the BAP SDU, an egress link identifier of the entry corresponds to a selected egress link, and a topology to which the egress link identifier of the entry belongs is the same as a topology to which the selected egress link belongs.

Claims

1. An information configuration device, applied to an IAB node, comprising: a first processing unit, the first processing unit comprising: An apparatus configured to match a topology in a backhaul routing configuration indicated by a first type indicator with a topology to which a BAP data protocol data unit (PDU) belongs.

2. 2. The apparatus of claim 1, wherein when a BAP entity needs to transmit a BAP data PDU, if a BAP address of an entry in a backhaul routing configuration matches a destination field, a path identifier of the BAP address of the entry is the same as a path field of the BAP address, a topology obtained by a first type indicator of the BAP address of the entry is the same as a topology of the BAP data PDU, and an egress link corresponding to a next-hop BAP address of the BAP address of the entry is available, the apparatus selects an egress link corresponding to the next-hop BAP address of the BAP address of the entry.

3. If there is no BAP address of an entry in the backhaul routing configuration that matches the destination field, path field, and topology, or if the egress link corresponding to the matching entry is unavailable, 3. The apparatus of claim 1 or 2, wherein when there is at least one entry in a backhaul routing configuration having a BAP address that matches a destination field, the topology obtained by the first type indicator of the entry is identical to the topology of the BAP data PDU, and an egress link corresponding to the next-hop BAP address of the entry is available, the apparatus selects an entry from the at least one entry and selects an egress link corresponding to the next-hop BAP address of the entry.

4. The apparatus of claim 1 , wherein in a backhaul routing configuration, for a same first type indicator, each combination of a BAP address and a BAP path indicator corresponds to at most one entry.

5. The apparatus of claim 1 , wherein in a backhaul routing configuration, for a same first type indicator, each BAP address corresponds to at least one entry.

6. An information configuration device, which is applied to an IAB node, includes a second processing unit, the second processing unit comprising:

1. An apparatus configured to receive Uplink Traffic to Routing ID Mapping Configuration information, the configuration information including a second type indicator, the second type indicator being used to indicate whether an entry or a BAP Routing ID in an entry belongs to a topology of a non-F1 termination donor.

7. The apparatus of claim 6 , wherein the second type indicator is indicated or configured by a non-F1 terminated topology indicator IE in F1 Application Protocol (F1AP) signaling.

8. The apparatus of claim 6 , wherein the second type indicator is a Boolean variable.

9. if a non-F1 terminated topology indicator is configured in F1AP signaling for the entry, the second type indicator is a first value; The apparatus of claim 8 , wherein if a non-F1 terminated topology indicator is not configured in F1 AP signaling for the entry, the second type indicator is a second value.

10. The apparatus of claim 6 , wherein the second type indicator is an enumerated variable and is used to indicate a topology type.

11. The apparatus of claim 10 , wherein if a non-F1 terminated topology indicator is configured in F1 AP signaling for the entry, the second type indicator is a value corresponding to a non-F1 terminated topology.

12. The apparatus of claim 10 , wherein if a non-F1 terminated topology indicator is not configured in F1 AP signaling for the entry, the second type indicator is a value corresponding to an F1 terminated topology.

13. 7. The apparatus of claim 6, wherein when a BAP service data unit (SDU) is received by the IAB node from a higher layer and needs to be transmitted in an upstream direction, a BAP entity determines a topology over which the data needs to be transmitted based on a mapping configuration of uplink traffic to a routing ID.

14. 14. The apparatus of claim 13, wherein when a BAP service data unit (SDU) is received by the IAB node from a higher layer and needs to be transmitted in an upstream direction, a BAP entity selects an entry from a mapping configuration for uplink traffic to a routing ID based on a traffic type designator corresponding to the BAP SDU, and then determines a topology of a BAP data PDU corresponding to the BAP SDU based on the second type indicator in the entry.

15. If the second type indicator corresponding to the selected entry indicates a non-F1 terminated topology, the BAP Data PDU corresponding to the BAP SDU is data belonging to a non-F1 terminated donor topology; or 15. The apparatus of claim 14, wherein if the second type indicator corresponding to a selected entry indicates an F1 terminated topology, then a BAP Data PDU corresponding to the BAP SDU is data belonging to an F1 terminated donor topology.

16. An information configuration device, which is applied to an IAB node, includes a third processing unit, the third processing unit comprising: An apparatus configured to perform BH RLC channel mapping for BAP data packets from a collocated BAP entity or perform BH RLC channel mapping for BAP SDUs from an upper layer based on topology information of a link to which the BH RLC channel belongs.

17. 17. The apparatus of claim 16, for a BAP Data PDU received from an ingress BH RLC channel at an ingress link, after an egress link is selected, if an entry exists in a BH RLC channel mapping configuration, an ingress BH RLC channel identifier of the entry matches the ingress BH RLC channel of the BAP Data PDU, an ingress link identifier of the entry matches the ingress link of the BAP Data PDU, a topology to which the ingress link identifier of the entry belongs is the same as a topology to which the ingress link of the BAP Data PDU belongs, an egress link identifier of the entry corresponds to the selected egress link, and a topology to which the egress link identifier of the entry belongs is the same as a topology to which the selected egress link belongs, the apparatus selects an egress BH RLC channel corresponding to an egress BH RLC channel identifier in the entry.

18. When the IAB node receives a BAP SDU from an upper layer and transmits it in the upstream direction, the BAP entity selects an egress link according to the BAP sublayer routing device, and then:

17. The apparatus of claim 16, wherein for a BAP SDU in which an F1-U data packet is encapsulated, if an entry exists in a mapping configuration of uplink traffic to a BH RLC channel, a traffic type specifier of the entry corresponds to a destination IP address and a TEID (Tunnel Endpoint Identifier) ​​of the BAP SDU, an egress link identifier of the entry corresponds to a selected egress link, and a topology to which the egress link identifier of the entry belongs is the same as a topology to which the selected egress link belongs, then the apparatus selects an egress BH RLC channel corresponding to an egress BH RLC channel identifier in the entry.

19. When the IAB node receives a BAP SDU from an upper layer and transmits it in the upstream direction, the BAP entity selects an egress link according to the BAP sublayer routing device, and then:

17. The apparatus of claim 16, further comprising: for a BAP SDU encapsulating a non-F1-U data packet, if an entry exists in a mapping configuration of uplink traffic to a BH RLC channel, a traffic type specifier of the entry corresponds to a traffic type of the BAP SDU, an egress link identifier of the entry corresponds to a selected egress link, and a topology to which the egress link identifier of the entry belongs is the same as a topology to which the selected egress link belongs, the apparatus selects an egress BH RLC channel corresponding to an egress BH RLC channel identifier in the entry.

Images