Multipath communication for user devices in centralized unit and distributed unit partitioning architectures

Abstract

Presented is a system, method, apparatus, or computer-readable medium for multipath communication. A centralized unit (CU) may send multipath configuration information to a distributed unit (DU). The CU may receive multipath configuration response information from the DU. In some embodiments, the multipath configuration information comprises mapping information that may identify an association between an F1-U tunnel of a data radio bearer (DRB) for a remote wireless communication device and a Uu radio link control (RLC) channel for a relay wireless communication device, or an association between an F1-U tunnel of a data radio bearer (DRB) for an anchor wireless communication device and a Uu radio link control (RLC) channel for an aggregated wireless communication device.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication, including, but not limited to, systems and methods for multipath transmission and reception for user equipment (UE) in a centralized unit (CU) and distributed unit (DU) split architecture.

Background Art

[0002] The standardization organization, the Third Generation Partnership Project (3GPP (registered trademark)), is currently proceeding with the specification of a new radio interface called 5G New Radio (5G NR) and a next-generation packet core network (NG-CN or NGC). 5G NR will have three main components, namely, a 5G access network (5G-AN), a 5G core network (5GC), and user equipment (UE). To facilitate the enabling of different data services and requirements, elements of the 5GC, also called network functions, are simplified such that some of them are software-based so that they can be adapted according to necessity.

Summary of the Invention

Means for Solving the Problems

[0003] The exemplary embodiments disclosed herein are directed to solving one or more problems presented by the prior art and providing additional features that will be readily apparent by reference to the following detailed description when considered in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it is to be understood that these embodiments are presented by way of example and not limitation, and that various modifications to the disclosed embodiments can be made within the scope of the present disclosure, as will be apparent to those skilled in the art upon a review of the present disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium for multipath communication. A centralized unit (CU) may transmit multipath configuration information to a distributed unit (DU). The CU may receive multipath configuration response information from the DU. In some embodiments, the multipath configuration information may include route indication information that identifies at least one of direct or indirect routes.

[0005] In some embodiments, the multipath configuration information includes mapping information that can identify associations between F1-U tunnels of data radio bearers (DRBs) relating to remote radio communication devices and Uu radio link control (RLC) channels relating to relay radio communication devices, or between F1-U tunnels of data radio bearers (DRBs) relating to anchor radio communication devices and Uu radio link control (RLC) channels relating to aggregated radio communication devices.

[0006] In some embodiments, the multipath configuration information includes mapping information that can identify associations between signaling radio bearers (SRBs) relating to remote radio communication devices and Uu radio link control (RLC) channels relating to relay radio communication devices, or between signaling radio bearers (SRBs) relating to anchor radio communication devices and Uu radio link control (RLC) channels relating to aggregated radio communication devices.

[0007] In some embodiments, the multipath configuration information may include at least one of the following: a radio bearer (RB) identifier, uplink (UL) user plane (UP) tunnel (TNL) information, an identifier for a relay radio communication device, an identifier for an aggregated radio communication device, an identifier for a Uu radio link control (RLC) channel, a route identifier, an indication for a direct or indirect route, an indication for a primary or secondary route, an indication for data partitioning or data replication, or a route activation indication.

[0008] In some embodiments, the identifier of the RB may be at least one of the identifiers of the DRB or SRB. In some embodiments, multipath configuration information with mapping information may be used by the DU to refrain from setting up an RLC channel for a relay radio communication device or an anchor radio communication device with respect to the DRB. In some embodiments, multipath configuration information with indirect path indication may be used by the DU to refrain from setting up an RLC channel for a relay radio communication device or an anchor radio communication device with respect to the DRB or SRB.

[0009] In some embodiments, multipath configuration information may be used by the DU to configure a first RLC channel of a relay radio communication device or anchor radio communication device with respect to a direct path of a DRB or SRB. In some embodiments, the multipath configuration information may include path activation indications that identify paths as active or inactive. In some embodiments, data partitioning indications may include at least one of a data partitioning threshold or a data partitioning ratio.

[0010] In some embodiments, the multipath configuration information with data partitioning may indicate the distribution of multiple data packets across a first RLC channel corresponding to a direct route and a second RLC channel corresponding to an indirect route. In some embodiments, the multipath configuration information may identify DRBs for multiple F1 user plane tunnels between the CU and DU.

[0011] In some embodiments, the multipath configuration information may include uplink (UL) user plane (UP) tunnel (TNL) information relating to at least one of the direct or indirect routes. In some embodiments, the multipath configuration information may include two or more UL UP TNL pieces relating to the partitioned DRBs.

[0012] In some embodiments, the multipath configuration response information may indicate at least one of the acceptance or rejection of a route. In some embodiments, the multipath configuration response information may include identifiers relating to a route, or indications of a direct or indirect route, or indications of a primary or secondary route being accepted or rejected. In some embodiments, the multipath configuration response information may identify the cause of a route failure, or one of the identifiers relating to an unacceptable or unacceptable route for data packet delivery.

[0013] In some embodiments, the multipath configuration response information may indicate a failure in multipath SRB or DRB configuration or a failure in multipath SRB or DRB modification. In some embodiments, the multipath configuration response information may include downlink (DL) user plane (UP) tunnel (TNL) information for acceptable routes. In some embodiments, the multipath configuration information may include at least one of a multipath configuration request, a multipath modification request, or a multipath release request. The present invention provides, for example, the following items: (Item 1) A method of multipath communication, The centralized unit (CU) transmits multipath configuration information to the distributed units (DU), The above CU receives multipath configuration response information from the above DU. Methods that include... (Item 2) The method according to item 1, wherein the multipath configuration information described above includes route indication information that identifies at least one of a direct route or an indirect route. (Item 3) The above multipath configuration information is, The association between the F1-U tunnel of a data radio bearer (DRB) for a remote radio communication device and the Uu radio link control (RLC) channel for a relay radio communication device, or Association between the F1-U tunnel of a data radio bearer (DRB) for anchor wireless communication devices and the Uu radio link control (RLC) channel for aggregated wireless communication devices. The method according to item 1, comprising identifying mapping information. (Item 4) The above multipath configuration information is, The association between a signaling radio bearer (SRB) for a remote radio communication device and a Uu radio link control (RLC) channel for a relay radio communication device, or Association between a signaling radio bearer (SRB) for an anchor wireless communication device and a Uu radio link control (RLC) channel for an aggregated wireless communication device. The method according to item 1, comprising identifying mapping information. (Item 5) The method according to item 1, wherein the multipath configuration information comprises at least one of the following: a radio bearer (RB) identifier, uplink (UL) user plane (UP) tunnel (TNL) information, an identifier for a relay radio communication device, an identifier for an aggregated radio communication device, an identifier for a Uu radio link control (RLC) channel, an identifier for a route, an indication for a direct or indirect route, an indication for a primary or secondary route, an indication for data partitioning or data replication, or a route activation indication. (Item 6) The method described in item 5, wherein the identifier of the above RB may be at least one of the identifiers of the DRB or SRB. (Item 7) The multipath configuration information with mapping information is used by the DU to refrain from setting the RLC channel of the relay radio communication device or anchor radio communication device with respect to the DRB, as described in item 3-5. (Item 8) The multipath configuration information with indirect path indication is used by the DU to refrain from setting up the RLC channel of the relay radio communication device or anchor radio communication device with respect to the DRB or SRB, as described in item 3-5. (Item 9) The method according to item 1, wherein the above multipath configuration information is used by the DU to configure a first RLC channel of a relay radio communication device or anchor radio communication device with respect to a direct path of a DRB or SRB. (Item 10) The method according to item 1, wherein the multipath configuration information described above includes a route activation indication that identifies a route as active or inactive. (Item 11) The method according to item 5, wherein the indication for data partitioning described above comprises at least one of a data partitioning threshold or a data partitioning ratio. (Item 12) The method described in item 1, wherein the multipath configuration information with data partitioning indicates the distribution of multiple data packets across a first RLC channel corresponding to a direct path and a second RLC channel corresponding to an indirect path. (Item 13) The multipath configuration information described above identifies the DRBs relating to multiple F1 user plane tunnels between the CU and DU, as described in item 1. (Item 14) The method according to item 1, wherein the multipath configuration information described above includes uplink (UL) user plane (UP) tunnel (TNL) information relating to at least one of a direct or indirect route. (Item 15) The multipath configuration information described above is the method described in item 1, comprising two or more UL UP TNL pieces of information relating to the partitioned DRB. (Item 16) The above multipath configuration response information indicates at least one of the following: acceptance or rejection of the path, as described in item 1. (Item 17) The multipath configuration response information described above includes identifiers relating to the route, or indications for direct or indirect routes, or indications for primary or secondary routes that are accepted or rejected, as described in item 16. (Item 18) The method described in item 16, wherein the multipath configuration response information described above identifies the cause of the failure of the above path, or one of the identifiers relating to the above path that is not tolerable or is not tolerable for data packet delivery. (Item 19) The above multipath configuration response information indicates a failure in multipath SRB or DRB configuration or a failure in multipath SRB or DRB modification, as described in item 16. (Item 20) The multipath configuration response information described above includes downlink (DL) user plane (UP) tunnel (TNL) information relating to the accepted routes, as described in item 16. (Item 21) The method according to item 1, wherein the multipath configuration information described above comprises at least one of a multipath setting request, a multipath modification request, or a multipath release request.

