Enhanced resource efficiency of IAB networks

Abstract

As part of the RAN communicating with the UE, the IAB network node performs the following operations: receiving configuration information indicating which data should be copied in the downlink direction and merged in the uplink direction; in the downlink direction, for a single DRB associated with the UE, receiving first data via a backhaul link, determining that the first data is indicated to be copied, copying the first data into multiple downlink traffic flows, and sending the multiple downlink traffic flows toward the UE; and in the uplink direction, receiving second data from the UE via multiple uplink traffic flows, determining that the second data is indicated to be merged, merging the second data into a single traffic flow, and forwarding the single traffic flow toward the network via a backhaul link. Additional technologies utilize IAB DU and CU nodes.

Description

Technical Field

[0001] The exemplary embodiments described herein generally relate to wireless communication networks, and more specifically to networks with integrated access and backhaul (IAB). Background Technology

[0002] In cellular communication systems, the term "backhaul" is used to refer to the communication path from base station to base station or from base station to the core network. Typically, backhaul from base station to core network uses very high-speed communication, such as fiber optic communication. Backhaul between base stations was originally wired, but recently there has been a trend towards wireless backhaul between base stations in certain situations.

[0003] For example, the Integrated Access and Backhaul (IAB) feature was introduced in the 3GPP Rel-16 (Release 16) specification. Due to this feature, user services can be relayed via a radio interface (e.g., Uu) between two relay nodes, for example, called IAB nodes. Relaying can occur on one or more hops (called air interface segments).

[0004] While the IAB feature offers advantages, it also presents challenges. For example, base stations can use the same spectrum or radio channels to serve mobile devices (called user equipment (UEs) within their coverage area and to provide backhaul connections to other base stations. This and other resource challenges can lead to resource inefficiencies. Summary of the Invention

[0005] This section is intended to include examples, not to be restrictive.

[0006] In an exemplary embodiment, a method is disclosed, comprising performing the following operations in an integrated access and backhaul network node that is part of a radio access network communicating with a user equipment: receiving a configuration having information indicating which data to be copied in the downlink direction and to be merged in the uplink direction; in the downlink direction, receiving first data via a backhaul link for a single data radio bearer associated with the user equipment, determining that the first data is indicated as data to be copied, copying the first data into multiple downlink traffic flows, and sending the multiple downlink traffic flows toward the user equipment; and in the uplink direction, receiving second data from the user equipment via the multiple uplink traffic flows, determining that the second data is indicated as data to be merged, merging the second data into a single traffic flow, and forwarding the single traffic flow toward the network via a backhaul link.

[0007] Additional exemplary embodiments include a computer program that includes code for performing the method of the preceding segment when the computer program is run on a processor. According to this paragraph, the computer program is a computer program product including a computer-readable medium in which computer program code for use with a computer is implemented. Another example is a computer program according to this paragraph, wherein the program is directly loadable into the computer's internal memory.

[0008] An exemplary apparatus includes one or more processors and one or more memories including computer program code. The one or more memories and computer program code are configured, together with the one or more processors, to cause the apparatus to perform operations including: receiving a configuration having information indicating which data to be copied in the downlink direction and to be merged in the uplink direction; in the downlink direction, receiving first data via a backhaul link for a single data radio bearer associated with a user equipment, determining that the first data is indicated to be copied, copying the first data into multiple downlink traffic flows, and transmitting the multiple downlink traffic flows toward the user equipment; and in the uplink direction, receiving second data from the user equipment via the multiple uplink traffic flows, determining that the second data is indicated to be merged, merging the second data into a single traffic flow, and forwarding the single traffic flow toward the network via a backhaul link.

[0009] An exemplary computer program product includes a computer-readable storage medium in which computer program code for use with a computer is implemented. The computer program code includes code for: receiving a configuration having information indicating which data to be copied in the downlink direction and to be merged in the uplink direction; in the downlink direction, receiving first data via a backhaul link for a single data radio bearer associated with a user equipment, determining that the first data is indicated to be copied, copying the first data into multiple downlink traffic flows, and transmitting the multiple downlink traffic flows toward the user equipment; and in the uplink direction, receiving second data from the user equipment via the multiple uplink traffic flows, determining that the second data is indicated to be merged, merging the second data into a single traffic flow, and forwarding the single traffic flow toward the network via a backhaul link.

[0010] In another exemplary embodiment, an apparatus includes components for performing the following operations: receiving a configuration having information indicating which data to be copied in the downlink direction and to be merged in the uplink direction; in the downlink direction, receiving first data via a backhaul link for a single data radio bearer associated with a user equipment, determining that the first data is indicated as data to be copied, copying the first data into multiple downlink traffic flows, and transmitting the multiple downlink traffic flows toward the user equipment; and in the uplink direction, receiving second data from the user equipment via the multiple uplink traffic flows, determining that the second data is indicated as data to be merged, merging the second data into a single traffic flow, and forwarding the single traffic flow toward the network via a backhaul link.

[0011] In an exemplary embodiment, a method is disclosed that includes receiving data for a user equipment at an integrated access and backhaul donor distributed unit node, and determining by the integrated access and backhaul donor distributed unit node that the data is associated with a data radio bearer to be replicated. The method also includes adding a replication instruction associated with the data by the integrated access and backhaul donor distributed unit node, and forwarding the data and the added replication instruction by the integrated access and backhaul donor distributed unit node toward the integrated access and backhaul node to which data replication is to be performed.

[0012] Additional exemplary embodiments include a computer program that includes code for performing the method of the preceding segment when the computer program is run on a processor. According to this paragraph, the computer program is a computer program product including a computer-readable medium in which computer program code for use with a computer is implemented. Another example is a computer program according to this paragraph, wherein the program is directly loadable into the computer's internal memory.

[0013] An exemplary device includes one or more processors and one or more memories including computer program code. The one or more memories and computer program code are configured, together with the one or more processors, to cause the device to perform operations including: receiving data for a user equipment at an integrated access and backhaul donor distributed unit node; determining, by the integrated access and backhaul donor distributed unit node, that the data is associated with a data radio bearer to be copied; adding a copy instruction associated with the data by the integrated access and backhaul donor distributed unit node; and forwarding the data and the added copy instruction by the integrated access and backhaul donor distributed unit node toward the integrated access and backhaul node to which the copying of the data is to be performed.

[0014] An exemplary computer program product includes a computer-readable storage medium in which computer program code for use with a computer is implemented. The computer program code includes: code for receiving data for a user equipment at an integrated access and backhaul donor distributed unit node; code for determining, by the integrated access and backhaul donor distributed unit node, that the data is associated with a data radio bearer to be replicated; code for adding a replication instruction associated with the data by the integrated access and backhaul donor distributed unit node; and code for forwarding the data and the added replication instruction by the integrated access and backhaul donor distributed unit node toward the integrated access and backhaul node to which data replication is to be performed.

[0015] In another exemplary embodiment, an apparatus includes components for performing the following operations: receiving data for a user equipment at an integrated access and backhaul donor distributed unit node; determining, by the integrated access and backhaul donor distributed unit node, that the data is associated with a data radio bearer to be copied; adding a copy instruction associated with the data by the integrated access and backhaul donor distributed unit node; and forwarding the data and the added copy instruction by the integrated access and backhaul donor distributed unit node toward the integrated access and backhaul node to which the copying of the data is to be performed.

[0016] In an exemplary embodiment, a method is disclosed, which includes performing the following operations at an integrated access and backhaul donor control unit in a network: determining that the service flow of a user equipment (UE) is to be replicated by an integrated access and backhaul network node in the network; and configuring at least one of the following for the integrated access and backhaul network node: information that the UE's service flow in the downlink direction is to be replicated and information that the UE's service flow in the uplink direction is to be merged.

[0017] Additional exemplary embodiments include a computer program that includes code for performing the method of the preceding segment when the computer program is run on a processor. According to this paragraph, the computer program is a computer program product including a computer-readable medium in which computer program code for use with a computer is implemented. Another example is a computer program according to this paragraph, wherein the program is directly loadable into the computer's internal memory.

[0018] An exemplary device includes one or more processors and one or more memories including computer program code. The one or more memories and computer program code are configured, together with the one or more processors, to cause the device to perform operations including: at an integrated access and backhaul donor control unit in a network, performing the following operations: determining that a user equipment's traffic flow is to be replicated by an integrated access and backhaul network node in the network; and configuring the integrated access and backhaul network node with at least one of the following: information that the user equipment's traffic flow in the downlink direction is to be replicated and information that the user equipment's traffic flow in the uplink direction is to be merged.

[0019] An exemplary computer program product includes a computer-readable storage medium in which computer program code for use with a computer is implemented. The computer program code includes code for performing the following operations at an integrated access and backhaul donor control unit in a network: determining that the service flow of a user equipment (UE) is to be replicated by an integrated access and backhaul network node in the network; and configuring at least one of the following for the integrated access and backhaul network node: information that the UE's service flow in the downlink direction is to be replicated and information that the UE's service flow in the uplink direction is to be merged.

[0020] In another exemplary embodiment, an apparatus includes components for performing the following operations: at an integrated access and backhaul donor control unit in a network, performing the following operations: determining that a user equipment's service flow is to be replicated by an integrated access and backhaul network node in the network; and configuring the integrated access and backhaul network node with at least one of the following: information that the user equipment's service flow in the downlink direction is to be replicated and information that the user equipment's service flow in the uplink direction is to be merged. Attached Figure Description

[0021] In the attached diagram:

[0022] Figure 1 This is a block diagram of a possible and non-limiting exemplary system in which exemplary embodiments can be practiced;

[0023] Figure 2 The diagram illustrates the overall IAB architecture, in which... Figure 2 Figure A illustrates the configuration of an IAB node using CA mode with NGC, and Figure 2 Figure B illustrates the IAB node configuration using EN-DC;

[0024] Figure 3 The diagram illustrates the parent and child node relationships for an IAB node.

[0025] Figure 4 The diagram illustrates the protocol stack used to support the F1-U protocol (left) and the F1-C protocol (right).

[0026] Figure 5 The diagram illustrates routing and BH RLC channel selection at the BAP sublayer;

[0027] Figure 6 The illustration depicts resource inefficiencies in an IAB network that uses carrier aggregation (CA) (Scenario 1) and dual connectivity (DC) (Scenario 2) to carry radio bearers configured with PDCP packet replication.

[0028] Figure 7 This is a block diagram illustrating a replica processing function in an access IAB node for CA-based replication according to a first exemplary embodiment.

[0029] Figure 8 This is a flowchart of the first embodiment, in which the UE is configured with CA replication; and

[0030] Figure 9 This is a block diagram illustrating the replica discarding function in an intermediate IAB node for DC-based replication according to a second embodiment. Detailed Implementation

[0031] The abbreviations that may appear in the specification and / or drawings are defined as follows, and are located at the end of the detailed description section.

[0032] The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as being more preferred or advantageous than other embodiments. All embodiments described in this “Detailed Description” are exemplary embodiments provided to enable those skilled in the art to make or use the invention without limiting the scope of the invention as defined by the claims.

[0033] The exemplary embodiments described herein illustrate techniques for enhancing resource efficiency in IAB networks. Further descriptions of these techniques are given after describing systems in which exemplary embodiments may be used.

[0034] Turning Figure 1 This figure illustrates a block diagram of a possible, and non-limiting, exemplary system in which exemplary embodiments can be practiced. It shows a user equipment (UE) 110, multiple IAB nodes 170 and 170-1, and (multiple) network elements 190. Figure 1In this configuration, User Equipment (UE) 110 wirelessly communicates with Wireless Network 100. The UE is wireless and is typically a mobile device capable of accessing the wireless network. UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected via one or more buses 127. Each of the one or more transceivers 130 includes a receiver Rx 132 and a transmitter Tx 133. The one or more buses 127 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic cables, or other optical communication devices. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. UE 110 includes a control module 140, which includes one or both of portions 140-1 and / or 140-2, and may be implemented in various ways. The control module 140 may be implemented in hardware as control module 140-1, such as as part of one or more processors 120. Control module 140-1 can also be implemented as an integrated circuit or through other hardware such as a programmable gate array. In another example, control module 140 can be implemented as control module 140-2, which is implemented as computer program code 123 and executed by one or more processors 120. For example, one or more memories 125 and computer program code 123 can be configured, together with one or more processors 120, to cause user equipment 110 to perform one or more of the operations described herein. UE 110 communicates with IAB node 170-1 via radio link 111, and IAB node 170 communicates with IAB donor node 170 via backhaul link 176.

[0035] Two IAB network nodes, 170 and 170-1, are shown, with IAB network node 170 represented as a donor node in one example. Further details regarding possible network structures using IAB network nodes 170, 170-1 (and additional IAB nodes) are provided below; however, for simplicity, it is assumed that the circuitry between IAB network nodes 170 and 170-1 is similar. That is, each of the network nodes 170 and 170-1 will contain a processor, memory, and computer program code (described below), and the operations performed by the respective network nodes 170 / 170-1 can be implemented in hardware, software, or a combination of both, as described below. Therefore, only the circuitry of IAB network node 170 is shown.

[0036] It should also be noted that the Central Unit (CU) 196 and the Distributed Unit (DU) are shown as part of the IAB donor node 170. However, this is for illustrative purposes; for example, DUs and CUs are typically separate in cloud RAN implementations. Therefore, the DU 195 and CU 196 portions of the IAB network node 170 can be physically separated, and each has its own processor / memory / computer program code. Further note that an IAB DU can also be referred to as an IAB DU node, because in the case of a DU separated from a CU, each of the DU and CU can be its own node. As used herein, the integrated access and backhaul network node can be IAB node 170-x (where “x” is 1, 2, ...) or IAB DU node 195.

[0037] IAB network nodes 170 / 170-1 are base stations that provide access to wireless network 100 through wireless devices such as UE 110, and can be either donor nodes (170) or IAB nodes (170-1). Donor node 170 is typically connected to the core network, which is illustrated here in part using network elements (multiple) 190. This connection is shown as link 131, which is typically a fiber optic link, but can also be any other suitable link.

[0038] For example, IAB network node 170 can be a 5G (also known as New Radio (NR)) base station. In 5G, IAB node 170 can be an NG-RAN node, defined as a gNB or ng-eNB. For clarification, in a non-standalone (NSA) network, an IAB can be deployed using an EN-DC (EUTRAN NR Dual Connectivity) connection, where the serving node of the IAB node can be an eNB (master node). However, the eNB only provides a control interface, and the backhaul (BH) (e.g., data) is carried on the NR tributary of the DC. A gNB is a node that provides NR user plane and control plane protocol termination to the UE and is connected to the 5GC (e.g., multiple network elements 190) via an NG interface. An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination to the UE and is connected to the 5GC via an NG interface. An NG-RAN node may include multiple gNBs, and a gNB may also include a central unit (CU) (gNB-CU) 196 and (multiple) distributed units (DUs) (gNB-DUs), of which DU 195 is shown. Note that a DU may include or be coupled to a radio unit (RU) and control the RU. A gNB-CU is a logical node that hosts the RRC, SDAP, and PDCP protocols of the gNB or the RRC and PDCP protocols of the en-gNB. An F1-C connection exists between the CU and the DU, through which the CU controls the DU using the F1AP protocol. The gNB-CU terminates the F1 interface connected to the gNB-DU. The F1 interface is shown as reference numeral 198, although reference numeral 198 also shows a link between a remote element of IAB network node 170 and a centralized element of IAB network node 170, such as the link between gNB-CU 196 and gNB-DU 195. For the CU 196 connected to DU 195-1, link 198-1 is a1. The gNB-DU is a logical node that hosts the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. A gNB-CU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface 198 connected to the gNB-CU. Note that DU 195 is considered to include transceiver 160, for example, as part of an RU; however, some examples in this regard could allow transceiver 160 to be part of a separate RU, for example, under the control of and connected to DU 195. The IAB node 170 can also be an eNB (evolved Node B) base station for LTE (Long Term Evolution), or any other suitable base station.

[0039] IAB node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (multiple N / WI / F) 161, and one or more transceivers 160 interconnected via one or more buses 157. Each of the one or more transceivers 160 includes a receiver Rx 162 and a transmitter Tx 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. CU 196 may include multiple processors 152, memories 155, and network interfaces 161. Note that DU 195 may also contain its own memories (and corresponding computer program code) and multiple processors, and / or other hardware, but these are not shown.

[0040] IAB node 170 includes a control module 150, which includes one or both of portions 150-1 and / or 150-2, and can be implemented in various ways. Control module 150 can be implemented in hardware as control module 150-1, such as as part of one or more processors 152. Control module 150-1 can also be implemented as an integrated circuit or via other hardware such as a programmable gate array. In another example, control module 150 can be implemented as control module 150-2, which is implemented as computer program code 153 and executed by one or more processors 152. For example, one or more memories 155 and computer program code 153 are configured, together with one or more processors 152, to cause IAB node 170 to perform one or more operations as described herein. Note that the functionality of control module 150 can be distributed, such as distributed between DU 195 and CU 196, or implemented only in DU 195.

[0041] One or more network interfaces 161 communicate over a network, such as via links 176 and 131. Two or more IAB nodes 170, 170-1 communicate using, for example, link 176. Link 176 may be wireless and may implement, for example, an NR Uu interface.

[0042] One or more buses 157 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber or other optical communication equipment, wireless channels, etc. For example, one or more transceivers 160 may be implemented as a Remote Radio Header (RRH) 195 for LTE or a Distributed Unit (DU) 195 for a gNB implementation of 5G, wherein other elements of the IAB node 170 may be physically located in a different location from the RRH / DU, and one or more buses 157 may be partially implemented, for example, as fiber optic cables or other suitable network connections for connecting other elements of the IAB node 170 (e.g., Central Unit (CU), gNB-CU) to the RRH / DU 195. Reference numeral 198 also indicates those suitable network links(s).

[0043] IAB node 170-1 includes DU 195-1 and MT 70. These will be described in more detail below. DU 195-1 and MT70 can be implemented as hardware or software or some combination thereof. That is, for ease of reference, only CU 196 with processor(s) 152 and memory(s) 155 is shown. However, any DU or MT may also have this circuitry. Note that only one IAB node 170-1 is shown, but there may be two or more such nodes (as shown below), and the term "170-x" (where x = 1, 2, 3, ...) is used below to refer to any of these nodes.

[0044] Wireless network 100 may include one or more network elements 190, which may include core network functions and provide connectivity to data network 191, such as telephone networks and / or data communication networks (e.g., the Internet), via one or more links 181. Such core network functions for 5G may include access and mobility management functions (AMF) and / or user plane functions (UPF) and / or session management functions (SMF). Such core network functions for LTE may include MME (Mobility Management Entity) / SGW (Serving Gateway) functions. These are merely exemplary functions that the network elements 190 may support, and it should be noted that both 5G and LTE functions may be supported. IAB node 170 is coupled to network element 190 via link 131. Link 131 may be implemented as, for example, an NG interface for 5G, or an S1 interface for LTE, or other suitable interfaces for other standards. Network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N / WI / F) 180 interconnected via one or more buses 185. One or more memories 171 include computer program code 173. The one or more memories 171 and computer program code 173 are configured to, together with one or more processors 175, cause network element 190 to perform one or more operations.

