Information configuration method, apparatus, 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

[0004] , ,

[0001] Embodiments of the present invention relate to the field of communication technologies.

Background Art

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

[0003] The IAB node can be connected to one IAB-donor via single-hop 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 performs unified resource management, topology management, and routing management of the IAB network topology.

[0004] The IAB-node supports the functionality of the gNB-DU (distributed unit). The IAB-node DU, also known as the IAB-DU, is the endpoint for the radio access (NR access) interface between the terminal device (UE) and the next-hop IAB-node, and the endpoint for the F1 protocol to the gNB-CU (IAB-node: aggregate unit) at the IAB-donor. The IAB-DU can provide services to normal UEs and IAB child nodes. The IAB-DU implements the functionality of the network-side device, connects to downstream child IAB-nodes, provides NR air interfaces to UEs and downstream child IAB-nodes, and establishes F1 connectivity with the IAB donor-CU.

[0005] In addition to gNB-DU functionality, an IAB-node supports some UE functionality known as IAB-MT (mobile termination). IAB-MT includes physical layer, Layer 2, RRC, and NAS functions for connecting to gNB-DUs of other IAB-nodes or IAB-donors, continuing to gNB-CUs on IAB-donors, and continuing to the core network. IAB-MT can support functions such as the 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] An IAB-donor is the network-side termination node, providing network access for the IAB-MT or UE via a backhaul or access link. An IAB-donor is further divided into an IAB-donor-CU (central unit) and an IAB-donor-DU. The IAB-DU and IAB-donor-CU are connected via an F1 interface. In scenarios where the network is deployed independently, the gNB and IAB-donor-CU are connected via an Xn interface.

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

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

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

[0010] Furthermore, the above explanation of the background art is merely intended to provide a clearer and more complete explanation of the present invention's structure and to facilitate understanding for those skilled in the art. These structures, as described in the background art section of the present invention, should not be construed as being well-known to those skilled in the art. [Overview of the Initiative] [Problems that the invention aims to solve]

[0011] In a multi-hop scenario, to enable the forwarding of data packets, the IAB node must determine the destination node to which the data packet will arrive, then, based on the routing table, determine the next-hop node corresponding to the destination node and transmit the packet. The donor-CU configures the mapping from each uplink F1-U Tunnel initiated from the IAB node, non-UE associated F1AP messages, UE-associated F1AP messages, and non-F1 traffic to BAP routing identifiers for the IAB node via F1AP (F1 application protocol) signaling.

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

[0013] The BAP routing identifier includes the destination BAP address and the path identifier (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] During IAB node integration, the RRC may configure a default BH (backhaul) 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 the mapping relationships for the IAB node, including upstream F1 and non-F1 traffic from the IAB node, the appropriate BAP routing ID, the next-hop BAP address, and the BH RLC channel. Specific mapping relationships are configured for each F1-U GTP-U tunnel, non-UE related F1AP messages, UE related F1AP messages, 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-DC (NR-NR Dual Connectivity) to achieve redundancy in the backhaul path. The 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 a parent node, together with its corresponding IAB-donor-CU, acts as the master node (MN) and / or secondary node (SN) of the IAB-MT. The NR-DC framework, for example, the procedures related to MCG (master cell group) / SCG (secondary cell group) are used to configure dual radio connectivity from the IAB node to the parent node.

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

[0018] As shown in Figure 2, node 3 is referred to as a boundary IAB node. A boundary IAB node means that its RRC interface and F1 interface terminate to different IAB-donor-CUs. Boundary IAB nodes are applicable to partial migration, inter-donor topology redundancy, and inter-donor RLF (radio link failure) recovery. As shown in Figure 2, node 3's DU terminates to CU1, and node 3's MT has interfaces to both CU1 and CU2, thus meeting 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 boundary IAB nodes and descendant nodes; for example, donor-CU1 is an F1-terminating node, meaning that the F1 interfaces of IAB-DU3 and IAB-DU4 in Figure 2 terminate to donor-CU1. A non-F1-terminating donor node refers to a CU that functions as a donor without terminating the F1 interfaces of the boundary IAB node and the descendant nodes, such as donor-CU2 in Figure 2. In the topology redundancy scenario shown in Figure 2, the boundary node (i.e., node 3) is a dual-connected node. In the donor-to-donor topology redundancy scenario, the boundary IAB node (i.e., IAB node 3) and the descendant nodes can communicate with CU1 via the first path and second path, respectively.

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

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