Brief Description of the Drawings

[0014] Various exemplary embodiments of this solution are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and merely depict exemplary embodiments of this solution to facilitate the reader's understanding of this solution. Therefore, the drawings should not be considered as limitations on the scope, scope, or applicability of this solution. Note that these drawings are not necessarily drawn to scale for clarity and ease of illustration.

[0015] [Figure 1] Figure 1 illustrates an exemplary cellular communication network in which the techniques disclosed herein may be implemented according to one embodiment of the present disclosure.

[0016] [Figure 2] Figure 2 illustrates block diagrams of exemplary base stations and user equipment devices according to several embodiments of the present disclosure.

[0017] [Figure 3] Figure 3 illustrates a block diagram of user equipment (UE) connected to a network relay according to an illustrative embodiment.

[0018] [Figure 4] Figure 4 illustrates a block diagram of user equipment (UE) aggregation according to an illustrative embodiment.

[0019] [Figure 5A] Figure 5A illustrates a block diagram of an intra-distributed unit (DU) multipath configuration according to an illustrative embodiment.

[0020] [Figure 5B] Figure 5B illustrates a block diagram of an interdistributed unit (DU) multipath configuration according to an illustrative embodiment.

[0021] [Figure 6]Figure 6 illustrates a communication diagram of a multipath configuration involving different radio bearers (RBs) and multiple distributed units (DUs) according to an illustrative embodiment.

[0022] [Figure 7] Figure 7 illustrates a communication diagram of a multipath configuration relating to a segmented bearer and multiple distributed units (DUs) according to an illustrative embodiment.

[0023] [Figure 8] Figure 8 illustrates a communication diagram of a multipath configuration relating to different radio bearers (RBs) and a single distributed unit (DU) according to an illustrative embodiment.

[0024] [Figure 9] Figure 9 illustrates a communication diagram of a multipath configuration relating to split bearers under the same centralized unit (CU) and distributed unit (DU) according to an illustrative embodiment.

[0025] [Figure 10] Figure 10 illustrates a communication diagram of a multipath configuration for data partitioning bearers under the same centralized unit (CU) and distributed unit (DU) according to an illustrative embodiment.

[0026] [Figure 11] Figure 11 illustrates a communication diagram of a multipath signaling radio bearer (SRB) configuration under identical centralized units (CUs) and distributed units (DUs) for data partitioning or replication, according to an illustrative embodiment.

[0027] [Figure 12] Figure 12 illustrates a flowchart of a method for multipath communication according to an illustrative embodiment. [Modes for carrying out the invention]

[0028] Detailed explanation Various exemplary embodiments of this solution are described below with reference to accompanying drawings to enable those skilled in the art to manufacture and use this solution. As will be obvious to those skilled in the art, after careful reading of this disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of this solution. Therefore, this solution is not limited to the exemplary embodiments and uses described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein is merely an exemplary approach. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and that this solution is not limited to the specific order or hierarchy presented unless expressly stated otherwise. 1. Mobile communication technologies and environment

[0029] Figure 1 illustrates an exemplary wireless communication network and / or system 100 in which the techniques disclosed herein may be implemented according to one embodiment of the present disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and will be referred to herein as “Network 100”. Such exemplary Network 100 includes a base station 102 (hereinafter referred to as “BS102” or also as a wireless communication node), user equipment devices 104 (hereinafter referred to as “UE104” or also as wireless communication devices) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel), and clusters of cells 126, 130, 132, 134, 136, 138, and 140 that overlay a geographical area 101. In Figure 1, BS102 and UE104 are contained within the individual geographical boundaries of cell 126. The other cells 130, 132, 134, 136, 138, and 140 may each include at least one base station that operates within its allocated bandwidth and provides adequate radio coverage to its intended users.

[0030] For example, BS102 may operate within an allocated channel transmission bandwidth and provide adequate coverage to UE104. BS102 and UE104 may communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 may be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, BS102 and UE104 are generally described herein as non-limiting embodiments of a “communication node” capable of practicing the methods disclosed herein. Such a communication node may be capable of wireless and / or wired communication according to various embodiments of the solution.

[0031] Figure 2 illustrates a block diagram of an exemplary wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to several embodiments of the present solution. The system 200 may include components and elements configured to support known or conventional operating features that do not need to be described in detail herein. In one exemplary embodiment, the system 200 can be used to communicate (e.g., transmit and receive) data symbols within a wireless communication environment such as the wireless communication environment 100 in Figure 1, as described above.

[0032] The system 200 generally includes a base station 202 (hereinafter, "BS202") and a user equipment device 204 (hereinafter, "UE204"). The BS202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected to one another via a data communication bus 220 as needed. The UE204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected to one another via a data communication bus 240 as needed. The BS202 communicates with the UE204 via a communication channel 250, which may be any radio channel or other medium suitable for data transmission as described herein.

[0033] As will be understood by those skilled in the art, System 200 may further include any number of modules other than those shown in Figure 2. Those skilled in the art will understand that various illustrative blocks, modules, circuits, and processing logic described in relation to the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate the interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software may depend on the specific application and the design constraints imposed on the overall system. Those skilled in the art familiar with the concepts described herein may implement such functionality in a manner suitable for each specific application, but such implementation decisions should not be construed as limiting the scope of this disclosure.

[0034] According to some embodiments, the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230, comprising a radio frequency (RF) transmitter and an RF receiver, each having a network coupled to an antenna 232. A duplex switch (not shown) may, alternatively, couple the uplink transmitter or receiver to the uplink antenna in a time-duplex configuration. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210, comprising an RF transmitter and an RF receiver, each having a network coupled to an antenna 212. A downlink duplex switch may, alternatively, couple the downlink transmitter or receiver to the downlink antenna 212 in a time-duplex configuration. The operation of the two transceiver modules 210 and 230 may be time-coordinated so that the uplink receiver network is coupled to the uplink antenna 232 for receiving transmissions over the radio transmission link 250, while the downlink transmitter is coupled to the downlink antenna 212 at the same time. Conversely, the operation of the two transceivers 210 and 230 may be time-coordinated such that the downlink receiver couples to the downlink antenna 212 for receiving transmissions over the radio transmission link 250, while the uplink transmitter couples to the uplink antenna 232. In some embodiments, proximity time synchronization exists with a minimum protection time between changes in duplex direction.

[0035] The UE transceiver 230 and base station transceiver 210 are configured to communicate via a radio data communication link 250 and to cooperate with a suitably configured RF antenna array 212 / 232 capable of supporting specific radio communication protocols and modulation schemes. In some illustrative embodiments, the UE transceiver 210 and base station transceiver 210 are configured to support industry standards such as Long-Term Evolution (LTE) and newer 5G standards and equivalents. However, it should be understood that this disclosure is not necessarily limited to specific standards and associated protocols. Rather, the UE transceiver 230 and base station transceiver 210 may be configured to support alternative or additional radio data communication protocols, including future standards or variations thereof.

[0036] According to various embodiments, BS202 may be, for example, an evolved NodeB (eNB), a serving eNB, a target eNB, a femtostation, or a picostation. In some embodiments, UE204 may be embodied in various types of user devices such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptop computers, and wearable computing devices. Processor modules 214 and 236 may be implemented or realized using general-purpose processors, content-addressable memory, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, any suitable programmable logic devices, discrete gates or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. Thus, the processor may be realized as a microprocessor, controller, microcontroller, state machine, or equivalent. The processor may also be implemented as a combination of computing devices, for example, a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other combination of such configurations.

[0037] Furthermore, steps of methods or algorithms described in relation to embodiments disclosed herein may be embodied in hardware, firmware, software modules, or any practical combination thereof, which are performed directly by processor modules 214 and 236, respectively. Memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to processor modules 210 and 230, respectively, so that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the execution of instructions to be performed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also include non-volatile memory, each for storing instructions to be executed by processor modules 210 and 230.

[0038] The network communication module 218 generally represents the hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bidirectional communication between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communication module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, but not limited to, the network communication module 218 provides an 802.3 Ethernet® interface so that the base station transceiver 210 can communicate with conventional Ethernet®-based computer networks. Thus, the network communication module 218 may include a physical interface for connection to a computer network (e.g., a mobile switching center (MSC)). The terms “configured for,” “configured to,” and their inflections as used herein in relation to a specified operation or function refer to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted, and / or arranged to perform a specified operation or function.