[0045] Wireless network 100 can implement network virtualization, which is a process of combining hardware and software network resources and network functions into a single software-based managed entity (virtual network). Network virtualization involves platform virtualization, which is often combined with resource virtualization. Network virtualization can be divided into external network virtualization or internal network virtualization. External network virtualization combines many networks or parts of networks into a virtual unit, while internal network virtualization provides network-like functionality to software containers on a single system. Note that, to some extent, the virtualized entity created by network virtualization is still implemented using hardware such as processors 152 or 175 and memories 155 and 171, and this virtualized entity also produces technical effects.

[0046] Computer-readable storage devices 125, 155, and 171 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic storage devices and systems, optical storage devices and systems, fixed storage, and removable storage. Computer-readable storage devices 125, 155, and 171 can be components for performing storage functions. Processors 120, 152, and 175 can be of any type suitable for the local technical environment and, as non-limiting examples, can include one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Processors 120, 152, and 175 can be components for performing functions such as controlling UE 110, IAB node 170, and other functions described herein.

[0047] Typically, various embodiments of user equipment 110 may include, but are not limited to, cellular phones such as smartphones, tablets, personal digital assistants (PDAs) with wireless communication capabilities, portable computers with wireless communication capabilities, vehicles with modem devices for wireless V2X (vehicle-to-everything) communication, image capture devices such as digital cameras with wireless communication capabilities, gaming devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, internet devices (including Internet of Things (IoT) devices) that allow wireless internet access and possible browsing, IoT devices with sensors and / or actuators for automation applications with wireless communication tablets, and portable units or terminals that combine such functions.

[0048] Having introduced a suitable but non-limiting technical context for the practice of exemplary embodiments, exemplary embodiments will now be described in more detail.

