Data splitting for multipath transmissions

Abstract

Systems, methods, apparatus, or computer-readable media for splitting data for multipath transmissions are presented. The first wireless communication device may receive information of the first path or the second path from the wireless communication node. The first wireless communication device may determine to split the data transmission via the first path or the second path.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, including but not limited to systems and methods for data splitting for multipath transmissions. Background Art

[0002] The third generation partnership project (3GPP), a standardization organization, is currently developing a new radio interface called 5G New Radio (5G NR), as well as the next generation packet core network (NG-CN or NGC). 5G NR will have three main components: 5G access network (5G-AN), 5G core network (5GC) and user equipment (UE). To facilitate the realization of different data services and requirements, the elements of 5GC (also known as network functions) have been simplified, some of which are software-based so that they can be adapted as needed. Summary of the invention

[0003] The example embodiments disclosed herein are intended to solve problems related to one or more of the problems raised in the prior art, as well as to provide additional features that will become clear by reference to the following detailed description when taken in conjunction with the accompanying drawings. According to various embodiments, example systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example, not limitation, and it will be clear to those of ordinary skill in the art who read this disclosure that various modifications may be made to the disclosed embodiments while remaining within the scope of this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium for splitting data for multipath transmission. A first wireless communication device may receive quality of service (QoS) information of a first path from a wireless communication node. The first wireless communication device may determine to split the data transmission via the first path or the second path.

[0005] In some embodiments, the first wireless communication device may receive QoS information of the second path from the second wireless communication device. In some embodiments, the first wireless communication device may receive QoS information of the second path from the wireless communication node.

[0006] In some embodiments, the QoS information may include at least one of an aggregate maximum bit rate (AMBR), a guaranteed flow bit rate (GFBR), or a maximum flow bit rate (MFBR) for communications on the first path or the second path. In some embodiments, the AMBR may include at least one of the following: an AMBR for a UL protocol data unit (PDU) session or a UL AMBR for the first wireless communication device for communications on the first path or the second path.

[0007] In some embodiments, the QoS information may include an aggregate maximum bit rate (AMBR) of at least one of the first wireless communication device, the second wireless communication device, or the bearer. In some embodiments, the first path is between the first wireless communication device and the wireless communication node. In some embodiments, the second path is between the first wireless communication device and the wireless communication node via the second wireless communication device.

[0008] At least one aspect relates to a system, method, apparatus, or computer-readable medium for splitting data for multipath transmission. A first wireless communication device may receive link state information of a first path from a second wireless communication device. The first wireless communication device may determine to split the data transmission via the first path or the second path.

[0009] In some embodiments, the first wireless communication device may send link state information of the first path to the wireless communication node. In some embodiments, the link state information may include a data rate for a Uu link or an inter-UE link on the first path. In some embodiments, the data rate may be for at least one of the first wireless communication device, the second wireless communication device, or the bearer.

[0010] In some embodiments, the link state information may include the spectrum efficiency of the first path for the Uu link or the inter-UE link. In some embodiments, the link state information may include the available buffer size of the second wireless communication device. In some embodiments, the first path may be between the first wireless communication device and the wireless communication node via the second communication device. In some embodiments, the second path may be between the first wireless communication device and the wireless communication node.

[0011] At least one aspect relates to a system, method, apparatus, or computer-readable medium for splitting data for multipath transmission. A first wireless communication device may send channel condition information about a first path between the first wireless communication device and the wireless communication node to a wireless communication node. In some embodiments, the first wireless communication device may receive path information from the wireless communication node to be used for splitting data transmission via the first path or the second path.

[0012] In some embodiments, the wireless communication node may receive second channel condition information of a second path between the first wireless communication device and the wireless communication node via the second wireless communication device from the second wireless communication device. In some embodiments, the channel condition information of the first path or the second path may include at least one of channel state information or link state information.

[0013] In some embodiments, the channel condition information of the first path or the second path may include link state information of at least one of the first wireless communication device or the second wireless communication device. In some embodiments, the path information may include at least one of a data split ratio, a data split threshold, or a target data rate of the first path or the second path. In some embodiments, the first path may be between the first wireless communication device and the wireless communication node.

[0014] At least one aspect relates to a system, method, apparatus, or computer-readable medium for processing data splitting of multipath transmissions. A first network element may receive channel condition information about a first path or a second path from a second network element of a wireless communication node. In some embodiments, the wireless communication node may determine path information for splitting data transmission via the first path or the second path. In some embodiments, the channel condition information may include at least one of channel state information or link state information.

[0015] In some embodiments, the first network element may be a central unit (CU) and the second network element may be a distributed unit (DU). In some embodiments, the first network element may receive link state information of at least one of the first wireless communication device or the second wireless communication device from at least one of the second network element or the third network element. In some embodiments, the link state information may include at least one of: a data rate for a Uu link or an inter-UE link on the first path; a spectrum efficiency for a Uu link or an inter-UE link of the first path; or an available buffer size of the second wireless communication device. In some embodiments, the data rate may be for at least one of the first wireless communication device, the second wireless communication device, or a bearer.

[0016] In some embodiments, the first network element may send path information identifying quality of service (QoS) information of the first path to the first wireless communication device. In some embodiments, the QoS information may include at least one of an aggregate maximum bit rate (AMBR), a guaranteed flow bit rate (GFBR), or a maximum flow bit rate (MFBR) for communications on the first path or the second path. In some embodiments, the AMBR may include at least one of the following: an AMBR for a UL protocol data unit (PDU) session or a UL AMBR for the first wireless communication device for communications on the first path or the second path. In some embodiments, the QoS information may include an aggregate maximum bit rate (AMBR) of at least one of the first wireless communication device, the second wireless communication device, or a bearer. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Various example embodiments of the present solution are described in detail below with reference to the following drawings or figures. The drawings are provided for illustrative purposes only and depict only example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the breadth, scope or applicability of the present solution. It should be noted that for clarity and ease of description, these drawings are not necessarily drawn to scale.

[0018] Figure 1 illustrates an example cellular communication network in which the techniques disclosed herein may be implemented according to embodiments of the present disclosure;

[0019] Figure 2 illustrates a block diagram of example base station and user equipment devices according to some embodiments of the present disclosure;

[0020] Figure 3 illustrates a block diagram of an environment for user equipment to network relay according to an illustrative embodiment;

[0021] Figure 4 illustrates a block diagram of an environment for aggregation of multiple user devices for network relaying according to an illustrative embodiment;