[0039] The Open System Interconnection (OSI) model (hereinafter referred to as the “Open System Interconnection Model”) is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that are open to interconnecting and communicating with other systems. The model is divided into seven subcomponents or layers, each representing a conceptual set of services provided in the layers above and below it. The OSI model also effectively describes computer packet forwarding by defining a logical network and using different layer protocols. The OSI model may also be referred to as the 7-layer OSI model or the 7-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the medium access control (MAC) layer. In some embodiments, the third layer may be the radio link control (RLC) layer. In some embodiments, the fourth layer may be the packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer may be the radio resource control (RRC) layer. In some embodiments, the sixth layer may be a Non-Accessible System (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer may be any other layer. 2. Multipath communication for user equipment (UE) in a centralized unit (CU) and distributed unit (DU) partitioned architecture.

[0040] Presented herein are systems and methods for multipath transmission and reception for UEs in CU / DU partitioned architectures, focusing on data partitioning, data replication via multipath, and route switching between direct and indirect routes.

[0041] With the development of wireless multimedia services, the demand for high data-rate services may increase significantly. Under such conditions, the system capacity and coverage requirements of conventional cellular networks may become higher. On the other hand, the demand for proximity services, which enable users to recognize or communicate with adjacent users or objects, may also increase, particularly due to application scenarios such as public safety, social networks, near-field data sharing, and local content placement.

[0042] However, cellular networks may have limitations in supporting high data-rate and proximity services. As a result, device-to-device (D2D) communication technology can be proposed to meet such demands. By adopting D2D technology, the load on the cellular network can be reduced, power consumption of user equipment can be lowered, data rates can be increased, and the robustness of the network infrastructure can be improved. The demand for high data-rate and proximity services can therefore be met. D2D technology may also be called proximity service (ProSe) or sidelink communication, and the interface between devices may be a PC5 interface.

[0043] To support applications and services with wider coverage, sidelink-based relay communication can be used to extend coverage and improve network power consumption. For example, sidelink-based relay communication can be applied to indoor relay communication, smart agriculture, smart factories, and public safety services. Referring to Figure 3, what is depicted is a block diagram of user equipment (UE) to a network relay. As shown, sidelink-based relay communication may involve user equipment (UE) (e.g., UE1 shown in Figure 3) in an area with weak or no coverage. Under such conditions, UE1 may be able to communicate with the network (e.g., a base station (BS) shown in Figure 3) via a nearby UE2 that is covered by the network. As a result, network coverage can be extended and network capacity can be increased. Under this scenario, UE2 may be called a UE-network relay, and UE1 may be called a remote UE. On the other hand, if the remote UE is within coverage, multipath relay can be supported. In coverage, remote UEs can be connected to the network via both direct (e.g., data is transmitted directly between the remote UE and the network) and indirect (e.g., data is automatically forwarded via relay UEs) paths. This has the potential to improve reliability, robustness, and throughput.

[0044] This multipath relay approach can also be used for UE aggregation, where UEs connect to the network via direct paths and via other UEs using non-standardized UE-UE interconnects. Figure 4 illustrates a block diagram of user equipment (UE) aggregation. As shown, UE aggregation may involve one user equipment (UE) (e.g., UE1 shown in Figure 4) that aggregates other UEs (e.g., UE2 and UE3 shown in Figure 4) for its uplink (UL) transmission to the network or downlink reception therefrom. Here, the interconnection between UE1 and UE2 or between UE1 and UE3 may be based on sidelink, Wi-Fi, Bluetooth®, or wired connections. Nevertheless, the interconnection between UEs may be an ideal connection. UE aggregation may aim to provide applications that require high UL bitrates on 5G terminals when a normal UE is too limited by UL UE transmission power and cannot achieve the required bitrate, especially at the edge of the cell. In addition, UE aggregation can improve reliability and stability and reduce service latency as well.

[0045] With the advancement of 5G mobile wireless technology, one such technology that may be used is a segmented network architecture in which the radio access network (RAN) functionality is divided between a centralized unit (CU) and multiple distributed units (DUs). For example, the RAN functionality may be divided between the Packet Data Convergence Protocol (PDCP) layer and the Radio Link Control (RLC) layer of the 5G protocol stack. In the stack, the DU may handle all processes up to and including the RLC layer functionality, while the CU may handle the PDCP layer and higher-layer functionality prior to the core network. This segmentation of RAN functionality can offer numerous advantages to mobile network operators. For example, through isolation of the stack from the PDCP layer and above, the CU may be able to act as a cloud-based convergence point between multiple heterogeneous technologies in the provisioned network and thus be able to serve multiple heterogeneous DUs.

[0046] Regarding support for multipath UE-network relay and UE aggregation, the impact on the CU / DU partitioned architecture is focused on multipath configuration and routing, and can be used for multipath support (e.g., direct routes through UEs and indirect routes through UE-network relay or aggregated UEs). Under UE multipath transmission, UEs may be limited in UL transmission (Tx) capability, with one UE being associated with many UEs for UE aggregation, or connected to many relay UEs for UE-network relay. Multipath transmission can be used to support higher requirements for UL traffic, including data rate, latency, and reliability. UEs can be connected to the network and perform data traffic transmission or reception with the network via direct routes and via one or more indirect routes (e.g., data traffic is automatically forwarded by another UE). UE-UE interconnects can be based on sidelink connections or can use non-standardized connections.

[0047] Figure 5A illustrates a block diagram of an intra-distributed unit (DU) multipath configuration, and Figure 5B illustrates a block diagram of an inter-distributed unit (DU) multipath configuration. With respect to UEs connected to the same gNB using one direct path and one indirect path, the direct and indirect paths may be via the same DU or different DUs. UE1 may be a remote UE, traffic-initiating UE, or anchor UE, while UE2 may be a relay UE or an aggregated UE. UE1 and UE2 may be interconnected via PC5 or an internal interface. UE1 and UE2 may be serviced by the same DU (e.g., as in Figure 5A) or different DUs (e.g., as in Figure 5B). To support this multipath scenario under a CU-DU partitioned architecture, the following issues may be examined, and potential solutions are discussed below in this specification. A. Interdistributed Unit (DU) Scenario

[0048] In one scenario, UE1 and UE2 may be serviced by different DUs, and the multipath transmission configuration of UE1 between the CU and the DU is discussed herein. I. Multipath Configurations for Different Radio Bearers (RBs) and Multiple Distributed Units (DUs)

[0049] UE1 and UE2 are serviced by different DUs for multipath distribution of UE1's traffic. The quality of service (QoS) flow for UE1 may be mapped to two bearers, namely data radio bearers DRB1 and DRB2. DRB1 may be delivered via a direct path, while DRB2 may be delivered via an indirect path (to be automatically forwarded by UE2). DRB1 and DRB2 may share the same Service Data Adaptation Protocol (SDAP) entity, while separate PDCP entities may be established for DRB1 and DRB2.

[0050] Referring here to Figure 6, what is depicted is a communication diagram of a multipath configuration with different radio bearers (RBs) and multiple distributed units (DUs). The CU may request DU1 to configure DRB1 and send a direct routing indication via a UE context modification request. In addition, uplink (UL) user plane (UP) tunnel (TNL) information may be included in the UE context modification request. If, in response to receiving the DRB1 configuration request, the UL UP TNL Information information element (IE) is included in the UE CONTEXT MODIFICATION REQUEST message for DRB1, the gNB-DU may also include a downlink (DL) user plane (UP) tunnel (TNL) Information IE in the UE CONTEXT MODIFICATION RESPONSE message and configure a single radio link control (RLC) entity for DRB1 using a direct routing indication.

[0051] With respect to DRB2, the relevant data packets may be delivered via the relay of UE2, and therefore a Uu RLC channel between DU2 and UE2 should be established. As shown, CU may request DU2 to establish the Uu RLC channel via UE2-specific F1AP signaling. CU may also request DU2 to establish DRB2 via UE1-specific F1AP signaling. CU also transmits indirect routing indication, UL UP TNL information, or mapping information between the F1-U tunnel of DRB2 and the Uu RLC channel of relay UE2 to DU2. The mapping information may include any combination of the following fields: Data Radio Bearer Identifier (DRB ID), Relay UE ID or aggregated UE ID, and Uu RLC channel ID.

[0052] If the UL UP TNL Information IE is included in the UE CONTEXT SETUP REQUEST message for DRB2 in response to receiving a DRB2 setup request, the gNB-DU may include the UL UP TNL Information IE in the UE CONTEXT SETUP RESPONSE message. However, because this DRB indicates an indirect route, or because a mapping is established between the F1-U tunnel of DRB2 and the Uu RLC channel, the DU2 cannot set up one additional RLC channel with UE1 for DRB2. The DU2 may send a response message to the CU with the established DRB2 ID and logical channel identifier (LCID).

[0053] After F1AP-based configuration, the CU may send an RRCReconfiguration message to the UE1, including the configuration of DRB1 and DRB2, or route indications. In addition, the CU may send an RRCReconfiguration message to the UE2, including the configuration of the Uu RLC channel or mapping information between the Uu RLC channel and the DRB on the UE1.

[0054] Subsequently, when DU2 receives a data packet from CU via the F1-U tunnel corresponding to DRB2, DU2 may map the packet to the Uu RLC channel with UE2 and deliver the data packet to UE2. Upon receiving the data packet, UE2 may automatically forward the packet to UE1 via the internal connection or via the PC5 RLC channel. II. Multipath Configurations for Split Bearers and Multiple Distributed Units (DUs)

[0055] Referring now to Figure 7, what is depicted is a communication diagram of a multipath configuration relating to a partition bearer and multiple distributed units (DUs). Some of the QoS flows of UE1 may be mapped to DRB3, which may be configured as a partition bearer to be delivered via both direct and indirect paths. In this case, the CU may request DU1 and DU2 to configure DRB3, respectively. Two F1-U tunnels corresponding to DU1 and DU2 may be established for DRB3. With respect to DL packets, the PDCP entity in the CU may participate in data partitioning and deliver the partitioned packets to the corresponding F1-U tunnels. Thus, DU1 and DU2 may receive packets to be delivered to UE1 via direct and indirect paths, respectively.

[0056] Using DU2 as an example, CU may request DU2 to configure DRB3 via UE1-specific F1AP signaling. CU may also send DU2 indirect route indication, UL UP TNL information, or mapping information between the F1-U tunnel of DRB3 and the Uu RLC channel of UE2. The mapping information may include any combination of the following fields: DRBID, relay UE ID or aggregated UE ID, and Uu RLC channel ID. If UL UP TNL Information IE is included in the UE CONTEXT SETUP REQUEST message for DRB3 in response to receiving a DRB3 configuration request, gNB-DU may include UL UP TNL Information IE in the UE CONTEXT SETUP RESPONSE message. Because this DRB indicates an indirect route or a mapping between the F1-U tunnel of DRB3 and the Uu RLC channel is configured, DU2 cannot configure an additional RLC channel with UE1 for DRB3. DU2 may send a response message to CU with the established DRB3 ID and LCID.

[0057] After F1AP-based configuration, the CU may send an RRCReconfiguration message to the UE1 containing the DRB3 configuration, data partitioning rules, or indirect path mapping information. In addition, the CU may send an RRCReconfiguration message to the UE2 containing the Uu RLC channel configuration or mapping information between the Uu RLC channel on the UE2 and the DRB on the UE1.

[0058] When DU2 receives a DL packet from an F1-U tunnel corresponding to DRB3, DU2 may detect that the packet from this F1-U tunnel should be mapped to a Uu RLC channel with UE2 (a relay UE or an aggregated UE). DU2 may then add a conformance layer header and deliver the packet to the Uu RLC channel with UE2, and transmit it to UE2. When UE2 receives a data packet from the Uu RLC channel, UE2 may check the conformance layer header and then automatically forward the packet to UE1 via the PC5 interface or an internal connection.

[0059] With respect to UL packets, the PDCP entity in UE1 may perform data partitioning based on partitioning rules configured by the CU and deliver the packets to Uu via its own RLC channel (direct route) or to UE2 (indirect route) via the PC5 interface or internal connection. When UE2 receives a data packet from UE1, UE2 may detect the corresponding source UE and RB ID, then map the packet to the Uu RLC channel, and deliver the packet to DU2. DU2 may identify the source UE ID and radio bearer (RB) ID in the conformance layer header and detect that this is a packet for UE1's DRB3. DU2 may then automatically forward the packet to the CU via the F1-U tunnel corresponding to UE1's DRB3. Data packets transmitted via the indirect route may include a conformance layer header (i.e., including the UE ID and RB ID), which can be encapsulated by UE1 or UE2. Regarding the internal connection between UE1 and UE2 or the indirect path via the PC5 connection, UE2 may be configured using a mapping between the DRB ID of UE1 and the Uu RLC channel ID of UE2. DU2 may further automatically forward packets to the CU via the F1-U tunnel. The PDCP entity of DRB3 located in the CU may perform PDCP PDU decoding, decompression, and reordering. III. Multipath Configuration for Packet Data Convergence Protocol (PDCP) Replication

[0060] Some of the QoS flows in UE1 may be mapped to DRB4. DRB4 may be configured for PDCP replication, and packets may be delivered via both direct and indirect routes. In this case, CU may request DU1 and DU2 to configure DRB4, respectively. Two F1-U tunnels corresponding to DU1 and DU2 may be established for DRB4. With respect to DL packets, PDCP entities in CU may engage in data replication and deliver replicated packets to the corresponding F1-U tunnels. Thus, DU1 and DU2 may receive packets to be delivered to UE1 via direct and indirect routes, respectively.

[0061] Using DU2 as an example, CU may request DU2 to configure DRB4 via UE1-specific F1AP signaling. CU may also send DU2 primary or secondary route indication, configured multipath replication, multipath replication activation, UL UP TNL information, or mapping information between the F1-U tunnel of DRB4 and the Uu RLC channel of UE2. Of these, multipath replication activation can be configured as active or inactive. Mapping information may include any combination of the following fields: DRBID, relay UE ID or aggregated UE ID, and Uu RLC channel ID. If UL UP TNL Information IE is included in the UE CONTEXT SETUP REQUEST message for DRB4 in response to receiving a DRB4 configuration request, gNB-DU may include UL UP TNL Information IE in the UE CONTEXT SETUP RESPONSE message. Because the mapping between the DRB4's F1-U tunnel and the Uu RLC channel is configured, DU2 cannot set up an additional RLC channel with UE1 for DRB4. DU2 may send a response message to the CU with the established DRB4 ID and LCID.

[0062] After F1AP-based configuration, the CU may send an RRCReconfiguration message to the UE1 containing DRB4 configuration, data replication indication, or indirect path mapping information. In addition, the CU may send an RRCReconfiguration message to the UE2 containing Uu RLC channel configuration or mapping information between the Uu RLC channel and the UE1's DRB. If the DU2 receives multipath replication activation as inactive, replication packets received from the corresponding F1-U tunnel may be discarded.

[0063] When DU2 receives a DL packet from an F1-U tunnel corresponding to DRB4, DU2 may detect that the packet from this F1-U tunnel should be mapped to a Uu RLC channel with UE2 (a relay UE or an aggregated UE). DU2 may then add a conformance layer header and deliver the packet to the Uu RLC channel with UE2, and transmit it to UE2. When UE2 receives a data packet from the Uu RLC channel, DU2 may check the conformance layer header and then automatically forward the packet to UE1 via the PC5 interface or an internal connection.

[0064] With respect to the UL, UE1 may duplicate the data packets of DRB4 and distribute the packets to DU1 and UE2, respectively. When UE2 receives the data packets from UE1, DU2 may detect the corresponding source UE and RB ID, then map the packets to the Uu RLC channel, and distribute the packets to DU2. DU2 may further automatically forward the packets to the CU via the F1-U tunnel. The PDCP entity of DRB4 located in the CU may perform PDCP PDU decoding, decryption, reordering, and duplicate packet discarding.

[0065] With respect to UL packets, the PDCP entity in UE1 may perform data replication and deliver the packets to Uu via its own RLC channel (e.g., via a direct route) or to UE2 via the PC5 interface or internal connection (e.g., via an indirect route). When UE2 receives a data packet from UE1, UE2 may detect the corresponding source UE and RB ID. UE2 may then map the packet to the Uu RLC channel and deliver the packet to DU2. DU2 identifies the source UE ID and RB ID in the conformance layer header and detects that the packet is for UE1's DRB4. DU2 may then automatically forward the packet to the CU via the F1-U tunnel corresponding to UE1's DRB4. Data packets transmitted via an indirect route may include a conformance layer header (e.g., including the UE ID and RB ID), which can be encapsulated by UE1 or UE2. DU2 may further automatically forward the packet to the CU via the F1-U tunnel. UE2 may be configured by gNB using a mapping between the UE1 DRB ID and the Uu RLC channel of UE2. The PDCP entities of DRB4 located in CU may perform PDCP PDU decoding, decompression, and reordering. B. Intra-distributed unit (DU) scenario

[0066] UE1 and UE2 may be serviced by the same DU for multipath distribution of UE1's traffic, and what is discussed herein is the multipath transmission configuration of the UE between the CU and the DU. I. Multipath configuration for different radio bearers (RBs) under the same distributed unit (DU)

[0067] UE1 and UE2 are serviced by the same DU for multipath distribution of UE1's traffic, and the following scenarios can be considered: UE1's QoS flow may be mapped to two bearers, namely DRB1 and DRB2. DRB1 may be delivered via a direct path, while DRB2 may be delivered via an indirect path (automatically forwarded by UE2). DRB1 and DRB2 may share the same SDAP entity, while separate PDCP entities are established for DRB1 and DRB2.

[0068] Referring here to Figure 8, what is depicted is a communications diagram of a multipath configuration with different radio bearers (RBs) and a single distributed unit (DU). As shown, the CU may request DU1 to configure DRB1 via a UE context modification request. In addition, UL UP TNL information may be included in the UE context modification request. If, in response to receiving the DRB1 configuration request, UL UP TNL Information IE is included in the UE CONTEXT MODIFICATION REQUEST message for DRB1, DU1 may include UL UP TNL Information IE in the UE CONTEXT MODIFICATION RESPONSE message and configure one RLC entity for DRB1.

[0069] With respect to DRB2, the relevant data packets may be delivered via the relay of UE2, and therefore the Uu RLC channel between DU1 and UE2 needs to be set up. CU may request DU1 to set up the Uu RLC channel via UE2-specific F1AP signaling. CU may also request DU1 to set up DRB2 via UE1-specific F1AP signaling. CU may also send UL UP TNL information and mapping information between the F1-U tunnel of DRB2 and the Uu RLC channel of UE2 to DU1. The mapping information may include any combination of the following fields: DRB ID, relay UE ID or aggregated UE ID, and Uu RLC channel ID. If UL UP TNL Information IE is included in the UE CONTEXT SETUP REQUEST message for DRB2 in response to receiving a DRB2 setup request, DU1 may include UL UP TNL Information IE in the UE CONTEXT SETUP RESPONSE message. Because the mapping between the DRB2 F1-U tunnel and the Uu RLC channel is configured, DU1 cannot set up an additional RLC channel with UE1 for DRB2. Instead, the Uu RLC channel of UE2 may be used for the delivery of DRB2 data packets. DU2 may send a response message to the CU with the established DRB2 ID and LCID.

[0070] After F1AP-based configuration, the CU may send an RRCReconfiguration message to the UE1, including the configuration of DRB1 and DRB2, or route indications. In addition, the CU may send an RRCReconfiguration message to the UE2, including the configuration of the Uu RLC channel or mapping information between the Uu RLC channel and the DRB on the UE1.

[0071] Subsequently, when DU1 receives a data packet from CU via the F1-U tunnel corresponding to DRB2, DU1 may map the packet to the Uu RLC channel with UE2 and deliver the data packet to UE2. Upon receiving the data packet, UE2 may automatically forward the packet to UE1 via the internal connection or via the PC5 RLC channel. II. Multipath partitioning bearer configuration under the same DU and CU for data partitioning

[0072] Some of the QoS flows of UE1 may be mapped to DRB3, which is configured as a split bearer to be delivered via both direct and indirect routes. In this case, CU may request DU1 to configure DRB3. Referring now to Figure 9, what is depicted is a communication diagram of a multipath configuration with split bearers under the same centralized unit (CU) and distributed unit (Du). Two F1-U tunnels corresponding to direct and indirect routes may be established for DRB3a. With respect to DL packets, a PDCP entity in CU may participate in data splitting and deliver the split packets to the corresponding F1-U tunnels. Thus, DU1 may receive split packets from different F1-U tunnels and then deliver them to UE1 via direct and indirect routes, respectively.

[0073] Since DRB3 data packets will be delivered via UE2's relay (indirect route), a Uu RLC channel between DU1 and UE2 may be configured. As shown, CU may request DU1 to configure the Uu RLC channel via UE2-specific F1AP signaling. CU may then request DU1 to configure DRB3 via UE1-specific F1AP signaling. CU may also send DU1 a set of routing information which may include at least one of the following: route ID, direct or indirect route indication, primary or secondary route indication, UL UP TNL information, or mapping information between the F1-U tunnel of DRB3 and the Uu RLC channel of UE2. The mapping information may include any combination of the following fields: DRB ID or UL UP TNL information, relay UE ID or aggregated UE ID, and Uu RLC channel ID.

[0074] More than one UL UP TNL information may be included. One may relate to a direct route, and others may relate to indirect routes. Alternatively, one normal UL UP TNL information may be sent by the CU to DU1, and one or more additional UL UP TNLs relating to data partitioning may be sent by the CU to DU1. In addition, the CU may also include primary or secondary route indications to DU1. For example, the CU may indicate to DU1 that an indirect route (or one of the F1-U tunnels) is the primary route and a direct route (another F1-U tunnel) is the secondary route, or vice versa.

[0075] Upon receiving a DRB3 setup request, DU1 may configure one RLC entity or logical channel for the direct route of DRB3. For indirect routes, DU1 may not configure one additional RLC channel with UE1 for DRB3. Instead, a Uu RLC channel with UE2 may be used for DRB3 delivery. DU1 may send a response message to the CU with the established DRB3 ID and LCID. If, upon receiving a DRB3 setup request, the UL UP TNL Information IE is included in the UE CONTEXT SETUP REQUEST message for DRB3, the gNB-DU may include the DL UP TNL Information IE in the UE CONTEXT SETUP RESPONSE message.

[0076] If DU1 can accept one of the data packet delivery routes, DU1 may send a response to the CU to indicate the accepted route. For example, DU1 may send a response to the CU to indicate that a direct route, an indirect route, or both are accepted. Alternatively, DU1 may send a response to the CU to indicate that a primary route, a secondary route, or both are accepted. DU1 may also send an accepted or rejected route ID to the CU. In addition, one or more corresponding DL UP TNL pieces of information may be included in the response message sent by DU1 to the CU. Alternatively, if DU1 can accept one of the data packet delivery routes, DU1 may send a response to the CU to indicate that the DRB failed to configure. In addition, DU1 may send a response to the CU to indicate that the cause of the failure is that the data packet delivery route is not accepted or is one of the rejected route IDs.

[0077] After F1AP-based configuration, the CU may send an RRCReconfiguration message to the UE1 containing DRB3 configuration, data partitioning rules, or indirect route mapping information. In addition, the CU may send an RRCReconfiguration message to the UE2 containing Uu RLC channel configuration or mapping information between the Uu RLC channel and the UE1's DRB. Subsequently, DRB3 data packets may be delivered between the UE1 and the DU / CU via both direct and indirect routes. III. Multipath configuration for partition bearers under the same centralized unit (CU) and distributed unit (DU) for data partitioning.

[0078] Some of the QoS flows of UE1 may be mapped to DRB3, which may be configured as a split bearer to be delivered via both direct and indirect paths. In this case, CU may request DU1 to configure DRB3. Compared to the scenario with a multipath split bearer configuration as discussed above, in this scenario there may be one F1-U tunnel between DU1 and CU regarding DRB3. CU may send data splitting rules to DU1, which may participate in data splitting and deliver the split packets to the corresponding RLC channels.

[0079] Since DRB3 data packets will be delivered via UE2's relay (indirect path), a Uu RLC channel may be established between DU1 and UE2. Referring now to Figure 10, what is depicted is a communication diagram of a multipath configuration for data partitioning with partition bearers under the same centralized unit (CU) and distributed unit (DU). As shown, the CU may request DU1 to establish a Uu RLC channel via UE2-specific F1AP signaling.

[0080] Next, the CU may request the DU1 to configure DRB3 via UE1-specific F1AP signaling. The CU may also transmit data partitioning rules for DRB3 and a set of routing information, which may include at least one of the following: route ID, direct or indirect route indication, primary or secondary route indication, or mapping information. The data partitioning rules may include a threshold for data partitioning or a data partitioning ratio between sets of routes. The mapping information may include any combination of the following fields, namely, DRBID, relay UE ID or aggregated UE ID, or Uu RLC channel ID, among others. One UL UP TNL piece of information may be included in the DRB3 configuration request transmitted from the CU to the DU1.

[0081] In response to receiving a DRB3 configuration request, DU1 may configure an additional RLC entity or logical channel with UE1 for routes not associated with direct or bearer mapping information for DRB3. For routes associated with indirect or bearer mapping information, DU1 may not configure an additional RLC entity or logical channel with UE1 for DRB3. Instead, a Uu RLC channel with UE2 may be used for DRB3 delivery. DU1 may send a response message to the CU with the established DRB3 ID. In response to receiving a DRB3 configuration request, if UL UP TNL Information IE is included in the UE CONTEXT SETUP REQUEST message for DRB3, gNB-DU may include DL UP TNL Information IE in the UE CONTEXT SETUP RESPONSE message.

[0082] If DU1 can accept one of the data packet delivery routes, DU1 may send a response to the CU to indicate the accepted route. For example, DU1 may send a response to the CU to indicate that a direct route, an indirect route, or both are accepted. Alternatively, DU1 may send a response to the CU to indicate that a primary route, a secondary route, or both are accepted. DU1 may also send an accepted or rejected route ID to the CU. In addition, one or more corresponding DL UP TNL pieces of information may be included in the response message sent by DU1 to the CU. Alternatively, if DU1 can only accept one of the data packet delivery routes, DU1 may send a response to the CU to indicate that the DRB failed to configure. In addition, DU1 may send a response to the CU to indicate that the cause of the failure is that the data packet delivery route is not accepted or that one of the rejected route IDs is not accepted.

[0083] After F1AP-based configuration, the CU may send an RRCReconfiguration message to the UE1 containing DRB3 configuration, data partitioning rules, or indirect route mapping information. In addition, the CU may send an RRCReconfiguration message to the UE2 containing Uu RLC channel configuration or mapping information between the Uu RLC channel and the UE1's DRB. Subsequently, DRB3 data packets may be delivered between the UE1 and the DU / CU via both direct and indirect routes.

[0084] When DU1 receives a DL packet from an F1-U tunnel corresponding to DRB3, DU1 may detect that the packet from this F1-U tunnel should be split into direct and indirect routes. The direct route may be configured as a primary route, and the indirect route may be configured as a secondary route, and a threshold for data partitioning may be configured. In such a case, DU1 may send the data packet toward the direct route if the data buffer size of DRB3 is lower than the threshold for data partitioning. Otherwise, DU1 may send the packet toward either the direct or indirect route. Alternatively, if a data partitioning ratio is configured in DU1, DU1 may distribute the data packet to the RLC channel corresponding to the direct or indirect route based on the data partitioning ratio.

[0085] With respect to UL packets, the PDCP entity in UE1 may perform data partitioning based on partitioning rules configured by the CU and deliver the packets to Uu via its own RLC entity or logical channel (e.g., via a direct route) or to UE2 via the PC5 interface or internal connection (e.g., via an indirect route). When UE2 receives a data packet from UE1, UE2 may detect the corresponding source UE and RB ID. UE2 may then map the packet to the Uu RLC channel and deliver the packet to DU1. DU1 identifies the source UE ID and RB ID in the conformance layer header and detects that the packet is for UE1's DRB3. DU1 may then automatically forward the packet to the CU via the F1-U tunnel corresponding to UE1's DRB3. Also, when DU1 receives a DRB3 data packet from UE1, DU1 may also automatically forward the packet to the CU via the same F1-U tunnel corresponding to UE1's DRB3. The PDCP entities of DRB3 located in the CU may perform PDCP PDU decoding, decompression, and reordering. IV. Multipath Signaling Radio Bearer (SRB) Configuration under Identical Centralized Units (CUs) and Distributed Units (DUs) for Data Partitioning or Replication

[0086] UE1's SRB2 may be configured as a replication or splitting bearer to be delivered via both direct and indirect routes. In this case, CU may request DU1 to configure SRB2. CU may send data splitting rules or replication indications to DU1, which may then participate in data splitting or replication and deliver the split or replicated packets to the corresponding RLC channels.

[0087] Since SRB2 data packets will be delivered via UE2's relay (indirect path), a Uu RLC channel may be established between DU1 and UE2. Referring now to Figure 11, what is depicted is a communication diagram relating to a multipath signaling radio bearer (SRB) configuration under identical centralized unit (CU) and distributed unit (DU) for data partitioning or replication. As shown, the CU may request DU1 to establish a Uu RLC channel via UE2-specific F1AP signaling. The CU may then request DU1 to establish SRB2 via UE1-specific F1AP signaling. The CU may also send data partitioning rules or replication indications regarding SRB2 to DU1.

[0088] In addition, the CU may transmit a set of routing information which may include at least one of the following: route ID, direct or indirect route indication, primary or secondary route indication, or mapping information. Data partitioning rules may include thresholds for data partitioning or data partitioning ratios between sets of routes. Mapping information may include any combination of the following fields: SRB ID, relay UE ID or aggregated UE ID, and Uu RLC channel ID.

[0089] In response to receiving an SRB2 configuration request, DU1 may configure one RLC entity or logical channel for SRB2 if a direct route is configured or a route not associated with bearer mapping information is configured. For indirect routes or routes associated with bearer mapping information, DU1 may not configure one additional RLC entity or logical channel with UE1 for SRB2. Instead, a Uu RLC channel with UE2 may be used for DRB3 delivery. DU1 may send a response message to CU with the established SRB ID.

[0090] If DU1 can accept one of the data packet delivery paths, DU1 may send a response to the CU to indicate the accepted path. For example, DU1 may send a response to the CU to indicate that the direct path, or the indirect path, or both, or all of them are accepted. Alternatively, DU1 may send a response to the CU to indicate that the primary path, or the secondary path, or both, or all of them are accepted. DU1 may also send accepted or rejected path IDs to the CU. Alternatively, if DU1 cannot accept any of the data packet delivery paths, DU1 may send a response to the CU to indicate that the SRB failed to configure. In addition, DU1 may send a response to the CU to indicate that the cause of the failure is that the data packet delivery path is not accepted, or that one of the rejected path IDs is not accepted.

[0091] After F1AP-based configuration, the CU may send an RRCReconfiguration message to the UE1 containing SRB2 configuration, data partitioning rules, or indirect route mapping information. In addition, the CU may send an RRCReconfiguration message to the UE2 containing Uu RLC channel configuration or mapping information between the Uu RLC channel and the UE1's SRB. Subsequently, SRB2 data packets may be delivered between the UE1 and the DU / CU via both direct and indirect routes.

[0092] When DU1 receives data packets relating to SRB2 included in F1AP signaling to UE1, DU1 may detect that the SRB2 data packets should be split or duplicated for direct and indirect routes. A threshold for data splitting may be configured. Using this configuration, DU1 may send data packets toward the direct route when the data buffer size of DRB3 is lower than the threshold for data splitting. Otherwise, DU1 may send packets toward either the direct or indirect route. Alternatively, if a data splitting ratio is configured in DU1, DU1 may distribute the SRB2 data packets to the RLC channels corresponding to the direct or indirect route based on the data splitting ratio. On the other hand, if the SRB2 data packets are configured to be duplicated, DU1 may perform packet duplication and then distribute the duplicated SRB2 data packets to the RLC entities or logical channels corresponding to both the direct and indirect routes.

[0093] When UE1 first accesses the network via a direct route, the SRB of UE1 via the direct route may be used for signaling distribution. After some time, if an indirect route is configured, both the direct and indirect routes may become available for SRB packet distribution. The CU may send a request to DU1 to correct the SRBs. The CU may send a list of SRBs to be corrected to DU1. The list may include at least one of the following fields, namely, among other things, the SRB ID, data partitioning rule or replication indication, replication activation indication, and a set of routing information to be added, modified, or released.

[0094] With respect to routing information to be added or modified, the information may include at least one of the following: route ID, direct or indirect route indication, primary or secondary route indication, or mapping information. With respect to routing information to be released, the information may include route ID, direct or indirect route indication, primary or secondary route indication. The mapping information may include any combination of the following fields: SRB ID, relay UE ID or aggregated UE ID, and Uu RLC channel ID. The replication activation indication may indicate active or inactive. Based on the SRB modification request sent from the CU, DU1 may modify the corresponding SRB configuration and then, accordingly, perform SRB packet distribution. Multiple F1-U tunnel configurations for V.UE aggregation

[0095] Regarding CU / DU splitting scenarios, multiple F1-U tunnels may be established between the CU and DU for each aggregated transmission. For example, DRB1 traffic from UE1 may be delivered via the aggregation of UE1, UE2, and UE3, and a dual-active protocol stack (DAPS)-like aggregation mode may be used. In such a case, the DRB may be configured for UE1, UE2, and UE3 with respect to the same set of QoS flows. Here, the DAPS-like aggregation mode may mean that a common PDCP entity involved in PDCP sequence number (SN) assignment or PDCP reordering and copy discard may be established in UE1 and CU. On the other hand, separate PDCP entities involved in packet encryption and decryption or compression and decompression of UE1 may be established in UE1, UE2, and UE3, and CU. When the DU delivers data packets from these DRBs to the CU, the DU may deliver the DRBs via different F1-U tunnels so that the CU can further deliver these data packets to different PDCP entities. In this sense, multiple DRBs and corresponding F1-U tunnels may be established between the CU and DU for DAPS-like aggregation with respect to a given traffic source UE.

[0096] Regarding DAPS-like aggregation, different GTP-U tunnels may be established between the CU and DU for each aggregated route. Alternatively, the F1-U may be extended to include route ID or UE ID and DRB ID information so that the CU can identify the corresponding PDCP entity for subsequent decryption and decryption processing.

[0097] On the other hand, with respect to L2 SL U2N relay-based aggregation, one F1-U tunnel may be used independently of the number of routes configured for data distribution of a given DRB. However, the CU may send data partitioning rules to the DU so that the DU can perform data partitioning and distribute data packets to the RLC channels or logical channels of the corresponding UEs. With respect to replication, the CU may also inform the DU of DRB aggregation-based replication. The CU may configure two GTP-U tunnels with DUs corresponding to source and replicate packet distribution. In this case, the UE DRB request and response to be configured may include two GTP-U tunnel configurations. One configuration may be for source packets, and the other for replicate packets. In addition, the DU may be informed of the mapping between the two GTP-U tunnels and the aggregated routes, UE IDs, and RLC channels or logical channel IDs. C. Route switching

[0098] UE1 and UE2 may be serviced by the same DU. The CU may configure UE1 to use multipath distribution of UE1's DRB or SRB. Multipath distribution may be reconfigured based on radio conditions and traffic load requirements. The following routing scenarios may be considered. I. Direct routes to multipath routes and multipath routes to direct routes

[0099] UE1's SRB1 may initially be configured to use direct route distribution. After some time, CU may reconfigure UE1's SRB1 using multipath distribution. With respect to DL, CU may split or duplicate SRB1's signaling into two or more routes. CU may request DU to configure Uu RLC channels and mapping rules on the indirect routes. In addition, CU may request DU to modify UE1's SRB configuration, which may include the SRB ID and the modified route configuration. The modified route configuration may include additional route information. The additional route information configuration may include any combination of the following fields, namely, among other things, route ID, direct or indirect route, primary or secondary route, route activation, and bearer mapping. CU may then split or duplicate the PDCP PDU and transmit the PDU through multiple direct and indirect routes. From the perspective of the traffic-terminating UE1, UE1 may now begin receiving DL PDCP PDUs from multiple routes. With respect to UL, once anchor UE1 receives a configuration to switch to multiple paths, UE1 may begin sending subsequent PDCP PDUs to multiple direct and indirect paths.

[0100] On the other hand, the CU may switch the DRB transmission of UE1 from multiple paths and use only the direct path. With respect to DL, the CU may request the DU to modify the DRB configuration of UE1, which may include the DRB ID and the modified path configuration. The modified path configuration may include path release information. The path release information configuration may include any combination of the following fields, namely, among others, the path ID, direct or indirect path, primary or secondary path, and deactivation. The CU or anchor UE1 can no longer deliver DL or UL PDCP PDUs to the RLC channel of the indirect path. Instead, the CU or UE1 may deliver DL or UL PDCP PDUs toward the logical channel of the direct path. With respect to packets delivered to the RLC channel of the indirect path, packets can still be transmitted until the RLC channel or logical channel is empty. II. Direct routes to indirect routes and indirect routes to direct routes

[0101] Regarding the switching from a direct route to an indirect route, the CU or anchor UE can no longer deliver DL or UL PDCP PDUs to the RLC entity or logical channel of the direct route. Instead, the CU or UE may deliver DL or UL PDCP PDUs toward the RLC channel of the indirect route. To support this, the CU may request the DU to modify the DRB configuration of UE1, which may include the DRB or SRB ID and the modified route configuration. The modified route configuration may include indirect route addition and direct route release configurations, which may further include, among other things, route ID, direct or indirect route, primary or secondary route, route activation, or deactivation in any combination. With respect to packets delivered to the RLC entity or logical channel of the direct route, the packets can still be transmitted until the RLC entity or logical channel is empty. This may also apply to the switching from an indirect route to a direct route. III. Indirect routes to multipath and multipath to indirect routes

[0102] The gNB may send the Uu RLC channel configuration to the UE2. The gNB may then switch the data packets from the UE1 to the UE2. Similarly, with respect to the uplink, the gNB may send the Uu RLC channel to the UE2, and then the UE1 may send the UL data packets to the UE2, which the UE2 then automatically forwards to the gNB. D. Process for multipath communication

[0103] Referring now to Figure 12, what is depicted is a flowchart of Method 1200 for multipath communication. Method 1200 is implemented using, or may be implemented using, any of the components discussed above, such as a centralized unit (CU) and one or more distributed units (DUs) of base stations 102 or 202. Under Method 1200, the CU may transmit multipath configuration information (1205). The DU may receive multipath configuration information (1210). The DU may transmit multipath configuration response information (1215). The CU may receive multipath configuration response information (1220).

[0104] More specifically, the CU may provide, transmit, or otherwise send multipath configuration information to the DU (e.g., DU1 or DU2) (1205). The multipath configuration information may include various information for adding, establishing, modifying, or releasing routes at the DU. In some embodiments, the multipath configuration information may include multipath configuration requests for establishing, adding, or setting routes, multipath modification requests for modifying existing routes, or multipath release requests for releasing routes. The multipath configuration information may include or identify route indication information. The route indication information may identify direct or indirect routes to be configured.

[0105] The multipath configuration information may identify or include mapping information. In some embodiments, the mapping information may include or identify an association between an F1-U tunnel of a data radio bearer (DRB) relating to a remote UE (e.g., UE104 or 204) and a Uu radio link control (RLC) channel relating to a relay UE (e.g., UE104 or 204). In addition, the mapping information may include an association between a signaling radio bearer (SRB) relating to a remote UE and a Uu radio link control (RLC) channel relating to a relay UE. The remote UE (or remote radio communication device) may be connected to the base station via a relay UE (or relay radio communication device) that is directly connected to the base station.

[0106] In some embodiments, the mapping information may include or identify an association between the F1-U tunnel of the DRB relating to the anchor UE (e.g., UE104 or 204) and the Uu RLC channel relating to the aggregated UE. In some embodiments, the mapping information may include or identify an association between the signaling radio bearer (SRB) relating to the anchor radio communication device and the Uu radio link control (RLC) channel relating to the aggregated radio communication device. The aggregated UE (or aggregated radio communication device) may be connected to or from a base station through another UE (e.g., the anchor UE or anchor radio communication device).

[0107] In addition, the multipath configuration information may include or identify various identifiers. In some embodiments, the multipath configuration information may include identifiers relating to the routes (e.g., indirect or direct routes) to be configured (e.g., added, modified, or released). In some embodiments, the multipath configuration information may include identifiers for radio bearers (RBs). The identifiers may relate to data radio bearers (DRBs) or signaling radio bearers (SRBs) relating to the routes to be configured.

[0108] Next, the multipath configuration information may include or identify identifiers for UEs. In some embodiments, the multipath configuration information may include identifiers for relay UEs. Relay UEs may be directly connected to a base station or support indirect connections for remote UEs. In some embodiments, the multipath configuration information may include identifiers for aggregated UEs. Aggregated UEs may include a set of UEs that are interconnected and connected to base stations.

[0109] Multipath configuration information may include or identify various indicators associated with the routes to be configured. In some embodiments, the multipath configuration information may include route indications such as direct routes or indirect routes. A direct route may be a direct link between the UE and the base station. In some embodiments, the multipath configuration information may include route indications such as primary routes or secondary routes. A primary route may correspond to a route through which packet transmission takes precedence over a secondary route. In some embodiments, the multipath configuration information may include route activation indications. Route activation indications may identify whether a route should be active or inactive to receive data packets.

[0110] In some embodiments, the multipath configuration information may include indications for data partitioning or replication for one or more paths. Data partitioning may specify the division of packets across direct and indirect paths. Data replication may specify copies of packets over and in the direct path. In some embodiments, the data partitioning indication may identify a data partitioning threshold or data partitioning ratio. The data partitioning threshold may define the amount of data over which data partitioning should be initiated. The data partitioning ratio may define the ratio of the amount of data communicated over a path. In some embodiments, the multipath configuration information may define, identify, or indicate the distribution of data packets over direct paths (e.g., corresponding to a first RLC channel) and indirect paths (e.g., corresponding to a second RLC channel) for data partitioning.

[0111] Multipath configuration information may include or identify tunnel information. In some embodiments, multipath configuration information may identify or include uplink (UL) user plane (UP) tunnel (TNL) information. In some embodiments, UL UP TNL information may relate to direct or indirect routes. UL UP TNL information may be included for a particular DRB. In some embodiments, multiple sets of UL UP TNL information may relate to segmented DRBs. In some embodiments, multipath configuration information may include identifiers for Uu radio link control (RLC) channels for use. The Uu RLC channels of the UE may be mapped to F1-U tunnels of the DRB. In some embodiments, multipath configuration information may identify a DRB for a set of F1-U tunnels between a CU and a DU (e.g., using a DRB ID).

[0112] The DU may read, identify, or otherwise receive multipath configuration information from the CU (1210). Upon receipt, the DU may analyze the multipath configuration information and extract or identify various information, such as mapping information. The DU may use the multipath configuration to configure direct routes or routes not associated with mapping information (e.g., using a DRB or SRB). Direct routes or unassociated routes may correspond to RLC channels. In some embodiments, the DU may use the multipath configuration information to configure RLC channels for relay UEs or anchor UEs related to direct routes of a DRB or SRB.

[0113] On the other hand, the DU may use a multipath configuration and refrain from configuring additional RLC channels for RBs such as DRBs or SRBs. The additional RLC channels may relate to indirect paths. In some embodiments, the DU may use mapping information and refrain from configuring RLC channels for relay UEs or anchor UEs for DRBs. In some embodiments, the DU may use indirect path indication and refrain from configuring RLC channels for relay UEs or anchor UEs for DRBs or SRBs.

[0114] The DU may provide, transmit, or otherwise send multipath configuration response information to the CU (1215). When using multipath configuration information, the DU may generate multipath configuration response information. The CU may read, identify, or otherwise receive multipath configuration response information from the DU (1220). In some embodiments, the multipath configuration response information may identify or include downlink (DL) user plane (UP) tunnel (TNL) information relating to the routes to be configured. The routes may correspond to those accepted by the DU.

[0115] In some embodiments, the multipath configuration response information may identify or include identifiers relating to routes. Routes may correspond to those configured using the multipath configuration information. In some embodiments, the multipath configuration response information may identify or include indications for direct or indirect routes. Indirect or direct routes may correspond to those configured using the multipath configuration information. In some embodiments, the multipath configuration response information may identify or include indications for primary or secondary routes that are accepted or rejected.

[0116] In some embodiments, the multipath configuration response information may identify or indicate the acceptance or failure of a route. Indication and related information may be generated and provided by the DU. In some embodiments, the multipath configuration response information may include or identify the cause of a route failure. The cause may include, for example, an identifier relating to an unacceptable or unaccepted route for data packet delivery through the route. In some embodiments, the multipath configuration response information may identify or indicate a failure of multipath SRB or DRB configuration. In some embodiments, the multipath configuration response information may identify or indicate a failure of multipath SRB or DRB modification.

[0117] While various embodiments of the Solution are described above, it should be understood that they are presented only as examples and not as limitations. Similarly, various schematic diagrams may depict exemplary architectures or configurations, which are provided to enable those skilled in the art to understand the exemplary features and functions of the Solution. However, such those skilled in the art will understand that the Solution is not limited to the illustrated exemplary architectures or configurations and can be implemented using various alternative architectures and configurations. In addition, as will be understood by those skilled in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Therefore, the scope and scope of this disclosure should not be limited by any of the exemplary embodiments described above.

[0118] Furthermore, it should be understood that any reference to elements in this specification using designations such as “first,” “second,” etc., does not generally limit the quantity or order of those elements. Rather, these designations can be used in this specification as a convenient means of distinguishing two or more elements or instances of elements. Therefore, the references to first and second elements do not mean that only two elements may be employed, or that the first element must precede the second element in any given form.

[0119] In addition, those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, and symbols, which may be referenced in the above description, can be represented by voltage, electric current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0120] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in relation to the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination thereof), firmware, various forms of programs or design code incorporating instructions (which may be referred to herein for convenience as “software” or “software modules”), or any combination of these techniques. To clearly illustrate the interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described above in general terms of their functionality. Whether such functionality is implemented as hardware, firmware, software, or a combination of these techniques depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art will understand that the described functionality may be implemented in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of this disclosure.