[0049] As mentioned earlier, due to the characteristics of IAB, it can be accessed via a wireless interface (Uu) (e.g., Figure 1 Link 176 in the IAB relays user services between two relay nodes, designated IAB nodes 170 and 170-1. Relays can occur on one or more hops. The overall IAB architecture is... Figure 2 As shown in the image. Figure 2 The diagram illustrates the overall IAB architecture, in which... Figure 2 Figure A illustrates the configuration of an IAB node using CA mode with NGC, while Figure 2 Figure B illustrates the IAB node configuration using EN-DC. This figure is sourced from 3GPP TS38.300V16.2.0 (2020-07). Figure 4 7.1-1.

[0050] exist Figure 2 In A, there are two AMF / UPF 190-1 and 190-2, gNB 210, IAB donor node (e.g., gNB) 170, and two IAB nodes 170-1 and 170-2. Interfaces NG, Xn, NR Uu, and F1 are shown. Figure 2 In section B, there are two MME / S-PGWs 190-3 and 190-4, an eNB 220, an eNB acting as a MeNB, an IAB donor node (e.g., SgNB) 170, and two IAB nodes 170-1 and 170-2. Interfaces S1, X2, S1-U, X2-C, LTE Uu, NR Uu, and F1 are shown.

[0051] In the IAB architecture, there are two types of nodes—IAB donor 170 and IAB node 170-1. IAB donor node 170 is a node with a wired connection to the core network. IAB donor 170 includes donor CU 196, which hosts the RRC, SDAP, and PDCP layers of the NR air interface, and donor DU 195, which hosts the RLC, MAC, and PHY layers of the NR air interface stack. On the other hand, IAB node 170-1 consists of IAB-DU 195-1 and IAB-MT 70. IAB DU 195 connects to the donor CU 196 via an F1 interface and provides radio connectivity for access UE 110 and for child nodes or other next-hop IAB nodes 170-1 (i.e., those served by IAB-DU). IAB-MT 70 is responsible for providing radio backhaul connectivity to upstream IAB node 170-x or IAB donor 170, or may have other connections besides backhaul, such as PDU sessions for OAM (Operation and Maintenance) services. In IAB, downstream nodes connected to an IAB node are called its child nodes. Upstream nodes of an IAB node are called its parent nodes. IAB nodes can connect to up to two parent nodes simultaneously using NR dual-connectivity mode to provide topology redundancy for backhaul links. These dependencies are... Figure 3 The information is provided in the text.

[0052] Figure 3 The diagram illustrates the parent and child relationships of IAB nodes. This diagram is sourced from 3GPP TS38.300V16.2.0 (2020-07). Figure 47.1-2. In this example, parent nodes 170A and 170B include IAB-DU195A and 195B. IAB node 170-1 includes IAB-MT 70 and IAB-DU 195-1. Parent nodes 170A and 170B are upstream of IAB node 170-1, and child nodes 170-2A, 170-2B, and 170-2C are downstream. Child nodes 170-2A, 170-2B, and 170-2C include corresponding IAB-MT 70-1A, 70-1B, and 70-1C. The interface between these nodes is an NR Uu interface.

[0053] To enable wireless backhaul, a new protocol layer, called Backhaul Adaptation Protocol (BAP), was introduced into the air interface between the IAB donor DU and the IAB node, as well as between two IAB nodes. The protocol stack used to carry user plane and control plane data over the two-hop IAB chain is... Figure 4 The diagram is provided in [the document / reference]. The source of this diagram is 3GPP TS 38.300, and... Figure 4 The protocol stacks used to support the F1-U protocol (left) and the F1-C protocol (right) are shown.

[0054] In this example, IAB donor 170 has CU 196 with layers GTP-U and UDP, and DU 195 with layers IP, BAP, RLC, MAC, and PHY. In the stack shown, the lowest layer is the PHY (physical) layer, and the highest layer is the GTP-U layer. A BH NR RLC channel exists between IAB donor 170 and IAB node 1 170-1. Figure 4 In this configuration, the F1-U interface is located between IAB donor 170 and IAB node 2 170-2. This is transparent and relayed only by IAB node 1 170-1. Figure 4 There is also an F1-U interface that terminates at IAB node 1 but is not shown in the diagram. IAB node 1 170-1 has an IAB-MT 70 with layers BAP, RLC, MAC, and PHY, and an IAB-DU 195-1 with layers BAP, RLC, MAC, and PHY. An F1-U interface and a BH NR RLC channel exist between IAB node 1 170-1 and IAB node 2 170-2. The F1-U interface terminates at IAB-DU195-2 at IAB node 2 170-2, which has GTP-U, UDP, and IP layers. The BH NR RLC channel terminates at IAB-MT 70-1, which includes layers BAP, RLC, MAC, and PHY.

[0055] BAP is responsible for mapping upper-layer services (F1-U, F1-C, or non-F1 services) to BH RLC channels using channel mapping configurations. These channel mapping configurations are provided to IAB nodes and IAB donor DUs using F1AP and / or RRC protocols. Services are mapped based on information included in the headers of higher-layer protocols such as IP or GTP-U. Specific mappings are configured as follows:

[0056] 1) Used for each F1-U GTP-U tunnel;

[0057] 2) Used for non-UE related F1AP messages;

[0058] 3) UE-related F1AP messages for each UE; and

[0059] 4) Used for non-F1 business.

[0060] Another responsibility of the BAP is to determine the destination node of higher-layer packets and to route BAP packets within the IAB network based on the BAP address and BAP path identifier carried in the BAP header and the routing configuration provided by the F1AP protocol. The BAP header is generated in the IAB node 170-x (in this example, "x" is 1 or 2) where the service originates (for upstream services) and in the IAB donor DU 195 for downstream services. When a BAP packet arrives at IAB node 170-x, the node checks the BAP address included in the BAP header to determine if it matches its own BAP address (previously configured by donor CU 196). If so, it is provided to higher layers within the IAB node for further processing. Otherwise, IAB node 170-x checks its routing table and BH RLC channel mapping configuration to determine the links and BH RLC channels in which the BAP packet should be routed. An example of this operation is... Figure 5 The information is provided in the text.

[0061] Figure 5 The diagram illustrates routing and BH RLC channel selection at the BAP sublayer. It is sourced from 3GPP TS 38.300. Route from one hop to the next is performed through the selection of BH RLC channels. The diagram shows the ingress BH link and ingress BH RLC channel, as well as the egress BH link and egress BH RLC channel.

[0062] The initial IAB network is expected to be deployed in a controlled and planned manner, such as:

[0063] 1) Fixed location of IAB nodes;

[0064] 2) Comprehensive network and radio planning prior to deployment;

[0065] 3) Use of directional antennas; and / or

[0066] 4) Sight insurance.

[0067] In such a deployment, the BH link is far more reliable than the access radio link between the UE and the IAB node. The BH network can also be protected via path redundancy; that is, in the event of a BH link failure, BH services can be routed via another BH link or IAB segment. On the other hand, for access UEs, one method to increase service reliability is the use of PDCP packet replication, such as:

[0068] 1) Carrier aggregation (CA) replication, in which the same packets are transmitted through different cells of the same gNB;

[0069] 2) Dual-connection (DC) replication, in which the same packets are sent through cells belonging to two different gNBs;

[0070] 3) In Rel-15, replication over two cells is possible, while Rel-16 allows replication over up to four cells; and / or

[0071] 4) In Rel-16, CA replication can be configured together with DC replication.

[0072] Packet replication is described in section 16.1.3 of 3GPP TS 38.300.

[0073] When PDCP replication is configured for the UE's radio bearer, a separate GTP-U tunnel is established for each RLC channel participating in replication. This means that data is replicated not only through the air interface but also through the F1 or Xn interface in the RAN network. While replication is reasonable for the UE's access link, for example in a fixed IAB deployment, it is unnecessary on the BH link, which the inventors consider reliable and replication unnecessary for fixed IAB networks. Therefore, the benefit of replicating packets through the BH link is minimal, while reducing network resource efficiency and capacity. This can also cause donor DU195 and IAB node 170-1, which is close to donor DU195, to become bottlenecks in the IAB system. This problem is... Figure 6 The presentation is tailored to two different scenarios.

[0074] Scenario 1 610 involves CA replication between a single IAB node 170-2 and UE 110. Donor CU 196, Donor DU 195, IAB node #1 170-1, and IAB node #2 170-2 are shown, and CA replication 620 performed via radio links 613 and 614 is illustrated. Waste of resource 650 occurs because dashed lines 611 and solid lines 612 indicate two paths, each carrying the same data. Path 611 is used for the first GTP-U#1 path, and path 612 is used for the second GTP-U#2 path. Paths 611 and 612 carry the same user data via a BH link. Replication and GPT tunneling terminate at the access IAB node 170-2. Two RLC / MAC / PHY connections exist via the CA carrier through the Uu interface (via links 613 and 614), while PDCP is end-to-end between UE 110 and IAB donor node 196. In fact, assuming that the other paths 611 and 612 are error-free or low-error, only IAB#2 170-2 needs to use radio links 613 and 614 to perform replication. A similar issue applies to the uplink when the UE transmits uplink data to donor CU 196 via the access node (IAB#2 170-2), intermediate IAB node (IAB#1 170-1), and donor DU 195. In one example, radio links 613 and 614 can be used for the primary cell (PCell) and secondary cell (SCell), respectively.

[0075] Scenario 2 630 involves DC replication between two IAB nodes (170-2A and 170-2B) and UE 110. Donor CU 196, donor DU 195, IAB node #1 170-1, and IAB nodes #2 170-2A and 170-2B are shown, and DC replication 640 performed using radio links 613 and 614 is illustrated. The waste of resources 650 occurs because dashed lines 611 and solid lines 612 indicate two paths, each carrying the same data. Path 612 is used for the first GTP-U#1 path, and path 611 is used for the second GTP-U#2 path. Only IAB #1 170-1 needs to use its paths 616 and 617 to perform replication; IAB nodes #2 170-2A and #3 170-2B will transmit this replication via radio links 613 and 614, respectively. This again assumes that other paths 611 and 612 are error-free or have low error rates. A similar issue applies to the uplink when the UE transmits uplink data to donor CU 196 via access nodes (IAB#2 170-2, IAB#3 170-2B), intermediate IAB nodes (IAB#1170-1), and donor DU 195. In one example, radio links 613 and 614 could be used for the primary / secondary cell (PSCell) and the primary cell (PCell), respectively.

[0076] For non-IAB replication operations, a previous proposal suggested using a single GTP-U tunnel on the Xn interface between the primary and secondary nodes, with both nodes participating in replication. This proposal has not yet been adopted in the 3GPP standard. It should be noted that in the IAB case, the previously proposed technique cannot be directly reused because additional mechanisms are needed for replication and copy dropping within the IAB node. Furthermore, this issue is more critical for IAB because traffic is replicated on air interfaces where radio resources are very scarce. For the non-IAB use cases discussed earlier, the problem is less severe because in RAN networks, traffic is replicated only on wired interfaces, which typically have high capacity.

[0077] In addition to the other issues mentioned above, this paper proposes a mechanism to address this problem by introducing a mechanism that avoids unnecessary duplicate packets in IAB Node 170-x or IAB donor DU195 before carrying packets on unnecessary backhaul links, while still allowing packet replication in necessary IAB network nodes and over the air interface. First, an overview is provided, followed by additional details.

[0078] In an exemplary embodiment, as an overview, the mechanism is based on the following.

[0079] 1) Donor CU 196 provides a "replication configuration" for the UE's radio bearer (RB) to enable packet replication. The configuration information is provided using one of the following options (a) through (c).

[0080] a) Within the backhaul configuration of the IAB donor DU (for DL ​​services) and / or the access IAB node (for UL services). Upon receiving such a configuration, the IAB donor DU or IAB node adds a replication indication to the BAP header of the packet associated with the replicated radio bearer. Note that the "access" IAB node is the node to which the UE is attached. An IAB node can be an access IAB node for some UEs, and can also be a regular BHIAB node for other UEs that are not directly attached to an IAB node but are attached through a sub-IAB node. For access IAB nodes, this can also be performed within the F1-U tunnel configuration or as part of the UE radio bearer configuration. When F1-C packets need to be replicated, the configuration in the access IAB node can be performed during the gNB-DU configuration update process or the gNB-CU configuration update process.