[0021] As shown in Figure 3, IAB node 3 is the boundary IAB node, and IAB-MT3 changes 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 of this F1 connection goes through IAB node 2 and finally reaches donor-CU1. In the donor-to-donor partial migration scenario shown in Figure 3, the boundary node (node ​​3) is the transition node. The donor-to-donor partial migration scenario is similarly applicable to partial RLF recovery.

[0022] The inventors of this invention have discovered that boundary IAB nodes belong to two IAB topologies, and in the prior art, when configuring uplink traffic mapping for IAB nodes or performing BAP routing, the routing ID does not indicate which topology it belongs to, leading to routing ID collisions or ambiguity. Furthermore, when performing BH RLC channel mapping, the topology is not taken into consideration, resulting in unclear link indicators and preventing the correct execution of BH RLC channel mapping.

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

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

[0025] In another aspect of an embodiment of the present invention, there is provided an apparatus for configuring information, which is applied to an IAB node and includes a second processing unit. The second processing unit is configured to receive Uplink Traffic to Routing ID Mapping Configuration information. The configuration information includes a second type indicator, and the second type indicator is used to indicate whether the BAP routing ID in an entry or entries belongs to a topology of a non-F1 termination donor.

[0026] In another aspect of an embodiment of the present invention, there is provided an apparatus for configuring information, which is applied to an IAB node and includes a third processing unit. The third processing unit is configured to perform BH RLC channel mapping for BAP data packets from collocated BAP entities or perform BH RLC channel mapping for BAP SDUs from upper layers based on topology information of a link to which the BH RLC channel belongs.

[0027] The advantageous effects of the embodiments of the present invention are as follows. An appropriate routing entry can be selected for BAP data PDUs.

[0028] As shown in the following description and drawings, specific embodiments of the present invention are disclosed in detail, and the ways in which the principles of the present invention can be adopted are shown. It should be noted that the scope of the embodiments of the present invention is not limited thereto. The embodiments of the present invention include modifications, corrections, and equivalents within the gist and scope of the appended patent claims.

[0029] The features described and / or shown in one embodiment may be used in one or more other embodiments in the same or similar manner, or may be combined with features in other embodiments, or may be replaced by features in other embodiments.

[0030] In this text, the terms "includes / have" mean the presence of a feature, component, step, or constituent element, and do not exclude the presence or addition of one or more other features, components, steps, or constituent elements. [Brief explanation of the drawing]

[0031] Elements and features described in one drawing and one embodiment of the embodiments of the present invention may be combined with elements and features shown in one or more drawings or embodiments. In addition, similar reference numerals in the drawings may indicate corresponding elements in multiple drawings, and may indicate corresponding elements used in one or more embodiments. [Figure 1] This is a schematic diagram illustrating an example of the relationship between IAB parent and child nodes. [Figure 2] This is a schematic diagram of an example of a network structure with inter-donor topology redundancy. [Figure 3] This is a schematic diagram of an example of partial donor transfer. [Figure 4] This is a schematic diagram of an example of an information configuration method according to Example 1. [Figure 5] This is a schematic diagram of an example of an information configuration method according to Example 2. [Figure 6] This is a schematic diagram of an example of an information configuration method according to Example 3. [Figure 7] This is a schematic diagram of an example of an information configuration method according to Example 4. [Figure 8] This is a schematic diagram of an example of an information configuration device according to Example 5. [Figure 9] This is a schematic diagram of an example of an information configuration device according to Example 6. [Figure 10] This is a schematic diagram of an example of an information configuration device according to Example 7. [Figure 11] This is a schematic diagram of an example of the configuration of an electronic device according to an embodiment of the present invention. [Modes for carrying out the invention]

[0032] The above and other features of the present invention will become apparent from the following description. Specific embodiments of the present invention are disclosed in detail in the specification and drawings, and some embodiments in which the principles of the present invention can be employed are shown. However, the present invention is not limited to the embodiments described. The present invention includes all modified, altered and equivalent versions of the appended claims.

[0033] In embodiments of the present invention, terms such as "first," "second," etc., are used in titles to distinguish different elements, but do not represent a spatial arrangement or temporal order of these elements, and these elements are not limited to these terms. The term "and / or" includes any one or more of the terms listed in the relevant list and all combinations thereof. The terms "include," "comprehensible," "have," etc., mean the presence of the listed features, elements, components, or components, but do not exclude the presence or addition of one or more other features, elements, components, or components.