[0121] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented in or carried out within an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits may further include antennas and / or transceivers that can communicate with various components in a network or within a device. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, e.g., a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable combination of configurations for carrying out the functions described herein.

[0122] When implemented in software, the functionality can be stored on a computer-readable medium as one or more instructions or code. Therefore, steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. The computer-readable medium includes both computer storage media and communication media, including any medium that can enable the transfer of computer programs or code from one location to another. The storage medium can be any available medium that can be accessed by a computer. Without limitation, as an embodiment, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0123] In this document, the term “module” as used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purposes of discussion, various modules are described as discrete modules; however, as will be obvious to those skilled in the art, two or more modules may be combined to form a single module that performs the associated functions according to embodiments of this solution.

[0124] In addition, memory or other storage devices and communication components may be employed in embodiments of this solution. For the purpose of clarification, it should be understood that the above description describes embodiments of this solution with reference to different functional units and processors. However, it will be apparent that any preferred distribution of functionality between different functional units, processing logic elements, or domains may be used without deviating from this solution. For example, functionality illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units are not intended to indicate a strict logical or physical structure or organization, but merely to refer to preferred means for providing the functionality described.

[0125] Various modifications of the embodiments described herein will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but rather to be given the broadest scope consistent with the novel features and principles disclosed herein, as enumerated in the following claims.