[0081] b) The service should be replicated for the access UE by indicating the BH RLC channel carrying the service. In this case, the IAB donor DU 195 and / or IAB node 170-x identify that the packet belongs to the replicated radio bearer based on the packet's ingress or egress BH RLC channel.

[0082] Based on this configuration, the IAB network node (donor DU or IAB node) detects relevant services and adds replication instructions.

[0083] In the DL direction, the indication may additionally include information about the number of copies required and / or which access logical channels should be used for packet delivery to the UE.

[0084] 2) Based on the replication instruction, the IAB node performs the following operations.

[0085] a) In the DL direction, when a packet marked with a copy instruction is received (e.g., carried in the BAP header or derived based on its ingress BH RLC channel), the IAB Node 170-x or IAB-MT 70-x function of IAB Node 170-x indicates that the packet should be copied via the air interface to the function responsible for packet delivery to the UE (e.g., to the upper layer or BAP sublayer transmission portion in the IAB node, etc.). After receiving such an instruction, IAB Node 170-x (or the IAB-DU 195-x function of IAB Node 170-x) copies the packet via the air interface.

[0086] b) In the UL direction, in response to receiving a packet via a radio bearer configured with replication, or based on a previously configured replication indication, IAB node 170-x performs a copy drop function, which is typically performed only in the PDCP layer hosted by donor CU 196.

[0087] Furthermore, the drop function can be performed based on the packet's PDCP sequence number (SN), meaning the IAB node needs to have basic PDCP functionality, such as PDCP replica drop and PDCP windowing. The drop function will remember the received PDCP sequence number. However, when all PDCP SNs have been used, the PDCP layer will reuse SNs starting from 0 (zero), and the PDCP layer uses a window to ensure no confusion. This window should be used by the IAB node to know the current SN's position within the PDCP SN window.

[0088] Copy-related functions can reside in either IAB-MT or IAB-DU. Consider the following: For UL, it makes more sense to detect and discard copies once they are received for the UE from the IAB-DU. For DL, the Rx portion of the BAP layer can indicate the need for copies to the upper layer, and the upper layer will handle this (the upper layer refers to the layer above the IAB-DU).

[0089] An overview has now been provided; more details will follow. In the first embodiment, the UE is configured with CA-based replication. Figure 7 An exemplary implementation is depicted in which a replica processing function 710 is introduced in the access IAB node 170-2 to handle access UE radio bearers configured with CA-based replication. The figure also illustrates a PCell (primary cell) 730 and an SCell (secondary cell) 720 formed by IAB 2 170-2. Note that each of the PCell 730 and SCell 720 has its own RLC and MAC layers, which are used to perform packet replication in the CA example. Figure 7 The layers and other blocks in the components can be parts used to perform those corresponding functions and can be implemented in hardware or software, as described above with respect to the processors and memories of each of the UE 110 and IAB donor nodes 170 and IAB nodes 170-x.

[0090] The following exemplary alternatives are proposed for services transmitted in the DL direction.

[0091] 1) In the first alternative:

[0092] a) The donor CU 196 configures the donor DU 195 to replicate specific traffic flows for the UE, identified for example by specific IP header content (e.g., IP address and / or port number and / or Differentiated Service Code Point (DSCP) and / or IPv6 flow label, etc.). The donor CU 196 can also configure the donor DU 195 to replicate specific traffic flows for the UE, identified for example by specific GTP-U header content (e.g., GTP-U tunnel endpoint identifier).

[0093] b) Later, when donor DU 195 receives downlink data from donor CU 196, the DU uses the previously received configuration to check the IP header content and / or GTP-U header content. If a match is found, donor CU 196 includes a "replication indication" for the packets associated with the flow in the BAP header. The indication may additionally include information about the number of copies required and / or which access logical channels should be used for packet delivery to the UE.

[0094] c) When such a BAP PDU arrives at the destination IAB node, the BAP layer instructs the upper layer that the packet should be copied through the air interface.

[0095] d) The replication processing function 710 in IAB node 170-2 ensures that BAP SDUs are replicated and provided for transmission to multiple logical channels based on configuration.

[0096] 2) In the second alternative:

[0097] a) Donor CU 196 uses a replication instruction at destination IAB node 170-2 to configure a specific BH RLC channel or a specific service of a specific BH RLC channel, identified by at least one of the following fields: Backhaul Radio Link Control Channel Identity, Routing Identifier, Tunnel Endpoint Identifier, or any field in the Backhaul Adaptation Protocol header. In this case, donor DU 195 maps incoming packets to the RLC channel as usual according to the instructions of the CU.

[0098] b) The copy processing function 710 at IAB node 170-2 ensures that every packet arriving on a certain BH RLC channel is copied via the air interface.

[0099] c) This instruction can be passed to the upper layer via the BAP sublayer, or it can be left to the IAB node to implement.

[0100] For services transmitted in the UL direction, the following is one possible implementation.

[0101] 1) Similar to DL, IAB node 170-2 is configured with information from donor CU 196, indicating that a certain UE DRB is configured to replicate. Such configuration can be part of the BH service mapping configuration or part of the F1 tunnel configuration used for radio bearer configuration, for example, during the UE's F1AP UE context establishment / modification process.

[0102] 2) UE 110 uses two or more RLC entity / logical channels to send data to access IAB node 170-2.

[0103] 3) IAB node 170-1 checks the identifier of packets belonging to the replicated service flow, such as the PDCP SN, and discards the PDCP PDU if the packet with this SN was received earlier. Thus, only one copy of the user data is sent to IAB#1 170-1 and further to donor CU 196. This merges the two service flows from the UE into a single uplink service flow, which contains information from only one service flow from the UE.

[0104] Figure 8 An exemplary flowchart of a first embodiment is provided. This diagram further illustrates the operation of one or more exemplary methods according to exemplary embodiments, the execution results of computer program instructions implemented on a computer-readable storage medium, functions executed by hardware-implemented logic, and / or interconnect components for performing functions. Assuming... Figure 8 The operations are performed at least in part by UE 110 under the control of control module 140, or at least in part by IAB network node 170 or 170-x under the control of control module 150.

[0105] exist Figure 8 In step 1, a DRB with CA PDCP replication is established. This occurs between UE 110 and IAB node 2170-2, and then further between IAB node 2170-2 and donor CU 196 via IAB node 1170-1 and donor DU 195. In step 2, donor CU 196 transmits a message to donor DU 195, which includes the backhaul mapping configuration for the DL service flow and a replication indication. Donor CU 196 also sends this message to IAB node 170-2 in step 3 to configure replication.

[0106] Box 810 indicates signaling that occurs for the processing of a duplicate DRB in the DL. Box 820 indicates signaling that occurs for the processing of a duplicate DRB in the UL. Box 810 is described first.

[0107] In box 810, donor CU 196 sends (step 4) a message including the DL user data of the replicated DRB. Donor DU 195 detects the user data that needs to be replicated based on the configuration received in step 2. Donor DU 195 adds (step 5) a replication indication to the BAP header (in this example) based on the BH mapping configuration. This conforms to the first alternative above, where donor DU 195 includes a "replication indication" for the packet associated with the flow in the BAP header.

[0108] Donor DU 195 performs (step 6) delivery of a BAP PDU with an instruction for IAB Node 2 via an intermediate IAB node (e.g., IAB Node #1 170-1). That is, the delivery terminates at IAB Node 170-2. In the case of carrier aggregation, replication is always performed by the access IAB node, so the intermediate IAB node does not receive any instructions from the CU regarding replication, and the BAP header does not indicate that the intermediate node should replicate. In this case, the access IAB node is IAB Node 2 170-2. IAB Node 170-2 performs (step 7) detection of the replication instruction in the BAP header, and then performs (step 8) providing the replication instruction to the upper layer. Steps 7 and 8 are performed by the replication processing function 710, which sends the replication instruction to at least the RLC layer in PCell 730 and SCell 720. The RLC layer then determines that the packet involved in the DRB is being replicated and performs a known replication procedure. IAB node 170-2 performs packet delivery using PCell 730 in step 9 and packet copy delivery using SCell 720 in step 10. If a packet has already been successfully received via another path, the UE discards the packet. According to the examples in this document, UE behavior is unaffected by these operations.

[0109] For block 820, which indicates signaling occurring for the processing of the replicated DRB in the UL, UE 110 is in CA mode. Therefore, the UE transmits UL packets, for example via PCell 730, on the primary RLC channel of the replicated DRB. This occurs in step 11. In step 12, the UE transmits the same UL packets, for example via SCell 720, on the secondary RLC channel of the replicated DRB. Replication is for PDCP packets transmitted on a different carrier to the RLC channel (in the case of CA). PDCP packets are transmitted via the primary link, and replica packets are transmitted via the secondary link, and vice versa.

[0110] Steps 13 through 15 can be performed by the replica processing function 710. In step 13, the replica processing function 710 performs a replica detection function, and in step 14, the replica packets are discarded. As described above, the IAB node 170-2 (e.g., via the replica processing function 710) checks the PDCP SN of packets belonging to the replicated service flow and discards the PDCP PDU if a packet with such a SN was received earlier. The remaining single packet is delivered to the upper layer, such as the BAP, for transmission (step 15). See step 16. This means that the replica service flows from the UE are merged into a single service flow.

[0111] In the second embodiment, the UE is configured with DC-based replication. When the access UE is configured with DC-based replication, the replication processing function must reside in one of the intermediate IAB nodes. Figure 9 In the example, for this specific configuration of three IAB nodes 170-1, 170-2, and 170-3, this is IAB node 170-1. However, this is merely an example. The situation is as follows... Figure 9 As shown in the figure, the PCell (primary cell) 930 formed by IAB node 170-2 and the PSCell (primary-secondary cell) 920 formed by IAB 170-3 are also illustrated. Note that each of the PCell 930 (for IAB node 170-2) and the PSell 920 (for IAB node 170-3) has its own RLC and MAC layers used to perform packet replication in the DC example. Figure 9 The layers and other blocks in the components can be parts for performing those corresponding functions and can be implemented in hardware or software, as described above regarding the processor and memory of each of UE 110 and IAB donor node 170 and IAB nodes 170-2 / 170-3. The following methods also apply when UE 110 is directly connected to IAB 170-1 without IAB 170-2 or without IAB 170-3. When IAB 170-2 is absent and IAB 170-3 is present, PCell (primary cell) 930 is formed by IAB node 170-1, and PSCell (primary / secondary cell) 920 is formed by IAB 170-3. When IAB 170-2 is present and IAB 170-3 is absent, PCell (primary cell) 930 can be formed by IAB node 170-2, and PSCell (primary / secondary cell) 920 can be formed by IAB 170-1.

[0112] For services transmitted in the DL direction, the following is one possible implementation.

[0113] 1) It is not necessary to replicate the group via the BH link. The BH link is a common path between each of the IAB nodes 170-2 / 170-3 involved in DC replication.

[0114] a) For two paths, the group only needs to be copied from the last common node (IAB node 1 170-1 in the example shown).