[0022] Figure 5A illustrates a block diagram of multipath transmission within a distributed unit (DU) according to an illustrative embodiment;

[0023] Figure 5B illustrates a block diagram of multipath transmission between distributed units (DUs) according to an illustrative embodiment;

[0024] Figure 6 illustrates a communication diagram of a multipath configuration process for different resource blocks and multiple distributed units (DUs) according to an illustrative embodiment;

[0025] Figure 7 illustrates a communication diagram of a multipath configuration process for split bearers and multiple distributed units (DUs) in accordance with an illustrative embodiment;

[0026] Figure 8 a communication diagram illustrating a process for multipath transmission initiated by a remote user device in accordance with an illustrative embodiment; and

[0027] Fig.9A and Fig. 9B A flow chart of a method of splitting data for multipath transmission is illustrated in accordance with an illustrative embodiment. DETAILED DESCRIPTION

[0028] Various example embodiments of the present solution are described below with reference to the accompanying drawings so that a person of ordinary skill in the art can make and use the present solution. As is clear to a person of ordinary skill in the art, after reading the present disclosure, various changes or modifications may be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example embodiments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely example methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be rearranged while remaining within the scope of the present solution. Therefore, a person of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.

[0029] 1. Mobile communication technology and environment

[0030] Figure 1 An example wireless communication network and / or system 100 is illustrated in which the techniques disclosed herein may be implemented in accordance with an 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 is referred to herein as "network 100." Such an example network 100 includes a base station 102 (hereinafter referred to as "BS 102"; also referred to as a wireless communication node) and a user equipment device 104 (hereinafter referred to as "UE 104"; also referred to as a wireless communication device) that may communicate with each other via a communication link 110 (e.g., a wireless communication channel), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 1 , BS 102 and UE 104 are contained within respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating within its allocated bandwidth to provide adequate radio coverage to its intended users.

[0031] For example, BS 102 may operate with the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 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 the present disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes", which may generally practice the methods disclosed herein. According to various embodiments of the present solution, such communication nodes may be capable of wireless and / or wired communication.

[0032] Figure 2 A block diagram of an example wireless communication system 200 for sending and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some embodiments of the present solution is illustrated. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In an illustrative embodiment, the system 200 may be used in applications such as Figure 1 The data symbols are communicated (eg, sent and received) in a wireless communication environment such as the wireless communication environment 100 of FIG. 1 , as described above.

[0033] System 200 generally includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment device 204 (hereinafter referred to as "UE 204"). BS 202 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 of which is coupled to and interconnected with each other via a data communication bus 220 as needed. UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled to and interconnected with each other via a data communication bus 240 as needed. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for data transmission as described herein.

[0034] As will be appreciated by those skilled in the art, the system 200 may also include Figure 2Any number of other modules outside the modules shown. It will be appreciated by those skilled in the art that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any actual combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described according to their functions. Whether such functions are implemented as hardware, firmware, or software may depend on specific applications and design constraints imposed on the entire system. People familiar with the concepts described herein can implement such functions in a suitable manner for each specific application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.

[0035] According to some embodiments, the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230, which includes a radio frequency (RF) transmitter and an RF receiver, each of which includes circuitry 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 manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210, which includes an RF transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 212. The downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time duplex manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions made over the wireless transmission link 250 when the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operation of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 when the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is tight time synchronization with minimal guard times between changes in duplex direction.

[0036] The UE transceiver 230 and the base station transceiver 210 are configured to communicate via a wireless data communication link 250 and cooperate with an appropriately configured RF antenna arrangement 212 / 232 capable of supporting a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 230 and the base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to application to specific standards and related protocols. Instead, the UE transceiver 230 and the base station transceiver 210 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0037] According to various embodiments, for example, BS 202 may be an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell or a microcell. In some embodiments, UE 204 may be embodied in various types of user equipment, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. Processor modules 214 and 236 may be implemented or implemented with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, for example, a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

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

[0039] The network communication module 218 generally represents the hardware, software, firmware, processing logic and / or other components of the base station 202 for enabling 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 can be configured to support Internet or WiMAX services. In a typical deployment, without limitation, the network communication module 218 provides an 802.3 Ethernet interface so that the base station transceiver 210 can communicate with a conventional Ethernet-based computer network. In this way, the network communication module 218 can include a physical interface for connection to a computer network (e.g., a mobile switching center (MSC)). The terms "configured for", "configured to" and variations thereof as used herein with respect 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.

[0040] The open systems interconnection (OSI) model (referred to herein as the "open systems interconnection model") is a concept and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that are open to interconnect and communicate with other systems. The model is divided into seven subcomponents or layers, each of which represents a conceptual set of services provided to the layers above and below it. The OSI model also defines a logical network and effectively describes computer packet transmission by using different layer protocols. The OSI model may also be referred to as a seven-layer OSI model or a seven-layer model. In some embodiments, the first layer may be a physical layer. In some embodiments, the second layer may be a media access control (MAC) layer. In some embodiments, the third layer may be a radio link control (RLC) layer. In some embodiments, the fourth layer may be a packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer may be a radio resource control (RRC) layer. In some embodiments, the sixth layer may be a non-access stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is another layer.

[0041] 2. Data splitting for multipath transmission

[0042] Data splitting systems and methods for multipath transmission for remote UEs are presented herein. When splitting data traffic towards direct and indirect paths, channel conditions, traffic loads for both direct and indirect paths, and UE capabilities of both remote UEs and relay UEs may be used.

[0043] With the development of wireless multimedia services, the demand for high data rate services may increase significantly. In this case, the system capacity and coverage requirements of conventional cellular networks may become higher. On the other hand, due to application scenarios such as public safety, social networks, short-range data sharing and local advertising, as well as other considerations, the demand for proximity services that allow users to confirm or communicate with nearby people or objects may also increase.

[0044] However, conventional cellular networks may have limitations in supporting high data rate services and proximity services. Therefore, device-to-device (D2D) communication technology can be used to meet such needs. By adopting D2D technology, the burden on cellular networks can be reduced, the power consumption of user devices can be reduced, the data rate can be increased, and the robustness of the network infrastructure can be improved. Therefore, the needs of high data rate services and proximity services can be met. D2D technology can also be called proximity services (ProSe) or sidelink communication, and the interface between devices can be called PC5 interface.