Claims

1. A method of multipath communication, The centralized unit (CU) transmits multipath configuration information to the distributed unit (DU) which includes mapping information that identifies the association between the F1-U tunnel and the Uu radio link control (RLC) channel relating to at least one wireless communication device, The CU receives multipath configuration response information from the DU based on the multipath configuration information. Methods that include...

2. The method according to claim 1, wherein the multipath configuration information comprises route indication information that identifies at least one of a direct route or an indirect route.

3. The aforementioned mapping information is The association between the F1-U tunnel of a data radio bearer (DRB) for a remote radio communication device and the UuRLC channel for a relay radio communication device, or Association between the F1-U tunnel of a data radio bearer (DRB) for anchor wireless communication devices and the UuRLC channel for aggregated wireless communication devices. The method according to claim 1, which identifies the

4. The aforementioned mapping information is The association between a signaling radio bearer (SRB) for a remote radio communication device and a UuRLC channel for a relay radio communication device, or Association between signaling radio bearers (SRBs) for anchor wireless communication devices and UuRLC channels for aggregated wireless communication devices. The method according to claim 1, which identifies the

5. The method according to claim 1, wherein the multipath configuration information comprises at least one of the following: a radio bearer (RB) identifier, uplink (UL) user plane (UP) tunnel (TNL) information, an identifier relating to a relay radio communication device, an identifier relating to an aggregated radio communication device, an identifier relating to the UuRLC channel, an identifier relating to a route, an indication of a direct or indirect route, an indication of a primary or secondary route, an indication of data partitioning or data replication, or a route activation indication.