[0034] In the embodiments of the present invention, singular nouns such as "one" and "the" should be understood broadly as "one type" or "one category," including plural forms, and not limited to "one." Furthermore, the term "the foregoing" should be understood to include both singular and plural forms unless the context explicitly indicates otherwise. Also, unless the context explicitly indicates otherwise, the term "as described" should be understood as "at least partially described," and the term "based on" should be understood as "based on at least partially."

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

[0036] Furthermore, communication between devices in a communication system may be carried out according to a communication protocol of any stage, and such communication protocol may include, but is not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, and new radio (NR), and / or other currently known communication protocols or other communication protocols to be developed in the future.

[0037] In embodiments of the present invention, the term "network device" means, for example, a device within a communication system that allows a terminal device to access the communication system and provides services to said terminal device. A network device may include, but is not limited to, an access backhaul integration node (IAB-node), relay device (relay), base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), and the like.

[0038] Here, base stations may include, but are not limited to, node B (NodeB or NB), evolutionary node B (eNodeB or eNB), and 5G base stations (gNB), as well as remote radio heads (RRH), remote radio units (RRU), relays, or low-power nodes (e.g., femto, pico). The term “base station” may also include some or all of their functions, and each base station may provide communication coverage to a specific geographic area. The term “cell” may mean a base station and / or its coverage area, depending on the context in which the term is used.

[0039] In embodiments of the present invention, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer to a device that accesses a communication network and receives network services, for example, via a network device. The terminal equipment may be fixed or mobile, and may be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), mobile termination (MT), station, etc.

[0040] Here, terminal devices may include, but are not limited to, mobile phones (cellular phones), personal digital assistants (PDAs), radio modulators / demodulators, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smartwatches, digital cameras, and the like.

[0041] Furthermore, in scenarios such as the Internet of Things (IoT), the terminal device may be a monitoring or measurement device or apparatus, and may include, but is not limited to, machine-type communication (MTC) terminals, in-vehicle communication terminals, device-to-device (D2D) terminals, and machine-to-machine (M2M) terminals.

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

[0043] In embodiments of the present invention, the upper layer signaling may be, for example, a radio resource control (RRC) signaling, referred to as an RRC message, and including, for example, a MIB, system information, a dedicated RRC message, or referred to as an RRC IE (RRC information element). The upper layer signaling may also be, for example, an F1-C signaling, or referred to as an F1AP protocol. However, the present invention is not limited to these.

[0044] In this invention, each embodiment will be described using a multi-hop IAB network deployment scenario as an example. Here, multiple terminal devices (e.g., UEs) are connected to an IAB-donor via multi-hop IAB nodes and finally access the network. This network is, for example, a 5G network. However, the embodiments of this invention are not limited to the above scenario.

[0045] In each embodiment of the present invention, the IAB topology refers to all combinations of IAB nodes and IAB-donor-DUs that are connected to each other via backhaul links and whose F1 interfaces and / or RRCs terminate to 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 consisting of these nodes and Donor-CU1 is referred to as the first topology. Donor-DU2, IAB node 2, and IAB node 3 are nodes managed by Donor-CU2, and the IAB topology consisting of these nodes and Donor-CU2 is referred to as the second topology. The boundary node (i.e., IAB node 3) belongs to both the first and second topology.

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

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

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

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

[0050] To solve the above or similar problems, Embodiment 1 of the present invention provides an information structuring method. This method is applied to an IAB node.

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

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

[0053] In Example 1, the IAB node may be a boundary IAB node, for example, IAB node 3 shown in Figure 2 or Figure 3. However, the IAB node of the present invention is not limited to this, and other types of IAB nodes may also be used.

[0054] In step 401, when BAP routing is performed at the boundary 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 that the appropriate routing entry is selected and routing is performed for the BAP data PDU. The topology to which the BAP data PDU belongs is the topology to which the PDU needs to perform routing or select an egress link, and may be considered an egress topology.

[0055] In at least some embodiments, when a BAP entity needs to send a BAP data PDU, the egress link corresponding to the next-hop BAP address of an entry is selected if the BAP address of the 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 an egress link corresponding to the next-hop BAP address is available.

[0056] In at least several other embodiments, if the above conditions are not met, i.e., if the backhaul routing configuration does not have entries matching the destination field, path field, and topology, BAP addressIf no entry exists, or if an egress link corresponding to a matching entry is unavailable, an entry is selected from at least one entry in the backhaul routing configuration if there is at least one entry with a matching BAP address in the "Destination" field, the topology obtained by the first type indicator of that entry is identical to the topology of the BAP data PDU, and an egress link corresponding to the next-hop BAP address is available. The BAP address of the selected entry matches the "Destination" field, the topology obtained by the first type indicator of that entry is identical to the topology of the BAP data PDU, and an egress link corresponding to the next-hop BAP address is available. Then, the egress link corresponding to the next-hop BAP address of that entry is selected.

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

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

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