[0115] (b) Donor CU 196 is aware of the topology and therefore also knows that IAB node 170-1 should replicate packets. Donor CU 196 configures donor DU 195 to replicate specific traffic flows for the UE, identified for example by specific IP header content (e.g., IP address and / or port number and / or Differentiated Service Code Point (DSCP) and / or IPv6 flow label, etc.). Donor CU 196 can also configure donor DU 195 to replicate specific traffic flows for the UE, identified for example by specific GTP-U header content (e.g., GTP-U tunnel endpoint identifier). Donor CU 196 configures donor DU 195 to add replication instructions and configures IAB node 170-1 to perform replication based on the replication instructions. That is, in the exemplary embodiment, donor CU 196 configures IAB node 170-1 to enable replication using replication instructions, and then IAB node 171-1 performs replication when data with replication instructions arrives.

[0116] 2) The replication instruction (added by donor DU 195, which is the first BAP node in the DL direction) can be carried in the BAP header, similar to the CA case. However, for the DC case, the BAP should also instruct the IAB node to perform packet replication:

[0117] a) In addition to the BAP address of the destination IAB node, the IAB node 170-x used to perform replication (in...) Figure 9 In the example, the address of IAB node 171-1 can be carried in the BAP header (e.g., added by the donor DU according to the configuration from the donor CU). Alternatively, the BAP header can remain unchanged, but the donor CU 196 configures the IAB node to perform replication of a specific BAP PDU, for example, when performing the configuration in step (b) below. In this alternative, nothing is added to the regular BAP header, and the donor DU simply sets the path ID according to the CU's instructions.

[0118] b) A special path ID (identifier) ​​or indication can be configured in the IAB node that indicates which BAP PDU should be copied along with additional information about which links to use for transmission. In this example, the CU configures this for the IAB node performing the copy. The donor DU typically only sets the path ID based on the CU's configuration. This can be achieved by configuring two route entries with the same route ID for the IAB node, optionally configuring a "copy indication". The route ID typically includes a BAP address and a path ID. In this case, the path ID portion of the route ID indicates that the packet should be copied, and there will be two BAP addresses in the BAP header. In this example, the route ID has the BAP address of the destination node (170-2A or 170-2B), but there is an additional BAP address indicating the node (170-1) performing the copy.

[0119] c) IAB node 170-1 can also be configured to modify the routing ID in the BAP header before further forwarding the packet. In other words, since the replica is pointing to a different end IAB node, the BAP address of the packet can be modified accordingly. CU196 can configure IAB node 170-1, or IAB node 170-1 can be pre-configured to decide to modify the header itself because the replica is sent to different destination IAB nodes 170-2 / 3. The replication indication can be carried in the BAP header. If so, the donor DU adds the indication.

[0120] d) Since the packets received by the two final IAB nodes, IAB node 170-2 and IAB node 170-3, will include the same IP packets (same IP address, etc.), the IP nodes need to be configured so that neither of them will drop the corresponding IP packets.

[0121] For services transmitted in the UL direction, the following is one possible implementation:

[0122] 1) Similar to the CA case, the replica should be discarded by the IAB node, in which case it will be the first common node 170-1 of the UL path of the replicated packet. That is, in the described case, the common node is IAB 1 170-1.

[0123] 2) To enable IAB node 170-1 to recognize the replica, perform the following operations:

[0124] a) Similar to the CA scenario, the IAB node (e.g., IAB 1 170-1) is configured (e.g., by donor CU 196) with information about which BH RLC channels and / or route IDs and / or GTP-U TEIDs are used to carry replicated packets. Since multiple GTP-U tunnels sharing the same BH RLC channel / route ID can exist between the access IAB and the donor CU, IAB 1170-1 can provide additional information, such as TEIDs, to identify the relevant UL service.

[0125] b) In the absence of IPsec configuration, IAB node 170-1 can snoop on BAP SDUs, read their PDCP SNs, check if packets with the same PDCP SN as the radio bearer have been sent previously, and if so, discard such duplicate packets.

[0126] c) If encryption is enabled for the F1 tunnel carrying the replicated bearer:

[0127] i) IAB nodes cannot directly check PDCP SN in PDCP PDU.

[0128] ii) To address this issue, the access IAB nodes (e.g., IAB 2 170-2 and IAB 3 170-3 in the described case) that process the logical channel configured for the copy radio bearer copy the GTP-U TEID and PDCP SN into the BAP header. If F1-C needs to be considered, access IAB nodes 170-2 / 3 copy the SCTP flow identifier and flow sequence number into the BAP header. Alternatively, the F1 tunnel can be terminated at an intermediate node processing the copy function (in this case, IAB node 170-1).

[0129] The replica processing function 910 merges replica service flows from the UE into a single service flow. That is, only a single service flow (e.g., an individual packet created using replica packets received via IAB nodes 170-2 and 170-3) is sent from IAB node 171-1 to the parent node.

[0130] It should also be noted that the current F1-U security is peer-to-peer, meaning one transmitter encrypts the GTP-U, and one receiver decrypts the received GTP-U packets. In the presented scenario, the destination of the DL F1-U is set to IAB2 170-2, and it is encrypted with the IAB 2-CU security key. Even if IAB 1 170-1 can copy the DL F1-U and send it to IAB 3 170-3, IAB 3 cannot decrypt the DL F1-U packet encrypted with the IAB 2 key. A security mechanism similar to that in MBMS could be used to allow both IAB 2 and IAB 3 to decrypt the DL F1-U packet.

[0131] Now that the first and second exemplary embodiments have been described, the examples relate to potential implementations of the copy discarding function, such as copy processing functions 710 / 910.

[0132] In UL, simple push-based window handling and discarding functionality can be implemented in the node responsible for avoiding duplication. Since the node is unaware of the HFN of the PDCP packet, it can rely on the SN of the packet. The node should also know the window size of the PDCP entity used for DRB. The node has a variable RX_Next_SN initialized to 0 (zero).

[0133] When a PDCP packet with a given RCV_SN is received, the calculation is performed modulo 2, where the window size is the receive window of the PDCP entity of the DRB. The following procedure can be performed, as shown in the pseudocode.

[0134] 1> If RX_Next_SN <= RCV_SN <RX_Next_SN+Window_size:

[0135] 2> If a PDCP with the same SN has already been received, discard the packet; otherwise, transmit the packet and store the state SN = RCV_SN;

[0136] 2> Set RX_Next_SN to RCV_SN+1, and reset the receive state of SN between RX_Next_SN and RCV_SN;

[0137] 1> Otherwise: Discard the packet (this should not happen if the PCDP packet is sent within the Window_size).

[0138] The following are additional examples.

[0139] Example 1. A method comprising:

[0140] In the integrated access and backhaul network nodes that are part of the radio access network communicating with user equipment, the following operations are performed:

[0141] Receive configuration, which contains information indicating which data should be replicated in the downlink direction and merged in the uplink direction;

[0142] In the downlink direction, for a single data radio bearer associated with a user equipment, first data is received via the backhaul link, the first data is determined to be data to be copied, the first data is copied into multiple downlink traffic streams, and multiple downlink traffic streams are sent toward the user equipment; and

[0143] In the uplink direction, second data is received from the user equipment through multiple uplink service flows, the second data is determined to be data to be merged, the second data is merged into a single service flow, and the single service flow is forwarded to the network through the backhaul link.

[0144] Example 2. According to the method described in Example 1, wherein:

[0145] Integrated access and backhaul network nodes connect to user equipment via carrier aggregation; and

[0146] Sending multiple service flows toward the user equipment and receiving second data from the user equipment via multiple service flows are performed by the integrated access and backhaul network nodes using carrier aggregation.

[0147] Example 3. According to the method described in Example 1, wherein:

[0148] The integrated access and backhaul network node is connected to the user equipment via dual connectivity, via a radio link between the integrated access and backhaul network node and the user equipment, and via a second backhaul link between the integrated access and backhaul network node as a parent node and another integrated access and backhaul network node as a child node of the parent node.

[0149] Sending multiple downlink service flows toward the user equipment includes sending corresponding downlink service flows from multiple downlink service flows via a radio link and a second backhaul link; and

[0150] Receiving second data from a user equipment via multiple uplink service flows also includes receiving second data via a radio link and a second backhaul link.

[0151] Example 4. According to the method described in Example 1, wherein:

[0152] The integrated access and backhaul network node, acting as the parent node, connects to the two integrated access and backhaul nodes, acting as child nodes, to provide dual connectivity to the user equipment.

[0153] Sending multiple downlink service flows toward the user equipment includes: sending the corresponding downlink service flow from the multiple downlink service flows to the corresponding child nodes in the child nodes via the second backhaul link; and

[0154] Receiving second data from a user equipment via multiple uplink service flows also includes receiving second data from the corresponding sub-nodes in the sub-nodes via a second backhaul link.

[0155] Example 5. The method according to any one of Examples 1 to 4, wherein:

[0156] Determining that the first data is indicated to be copied also includes: for data received via the backhaul link, determining that the data has an associated copying indication and indicates that the data is the first data that should be copied; and

[0157] Replication is performed only on the first data that is identified as having an associated replication instruction.

[0158] Example 6. The method according to any one of Examples 1 to 5 further includes determining, based on at least one of the following, whether the first data is indicated to be copied in the downlink direction or the second data is indicated to be merged:

[0159] Copy instruction;

[0160] Backhaul radio link control channel identity;

[0161] Route identifier;

[0162] Tunnel endpoint identifier; or

[0163] Any field in the Return Route Adaptation Protocol header.

[0164] Example 7. The method according to any one of Examples 1 to 6 further includes receiving configuration from the integration access and backhaul donor nodes for identifying replication or merging, the configuration including one or more of the following:

[0165] Backhaul radio link control channel identity;

[0166] Route identifier;

[0167] Tunnel endpoint identifier; or

[0168] Any field in the Return Route Adaptation Protocol header.

[0169] Example 8. According to the method of Example 1, wherein determining that the second data is indicated as data to be merged includes checking the backhaul adaptation protocol header of the second data to determine whether at least one of the tunnel endpoint identifier or the packet data aggregation protocol sequence number indicates that the second data should be merged or whether at least one of the flow control transport protocol flow identifier or the flow sequence number indicates that the second data should be merged.

[0170] Example 9. The method according to any one of Examples 1 to 8, wherein the integrated access and backhaul network node is an integrated access and backhaul node.

[0171] Example 10. The method according to any one of Examples 1 to 8, wherein the integrated access and backhaul network nodes are integrated access and backhaul donor distributed unit nodes.

[0172] Example 11. A method comprising:

[0173] Receive data for user equipment at the integrated access and backhaul donor distributed unit node;

[0174] The data is associated with the radio bearer of the data to be replicated by the integrated access and backhaul donor distributed unit nodes.

[0175] The integrated access and backhaul donor distributed unit nodes add replication instructions associated with the data; and

[0176] The integrated access and backhaul donor distributed unit nodes forward data and added replication instructions to the integrated access and backhaul nodes that are to perform data replication.

[0177] Example 12. The method according to Example 11, wherein determining that data is associated with the data radio bearer to be replicated by the integrated access and backhaul donor distributed unit node includes: receiving configuration information from the integrated access and backhaul central unit node for a specific service flow to be replicated for a user equipment, and the data is part of the specific service flow.