[0045] Reference now Figure 3, depicting a block diagram of an environment 300 of user equipment to network relay. To support a wider range of applications and services, sidelink-based relay communication can be used to extend coverage and reduce power consumption of the network. For example, sidelink-based relay communication can be applied to indoor relay communication, smart agriculture, smart factories, and public safety services. The depicted scenario of applying sidelink-based relay communication may include user equipment (UE) (e.g., Figure 3 In this case, UE1 (also called remote UE) may allow communication with the network (e.g., Figure 3 The base station (BS) shown communicates.

[0046] Therefore, the coverage of the network can be expanded, and the capacity of the network can be expanded. In this case, UE2 can be referred to as a UE-to-Network relay, and UE1 can be referred to as a remote UE. On the other hand, if the remote UE can be within the coverage, multipath relay can be supported. Specifically, within the coverage, the remote UE can be connected to the network via both a direct path (e.g., data sent directly between the remote UE and the network) and an indirect path (e.g., data forwarded via a relay UE), which can help improve reliability / robustness and throughput.

[0047] Reference now Figure 4 , depicts a block diagram of an environment 400 for aggregation of multiple user devices for network relay. This multipath relay solution can also be used for UE aggregation, where a UE can connect to the network via a direct path and via another UE using non-standardized UE-UE interconnection. The depicted application includes a user equipment (UE) (such as Figure 3 The scenario of UE aggregation of UE1) can aggregate other UEs (such as Figure 2 UE2 and UE3 shown in the figure are used for uplink transmission or downlink reception from the network. Here, the interconnection between UE1 (referred to as remote UE) and UE2 (referred to as relay UE) or between UE1 and UE3 (referred to as relay UE) can be based on side link, Wi-Fi, Bluetooth or wired connection, etc. In addition, the interconnection between UEs can be an ideal connection. In situations where normal UEs may be limited by UL UE transmission power and cannot achieve the desired bit rate, especially at the cell edge, UE aggregation can be intended to provide applications requiring high UL bit rates on 5G terminals. In addition, UE aggregation can also improve service reliability, stability and reduce latency.

[0048] In this context, the development of fifth generation (5G) mobile wireless technologies and standards may be applicable. One such technology may include a split network architecture. Under this architecture, the radio access network (RAN) functions can be split between a central unit (CU) and multiple distributed units (DUs). For example, the RAN functions can be split between the packet data convergence protocol (PDCP) layer and the radio link control (RLC) layer of the 5G protocol stack. The DU can handle all processes, including the RLC layer functions, and the CU can handle the PDCP layer and high-level functions before the core network. This decomposition of RAN functions can provide many advantages for mobile network operators. For example, by isolating the stack from the PDCP layer and above, the CU can be able to act as a cloud-based aggregation point between multiple heterogeneous technologies in the configured network, and can therefore be able to serve multiple heterogeneous DUs.

[0049] In order to support multipath UE-to-network relay and UE aggregation, it is useful to consider how to split data traffic between two paths (e.g., direct path and indirect path). The impact on the CU / DU split architecture can also be considered. Methods, systems and devices for data splitting schemes for multipath remote UEs of networks based on both non-split and CU and DU split architectures are presented herein.

[0050] One motivation for UE multipath transmission may involve UEs with limited uplink transmission (UL Tx) capabilities. In a network environment, at least one UE may be associated with multiple UEs for UE aggregation, or connected to multiple relay UEs for UE-to-network relay. In order to support higher requirements for UL services, including data rate, latency, and reliability, multipath transmission may be used. Specifically, a UE may be connected to a network and perform data service transmission and reception with the network via a direct path and via one or more indirect paths (e.g., data services forwarded by another UE). UE-UE interconnection may be based on a sidelink connection or use a non-standardized connection.

[0051] refer to Figure 5A and Figure 5B , Figure 5A A block diagram depicting multipath transmission within a distributed unit (DU) is shown. Figure 5B A block diagram depicts multipath transmission between distributed units (DUs). For UEs connected to the same gNB using one direct path and one indirect path, the direct path and the indirect path can be via the same DU or different DUs as shown. UE1 can be a remote UE and UE2 can be a relay UE. In this case, UE1 and UE2 can be interconnected via PC5 or an internal interface. UE1 and UE2 can be connected by the same DU (such as Figure 5A ) or different DUs (e.g. Figure 5BIn order to support this multipath scenario in both non-split and CU-DU split architectures, the splitting of data packets between direct and indirect paths can be configured to fully utilize network performance. The configuration of data splitting will be described in detail below.

[0052] Typically, for the uplink, a UE with dual connectivity can be configured via radio resource control (RRC) signaling whether to use a primary cell group (MCG) path or to replicate transmissions on both the MCG and the secondary cell group (SCG) for split signaling radio bearers (SRBs). For split data radio bearers (DRBs), the gNB can configure the UE with a UL data split threshold and can indicate the primary path. The UE can determine whether to use the primary path or both to issue UL packets. If the total amount of PDCP data and radio link control (RLC) data waiting for initial transmission in the primary RLC entity and the split secondary RLC entity is equal to or greater than the UL data split threshold, the UE can submit a PDCP protocol data unit (PDU) to the primary RLC entity or the split secondary RLC entity. The UE can indicate the PDCP data amount to both the MAC entity associated with the primary RLC entity and the MAC entity associated with the split secondary RLC entity. At this point, how to split the data packets toward the two paths can actually depend on the UE implementation. Otherwise, the UE may submit the PDCP PDU to the primary RLC entity and may indicate the PDCP data amount to the MAC entity associated with the primary RLC entity.

[0053] On the other hand, from the perspective of the gNB in ​​the dual connection scenario, the master node (MN) can determine whether to implement MCG bearer, SCG bearer or split bearer. Based on this determination, the gNB can issue the corresponding quality of service (QoS) requirements to the secondary node (SN). For the QoS flow to be mapped to the split bearer, the QoS requirements of the SN can be different from the QoS flow parameters and can be received by the MN through the NG. The MN and the SN can jointly provide resources to ensure the QoS requirements of the split bearer. The MN and the SN can determine the QoS of the split bearer and can establish RLC bearers for the MCG and SCG respectively. The two RLC bearers can share the QoS of the split DRB together. In addition, for split SRBs and DRBs, the selection of the transmission path in the downlink may depend on the network implementation.

[0054] A. Splitting data traffic by remote user equipment using quality of service requirements

[0055] UE1 and UE2 may be served by the same gNB. Splitting data traffic for multipath transmission of remote UE1 may be a factor affecting QoS requirements. In this case, UE1 may be a remote UE and UE2 may be a relay UE, and both may be served by the same gNB. UE1 and UE2 may be connected to the network via the same DU1 or via different DU1 and DU2, respectively, as shown in FIG. Figure 5A and Figure 5B shown.

[0056] For multipath delivery of UE1's services, the data splitting operation may take into account QoS aspects. The QoS requirements of the data flows of the remote UE1 may reflect the long-term data transmission requirements. For non-guaranteed bit rate (GBR) QoS flows, DU1 and / or DU2 may use the UL PDU session aggregate maximum bit rate to enforce the uplink service policy for the non-GBR bearers of the associated UEs. On the other hand, DU1 and / or DU2 may receive gNB-DU UE aggregate maximum bit rate (AMBR) uplink, which may be regarded as a UE-specific UL AMBR enforced by DU1 and DU2. On the other hand, DU1 and / or DU2 may receive guaranteed flow bit rate (GFBR) uplink and maximum flow bit rate (MFBR) uplink, which may be delivered per DRB or per QoS flow. DU1 and / or DU2 may enforce such uplink bit rate limitation on the DRBs of UE1 during uplink scheduling. Some of UE1's non-GBR QoS flows may be mapped to DRB1, while other UE1's GBR QoS flows may be mapped to DRB2. Both DRB1 and DRB2 may be delivered via both a direct path and an indirect path (forwarded by UE2).

[0057] For Figure 5A In the split DRB scenario within a DU shown, DU1 can enforce UL AMBR for non-GBR bearers and GFBR or MFBR for GBR bearers. This may involve joint scheduling of one or more cells that can serve UE1. Figure 5B In the scenario of splitting DRBs between DUs shown, when a DRB1 request to be established or modified is sent to DU1, the CU can split the UE-specific AMBR or the PDU session-specific AMBR.

[0058] Reference now Figure 6, depicting a communication diagram of a multipath configuration process 600 for different resource blocks and multiple distributed units (DUs). Under process 600, the CU may issue a UE context modification request (605) for the UE to DU1, the request including UL UPTNL information of the DRB list to be established. DU1 may issue a UE context modification response (610) to the CU, the response including the established DRB list, DL UP TNL information. The CU may issue a UE context establishment request (615) for UE2, the request including the Uu RLC channel to be established. DU2 may issue a UE context establishment response (620), the response including the established Uu RLC channel list. The CU may issue a DL RRC message transmission (625). DU2 may then forward the RRC reconfiguration to UE2 (630). In combination, the CU may issue a DL RRC message transmission (640) to DU1. DU1 may issue an RRC reconfiguration (645). The reconfiguration message may include a UL AMBR for a direct path or an indirect path, a GFBR or MFBR for a primary path or a secondary path of DRB2. UE1 may determine UL data splitting based on the MFBR, GFBR, or MFBR configuration (650). The UE may send data packets of DRB1 or DRB2 of UE1 via the direct path (655). The UE may send data packets of DRB1 or DRB2 of UE1 via the indirect path (660).

[0059] For the indirect path, the CU can issue the UL AMBR of the UL traffic to be delivered to DU2 via the Uu RLC channel of UE2. Similarly, when issuing a request to establish or modify DRB2 to DU1, the CU can split the GFBR or MFBR requirement. For the indirect path, the CU can issue the split GFBR or MFBR of the UL traffic to be delivered to DU2 via the Uu RLC channel of UE2. Then, DU1 and DU2 can perform corresponding uplink bit rate control during scheduling. From this perspective, the CU can determine the data splitting scheme, and DU1 and DU2 can perform UL data rate control separately. In this sense, it is best for the remote UE1 to be consistent with the data splitting scheme intended by the CU.

[0060] In order to make the UL QoS splitting of UE1 consistent with that of CU or gNB, CU or gNB may send per-path UL AMBR and / or GFBR or MFBR information to UE. Specifically, the per-path UL AMBR information may include at least one of the following: UL PDU session AMBR for direct path, UL PDU session AMBR for indirect path, UL PDU session AMBR for primary path, UL PDU session AMBR for secondary path, UE UL AMBR for direct path, UE UL AMBR for indirect path, UE UL AMBR for primary path, UE UL AMBR for secondary path. In addition, the per-path GFBR or MFBR information may include at least one of the following: GFBR or MFBR for direct path, GFBR or MFBR for indirect path, GFBR or MFBR for primary path, GFBR or MFBR for secondary path, GFBR or MFBR for direct path, GFBR or MFBR for indirect path, GFBR or MFBR for primary path, GFBR or MFBR for secondary path.

[0061] For example, the CU may configure the UE UL AMBR for the direct path and the indirect path respectively for the remote UE1 (eg, Figure 6 In addition, the CU may configure the GFBR or MFBR of the primary path and the GFBR or MFBR of the secondary path for multipath data splitting DRB2 for the remote UE1 (e.g., Figure 6 Based on the UE UL AMBR and GFBR or MFBR configuration, the remote UE1 may perform data splitting operations on DRB1 and DRB2 ( Figure 6 For example, the remote UE1 may deliver the data packets of DRB1 to the direct path and the indirect path that do not exceed the UE UL AMBR of the direct path and the UE UL AMBR of the indirect path, respectively. On the other hand, the remote UE1 may deliver the data packets of DRB2 to the direct path and the indirect path that do not exceed the MFBR of the primary path and the MFBR of the secondary path, respectively.

[0062] B. Splitting data traffic by remote user equipment using channel conditions

[0063] UE1 and UE2 may be served by the same gNB. The splitting of multipath transmitted data traffic for remote UE1 may take into account the impact of channel conditions. For the downlink, the UE may measure the synchronization signal (SS) block to estimate the path loss and average channel quality. Due to limited bandwidth and low duty cycle, the SS block may not be suitable for more detailed channel sounding aimed at tracking channel properties that change rapidly in time or frequency.

[0064] To this end, the UE may also measure channel state information, reference signal (CSI-RS) to derive channel properties and report channel state information (CSI). CSI reports may include channel quality indicator (CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS-PBCH block resource indicator (SSBRI), layer indicator (LI), rank indicator (RI), beam-level reference signal received power (L1-SRP) or beam-level signal to interference and noise ratio (L1-SINR), etc. CSI reports may be used for link adaptation, multi-antenna precoding, and beam management. CSI-RS transmission and UE CSI reports may be configured for periodic, semi-persistent or aperiodic transmission. On the other hand, the network may configure the UE to send a sounding reference signal (SRS) for uplink sounding purposes. Based on the SRS sent by the device, the network may determine the precoder matrix used by the UE for uplink transmission. In addition, the UE may be explicitly scheduled for uplink data transmission using the same beam or panel that has been used for a certain SRS transmission.

[0065] Many UEs may be capable of multiple-input / multiple-output (MIMO). For example, a UE may support two transmit antennas and two receive antennas for the Uu link. The uplink of the UE may support parallel two-layer transmissions using the same time or frequency resources. For the sidelink, the UE may support one transmit antenna and two receive antennas. On the other hand, the maximum transmit power of the UE and the location of the UE may affect the channel conditions. The maximum power level may limit UL transmissions for cell-edge UEs (lower modulation and coding scheme (MCS), more retransmissions).

[0066] To achieve similar data rate or reliability as cell-enter UEs, cell-edge UEs may perform more retransmissions, occupying more radio resources. In this case, it is better to offload more data transmission to the indirect path. From the gNB perspective, the gNB can determine the uplink channel quality based on SRS or CSI reports (for reciprocal channels). The gNB can then configure the UE with appropriate precoder matrix, MCS, downlink control information (DCI) grant with one or two antenna layers. Based on the gNB configuration, the UE can perform uplink transmission / retransmission.

[0067] When multipath relay is involved, the remote UE 1 can detect the channel conditions of the direct link and the PC5 link (for scenario 1) or the internal connection between UEs (for scenario 2). However, the data throughput of the indirect path may depend on the channel conditions of the Uu link and PC5 link of the relay UE, or the internal connection between the relay UE and the remote UE. In addition, the AMBR, GFBR or MFBR of the relay UE for the Uu RLC channel and the PC5 AMBR of the remote UE may also affect the data throughput.

[0068] As far as we know, the remote UE may not know the achievable data rate or spectrum efficiency of the Uu link of the relay UE. When the remote UE performs UL data splitting for the direct path and the indirect path (or the primary path and the secondary path), the UE may deliver more or less data packets to the indirect path than preferred. Based on this observation, the following options can be considered from the UE's perspective.

[0069] First, the relay UE can send Uu link state information to the remote UE3. The Uu link state can be in the form of the expected / estimated data rate of the Uu link. Based on this information, the remote UE can attempt to deliver data packets to the relay UE according to the expected / estimated data rate. Alternatively, the expected data rate can be sent to the remote UE at the UE level (e.g., at the relay UE level or at the remote UE level) and by bearer (e.g., multipath split bearer or indirect bearer). In addition to the expected data rate, the relay UE can also send the spectral efficiency, RSRP or, rank indicator (RI), precoding matrix indicator (PMI) and channel quality indicator (CQI) values ​​of the Uu link to the remote UE. The remote UE can help the remote UE determine the channel conditions of the Uu link of the relay UE, and then determine the data splitting scheme.

[0070] Secondly, the relay UE can send a UL AMBR, GFBR, or MFBR value to the remote UE. The UL AMBR value sent to the remote UE can be at the UE level (e.g., by relay UE or by remote UE) or at the bearer level (e.g., multipath split bearer or indirect bearer for remote UE). It should be noted that UL AMBR can be used for non-GBR bearers, while GFBR or MFBR can be used for GBR bearers. The relay UE can send both for non-GBR bearers and GBR bearers, respectively. Based on this information, the remote UE can determine how many data packets of the multipath split bearer can be delivered via an indirect path.

[0071] Third, the congestion status can usually be reflected by the available buffer size at the relay UE and the remote UE. Similar to the channel condition, the remote UE can know the available buffer size for the Uu and PC5 links at the remote UE. However, it may not know the congestion status at the relay UE (e.g., the available buffer size). Therefore, the relay UE can send the available buffer size to the remote UE. The available buffer size can be per UE (e.g., per remote UE or per relay UE) or per bearer (e.g., per multipath split bearer or per indirect bearer). Based on the available buffer size information from the relay UE, the remote UE can attempt to deliver data packets that do not exceed the available buffer size via an indirect path.

[0072] Reference now Figure 7 , depicts a communication diagram of a multipath configuration process 700 for splitting a bearer and multiple distributed units (DUs). Under process 700, the relay UE may send a Uu link status congestion status or UL AMBR, GFBR, or MFBR to the remote UE (705). The remote UE may determine a data splitting scheme for a given split DRB (710). The remote UE may transmit data packets of the UE's split DRB via the primary path (715). The remote UE may transmit data packets of the UE's split DRB via the secondary path (720). As shown, the remote UE1 may receive the Uu link status of the relay UE from the relay UE2. In addition, the remote UE1 may also receive congestion status and / or UL AMBR, GFBR, or MFBR from the relay UE2. Based on this information, the remote UE may determine how many data packets of the multipath split bearer may be delivered via the primary path or the secondary path.

[0073] C. Splitting architecture to facilitate data splitting for multipath transmission.

[0074] Regarding data splitting for multipath relay, the following cases can be considered in conjunction with the split architecture of the gNB with CU and DU.

[0075] I.DU internal scene

[0076] For this case, the same DU can be responsible for Uu scheduling for both remote UE and relay UE. In addition, for scenario 1, PC5 scheduling for both remote UE and relay UE can also be performed by the same DU. In mode 2, the DU may not be aware of the PC5 channel conditions. In this case, the remote UE can send PC5 channel status information such as estimated data rate, spectrum efficiency, PC5 RSRP or PC5 CSI to the gNB or CU. When it comes to scenario 2, the remote UE can send the link status between the remote UE and the relay UE to the gNB or CU. The link status between the remote UE and the relay UE may include estimated data rate or congestion status, etc.

[0077] Based on this observation, the DU may be able to globally view the channel status, buffer size of both the relay UE and the remote UE. Therefore, the DU can configure the appropriate data rate for splitting the bearer for the remote UE. For example, the CU or gNB can send the desired data rate, or the AMBR, GFBR, or MFBR of the indirect path to the remote UE for multipath splitting of the bearer. Based on this information, the remote UE can determine the data splitting scheme.

[0078] Ⅱ. DU Inter-Scene

[0079] The remote UE may be served by DU1, while the relay UE may be served by DU2. In this case, DU1 may not know the UL channel condition of the relay UE. Similarly, DU2 may not know the UL channel condition of the remote UE. DU1 and DU2 may be configured with UL AMBR, GFBR or MFBR information for the remote UE and relay UE, respectively. In this case, DU1 / DU2 may report the Uu link status information of the remote UE / relay UE to the CU (considering that the CSI report is reported to the DU). Based on this information, the CU may determine the data splitting threshold, data splitting ratio or expected data rate for the direct path and the indirect path, respectively. The CU may then send the expected data rate, or the AMBR, GFBR or MFBR of the indirect path to the remote UE for multipath splitting bearer. Based on this information, the remote UE may determine the data splitting scheme.

[0080] D. User equipment used to initiate multipath transmission

[0081] UEs may initiate multipath transmission in the following manner. UE1 may be a remote UE and UE2 may be a relay UE. Both UE1 and UE2 may be served by the same gNB. UE1 and UE2 may be connected to the network via the same DU1 or via different DU1 and DU2, respectively, as shown in FIG. Figure 5A and Figure 5B shown.

[0082] Reference now Figure 8 , depicts a communication diagram of a multipath transmission process 800 initiated by a remote user equipment. Under process 800, the remote UE may issue a multipath transmission or UE aggregation request (805). The gNB may determine to enable multipath transmission for the remote UE via aggregation with a relay UE (810). The gNB may issue a multipath transmission or UE aggregation configuration to the remote UE (815). The remote UE may send data packets of the split DRB of UE1 via a primary path (820). The remote UE may send data packets of the split DRB of UE1 via a secondary path (825).

[0083] UE1 may have data transmission requirements. UE1 may send a multipath transmission request or indication to the gNB. In addition, UE1 may send a QoS profile of the service to the gNB. The QoS profile of the service may be at least one of the following fields: GFBR, MFBR, AMBR, priority, packet delay budget (PDB), packet error rate (PER), packet size, and periodicity. In addition, UE1 may send potential relay UE information to the gNB. Potential relay UE information may include relay UE ID or relay UE capabilities. Relay UE capabilities may include transmit (Tx) power and MIMO capabilities.

[0084] Based on such information, the gNB may determine to enable multipath transmission for the remote UE via aggregation with the relay UE2. The CU may then configure multipath transmission via direct and indirect paths for the remote UE1 for subsequent data traffic. After receiving such configuration, the remote UE1 may deliver data packets to the direct and indirect paths for the primary and secondary paths, respectively.

[0085] E. Data splitting process of multipath transmission

[0086] Reference now Fig.9A and Fig. 9B , depicting a flow chart of a method 900 for splitting data for multipath transmission. The method 900 may be implemented or performed using any of the components detailed above, such as BS 102 or 202, UE 104 or 204, gNB, CU, DU1, and DU2, etc. Under the method 900, a wireless communication node (e.g., BS 102 or 202) may provide, send, or otherwise issue quality of service (QoS) information (905) to a first wireless communication device (e.g., UE 104 or 204). The wireless communication node may identify QoS information of the first wireless communication node or the second wireless communication node, etc. The QoS information may be for a first path and a second path between the first wireless communication device and the wireless communication node. The first path may be a primary path or a direct path between the first wireless communication device (e.g., a remote UE) and the wireless communication node. The second path may be a secondary or indirect path between the first wireless communication device and the wireless communication node via a second wireless communication device (e.g., a relay UE).

[0087] For example, the QoS information may identify or include an aggregate maximum bit rate (AMBR), a guaranteed flow bit rate (GFBR), or a maximum flow bit rate (MFBR) for uplink (UL) communications on a first path or a second path. In some embodiments, the AMBR may be a UL AMBR for a first wireless communication device for communications on the first path or the second path or for a UL protocol data unit (PDU) session. In some embodiments, the AMBR may be for a first wireless communication device, a second communication device, or a bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB)), etc. In some embodiments, the QoS information provided by the wireless communication node may be for a first path between a first wireless communication device and the wireless communication node. In some embodiments, the QoS information may be for both the first path and the second path.

[0088] Using the identifier, the wireless communication node can generate a message (e.g., an RRC reconfiguration message) including QoS information. After generation, the wireless communication node can send it to the first wireless communication device. In turn, the first wireless communication device can obtain, identify, or otherwise receive QoS information from the wireless communication node (910). The QoS information can be received from the wireless communication node in a reconfiguration message (e.g., an RRC reconfiguration message). In some embodiments, the QoS information received from the wireless communication node can be for a first path between the first wireless communication device and the wireless communication node. In some embodiments, the QoS information received from the wireless communication node can be for both the first path and the second path.

[0089] The second wireless communication device (e.g., UE 104 or 204) may provide, send, or otherwise issue QoS information to the first wireless communication device (915). The QoS information issued by the second wireless communication device may be for a second path between the first wireless communication device and the wireless communication node via the second wireless communication device. The QoS information issued by the second wireless communication device may be different from the QoS information issued by the first wireless communication device. In some embodiments, when the QoS information provided by the wireless communication node is for the first path and lacks information about the second path, the second wireless communication device may issue QoS information for the second path.

[0090] For example, the QoS information may identify or include an aggregate maximum bit rate (AMBR), a guaranteed flow bit rate (GFBR), or a maximum flow bit rate (MFBR) for uplink (UL) communications on a second path (e.g., an indirect or auxiliary path). In some embodiments, the AMBR may be a UL AMBR for the first wireless communication device or for a UL protocol data unit (PDU) session for communications on the second path. In some embodiments, the AMBR may be for the first wireless communication device, the second communication device, or a bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB)), etc. The first wireless communication device may then obtain, identify, or otherwise receive the QoS information from the second wireless communication device (920).

[0091] The second wireless communication device may provide, send, or otherwise issue link state information to the first wireless communication device (925). The link state information may be for a second path between the first wireless communication device and the wireless communication node via the second wireless communication device. In some embodiments, the link state information may identify or include a data rate for a Uu link or an inter-UE link (e.g., between the first wireless communication device and the second wireless communication device) on the second path. For example, the data rate may be for the first wireless communication device, the second wireless communication device, or a bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB)), etc.

[0092] In some embodiments, the link state information may identify or include the spectrum efficiency of the second path for the Uu link or the inter-UE link. The spectrum efficiency may identify, for example, RSRP or rank indicator (RI), precoding matrix indicator (PMI) and channel quality indicator (CQI) values, etc. In some embodiments, the link state information may identify or include the available buffer size. The buffer size may be for the first wireless communication device, the second wireless communication device, or a bearer (e.g., DRB or SRB), etc.

[0093] The second wireless communication device may determine or identify link state information for the second path. With the identification, the second wireless communication device may send the link state information to the first wireless communication device (e.g., in a link state message). The first wireless communication device may obtain, identify, or otherwise receive link state information from the second wireless communication device (930). The link state information received from the second wireless communication device may be for the second path between the first wireless communication device and the wireless communication node via the second wireless communication device.

[0094] The first wireless communication device may provide, send, or otherwise issue channel condition information to the wireless communication node (935). In some embodiments, the first wireless communication device may identify channel condition information for the first path and the second path (e.g., both the direct path and the indirect path). In some embodiments, the first wireless communication device may identify channel condition information for the first path (e.g., the direct path or the main path). The channel condition information may identify or include channel state information or link state information (e.g., as described above) for a given path, etc. The channel state information may include, for example, an estimated data rate, spectral efficiency, PC5 RSRP, or PC5 CSI, etc. With this identification, the first wireless communication device may issue channel condition information (e.g., channel state or link state information) to the wireless communication node. The wireless communication node may obtain, identify, or otherwise receive channel condition information from the first wireless communication device (940).

[0095] The second wireless communication device may provide, send, or otherwise issue channel condition information to the wireless communication node (945). The channel condition information issued by the second wireless communication device may be different from the channel condition information issued by the wireless communication node. In some embodiments, when the channel condition information issued by the first wireless communication node is for the first path and lacks any information about the second path, the second wireless communication device may identify the channel condition information of the second path. The channel condition information may identify or include channel state information or link state information (e.g., as described above) of the second path (e.g., an indirect or auxiliary path), etc. The channel state information may include, for example, an estimated data rate, spectral efficiency, PC5 RSRP, or PC5 CSI, etc. The wireless communication node may obtain, identify, or otherwise receive the channel condition information (950) from the second wireless communication device.

[0096] The wireless communication node may exchange information between network elements (955). In some embodiments, the wireless communication node may include a first network element and one or more second network elements. The first network element and the second network element may conform to a split architecture (e.g., as in system 500A or 500B). For example, the first network element may be a central unit (CU) of a gNB corresponding to the wireless communication node, and the second network element may be its distributed unit (DU) (e.g., DU1 or DU2). The second network element may acquire, identify, or otherwise receive information (from the first wireless communication device or the second wireless communication device or both). The information may correspond to or include channel condition information or link state information for the first path, the second path, or both. Upon receipt, the second network may forward, relay, or otherwise issue the channel condition information to the first network element.

[0097] The first network element may in turn obtain, identify, or otherwise receive the information (e.g., channel condition information or link state information) from one or more second network elements. In some embodiments, the first network element may receive information about the first path, the second path, or both from one second network element. In some embodiments, the first network element may receive information about the first wireless communication device (or the first path) from one second network element (e.g., DU1) and information about the second wireless communication device (or the second path) from another second network element (e.g., DU2). Upon receipt, the first network element may use the information to determine or generate information to provide to the first wireless communication node when communicating over the first path and the second path.

[0098] The wireless communication node may identify or determine data splitting via a first path or a second path of a first wireless communication device (960). Based on the received information, the wireless communication node may determine path information for splitting data transmission via the first path and the second path. The information used to determine the path information may identify or include channel condition information, such as link state information and channel state information of the first path, the second path, or both. In some embodiments, the first network element (e.g., CU) may determine the path information using information received via one or more second network elements (e.g., DU1 or DU2).

[0099] The path information may identify or include a data split ratio, a data split threshold, or a target data rate, etc., for the first path or the second path or both. The data split ratio may define a ratio of data packets to be sent by the first wireless communication device on the first path and the second path. The data split threshold may define a value of a rate or amount of data packets to be sent by the first wireless communication device, at which rate or amount, at least a portion of the data packets will be sent on the first path or the second path or both. The target data rate may identify a rate at which data packets are to be sent on the first path, the second path, or both. In some embodiments, the path information may identify or include QoS information (e.g., as described above).

[0100] The wireless communication node may provide, send, or otherwise issue information about data splitting to the first wireless communication device (965). In some embodiments, the wireless communication node may issue path information to the first wireless communication device. In some embodiments, a first network element (e.g., CU) of the wireless communication node may issue path information to the first wireless communication device. In some embodiments, the first network element may issue path information to the first wireless communication device via a second network element (e.g., DU). In some embodiments, the wireless communication node may configure the first wireless communication device for communication via the first path and the second path. The first wireless communication device may then obtain, identify, or otherwise receive information about data splitting from the wireless communication node (970). In some embodiments, the first wireless communication device may receive path information from the first network element or the second network element of the wireless communication node.

[0101] The first wireless communication device may identify or determine data splitting via the first path and the second path (975). The first wireless communication device may determine the data splitting on the first path and the second path separately and independently of the wireless communication node's determination of the data splitting. For example, the first wireless communication device may determine the data splitting using QoS information and link state information received from the wireless communication node or the second wireless communication device. The wireless communication node may have experienced receiving channel condition information and uses the channel condition information received from the first wireless communication device or the second wireless communication device to determine the path information. Using the received information, the first wireless communication device may determine a data splitting ratio, a data splitting threshold, or a target data rate, etc. for the first path or the second path or both. The first wireless communication device's determination of the data splitting ratio, the data splitting threshold, and the target data rate may be similar to the wireless communication device's determination of the path information as described above.

[0102] The first wireless communication device may transmit, send, or otherwise communicate with the second wireless communication device or wireless communication node (980, 980', and 980") via the first path and the second path. Based on the determination of the data splitting, the first wireless communication device may send the data packet via the first path or the second path (or both). In some embodiments, the first wireless communication device may transmit the data packet via the first path or the second path or both based on the path information received from the wireless communication node. In some embodiments, the first wireless communication device may transmit the data packet via the first path or the second path or both as determined by the first wireless communication device.

[0103] Although various embodiments of the present solution have been described above, it should be understood that they are presented only by way of example rather than by way of limitation. Similarly, various figures may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the example features and functions of the present solution. However, these people will understand that the present solution is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. In addition, as will be understood by those of ordinary skill in the art, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-mentioned illustrative embodiments.

[0104] It should also be understood that any reference to an element using names such as "first," "second," etc., herein generally does not limit the number or order of these elements. Instead, these names can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Therefore, reference to a first element and a second element does not mean that only two elements can be used, or that the first element must precede the second element in some way.

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

[0106] Those of ordinary skill in the art will further understand that any of the various illustrative logic blocks, modules, processors, components, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design codes in conjunction with instructions (which, for convenience, may be referred to herein as "software" or "software modules"), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functions. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies depends on the specific application and the design constraints imposed on the entire system. A skilled technician may implement the described functionality in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of the present disclosure.

[0107] In addition, it will be understood by those of ordinary skill in the art that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented or performed 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 also include antennas and / or transceivers to communicate with various components within a network or within a device. A general-purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other suitable configuration for performing the functions described herein.

[0108] If implemented in software, these functions can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that can transfer a computer program or code from one place to another. The storage medium can be any available medium that a computer can access. As an example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer.

[0109] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. In addition, for the purpose of discussion, various modules are described as discrete modules; however, as is clear to one of ordinary skill in the art, two or more modules can be combined to form a single module that performs the associated functions according to an embodiment of the present solution.

[0110] In addition, memory or other storage devices and communication components can be used in the embodiment of the present solution. It should be understood that, for the sake of clarity, the above description has described the embodiment of the present solution with reference to different functional units and processors. However, it is clear that any suitable functional distribution between different functional units, processing logic elements or domains can be used without departing from the present solution. For example, the functions performed by a separate processing logic element or controller can be performed by the same processing logic element or controller. Therefore, reference to a specific functional unit is only a reference to an appropriate manner for providing the described function, rather than representing a strict logical or physical structure or organization.

[0111] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may 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 should be consistent with the broadest scope consistent with the novel features and principles disclosed herein, as described in the following claims.

Claims

1. A method for splitting data for multipath transmission, comprising: receiving, by the first wireless communication device, quality of service (QoS) information for a first path from a wireless communication node; as well as The first wireless communication device determines to split data transmission via the first path or the second path.

2. The method according to claim 1, further comprising: QoS information for the second path is received by the first wireless communication device from the second wireless communication device.

3. The method of claim 1 , wherein receiving the QoS information further comprises: The QoS information for a second path is received from the wireless communication node.

4. The method of claim 1, 2 or 3, wherein the QoS information further comprises at least one of: an aggregate maximum bit rate (AMBR), a guaranteed flow bit rate (GFBR), or a maximum flow bit rate (MFBR) for communications on the first path or the second path.

5. The method of claim 4, wherein the AMBR further comprises at least one of: an AMBR for a UL protocol data unit (PDU) session or a UL AMBR for the first wireless communication device for communication on the first path or the second path.

6. The method of claim 1, 2 or 3, wherein the QoS information further comprises an aggregate maximum bit rate (AMBR) for at least one of the first wireless communication device, the second wireless communication device, or a bearer.

7. The method of claim 1, 2 or 3, wherein the first path is between the first wireless communication device and the wireless communication node, and wherein the second path is between the first wireless communication device and the wireless communication node via a second wireless communication device.

8. A method for splitting data for multipath transmission, comprising: receiving, by the first wireless communication device, link state information for a first path from the second wireless communication device; as well as The first wireless communication device determines to split data transmission via the first path or the second path.

9. The method according to claim 8, further comprising: The link state information for the first path is sent by the first wireless communication device to a wireless communication node.

10. The method according to claim 9 or 10, wherein the link state information further comprises: The data rate on the first path used for the Uu link or the inter-UE link.

11. The method of claim 10, wherein the data rate is for at least one of the first wireless communication device, the second wireless communication device, or a bearer.

12. The method according to claim 8 or 9, wherein the link state information further comprises: The spectral efficiency of the first path for the Uu link or the inter-UE link.

13. The method according to claim 8 or 9, wherein the link state information further comprises: An available buffer size of the second wireless communication device.

14. The method of claim 8, wherein the first path is between the first wireless communication device and a wireless communication node via the second communication device, and the second path is between the first wireless communication device and the wireless communication node.

15. A method for splitting data for multipath transmission, comprising: A first wireless communication device sends channel condition information about a first path to a wireless communication node, wherein the first path is between the first wireless communication device and the wireless communication node.

16. The method of claim 15, wherein the wireless communication node receives second channel condition information for a second path from the second wireless communication device, the second path being between the first wireless communication device and the wireless communication node via the second wireless communication device.

17. The method according to claim 15 or 16, wherein the first wireless communication device receives path information from the wireless communication node, and the path information is used to split data transmission via the first path or the second path.

18. The method according to claim 15 or 16, wherein the channel condition information for the first path or the second path further comprises: At least one of channel state information or link state information.

19. The method according to claim 15 or 16, wherein the channel condition information for the first path or the second path further comprises: Link state information for at least one of the first wireless communication device or the second wireless communication device.

20. The method of claim 18, wherein the path information further comprises at least one of: a data splitting ratio, a data splitting threshold, or a target data rate for the first path or the second path.

21. The method of claim 17, wherein the first path is between the first wireless communication device and the wireless communication node.

22. A method for processing data splitting for multipath transmission, comprising: Channel condition information about a first path or a second path is received by a first network element of the wireless communication node from a second network element.

23. The method according to claim 22, further comprising: Path information is determined by the wireless communication node, and the path information is used to split transmission via the first path or the second path.

24. The method of claim 22, wherein the first network element is a central unit (CU) and the second network element is a distributed unit (DU).

25. The method of claim 22, wherein the channel condition information further comprises at least one of channel state information or link state information.

26. The method of claim 22, further comprising: Link state information for at least one of the first wireless communication device or the second wireless communication device is received by the first network element from at least one of the second network element or a third network element.

27. A method according to claim 25 or 26, wherein the link status information also includes at least one of the following: the data rate on the first path for the Uu link or the UE-to-UE link; the spectrum efficiency of the first path for the Uu link or the UE-to-UE link; or the available cache size of the second wireless communication device.

28. The method of claim 27, wherein the data rate is for at least one of the first wireless communication device, the second wireless communication device, or a bearer.

29. The method of claim 22, further comprising: Path information is sent by the first network element to the first wireless communication device, the path information identifying quality of service (QoS) information for the first path.

30. The method of claim 29, wherein the QoS information further comprises at least one of: an aggregate maximum bit rate (AMBR), a guaranteed flow bit rate (GFBR), or a maximum flow bit rate (MFBR) for communications on the first path or the second path.

31. The method of claim 30, wherein the AMBR further comprises at least one of: an AMBR for a UL protocol data unit (PDU) session or a UL AMBR for the first wireless communication device for communications on the first path or the second path.

32. The method of claim 30, wherein the QoS information further comprises: An aggregate maximum bit rate (AMBR) for at least one of the first wireless communication device, the second wireless communication device, or a bearer.

33. A system for data splitting of multipath transmission, comprising one or more processors coupled to a memory, the one or more processors being configured to perform the method according to any one of the preceding claims.

Images