6. The method according to claim 5, wherein the identifier of the RB may be at least one of the identifiers of a data radio bearer (DRB) or a signaling radio bearer (SRB).

7. The method according to claim 3, wherein the multipath configuration information accompanied by mapping information is used by the DU to refrain from setting up an RLC channel for a relay radio communication device or an anchor radio communication device with respect to the DRB.

8. The method according to claim 5, wherein the multipath configuration information with indirect path indication is used by the DU to refrain from setting up an RLC channel for a relay radio communication device or anchor radio communication device with respect to a data radio bearer (DRB) or signaling radio bearer (SRB).

9. The method according to claim 1, wherein the multipath configuration information is used by the DU to configure a first RLC channel of a relay radio communication device or anchor radio communication device with respect to a direct path of a data radio bearer (DRB) or signaling radio bearer (SRB).

10. The method according to claim 1, wherein the multipath configuration information involving data partitioning indicates the distribution of a plurality of data packets traversing a first RLC channel corresponding to a direct path and a second RLC channel corresponding to an indirect path.

11. The method according to claim 1, wherein the multipath configuration information identifies data radio bearers (DRBs) relating to a plurality of F1 user plane tunnels between the CU and the DU.

12. The method according to claim 1, wherein the multipath configuration information comprises uplink (UL) user plane (UP) tunnel (TNL) information relating to at least one of direct or indirect paths.