[0178] Example 13. The method according to Example 12, wherein the configuration information includes specific Internet Protocol header content that indicates a particular service flow to be copied for the user equipment.

[0179] Example 14. The method according to any one of Examples 11 to 12, wherein the replication instruction includes: a replication instruction in the backhaul adaptation protocol header for a packet associated with a specific service flow.

[0180] Example 15. The method according to any one of Examples 11 to 14, wherein the integrated access and backhaul nodes are access nodes for user equipment, and the access nodes use transmissions to user equipment via multiple radio links in carrier aggregation.

[0181] Example 16. The method according to Example 15, wherein the addition of data-associated replication instructions by the integrated access and backhaul donor distributed unit nodes further includes a replication instruction for packets associated with the service flow to be replicated in the backhaul adaptation protocol header.

[0182] Example 17. The method according to Example 16, wherein the replication indication in the backhaul adaptation protocol header includes information about the number of copies required and / or which access logical channels should be used for packet delivery to the user equipment.

[0183] Example 18. The method according to any one of Examples 11 to 14, wherein the integrated access and backhaul nodes use transmissions from at least one integrated access and backhaul sub-node to the user equipment via multiple backhaul links in dual connectivity, wherein the integrated access and backhaul node is the parent node of at least one integrated access and backhaul sub-node.

[0184] Example 19. The method described in Example 15, wherein:

[0185] The replication instructions added by the integrated access and backhaul donor distributed unit nodes, which are associated with the data, also include replication instructions for packets related to the service flow to be replicated in the backhaul adaptation protocol header; and

[0186] The method includes integrating access and backhaul donor distributed unit nodes to indicate that the integrated access and backhaul nodes should perform data replication.

[0187] Example 20. The method according to Example 19, wherein the integrated access and backhaul nodes that are instructed to perform data replication do so by including the addresses of the integrated access and backhaul nodes in the backhaul adaptation protocol header.

[0188] Example 21. The method according to Example 19, wherein the integrated access and backhaul nodes that indicate that data replication should be performed perform this action by adding a path identifier and a backhaul adaptation protocol address to the data, the path identifier indicating that the packet should be replicated, and the backhaul adaptation protocol address indicating the address of the integrated access and backhaul node used to perform the replication.

[0189] Example 22. A method comprising:

[0190] At the integrated access and backhaul donor control unit in the network, perform the following operations:

[0191] It is determined that the service flow of user equipment should be replicated by the integrated access and backhaul network nodes in the network; and

[0192] Configure at least one of the following for the integrated access and backhaul network nodes: information on which the service flows of the user equipment in the downlink direction are to be replicated, and information on which the service flows of the user equipment in the uplink direction are to be merged.

[0193] Example 23. The method according to Example 22, wherein the integrated access and backhaul network node is an integrated access and backhaul donor distributed unit node, and wherein the information includes at least one of the following information about the service flow in the downlink direction:

[0194] Internet Protocol address;

[0195] Differentiated service code point value;

[0196] Stream tags;

[0197] Fields in the Internet Protocol header; or

[0198] Tunnel endpoint identifier.

[0199] Example 24. The method according to Example 23, wherein information about the merging of service flows in the uplink direction of the user equipment further instructs the integrated access and backhaul donor distributed unit node that multiple service flows in the uplink direction of the user equipment should be merged into a single service flow, and wherein the information includes at least one of the following information about the service flows in the uplink direction:

[0200] Backhaul radio link control channel identity;

[0201] Route identifier;

[0202] Tunnel endpoint identifier; or

[0203] Any field in the Return Route Adaptation Protocol header.

[0204] Example 25. The method described in Example 22, wherein:

[0205] Integrated access and backhaul network nodes are integrated access and backhaul nodes;

[0206] The information to be replicated for the user equipment's downlink traffic includes at least one of the following:

[0207] Backhaul radio link control channel identity;

[0208] Route identifier;

[0209] Tunnel endpoint identifier; or

[0210] Any field in the Return Route Adaptation Protocol header; and

[0211] The information to be merged for the uplink traffic flow of the user equipment includes at least one of the following:

[0212] Backhaul radio link control channel identity;

[0213] Route identifier;

[0214] Tunnel endpoint identifier; or

[0215] Any field in the Return Route Adaptation Protocol header.

[0216] Example 26. A computer program comprising code for executing the method according to any one of Examples 1 to 25 when the computer program is run on a computer.

[0217] Example 27. An apparatus comprising components for performing the method according to any one of Examples 1 to 25.

[0218] Example 28. An apparatus comprising: one or more processors; and one or more memories including computer program code, wherein the one or more memories and the computer program code are configured together with the one or more processors to cause the apparatus to perform the method according to any one of Examples 1 to 25.

[0219] Without limiting the scope, interpretation, or application of the following claims in any way, the technical effects and advantages of one or more example embodiments disclosed herein are improved resource efficiency on backhaul links. Another technical effect and advantage of one or more example embodiments disclosed herein is increased IAB network capacity. Yet another technical effect of one or more example embodiments disclosed herein is that, simultaneously, additional reliability of the access link can still be ensured due to replication.

[0220] The term "circuit system" as used in this application may refer to one or more or all of the following:

[0221] (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems) and

[0222] (b) A combination of hardware circuitry and software, such as (if applicable):

[0223] (i) a combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) any part of (multiple) hardware processors having software (including (multiple) digital signal processors, software, and (multiple) memories), which work together to cause a device (such as a mobile phone or server) to perform various functions, and

[0224] (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (such as firmware) to operate, but may be absent when the software is not required to operate.

[0225] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term "circuit system" also covers only hardware circuitry or a processor (or processors) or a portion of hardware circuitry or a processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0226] The embodiments described herein can be implemented as software (executed by one or more processors), hardware (e.g., application-specific integrated circuits), or a combination of software and hardware. In example embodiments, software (e.g., application logic, instruction set) is maintained on any of a variety of conventional computer-readable media. In the context of this document, "computer-readable media" can be any medium or component capable of containing, storing, transmitting, propagating, or transporting instructions for use by or in conjunction with an instruction execution system, apparatus, or device (such as a computer), an example of which is, for example, a computer. Figure 1 The computer-readable medium may include a computer-readable storage medium (e.g., memory 125, 155, 171 or other devices), which may be any medium or component that can contain, store and / or transmit instructions for use by or in conjunction with an instruction execution system, apparatus or device (such as a computer). Computer-readable storage media do not include propagating signals.

[0227] If necessary, the different functions discussed in this document may be executed in different orders and / or simultaneously. Furthermore, if necessary, one or more of the above functions may be optional or may be combined.

[0228] Although various aspects of the invention are set forth in the independent claims, other aspects of the invention include other combinations of the features of the foregoing embodiments and / or dependent claims with the features of the independent claims, and not only combinations expressly set forth in the claims.

[0229] It should also be noted in this document that although exemplary embodiments of the invention have been described above, these descriptions should not be considered limiting. Rather, various changes and modifications may be made without departing from the scope of the invention as defined in the appended claims.

[0230] The following abbreviations may appear in the instruction manual and / or drawings and are defined as follows:

[0231] 3GPP: Third Generation Partnership Project

[0232] 5G: Fifth Generation

[0233] 5GC: 5G Core Network

[0234] AMF: Access and Mobility Management Function

[0235] BAP: Return Adapter Protocol

[0236] BH: Return trip

[0237] CA: Carrier Aggregation

[0238] CU: Central Unit

[0239] DC: Dual-connection

[0240] DL: Downlink

[0241] DRB: Data Radio Bearer

[0242] DSCP: Differential Service Code Point

[0243] DU: Distributed Unit

[0244] eNB (or eNodeB): Evolved Node B (e.g., LTE base station)

[0245] EN-DC: E-UTRA-NR Dual Connection

[0246] en-gNB or En-gNB: A node that provides NR user plane and control plane protocol termination to the UE and acts as a secondary node in the EN-DC.

[0247] E-UTRA: Evolved Universal Terrestrial Radio Access, also known as LTE radio access technology.

[0248] gNB (or gNodeB): A 5G / NR base station, i.e., a node that provides NR user plane and control plane protocol termination to the UE and connects to the 5GC via the NG interface.

[0249] HFN: Superframe Number

[0250] GPRS: General Packet Radio Service

[0251] GTP: GPRS Tunneling Protocol

[0252] GTP-U: GTP User Plane

[0253] IAB: Integrated Access and Backhaul

[0254] ID: Identifier

[0255] I / F: Interface

[0256] IP: Internet Protocol

[0257] IPsec: Internet Protocol Security

[0258] IPv6: Internet Protocol version 6

[0259] LTE: Long Term Evolution

[0260] MAC: Media Access Control

[0261] MBMS: Multimedia Broadcast and Multicast Service

[0262] MgNB or MeNB: The master node, gNB, or eNB in ​​this example.

[0263] MME: Mobility Management Entity

[0264] MT: Terminated or terminated during movement

[0265] ng or NG: Next generation

[0266] Ng-eNB or NG-eNB: Next-generation eNB

[0267] NR: New Radio

[0268] N / W or NW: Network

[0269] PCell: Main Cell

[0270] PDCP: Packet Data Convergence Protocol

[0271] PDCP SN: PDCP serial number

[0272] PDU: Protocol Data Unit

[0273] PHY: Physical layer

[0274] RAN: Radio Access Network

[0275] Rel: Version

[0276] RLC: Radio Link Control

[0277] RRH: Remote Radio Head

[0278] RRC: Radio Resource Control

[0279] RU: Radio Unit

[0280] Rx: Receiver

[0281] SCell: Secondary Cell

[0282] SCTP: Stream Control Transport Protocol

[0283] SDAP: Service Data Adaptation Protocol

[0284] SDU: Service Data Unit

[0285] SgNB or SeNB: Secondary node, gNB or eNB

[0286] SGW: Service Gateway

[0287] SMF: Session Management Function

[0288] SN: Serial Number

[0289] TEID: Tunnel Endpoint Identifier

[0290] TS: Technical Specifications

[0291] Tx: Transmitter

[0292] UE: User Equipment (e.g., wireless equipment, typically mobile equipment)

[0293] UL: Uplink

[0294] UPF: User Plane Functionality

Claims

1. A method for communication, comprising: In the integrated access and backhaul network nodes that are part of the radio access network communicating with user equipment, the following operations are performed: Receive configuration, the configuration having information indicating which data should be copied in the downlink direction and merged in the uplink direction; In the downlink direction, for a single data radio bearer associated with the user equipment, first data is received via the backhaul link, the first data is determined to be data to be copied, the first data is copied into multiple downlink service streams, and the multiple downlink service streams are sent toward the user equipment; as well as In the uplink direction, second data is received from the user equipment through multiple uplink service flows, the second data is determined to be data to be merged, the second data is merged into a single service flow, and the single service flow is forwarded to the network through the backhaul link; When the integrated access and backhaul network node is connected to the user equipment via carrier aggregation, the configuration instruction is performed only by the integrated access and backhaul network node to which the user equipment is attached: copying the first data into multiple downlink service flows and merging the second data into a single service flow; as well as When the integrated access and backhaul network node is connected to the user equipment via dual connectivity, the integrated access and backhaul network node as the parent node connects to the two integrated access and backhaul network nodes as child nodes to provide dual connectivity to the user equipment. The configuration instruction is performed only by the integrated access and backhaul network node as the parent node: copying the first data into multiple downlink service flows and merging the second data into a single service flow.