[0060] [Table 2] Example 1 shows a scenario where the IAB node is an intermediate node in the traffic (i.e., the IAB node receives and forwards data from other nodes). According to Example 1, appropriate routing entries and egress links can be selected for BAP data PDUs.

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

[0062] In the BAP sublayer's Uplink Traffic to Routing ID Mapping Configuration, each entry includes a traffic type specifier and a BAP routing identifier (ID). Because boundary nodes belong to multiple topologies, the BAP routing identifier can become ambiguous.

[0063] To solve the above problem or a similar problem, Example 2 provides an information structuring method, which is applied to an IAB node.

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

[0065] Step 501: Receive Uplink Traffic to Routing ID Mapping Configuration information. This configuration information includes a second type indicator, which is used to indicate whether an entry or the BAP routing ID in an entry belongs to a non-F1 terminated donor topology.

[0066] In Example 2, the IAB node may be a boundary IAB node, for example, IAB node 3 shown in Figure 2 or Figure 3. However, the IAB node of the present invention is not limited to this, and other types of nodes may also be used.

[0067] In step 501, a second type indicator may be added to each mapping relationship (i.e., each entry), which is used to indicate whether the BAP routing ID (in other words, the entry) belongs to a non-F1 terminated donor topology. 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. For example, if a non-F1 terminated topology indicator is configured for the entry in the F1AP signaling, the second type indicator has a first value, for example, the second type indicator is true. On the other hand, if a non-F1 terminated topology indicator is not configured for the entry in the F1AP signaling, the second type indicator has a second value, for example, the second type indicator is false.

[0069] In at least some other embodiments, the second type indicator may be an enumerated variable used to indicate a specific topology type. For example, if a non-F1 terminated topology indicator is configured in the F1AP signaling for the entry, the second type indicator is "non-F1 terminated topology," while if no non-F1 terminated topology indication is configured in the 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. The extension may also be applied to the procedure for selecting the BAP routing ID for an IAB node, as shown in Table 3.

[0071] [Table 3] In at least some embodiments, if an IAB node needs to receive a BAP SDU (service data unit) from a higher layer and transmit the BAP SDU upstream, the BAP entity may, based on a mapping configuration to the routing ID of the uplink traffic, clearly determine the topology to which the data needs to be transmitted and perform routing in the corresponding topology.