13. The method according to claim 1, wherein the multipath configuration information comprises two or more UL UP TNL pieces of information relating to the partitioned DRB.

14. A unified unit (CU), At least one processor, Transmitting multipath configuration information to a distributed unit (DU) via a transceiver, which includes mapping information identifying the association between the F1-U tunnel and a Uu radio link control (RLC) channel relating to at least one wireless communication device, The transceiver receives multipath configuration response information from the DU based on the multipath configuration information. at least one processor configured to perform A unified unit (CU) equipped with this feature.

15. A method of multipath communication, The distributed unit (DU) receives multipath configuration information from the centralized unit (CU) which includes mapping information that identifies the association between the F1-U tunnel and the Uu radio link control (RLC) channel relating to at least one wireless communication device, The DU transmits multipath configuration response information based on the multipath configuration information to the CU. Methods that include...

16. A distributed unit (DU), At least one processor, The system receives multipath configuration information from a centralized unit (CU) via a transceiver, which includes mapping information that identifies the association between the F1-U tunnel and a Uu radio link control (RLC) channel relating to at least one wireless communication device. The transceiver transmits multipath configuration response information based on the multipath configuration information to the CU. at least one processor configured to perform A distributed unit (DU) equipped with this feature.

17. The DU according to claim 16, wherein the multipath configuration information includes route indication information that identifies at least one of a direct route or an indirect route.

18. The aforementioned mapping information is The association between the F1-U tunnel of a data radio bearer (DRB) for a remote radio communication device and the UuRLC channel for a relay radio communication device, or Association between the F1-U tunnel of a data radio bearer (DRB) for anchor wireless communication devices and the UuRLC channel for aggregated wireless communication devices. The DU according to claim 16, which identifies the DU.

19. The aforementioned mapping information is The association between a signaling radio bearer (SRB) for a remote radio communication device and a UuRLC channel for a relay radio communication device, or Association between signaling radio bearers (SRBs) for anchor wireless communication devices and UuRLC channels for aggregated wireless communication devices. The DU according to claim 16, which identifies the DU.

20. The DU according to claim 16, wherein the multipath configuration information comprises at least one of the following: a radio bearer (RB) identifier, uplink (UL) user plane (UP) tunnel (TNL) information, an identifier relating to a relay radio communication device, an identifier relating to an aggregated radio communication device, an identifier relating to the UuRLC channel, an identifier relating to a route, an indication of a direct or indirect route, an indication of a primary or secondary route, an indication of data partitioning or data replication, or a route activation indication.

Images