2. The method according to claim 1, wherein: The integrated access and backhaul network nodes are connected to the user equipment via carrier aggregation; and The transmission of the multiple service flows toward the user equipment and the receipt of the second data from the user equipment via the multiple service flows are performed by the integrated access and backhaul network nodes using the carrier aggregation.

3. The method according to claim 1, wherein: The integrated access and backhaul network node, acting as a parent node, connects to two integrated access and backhaul nodes, acting as child nodes, to provide dual connectivity to the user equipment. This connection is established between the integrated access and backhaul network node acting as the parent node and another integrated access and backhaul network node acting as the child node via a second backhaul link, and between the integrated access and backhaul network node acting as the child node and the user equipment via a wireless link. Sending the plurality of downlink service flows toward the user equipment includes: sending a corresponding downlink service flow from the plurality of downlink service flows via the radio link and the second backhaul link; and Receiving second data from the user equipment via multiple uplink service flows also includes receiving the second data via the radio link and the second backhaul link.

4. The method according to claim 3, wherein: Sending the plurality of downlink service flows toward the user equipment includes: sending the corresponding downlink service flow among the plurality of downlink service flows to the corresponding child nodes among the child nodes via the second backhaul link; and Receiving the second data from the user equipment via multiple uplink service flows further includes receiving the second data from a corresponding sub-node among the sub-nodes via the second backhaul link.

5. The method according to any one of claims 1 to 4, wherein: Determining that the first data is indicated to be copied further includes: for data received via the backhaul link, determining that the data has an associated copying indication and that the data is the first data that should be copied; and The copying is performed only on the first data that is determined to have the associated copying instruction.

6. The method according to any one of claims 1 to 5, further comprising: The determination that the first data is indicated to be copied in the downlink direction or the second data is indicated to be merged is based on at least one of the following: Copy instruction; Backhaul radio link control channel identity; Route identifier; Tunnel endpoint identifier; or Any field in the Return Route Adaptation Protocol header.

7. The method according to any one of claims 1 to 6, further comprising: Receive configuration from the integrated access and backhaul donor nodes to identify replication or merging, the configuration including one or more of the following: Backhaul radio link control channel identity; Route identifier; Tunnel endpoint identifier; or Any field in the Return Route Adaptation Protocol header.

8. The method of claim 1, wherein determining the second data as data to be merged comprises: The Return Adapter header of the second data is examined to determine whether at least one of the Tunnel Endpoint Identifier or Packet Data Convergence Protocol Sequence Number indicates that the second data should be merged, or whether at least one of the Flow Control Transport Protocol Flow Identifier or Flow Sequence Number indicates that the second data should be merged.

9. The method according to any one of claims 1 to 8, wherein the integrated access and backhaul network node is an integrated access and backhaul donor distributed unit node.

10. A method for communication, comprising: At the integrated access and backhaul donor distributed unit node, perform the following operations: Receive data for user equipment; The system receives configuration information for a specific service flow to be replicated for the user equipment from the integrated access and backhaul central unit node, and the data is part of the specific service flow. Add a copy instruction associated with the data; and The data, along with the added replication instructions, is forwarded to the integrated access and backhaul nodes that are to perform the replication of the data. When the integrated access and backhaul network nodes are connected to the user equipment via carrier aggregation, the configuration information instruction is performed only by the integrated access and backhaul network nodes to which the user equipment is attached: in the downlink direction, determining that first data is indicated as data to be copied, and copying the first data into multiple downlink service flows; and in the uplink direction, determining that second data received from the user equipment through multiple uplink service flows is indicated as data to be merged, and merging the second data into a single service flow. as well as When the integrated access and backhaul network node is connected to the user equipment via dual connectivity, the integrated access and backhaul network node as the parent node connects to the two integrated access and backhaul network nodes as child nodes to provide dual connectivity to the user equipment. The configuration information indicates that only the integrated access and backhaul network node as the parent node performs the following: copying the first data into multiple downlink service flows and merging the second data into a single service flow.

11. The method according to claim 10, wherein the configuration information includes: Instructs the specific service flow to copy specific Internet Protocol header content to the user equipment.

12. The method according to any one of claims 10 to 11, wherein the copy instruction comprises: The backhaul adaptation protocol header includes a replication instruction for packets associated with the specific service flow.

13. The method according to any one of claims 10 to 12, wherein the integrated access and backhaul node is an access node for the user equipment, the access node using transmissions to the user equipment via multiple radio links in carrier aggregation.

14. The method of claim 13, wherein the addition of a replication instruction associated with the data by the integrated access and backhaul donor distributed unit node further comprises: The backhaul adaptation protocol header includes replication instructions for the packets associated with the business flows to be replicated.

15. The method of claim 14, wherein the replication instruction in the backhaul adaptation protocol header comprises: Information regarding the number of copies required, and / or which access logical channels should be used for packet delivery to the user equipment.

16. The method according to any one of claims 10 to 12, wherein the integrated access and backhaul node uses multiple backhaul links in dual connectivity from at least one integrated access and backhaul sub-node to the user equipment, wherein the integrated access and backhaul node is the parent node of the at least one integrated access and backhaul sub-node.

17. The method of claim 13, wherein: The addition of a replication instruction associated with the data by the integrated access and backhaul donor distributed unit node further includes: including a replication instruction for packets related to the service flow to be replicated in the backhaul adaptation protocol header; and The method includes: the integrated access and backhaul donor distributed unit node instructing the integrated access and backhaul node to perform data replication.

18. The method of claim 17, wherein the instruction to perform the replication of the data by the integrated access and backhaul node is performed by including the address of the integrated access and backhaul node in the backhaul adaptation protocol header.

19. The method of claim 17, wherein the integrated access and backhaul node instructing the data replication to be performed does so by adding a path identifier and a backhaul adaptation protocol address to the data, the path identifier indicating that the packet should be replicated, and the backhaul adaptation protocol address indicating the address of the integrated access and backhaul node for performing the replication.

20. A method for communication, comprising: At the integrated access and backhaul donor central unit node in the network, perform the following operations: It is determined that the service flow of the user equipment needs to be replicated by the integrated access and backhaul network nodes in the network; and To integrate access and backhaul network node configuration information, When the integrated access and backhaul network node is connected to the user equipment via carrier aggregation, the information indication is performed only by the integrated access and backhaul network node to which the user equipment is attached: in the downlink direction, determining that first data is indicated as data to be copied, and copying the first data into multiple downlink service flows; and in the uplink direction, determining that second data received from the user equipment through multiple uplink service flows is indicated as data to be merged, and merging the second data into a single service flow. as well as When the integrated access and backhaul network node is connected to the user equipment via dual connectivity, the integrated access and backhaul network node as the parent node connects to the two integrated access and backhaul network nodes as child nodes to provide dual connectivity to the user equipment. The information instruction is performed only by the integrated access and backhaul network node as the parent node: copying the first data into multiple downlink service flows, merging the second data into a single service flow, and forwarding the single service flow to the network via the backhaul link.

21. The method of claim 20, wherein the integrated access and backhaul network node is an integrated access and backhaul donor distributed unit node, and wherein the information includes at least one of the following information of the service flow in the downlink direction: Internet Protocol address; Differentiated service code point value; Stream tag; Fields in the Internet Protocol header; or Tunnel endpoint identifier.

22. The method of claim 21, wherein the information further indicates to the integrated access and backhaul donor distributed unit node that multiple service flows of the user equipment in the uplink direction are to be merged into a single service flow, and wherein the information includes: At least one of the following information for the service flow in the uplink direction: Backhaul radio link control channel identity; Route identifier; Tunnel endpoint identifier; or Any field in the Return Route Adaptation Protocol header.

23. The method of claim 20, wherein: The information includes at least one of the following information for the service flow in the downlink direction: Backhaul radio link control channel identity; Route identifier; Tunnel endpoint identifier; or Any field in the Return Route Adaptation Protocol header; and The information includes at least one of the following information about the service flow in the uplink direction: Backhaul radio link control channel identity; Route identifier; Tunnel endpoint identifier; or Any field in the Return Route Adaptation Protocol header.

24. A computer-readable medium having instructions stored thereon, which, when executed by at least one processor of the device, cause the device to perform the method according to any one of claims 1 to 23.

25. An apparatus for communication, comprising components for performing the following operations: In the integrated access and backhaul network nodes that are part of the radio access network communicating with user equipment, the following operations are performed: Receive configuration, the configuration having information indicating which data should be copied in the downlink direction and merged in the uplink direction; In the downlink direction, for a single data radio bearer associated with the user equipment, first data is received via the backhaul link, the first data is determined to be data to be copied, the first data is copied into multiple downlink service streams, and the multiple downlink service streams are sent toward the user equipment; as well as In the uplink direction, second data is received from the user equipment through multiple uplink service flows, the second data is determined to be data to be merged, the second data is merged into a single service flow, and the single service flow is forwarded to the network through the backhaul link; When the integrated access and backhaul network node is connected to the user equipment via carrier aggregation, the configuration instruction is performed only by the integrated access and backhaul network node to which the user equipment is attached: copying the first data into multiple downlink service flows and merging the second data into a single service flow; as well as When the integrated access and backhaul network node is connected to the user equipment via dual connectivity, the integrated access and backhaul network node as the parent node connects to the two integrated access and backhaul network nodes as child nodes to provide dual connectivity to the user equipment. The configuration instruction is performed only by the integrated access and backhaul network node as the parent node: copying the first data into multiple downlink service flows and merging the second data into a single service flow.

26. The apparatus according to claim 25, wherein: The integrated access and backhaul network nodes are connected to the user equipment via carrier aggregation; and The transmission of the multiple service flows toward the user equipment and the receipt of the second data from the user equipment via the multiple service flows are performed by the integrated access and backhaul network nodes using the carrier aggregation.

27. The apparatus according to claim 25, wherein: The integrated access and backhaul network node, acting as a parent node, connects to two integrated access and backhaul nodes, acting as child nodes, to provide dual connectivity to the user equipment. This connection is established between the integrated access and backhaul network node acting as the parent node and another integrated access and backhaul network node acting as the child node via a second backhaul link, and between the integrated access and backhaul network node acting as the child node and the user equipment via a wireless link. Sending the plurality of downlink service flows toward the user equipment includes: sending a corresponding downlink service flow from the plurality of downlink service flows via the radio link and the second backhaul link; and Receiving second data from the user equipment via multiple uplink service flows also includes receiving the second data via the radio link and the second backhaul link.

28. The apparatus according to claim 27, wherein: Sending the plurality of downlink service flows toward the user equipment includes: sending the corresponding downlink service flow among the plurality of downlink service flows to the corresponding child nodes among the child nodes via the second backhaul link; and Receiving the second data from the user equipment via multiple uplink service flows further includes receiving the second data from a corresponding sub-node among the sub-nodes via the second backhaul link.