[0072] In at least one specific embodiment, when an IAB node needs to receive a BAP SDU (service data unit) from a higher layer and transmit it upstream, the BAP entity selects an entry from a mapping configuration to routing IDs for uplink traffic based on a traffic type specifier corresponding to the BAP SDU, and then determines the topology of the 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 BAP routing ID (i.e., BAP address and 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; on the other hand, 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. The extension may also be applied to the procedure for selecting the BAP routing ID for an IAB node, as shown in Table 4.

[0074] [Table 4] In Example 2, the BAP entity can obtain the BAP routing ID and topology information of the BAP data PDU through the BAP routing ID selection procedure, and then perform BAP routing according to the method described in Example 1.

[0075] <Example 3> For BAP data packets received from a collocated BAP entity, i.e., BAP data packets that require forwarding, the transmitting unit of the BAP entity maps them to an Egress BH RLC channel based on the BH RLC Channel Mapping Configuration. The entries in the BH RLC Channel Mapping Configuration 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 scenarios shown in Figures 2 and 3, when a boundary IAB node performs BH RLC channel mapping for BAP data packets from a colocated BAP entity, if the topology information of the link to which the BH RLC channel belongs is not considered, link selection and BH RLC channel mapping become unclear.

[0077] To solve the above problem or a similar problem, Embodiment 3 provides an information structuring method that is applied to an IAB node.

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

[0079] Step 601: The IAB node performs BH RLC channel mapping for BAP data packets from colocated BAP entities 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 is necessary to select the appropriate 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 by 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 Example 3, the IAB node may be a boundary IAB node, for example, IAB node 3 shown in Figure 2 or Figure 3. However, the IAB node of the present invention is not limited to this, and other types of nodes may also be used.

[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 the BAP sublayer routing method, if an entry exists 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, then an egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry is selected.

[0082] For example, the BAP sublayer standard may be extended in TS 38.340. In the IAB node, the extensions shown in Table 5 may be made for BH RLC channel mapping for BAP data packets from colocated BAP entities.

[0083] [Table 5] In Embodiment 3, the IAB node may also be an intermediate node in the traffic, and when performing BH RLC channel mapping for BAP data packets from colocated BAP entities, the topology information of the link to which the BH RLC channel belongs can be considered, thereby avoiding ambiguity in link selection and BH RLC channel mapping.

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

[0085] In the donor routing scenarios shown in Figures 2 and 3, if the boundary IAB node does not consider the topology information of the link to which the BH RLC channel belongs when performing BH RLC channel mapping for BAP SDU from the upper layer, link selection and BH RLC channel mapping become unclear.

[0086] To solve the above problem or a similar problem, Example 4 provides an information structuring method which is applied to an IAB node.

[0087] Figure 7 is a schematic diagram of an example of an information structuring method according to Example 4. As shown in Figure 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 is necessary to select the appropriate mapping entry and egress BH RLC channel for the BAP SDU by matching the topology to which the egress link belongs in the mapping configuration of uplink traffic to the backhaul RLC channel with the topology to which the selected egress link belongs.

[0089] In Example 4, the IAB node may be a boundary IAB node, for example, IAB node 3 shown in Figure 2 or Figure 3. However, the IAB node of the present invention is not limited to this, and other types of nodes may also be used.

[0090] In step 701, if an IAB node receives a BAP SDU from a higher layer and transmits it upstream, the BAP entity selects an egress link according to the BAP sublayer routing method. Then, for the BAP SDU in which the F1-U data packet is encapsulated, if an entry exists in the mapping configuration for uplink traffic to a BH RLC channel, the traffic type specifier 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 egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry is selected. Similarly, for a BAP SDU encapsulating a non-F1-U data packet, if an entry exists in the mapping configuration for uplink traffic to a BH RLC channel, and the traffic type specifier of that entry corresponds to the traffic type of the BAP SDU, the egress link identifier of that entry corresponds to the selected egress link, and the topology to which the egress link identifier of that entry belongs is the same as the topology to which the selected egress link belongs, then the egress BH RLC channel corresponding to the egress BH RLC channel identifier in that entry is selected.

[0091] For example, the BAP sublayer standard may be extended in TS 38.340. At the IAB node, the extensions shown in Table 6 may be made for the BH RLC channel mapping procedure for BAP SDUs from higher layers.

[0092] [Table 6] In Example 4, the IAB node may also be the initial node for uplink traffic, and when performing BH RLC channel mapping for BAP SDU from a higher layer, the topology information of the link to which the BH RLC channel belongs can be considered, thereby avoiding ambiguity in link selection and BH RLC channel mapping.

[0093] <Example 5> Embodiment 5 of the present invention provides an information configuration device. This device corresponds to the information configuration method of Embodiment 1. This device is applied to an IAB node.

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

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

[0096] In Example 5, the IAB node may be a boundary IAB node, for example, IAB node 3 shown in Figure 2 or Figure 3. However, the IAB node of the present invention is not limited to this, and other types of nodes may also be used.

[0097] In Example 5, when performing BAP routing, the topology in the backhaul routing configuration indicated by the first type indicator is matched with the topology to which the BAP data PDU (protocol data unit) belongs, thereby allowing the selection of an appropriate routing entry for routing the BAP data PDU.

[0098] In at least some embodiments, when a BAP entity needs to send a BAP data PDU, the egress link corresponding to the next-hop BAP address is selected 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 an egress link corresponding to the next-hop BAP address of the entry's BAP address is available.

[0099] In at least several other embodiments, if the above conditions are not met, i.e., if there is no BAP address for an entry that matches the destination field, path field, and topology in the backhaul routing configuration, or if an egress link corresponding to a matching entry is unavailable, then an entry is selected from the at least one entry if there is at least one entry in the backhaul routing configuration that has a BAP address that matches the destination field, the topology obtained by the first type indicator of that entry is identical to the topology of the BAP data PDU, and an egress link corresponding to the next-hop BAP address is available.

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

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

[0102] <Example 6> Embodiment 6 of the present invention provides an information configuration device. This device is applied to an IAB node and corresponds to the information configuration method of Embodiment 2.

[0103] Figure 9 is a schematic diagram of an example of an information configuration device according to Embodiment 6. As shown in Figure 9, the information configuration device 900 includes a second processing unit 901.

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

[0105] In Example 6, the IAB node may be a boundary IAB node, for example, IAB node 3 shown in Figure 2 or Figure 3. However, the IAB node of the present invention is not limited to this, and other types of nodes may also be used.

[0106] In at least one embodiment, a second type indicator may be added to each mapping relationship (i.e., each entry), which is used to indicate whether the BAP routing ID (in other words, the entry) belongs to a non-F1 terminated donor topology. 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. For example, if a non-F1 terminated topology indicator is configured for the entry in the F1AP signaling, the second type indicator has a first value, for example, the second type indicator is true. On the other hand, if a non-F1 terminated topology indicator is not configured for the entry in the F1AP signaling, the second type indicator has a second value, for example, the second type indicator is false.

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

[0109] In at least some embodiments, if an IAB node needs to receive a BAP SDU (service data unit) from a higher layer and transmit the BAP SDU upstream, the BAP entity may, based on a mapping configuration to the routing ID of the uplink traffic, clearly determine the topology to which the data needs to be transmitted and perform routing in the corresponding topology.

[0110] In at least one specific embodiment, when an IAB node needs to receive a BAP SDU (service data unit) from a higher layer and transmit it upstream, the BAP entity selects an entry from a mapping configuration to routing IDs for uplink traffic based on a traffic type specifier corresponding to the BAP SDU, and then determines the topology of the 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 BAP routing ID (i.e., BAP address and 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; on the other hand, 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 Example 6, 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 performs BAP routing according to the method described in Example 1.

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

[0113] Figure 10 is a schematic diagram of an example of an information configuration device according to Embodiment 7. As shown in Figure 10, the information configuration device 1000 includes a third processing unit 1001.

[0114] The third processing unit 1001 is configured to perform BH RLC channel mapping for BAP data packets from colocated BAP entities or for BAP SDUs from higher layers, based on the topology information of the link to which the BH RLC channel belongs.

[0115] In Example 7, the IAB node may be a boundary IAB node, for example, IAB node 3 shown in Figure 2 or Figure 3. However, the IAB node of the present invention is not limited to this, and other types of nodes may also be used.

[0116] In at least one embodiment, for a BAP data PDU received from an ingress BH RLC channel on an ingress link, after an egress link is selected according to the BAP sublayer routing device, if an entry exists 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 a 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 an egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry is selected.

[0117] In at least other embodiments, when an IAB node receives a BAP SDU from a higher layer and transmits it upstream, after the BAP entity selects an egress link according to the BAP sublayer routing method, an egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry is selected for the BAP SDU in which the F1-U data packet is encapsulated, if an entry exists in the mapping configuration for uplink traffic to BH RLC channels, the traffic type specifier 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. Similarly, for a BAP SDU encapsulating a non-F1-U data packet, if an entry exists in the mapping configuration for uplink traffic to a BH RLC channel, and the traffic type specifier of that entry corresponds to the traffic type of the BAP SDU, the egress link identifier of that entry corresponds to the selected egress link, and the topology to which the egress link identifier of that entry belongs is the same as the topology to which the selected egress link belongs, then the egress BH RLC channel corresponding to the egress BH RLC channel identifier in that entry is selected.

[0118] In Example 7, the IAB node may also be an intermediate node in the traffic, and when performing BH RLC channel mapping for BAP data packets from colocated BAP entities, the topology information of the link to which the BH RLC channel belongs can be considered to avoid ambiguity in link selection and BH RLC channel mapping. Alternatively, the IAB node may also be an initial node in the uplink traffic, and when performing BH RLC channel mapping for BAP SDUs from higher layers, the topology information of the link to which the BH RLC channel belongs can be considered to avoid ambiguity in link selection and BH RLC channel mapping.

[0119] <Example 8> Embodiment 8 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 equipment configuration shown in Figure 11.

[0120] Figure 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 Figure 11, the electronic device 1100 may include a processor 1110 (for example, a CPU of a central processing unit) and a memory 1120. The memory 1120 is connected to the processor 1110. The memory 1120 may store various types of data, and may also 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 implement the methods in Examples 1 to 4.

[0122] Furthermore, as shown in Figure 11, the electronic equipment 1100 may further include a transceiver 1140 and an antenna 1150, etc. The functions of the above units are the same as in the prior art, and their explanation is omitted here. Note that the electronic equipment 1100 does not need to include all the units shown in Figure 11. Also, the electronic equipment 1100 may further include units not shown in Figure 11, and prior art may be referenced.

[0123] In embodiments of the present invention, the present invention further provides a computer program that, when the program is executed on an IAB node, causes the IAB node to execute the method described in any of Embodiments 1 to 4.

[0124] Embodiments of the present invention further provide a storage medium in which a computer program is stored, wherein when the computer program is executed, an IAB node is instructed to execute the method described in any of Embodiments 1 to 4.

[0125] The above-described apparatus and method of the present invention may be implemented by hardware, or by combining hardware and software. The present invention relates to a computer-readable program, and when the program is executed by a logic unit, the logic unit may implement the above-described apparatus or configuration requirements, or the logic unit may implement the above-described methods or steps. The present invention relates to a storage medium for storing the above-described program, such as a hard disk, magnetic disk, optical disk, DVD, flash memory, etc.

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

[0127] The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, mobile hard disk, 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 so that the processor can read information from and / or write information to the storage medium, or the storage medium may be a component of the processor. The processor and the storage medium may reside in an ASIC. The software module may be stored in the memory of the mobile terminal or on a memory card inserted into the mobile terminal. For example, if the device (e.g., a mobile terminal) uses a relatively large capacity MEGA-SIM card or a high-capacity flash memory device, the software module may be stored on the MEGA-SIM card or high-capacity flash memory device.

[0128] One or more functional blocks and / or one or more combinations of functional blocks in the functional block diagrams shown in the drawings may be implemented by 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 unit, a discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more functional blocks and / or one or more combinations of functional blocks in the functional block diagrams shown in the drawings may be implemented, for example, by a combination of computing equipment, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors combined with 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 can be made to the present invention as long as they do not deviate 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 additional information is disclosed regarding embodiments including the above-described examples. (Note 1) A method for structuring information that applies to IAB nodes, A method comprising the step of matching the topology in a backhaul routing configuration indicated by a first type indicator with the topology to which a BAP data protocol data unit (PDU) belongs. (Note 2) The method according to Appendix 1, wherein, when a BAP entity needs to send a BAP data PDU, the BAP address of an entry in the backhaul routing configuration matches the DESTINATION field, the path identifier 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's BAP address is the same as the topology of the BAP data PDU, and an egress link corresponding to the next-hop BAP address of the entry is available, the egress link corresponding to the next-hop BAP address is selected. (Note 3) If there is no entry in the backhaul routing configuration that matches the destination field, path field, and topology, or if an egress link corresponding to a matching entry is unavailable, The method according to Appendix 1 or 2, wherein, when the backhaul routing configuration has at least one entry having a BAP address that matches the destination field, the topology obtained by the first type indicator of the entry is the same as the topology of the BAP data PDU, and an egress link corresponding to the next-hop BAP address 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. (Note 4) In a backhaul routing configuration, each combination of a BAP address and a BAP path indicator corresponds to at most one entry for the same first type indicator, as described in Appendix 1. (Note 5) In a backhaul routing configuration, each BAP address corresponds to at least one entry for the same first type indicator, as described in Appendix 1. (Note 6) A method for structuring information that applies to IAB nodes, A method comprising the step of receiving Uplink Traffic to Routing ID Mapping Configuration information, wherein the configuration information includes 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 non-F1 terminating donor topology. (Note 7) The method described in Appendix 6, wherein the second type indicator is indicated or configured by a non-F1 termination topology indicator IE in F1 Application Protocol (F1AP) signaling. (Note 8) The method described in Appendix 6, wherein the second type indicator is a Boolean variable. (Note 9) If a non-F1 termination topology indicator is configured for the aforementioned entry using F1AP signaling, the second type indicator is the first value, If no non-F1 termination topology indicator is configured for the aforementioned entry in F1AP signaling, the second type indicator is the second value, as described in Appendix 8. (Note 10) The method described in Appendix 6, wherein the second type indicator is an enumerated variable used to indicate a topology type. (Note 11) The method as described in Appendix 10, wherein, if a non-F1 terminated topology indicator is configured for the aforementioned entry in F1AP signaling, the second type indicator is a value corresponding to the non-F1 terminated topology. (Note 12) If no non-F1 termination topology indicator is configured for the aforementioned entry in F1AP signaling, the second type indicator is a value corresponding to the F1 termination topology, as described in Appendix 10. (Note 13) The method described in Appendix 6, wherein, when a BAP service data unit (SDU) is received by the IAB node from a higher layer and needs to be transmitted upstream, the BAP entity determines the topology to which the data needs to be transmitted based on the mapping configuration to the routing ID of the uplink traffic. (Note 14) The method according to Appendix 13, wherein, when a BAP service data unit (SDU) is received by the IAB node from a higher layer and needs to be transmitted upstream, the BAP entity selects an entry from a mapping configuration to routing IDs for uplink traffic based on the traffic type designator corresponding to the BAP SDU, and then determines the topology of the BAP data PDU corresponding to the BAP SDU based on the second type indicator in the entry. (Note 15) If the second type indicator corresponding to the selected entry indicates a non-F1 terminated topology, then the BAP data PDU corresponding to the BAP SDU is data belonging to a non-F1 terminated donor topology, or The method according to Appendix 14, wherein if the second type indicator corresponding to the selected entry indicates an F1 termination topology, the BAP data PDU corresponding to the BAP SDU is data belonging to an F1 termination donor topology. (Note 16) A method for structuring information that applies to IAB nodes, A method comprising the steps of performing BH RLC channel mapping for BAP data packets from a colocated BAP entity, or for a BAP SDU from a higher layer, based on the topology information of the link to which the BH RLC channel belongs. (Note 17) The method according to Appendix 16, wherein, for a BAP data PDU received from an ingress BH RLC channel on an ingress link, after an egress link is selected, 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. (Note 18) When the IAB node receives a BAP SDU from a higher layer and transmits it upstream, the BAP entity selects an egress link according to the BAP sublayer routing device, The method according to Appendix 16, wherein, for a BAP SDU in which an F1-U data packet is encapsulated, an entry exists in the mapping configuration for uplink traffic to a BH RLC channel, the traffic type specifier 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 an egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry is selected. (Note 19) When the IAB node receives a BAP SDU from a higher layer and transmits it upstream, the BAP entity selects an egress link according to the BAP sublayer routing device, The method according to Appendix 16, wherein, for a BAP SDU in which a non-F1-U data packet is encapsulated, an entry exists in the mapping configuration of uplink traffic to a BH RLC channel, 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, the egress BH RLC channel corresponding to the egress BH RLC channel identifier in the entry is selected.

Claims

1. A device for configuring information that is applied to an IAB node, A processor configured to match the topology in a backhaul routing configuration indicated by a first type indicator with the topology to which a BAP data protocol data unit (PDU) belongs, and to receive an Uplink Traffic to Routing ID Mapping Configuration, wherein each entry in the configuration includes a second type indicator, the second type indicator being used to indicate whether the BAP routing ID in the entry belongs to a non-F1 terminated donor topology, When a BAP service data unit (SDU) is received by the IAB node from a higher layer and needs to be transmitted upstream, the BAP entity selects an entry from a mapping configuration to routing IDs for uplink traffic based on the traffic type designator corresponding to the BAP SDU, and then determines the topology of the BAP data PDU corresponding to the BAP SDU based on the second type indicator in the entry during the BAP routing ID selection procedure.

2. The apparatus according to claim 1, which, when a BAP entity needs to send a BAP data PDU, selects an egress link corresponding to the next-hop BAP address when the BAP address of an entry in the backhaul routing configuration matches the DESTINATION field, the path identifier 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 an egress link corresponding to the next-hop BAP address of the entry is available.

3. The apparatus according to claim 1, wherein, in a backhaul routing configuration, for each combination of a BAP address and a BAP path identifier, there is at most one entry having the same first type indicator.

4. The apparatus according to claim 1, wherein in the backhaul routing configuration, there is at least one entry for the same BAP address having the same first type indicator.

5. The apparatus according to claim 1, wherein the second type indicator is indicated by a non-F1 terminated IAB donor topology indicator IE in F1 Application Protocol (F1AP) signaling.

6. The apparatus according to claim 1, wherein the second type indicator is a Boolean variable.

7. If a non-F1 terminated IAB donor topology indicator is configured for the aforementioned entry using F1AP signaling, the second type indicator is the first value, If a non-F1 terminated IAB donor topology indicator is not configured for the aforementioned entry in F1AP signaling, the second type indicator is a second value, according to claim 6.

8. The apparatus according to claim 1, wherein the second type indicator is an enumerated variable used to indicate a topology type.

9. The apparatus according to claim 8, wherein if a non-F1 terminated IAB donor topology indicator is configured for the entry in F1AP signaling, the second type indicator is a value corresponding to the non-F1 terminated topology.

10. If a non-F1 terminated IAB donor topology indicator is not configured for the entry in F1AP signaling, the second type indicator is a value corresponding to the F1 terminated topology, according to claim 8.

11. 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 routed to a non-F1 terminated donor topology, or The apparatus according to claim 1, wherein if the second type indicator corresponding to the selected entry indicates an F1 termination topology, the BAP data PDU corresponding to the BAP SDU is data routed to an F1 termination donor topology.

Images