29. The apparatus according to any one of claims 25 to 28, wherein: Determining that the first data is indicated to be copied further includes: for data received via the backhaul link, determining that the data has an associated copying indication and that the data is the first data that should be copied; and The copying is performed only on the first data that is determined to have the associated copying instruction.

30. The apparatus according to any one of claims 25 to 29, further comprising: Components for determining whether the first data is indicated to be copied in the downlink direction or the second data is indicated to be merged based on at least one of the following: Copy instruction; Backhaul radio link control channel identity; Route identifier; Tunnel endpoint identifier; or Any field in the Return Route Adaptation Protocol header.

31. The apparatus according to any one of claims 25 to 30, further comprising: Components for receiving configurations from integrated access and backhaul donor nodes to identify replication or merging, the configurations including one or more of the following: Backhaul radio link control channel identity; Route identifier; Tunnel endpoint identifier; or Any field in the Return Route Adaptation Protocol header.

32. The apparatus of claim 25, wherein determining the second data as data to be merged includes: The Return Adapter header of the second data is examined to determine whether at least one of the Tunnel Endpoint Identifier or Packet Data Convergence Protocol Sequence Number indicates that the second data should be merged, or whether at least one of the Flow Control Transport Protocol Flow Identifier or Flow Sequence Number indicates that the second data should be merged.

33. The apparatus according to any one of claims 25 to 32, wherein the integrated access and backhaul network node is an integrated access and backhaul donor distributed unit node.

34. An apparatus for communication, comprising components for performing the following operations: Receive data for user equipment at the integrated access and backhaul donor distributed unit node; The system receives configuration information for a specific service flow to be replicated for the user equipment from the integrated access and backhaul central unit node, and the data is part of the specific service flow. The integrated access and backhaul donor distributed unit nodes add replication instructions associated with the data; as well as The integrated access and backhaul donor distributed unit node forwards the data and the added replication instruction to the integrated access and backhaul node that is to perform the replication of the data; When the integrated access and backhaul network nodes are connected to the user equipment via carrier aggregation, the configuration information instruction is performed only by the integrated access and backhaul network nodes to which the user equipment is attached: in the downlink direction, determining that first data is indicated as data to be copied, and copying the first data into multiple downlink service flows; and in the uplink direction, determining that second data received from the user equipment through multiple uplink service flows is indicated as data to be merged, and merging the second data into a single service flow. as well as When the integrated access and backhaul network node is connected to the user equipment via dual connectivity, the integrated access and backhaul network node as the parent node connects to the two integrated access and backhaul network nodes as child nodes to provide dual connectivity to the user equipment. The configuration information indicates that only the integrated access and backhaul network node as the parent node performs the following: copying the first data into multiple downlink service flows and merging the second data into a single service flow.

35. The apparatus of claim 34, wherein the configuration information includes: Instructs the specific service flow to copy specific Internet Protocol header content to the user equipment.

36. The apparatus according to any one of claims 34 to 35, wherein the copy instruction comprises: The backhaul adaptation protocol header includes a replication instruction for packets associated with the specific service flow.

37. The apparatus of any one of claims 34 to 36, wherein the integrated access and backhaul node is an access node for the user equipment, the access node using transmissions to the user equipment via multiple radio links in carrier aggregation.

38. The apparatus of claim 37, wherein the addition of a replication instruction associated with the data by the integrated access and backhaul donor distributed unit node further comprises: The backhaul adaptation protocol header includes replication instructions for the packets associated with the business flows to be replicated.

39. The apparatus of claim 38, wherein the copy instruction in the backhaul adaptation protocol header includes: Information regarding the number of copies required, and / or which access logical channels should be used for packet delivery to the user equipment.

40. The apparatus of any one of claims 34 to 36, wherein the integrated access and backhaul node uses multiple backhaul links in dual connectivity from at least one integrated access and backhaul sub-node to the user equipment, wherein the integrated access and backhaul node is the parent node of the at least one integrated access and backhaul sub-node.

41. The apparatus according to claim 37, wherein: The addition of a replication instruction associated with the data by the integrated access and backhaul donor distributed unit node further includes: including a replication instruction for packets related to the service flow to be replicated in the backhaul adaptation protocol header; and The integrated access and backhaul donor distributed unit node includes a component for instructing the integrated access and backhaul node to perform data replication.

42. The apparatus of claim 41, wherein the instruction to perform the replication of the data by the integrated access and backhaul node is performed by including the address of the integrated access and backhaul node in the backhaul adaptation protocol header.

43. The apparatus of claim 41, wherein the integrated access and backhaul node instructing the data replication to be performed does so by adding a path identifier and a backhaul adaptation protocol address to the data, the path identifier indicating that the packet should be replicated, and the backhaul adaptation protocol address indicating the address of the integrated access and backhaul node for performing the replication.

44. An apparatus for communication, comprising components for performing the following operations: At the integrated access and backhaul donor central unit node in the network, perform the following operations: It is determined that the service flow of the user equipment needs to be replicated by the integrated access and backhaul network nodes in the network; and To integrate access and backhaul network node configuration information, When the integrated access and backhaul network node is connected to the user equipment via carrier aggregation, the information indication is performed only by the integrated access and backhaul network node to which the user equipment is attached: in the downlink direction, determining that first data is indicated as data to be copied, and copying the first data into multiple downlink traffic flows; and in the uplink direction, determining that second data received from the user equipment through multiple uplink traffic flows is indicated as data to be merged, and merging the second data into a single traffic flow; and When the integrated access and backhaul network node is connected to the user equipment via dual connectivity, the integrated access and backhaul network node as the parent node connects to the two integrated access and backhaul network nodes as child nodes to provide dual connectivity to the user equipment. The information instruction is performed only by the integrated access and backhaul network node as the parent node: copying the first data into multiple downlink service flows, merging the second data into a single service flow, and forwarding the single service flow to the network via the backhaul link.

45. The apparatus of claim 44, wherein the integrated access and backhaul network node is an integrated access and backhaul donor distributed unit node, and wherein the information includes at least one of the following information about the service flow in the downlink direction: Internet Protocol address; Differentiated service code point value; Stream tag; Fields in the Internet Protocol header; or Tunnel endpoint identifier.

46. ​​The apparatus of claim 45, wherein the information further indicates to the integrated access and backhaul donor distributed unit node that multiple service flows of the user equipment in the uplink direction are to be merged into a single service flow, and wherein the information includes: At least one of the following information for the service flow in the uplink direction: Backhaul radio link control channel identity; Route identifier; Tunnel endpoint identifier; or Any field in the Return Route Adaptation Protocol header.

47. The apparatus according to claim 44, wherein: The information includes at least one of the following information for the service flow in the downlink direction: Backhaul radio link control channel identity; Route identifier; Tunnel endpoint identifier; or Any field in the Return Route Adaptation Protocol header; and The information includes at least one of the following information about the service flow in the uplink direction: Backhaul radio link control channel identity; Route identifier; Tunnel endpoint identifier; or Any field in the Return Route Adaptation Protocol header.

48. An apparatus for communication, comprising: One or more processors; as well as One or more memories, including computer program code, The one or more memories and the computer program code are configured, together with the one or more processors, to cause the device to perform operations, including: In the integrated access and backhaul network nodes that are part of the radio access network communicating with user equipment, the following operations are performed: Receive configuration, the configuration having information indicating which data should be copied in the downlink direction and merged in the uplink direction; In the downlink direction, for a single data radio bearer associated with the user equipment, first data is received via the backhaul link, the first data is determined to be data to be copied, the first data is copied into multiple downlink traffic streams, and the multiple downlink traffic streams are transmitted toward the user equipment; and In the uplink direction, second data is received from the user equipment through multiple uplink service flows, the second data is determined to be data to be merged, the second data is merged into a single service flow, and the single service flow is forwarded to the network through the backhaul link; When the integrated access and backhaul network node is connected to the user equipment via carrier aggregation, the configuration instruction is performed only by the integrated access and backhaul network node to which the user equipment is attached: copying the first data into multiple downlink traffic flows and merging the second data into a single traffic flow; and When the integrated access and backhaul network node is connected to the user equipment via dual connectivity, the integrated access and backhaul network node as the parent node connects to the two integrated access and backhaul network nodes as child nodes to provide dual connectivity to the user equipment. The configuration instruction is performed only by the integrated access and backhaul network node as the parent node: copying the first data into multiple downlink service flows and merging the second data into a single service flow.

49. An apparatus for communication, comprising: One or more processors; as well as One or more memories, including computer program code, The one or more memories and the computer program code are configured, together with the one or more processors, to cause the device to perform operations, including: Receive data for user equipment at the integrated access and backhaul donor distributed unit node; The system receives configuration information for a specific service flow to be replicated for the user equipment from the integrated access and backhaul central unit node, and the data is part of the specific service flow. The integrated access and backhaul donor distributed unit nodes add replication instructions associated with the data; and The integrated access and backhaul donor distributed unit node forwards the data and the added replication instruction to the integrated access and backhaul node that is to perform the replication of the data; When the integrated access and backhaul network nodes are connected to the user equipment via carrier aggregation, the configuration information instruction is performed only by the integrated access and backhaul network nodes to which the user equipment is attached: in the downlink direction, determining that first data is indicated as data to be copied, and copying the first data into multiple downlink service flows; and in the uplink direction, determining that second data received from the user equipment through multiple uplink service flows is indicated as data to be merged, and merging the second data into a single service flow; and When the integrated access and backhaul network node is connected to the user equipment via dual connectivity, the integrated access and backhaul network node as the parent node connects to the two integrated access and backhaul network nodes as child nodes to provide dual connectivity to the user equipment. The configuration information indicates that only the integrated access and backhaul network node as the parent node performs the following: copying the first data into multiple downlink service flows and merging the second data into a single service flow.

50. An apparatus for communication, comprising: One or more processors; as well as One or more memories, including computer program code, The one or more memories and the computer program code are configured, together with the one or more processors, to cause the device to perform operations, including: At the integrated access and backhaul donor central unit node in the network, perform the following operations: It is determined that the service flow of the user equipment needs to be replicated by the integrated access and backhaul network nodes in the network; and To integrate access and backhaul network node configuration information, When the integrated access and backhaul network node is connected to the user equipment via carrier aggregation, the information indication is performed only by the integrated access and backhaul network node to which the user equipment is attached: in the downlink direction, determining that first data is indicated as data to be copied, and copying the first data into multiple downlink service flows; and in the uplink direction, determining that second data received from the user equipment through multiple uplink service flows is indicated as data to be merged, and merging the second data into a single service flow. as well as When the integrated access and backhaul network node is connected to the user equipment via dual connectivity, the integrated access and backhaul network node as the parent node connects to the two integrated access and backhaul network nodes as child nodes to provide dual connectivity to the user equipment. The information instruction is performed only by the integrated access and backhaul network node as the parent node: copying the first data into multiple downlink service flows, merging the second data into a single service flow, and forwarding the single service flow to the network via the backhaul link.

Images