Uplink data partitioning by delayed state triggering

Abstract

Aspects of the present disclosure relate to UL data partitioning triggered by a delayed state. In one aspect, a UE receives at least one UL partition threshold from one of a first base station and a second base station, the at least one UL partition threshold associated with a delay state for a UL partition bearer. Based on the at least one UL partition threshold, the UE performs UL data transmission of the UL partition bearer using both a primary path associated with a primary RLC entity of the UE and a secondary path associated with a partition secondary RLC entity of the UE.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically, to user equipment (UE), base stations, and methods for supporting uplink (UL) data segmentation triggered by a delayed state. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which may also be referred to in other ways as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices (which may also be referred to in other ways as UE, or other suitable terms). The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may also support wireless communication across multiple radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth-generation (6G)).

[0003] Currently, in Dual Connectivity (DC), for split bearers, the Packet Data Convergence Protocol (PDCP) entity of the User Equipment (UE) is associated with two Radio Link Control (RLC) entities: a primary RLC entity and a split secondary RLC entity. A split bearer can be defined as: in Dual Connectivity, a bearer using resources from both the MgNB and SgNB, with its radio protocol residing in both the primary gNB (MgNB) and the secondary gNB (SgNB). A split secondary RLC entity can be defined as: in Dual Connectivity, the RLC entity responsible for split bearer operations, in addition to the primary RLC entity. If the PDCP entity is associated with two RLC entities, the split secondary RLC entity is the RLC entity other than the primary RLC entity. If the PDCP entity is associated with more than two RLC entities, the split secondary RLC entity is configured by the higher-level entity. Summary of the Invention

[0004] This disclosure relates to a UE and method that support UL data segmentation triggered by delay state. Using this UE and method, delay state information is considered for PDCP routing, for example, for selecting only the primary path, or both the primary and secondary paths, for segmented UL data transmission.

[0005] Some implementations of the UE described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: receive at least one UL segmentation threshold from one of a first base station and a second base station via the transceiver, the at least one UL segmentation threshold being associated with a delay state for a UL segmented bearer; and, based on the at least one UL segmentation threshold, perform UL data transmission of the UL segmented bearer using both a primary path associated with the UE's primary RLC entity and a secondary path associated with the UE's segmented secondary RLC entity.

[0006] In some implementations, at least one UL segmentation threshold includes a first UL segmentation threshold for the remaining time associated with the delay state; and the processor is configured to perform UL data transmission using both the primary path and the secondary path for UL segmentation by determining that the minimum remaining time of the UL data is less than or equal to the first UL segmentation threshold for the remaining time.

[0007] In some implementations, at least one UL segmentation threshold includes a second UL segmentation threshold for the amount of data associated with a delay state; and the processor is configured to perform UL data transmission using both the primary path and the secondary path by determining that the amount of data associated with a delay state is greater than or equal to the second UL segmentation threshold for the amount of data.

[0008] In some implementations, at least one UL segmentation threshold includes a first UL segmentation threshold for the remaining time associated with a delay state and a second UL segmentation threshold for the amount of data associated with the delay state; and the processor is configured to perform UL segmented data transmission using both the primary path and the secondary path by determining that the minimum remaining time of the UL data is less than or equal to the first UL segmentation threshold for the remaining time and the amount of data associated with the delay state is greater than or equal to the second UL segmentation threshold for the amount of data.

[0009] In some implementations, the amount of data associated with the delay state includes one of the following: a first amount of data for a first set of packets associated with the primary path, wherein the remaining time of the first set of packets is less than or equal to a threshold for triggering a DSR report; a second amount of data for a second set of packets associated with the secondary path, wherein the remaining time of the second set of packets is less than or equal to a threshold for triggering a DSR report; or the sum of the first amount of data and the second amount of data.

[0010] In some implementations, at least one UL segmentation threshold includes a third UL segmentation threshold; and the processor is configured to perform UL segmented bearer UL data transmission using both the primary path and the secondary path by determining that the total amount of a first data volume to be transmitted in the UE's PDCP entity and the total amount of a second data volume to be initially transmitted in the UE's primary RLC entity and the segmented secondary RLC entity are equal to or greater than the third UL segmentation threshold.

[0011] In some implementations, the processor is also configured to transmit a first DSR of a UL segmented bearer and a second DSR of a UL segmented bearer to a first base station and a second base station via the transceiver through a primary path and a secondary path, respectively, wherein the first DSR is associated with the primary path and the second DSR is associated with the secondary path.

[0012] In some implementations, the processor is also configured to: trigger the reporting of a first DSR based on the determination that the minimum remaining time of the UL data associated with the primary path is less than or equal to a first threshold for triggering the reporting of a first DSR; and the UL data associated with the primary path includes at least one of the following: a PDCP SDU or PDCP PDU that will be routed to the primary RLC entity or to both the primary RLC entity and the split secondary RLC entity; and an RLC SDU or RLC PDU that will be sent in the primary RLC entity.

[0013] In some implementations, the UL data associated with the primary path includes a first set of data packets associated with the primary path, the first DSR includes the amount of data in the first set of data packets, and the remaining time of the first set of data packets is less than or equal to a first threshold used to trigger the reporting of the first DSR.

[0014] In some implementations, the processor is also configured to: trigger the reporting of a second DSR based on the determination that the minimum remaining time of the UL data associated with the secondary path is less than or equal to a second threshold for triggering the reporting of a second DSR; and the UL data associated with the secondary path includes at least one of the following: a PDCP SDU or PDCP PDU that will be routed to a split secondary RLC entity or to both the primary RLC entity and the split secondary RLC entity; and an RLC SDU or RLC PDU that will be sent in the split RLC entity.

[0015] In some implementations, the UL data associated with the secondary path includes a second set of data packets associated with the secondary path, the second DSR includes the amount of data in the second set of data packets, and the remaining time of the second set of data packets is less than or equal to a second threshold used to trigger the reporting of the second DSR.

[0016] In some implementations, the processor is also configured to transmit the DSR of the UL segmented bearer to the first base station and the second base station via the transceiver through the main path and the secondary path, respectively, wherein the DSR is associated with both the main path and the secondary path.

[0017] In some implementations, the processor is also configured to: trigger DSR reporting based on the determination that the minimum remaining time of the UL data associated with both the primary path and the secondary path is less than or equal to a threshold used to trigger DSR reporting; and the UL data associated with both the primary path and the secondary path includes at least one of the following: a PDCP SDU or PDCPPDU to be sent; and an RLC SDU or RLC PDU to be sent in the primary RLC entity and the segmented secondary RLC entity.

[0018] In some implementations, the UL data associated with both the primary and secondary paths includes a third set of data packets associated with both the primary and secondary paths. The DSR includes the amount of data in the third set of data packets, and the remaining time of the third set of data packets is less than or equal to the threshold used to trigger the reporting of the DSR.

[0019] In some implementations, the third data packet set includes a first packet subset in the primary RLC entity, a second packet subset in the segmented secondary RLC entity, and a third packet subset in the UE's PDCP entity.

[0020] In some implementations, the processor is also configured to: provide a first data volume of a first packet subset from the primary RLC entity to a second media access control (MAC) entity of the UE associated with the segmented secondary RLC entity; provide a second data volume of a second packet subset from the segmented secondary RLC entity to a first MAC entity of the UE associated with the primary RLC entity; and provide a third data volume of a third packet subset from the PDCP entity to the first MAC entity and the second MAC entity, respectively.

[0021] In some implementations, the processor is also configured to: provide a first data volume of a first packet subset from the MAC entity of the UE associated with the primary RLC entity to a second media access control (MAC) entity of the UE associated with the secondary RLC entity; provide a second data volume of a second packet subset from the second MAC entity to a first MAC entity; and provide a third data volume of a third packet subset from the PDCP entity to the first MAC entity and the second MAC entity, respectively.

[0022] In some implementations, the processor is also configured to: receive an indication from one of the first and second base stations via the transceiver, the indication indicating that the secondary path is used for at least one set of PDUs having at least one value of Protocol Data Unit (PDU) Set Importance (PSI); and the processor is configured to perform UL segmented bearer UL data transmission using both the primary path and the secondary path by: using the secondary path based on the indication for UL data transmission of at least one set of PDUs having at least one value of PSI.

[0023] In some implementations, the processor is also configured to transmit a first DSR of a UL segmented bearer and a second DSR of a UL segmented bearer to a first base station and a second base station via the transceiver through a primary path and a secondary path, respectively, wherein the first DSR is associated with the primary path and the second DSR is associated with the secondary path.

[0024] In some implementations, the processor is also configured to: trigger the reporting of a second DSR based on the determination that the minimum remaining time of the UL data associated with the secondary path is less than or equal to a second threshold for triggering the reporting of a second DSR; and the UL data associated with the secondary path includes at least one set of PDUs.

[0025] In some implementations, the processor is also configured to: receive from the base station via a transceiver at least one threshold for triggering PDCP replication; replicate the PDCP PDU based on the at least one threshold; and use the primary path associated with the UE's primary RLC entity for UL transmission of the PDCP PDU, and use the secondary path associated with the UE's segmented secondary RLC entity for UL transmission of the replicated PDCP PDU.

[0026] In some implementations, at least one threshold includes a third threshold for the remaining time associated with the delay state; and the processor is configured to use the main path for UL transmission of the PDCP PDU and the secondary path for UL transmission of the replicated PDCP PDU by: using the main path for UL transmission of the PDCP PDU and the secondary path for UL transmission of the replicated PDCP PDU based on determining that the minimum remaining time of the UL data is less than or equal to the third threshold for the remaining time.

[0027] In some implementations, at least one threshold includes a fourth threshold for the amount of data associated with the delay state; and the processor is configured to use a primary path for UL transmission of the PDCP PDU and a secondary path for UL transmission of the replicated PDCP PDU by determining that the amount of data associated with the delay state is greater than or equal to the fourth threshold for the amount of data.

[0028] In some implementations, at least one threshold includes a third threshold for the remaining time associated with the delay state and a fourth threshold for the amount of data associated with the delay state; and the processor is configured to use a primary path for UL transmission of the PDCP PDU and a secondary path for UL transmission of the replicated PDCP PDU by determining that the remaining time of the UL data is less than or equal to the third threshold for the remaining time and the amount of data associated with the delay state is greater than or equal to the fourth threshold for the amount of data.

[0029] Some implementations of the methods described herein may include: receiving at the UE at one of a first base station and a second base station at the UE, the at least one UL segmentation threshold being associated with a delay state for a UL segmented bearer; and, based on the at least one UL segmentation threshold, performing UL data transmission of the UL segmented bearer using both a primary path associated with the UE's primary RLC entity and a secondary path associated with the UE's segmented secondary RLC entity.

[0030] Some implementations of the processor described herein may include at least one memory and a controller coupled to at least one memory, and are configured such that the controller: receives at least one UL segmentation threshold from one of a first base station and a second base station, the at least one UL segmentation threshold being associated with a delay state for a UL segmented bearer; and performs UL data transmission of the UL segmented bearer using both a primary path associated with the UE's primary RLC entity and a secondary path associated with the UE's segmented secondary RLC entity based on the at least one UL segmentation threshold.

[0031] It should be understood that the summary portion of this disclosure is not intended to identify key or essential features of the embodiments thereof, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0032] Figure 1A and 1BExamples of wireless communication systems supporting UL data segmentation triggered by a delayed state, according to various aspects of this disclosure, are illustrated respectively;

[0033] Figure 1C An example of UL data segmentation triggered by a delayed state according to various aspects of this disclosure is illustrated;

[0034] Figures 2 to 5 Signaling diagrams are illustrated, which illustrate example processes of UL data segmentation triggered by a delayed state in accordance with various aspects of this disclosure;

[0035] Figure 6 A signaling diagram is shown, illustrating an example process of PDCP replication triggered by a delayed state, in accordance with various aspects of this disclosure.

[0036] Figure 7 The illustration shows an example of a device that supports UL data segmentation and / or PDCP replication triggered by a delayed state, according to some aspects of this disclosure;

[0037] Figure 8 The illustration shows an example of a processor that supports UL data segmentation and / or PDCP replication triggered by a delayed state, according to various aspects of this disclosure; and

[0038] Figure 9 The diagram illustrates a flowchart of a method for UL data segmentation triggered by a delayed state, in accordance with various aspects of this disclosure. Detailed Implementation

[0039] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. This disclosure described herein can be implemented in various ways other than those described below.

[0040] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0041] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the embodiments described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiments. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is considered that in conjunction with other embodiments (whether explicitly described or not) affecting such feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0042] It should be understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the embodiments, a first element may also be referred to as a second element, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0043] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary implementations. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that, when used herein, the terms “comprising,” “including,” “having,” “having,” “containing,” and / or “comprising” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0044] As mentioned above, in dual connectivity, for split bearers, the UE's PDCP entity is associated with the primary RLC entity and the split secondary RLC entity.

[0045] In the traditional approach, a threshold is configured for split-bearer UL data transmission and BSR reporting. If the total amount of data in the PDCP and RLC entities is equal to or greater than this threshold, the UE should use both the primary and secondary paths for split-bearer UL data transmission. Otherwise, only the primary path is used for split-bearer UL data transmission.

[0046] Specifically, for UL data transmission with segmented bearers, if the total amount of PDCP data and RLC data to be initially transmitted in the main RLC entity and the segmented auxiliary RLC entity is equal to or greater than... ul-DataSplitThreshold If the UE's PDCP entity is in a good position, it should submit a PDCP PDU to the primary RLC entity or the segmented secondary RLC entity. Otherwise, the UE should submit a PDCPPDU to the primary RLC entity.

[0047] For a segmented bearer BSR report, if the total amount of PDCP data to be initially transmitted and RLC data in the primary RLC entity and the segmented secondary RLC entity is equal to or greater than 100%, then the BSR report is valid. ul-DataSplitThreshold If the PDCP data volume is specified, the UE indicates the PDCP data volume to both the Media Access Control (MAC) entity associated with the primary RLC entity and the MAC entity associated with the segmented secondary RLC entity. Otherwise, the UE indicates the PDCP data volume to the MAC entity associated with the primary RLC entity.

[0048] The DSR reporting procedure can be used to provide the base station with the delay status of UL data. This delay status can include the remaining time (RT) of the UL data, which is based on the value of the timer associated with the DSR at the time of the first symbol transmitted on the Physical Uplink Control Channel (PUSCH). The DSR reporting procedure can also be used to provide the base station with the amount of UL data associated with the reported remaining time. DSR reporting can improve UL scheduling.

[0049] An agreement has been reached that a new, separate MAC control unit (CE) can be defined for DSR reporting. For example, DSR reporting is not coupled with BSR reporting.

[0050] For NR-DC UL split bearers, the UE initially transmits UL data via the primary path. In some cases, such as when UL congestion occurs on the primary path, the UE needs to begin transmitting UL data via the secondary path when the remaining time for UL data is about to run out. In other words, the UE needs to consider delay state information used for PDCP routing, such as for selecting UL data transmission for split bearers using only the primary path, or both the primary and secondary paths.

[0051] In summary, this disclosure provides a solution for supporting UL data segmentation triggered by delay state. In this solution, the UE receives from the base station at least one UL segmentation threshold associated with the delay state for the UL segmented bearer. Based on the at least one UL segmentation threshold, the UE performs UL data transmission for the UL segmented bearer using both the primary path associated with the UE's primary RLC entity and the secondary path associated with the UE's segmented secondary RLC entity. Using this solution, the UE considers delay state information for PDCP routing, for example, for selecting only the primary path, or both the primary and secondary paths, for performing UL data transmission for the segmented bearer.

[0052] The aspects of this disclosure will be described in the context of wireless communication systems.

[0053] Figure 1AAn example of a wireless communication system 100A supporting UL data segmentation triggered by a delayed state, according to various aspects of this disclosure, is illustrated. The wireless communication system 100A may include at least one of the following: network entity 102 (also referred to as a network device (NE)), one or more terminal devices or UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100A may support various radio access technologies. In some implementations, the wireless communication system 100A may be a 4G network, such as an LTE network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100A may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100A may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100A may support radio access technologies beyond 5G. In addition, the wireless communication system 100A can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0054] Network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100A. One or more network entities in network entities 102 described herein may be, include, or may be referred to as network nodes, base stations (BS), network elements, radio access network (RAN) nodes, base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. In the following description, some implementations of this disclosure will be described by using base stations as examples of network entities 102. Therefore, network entity 102 may be used interchangeably with base station 102. For example, base station 102 may include a first base station 102-1 and a second base station 102-2.

[0055] Network entity 102 and UE 104 can communicate via communication link 110, which can be a wireless connection or a wired connection. For example, network entity 102 and UE 104 can perform wireless communication (e.g., receive signaling, send signaling) through the Uu interface.

[0056] Network entity 102 may provide a geographic coverage area 112 for which it may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0057] One or more UEs 104 may be distributed within a geographical area of ​​the wireless communication system 100A. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples. In some implementations, UE 104 may be stationary within the wireless communication system 100A. In other implementations, UE 104 may be mobile within the wireless communication system 100A.

[0058] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1A The diagram is shown in the image. Figure 1A As shown, UE 104 is capable of communicating with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device). Alternatively or additionally, UE 104 may support communication with other network entities 102 or UE 104, which may act as relays in the wireless communication system 100A.

[0059] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a sidelink. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0060] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with other core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0061] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) system, or any combination thereof.

[0062] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of network entity 102 in a decomposed RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0063] The functional splitting among CU, DU, and RU can be flexible and can depend on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are executed at the CU, DU, or RU to support different functions. For example, protocol stack functional splitting can be adopted between CU and DU so that CU can support one or more layers of the protocol stack, and DU can support one or more different layers of the protocol stack. In some implementations, CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU can be connected to one or more DU or RU, and one or more DU or RU can host lower-layer protocol layer, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer) functions and signaling, and each can be at least partially controlled by CU 160.

[0064] Alternatively or concurrently, functional splitting of the protocol stack can be employed between the DU and RU, such that the DU can support one or more layers of the protocol stack, and the RU can support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, functional splitting between the CU and DU, or between the DU and RU, can be performed within the protocol layer (e.g., some functions for the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by a different one of the CU, DU, or RU).

[0065] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by corresponding network entities 102 communicating via such communication links.

[0066] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route packets or interconnections to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0067] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session with core network 106 (e.g., Protocol Data Unit (PDU) session, etc.) via network entity 102. Core network 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0068] In the wireless communication system 100A, network entity 102 and UE 104 can use the resources of the wireless communication system 100A (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on parameter sets.

[0069] One or more parameter sets can be supported in the wireless communication system 100A, and the parameter sets may include subcarrier spacing and cyclic prefix. The first parameter set (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15kHz) and the normal cyclic prefix. In some implementations, the first parameter set (e.g., ) associated with the first subcarrier spacing (e.g., 15kHz) is... μ =0) can utilize one time slot per subframe. The second parameter set (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30kHz) and the normal cyclic prefix. The third parameter set (e.g., μ =2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. The fourth parameter set (e.g., μ =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth parameter set (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0070] The time intervals of resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0071] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100A. For example, a first parameter set, a second parameter set, a third parameter set, a fourth parameter set, and a fifth parameter set (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots used for a subframe can depend on the parameter set. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the parameter set. It should be understood that for a first parameter set (e.g., quantity) associated with a first subcarrier spacing (e.g., 15kHz), μ The reference of (=0) can be used interchangeably between subframes and time slots.

[0072] In the wireless communication system 100A, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100A can support one or more operating frequency bands, such as frequency range names FR1 (510MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication through one or more operating frequency bands. In some implementations, FR1 can be used by other devices or apparatuses such as network entity 102 and UE 104 for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by other devices or apparatuses such as network entity 102 and UE 104 for short-range, high data rate capabilities.

[0073] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with the following: the first parameter set (e.g., μ =0), which includes a 15kHz subcarrier spacing; the second parameter set (e.g., μ =1), which includes a 30kHz subcarrier spacing; and a third parameter set (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with the following: a third parameter set (e.g., μ =2), which includes a 60kHz subcarrier spacing; and a fourth parameter set (e.g., μ =3), which includes a subcarrier spacing of 120kHz.

[0074] Figure 1B An example of a wireless communication system 100B supporting UL data segmentation triggered by a delay state, according to various aspects of this disclosure, is illustrated. In the wireless communication system 100B, UE 104 can initially transmit UL data via a primary path between UE 104 and a first base station 102-1. For example, when UL congestion occurs in the primary path, UL data segmentation is triggered based on at least one UL segmentation threshold associated with a delay state for the UL segmented bearer. This type of UL data segmentation is referred to as UL data segmentation triggered by a delay state or UL data segmentation triggered by a delay state. In other words, based on at least one UL segmentation threshold, UE 104 performs UL data transmission for the UL segmented bearer using both the primary path and the secondary path between UE 104 and the second base station 102-2. Hereinafter, for simplicity, UL data segmentation is also referred to as UL segmentation.

[0075] In some implementations, the first base station 102-1 can act as a MgNB, and the second base station 102-2 can act as a SgNB. Alternatively, the first base station 102-1 can act as an SgNB, and the second base station 102-2 can act as a MgNB.

[0076] Figure 1C An example of UL data segmentation triggered by a delayed state according to various aspects of this disclosure is illustrated.

[0077] like Figure 1CAs shown, UE 104 may include PDCP entity 120, RLC entity 130 (also referred to as primary RLC entity 130), and MAC entity 140. MAC entity 140 is associated with primary RLC entity 130. The main path between UE 104 and the first base station 102-1 is associated with primary RLC entity 130. Initially, UE 104 may transmit UL data via the main path between UE 104 and the first base station 102-1.

[0078] For example, when UL congestion occurs in the primary path, UL segmentation will be triggered based on at least one UL segmentation threshold associated with the delay state for the UL segmented bearer. In other words, based on at least one UL segmentation threshold, UE 104 uses both the primary path and the secondary path between UE 104 and the second base station 102-2 to transmit UL data for the UL segmented bearer. The secondary path is associated with the segmented secondary RLC entity 132. MAC entity 142 is associated with the segmented secondary RLC entity 132.

[0079] Figure 2 A signaling diagram is illustrated, which illustrates an example process 200 for UL data segmentation triggered by a delayed state, supported by various aspects of this disclosure. Process 200 may involve... Figure 1A Alternatively, UE 104 in 1B and either the first base station 102-1 or the second base station 102-2. For discussion purposes, process 200 will refer to... Figure 1A , 1B Or it can be described as 1C.

[0080] like Figure 2 As shown, UE 104 receives the configuration of the 210 Data Radio Bearer (DRB) from either the first base station 102-1 or the second base station 102-2. This DRB configuration can indicate that the DRB is configured as a UL-segmented DRB in NR-DC.

[0081] In some implementations, the first base station 102-1 can act as a MgNB, and the second base station 102-2 can act as a SgNB. Alternatively, the first base station 102-1 can act as an SgNB, and the second base station 102-2 can act as a MgNB.

[0082] In some implementations, the first base station 102-1 or the second base station 102-2 may indicate the primary and secondary paths of the UL-segmented DRB. Information about the primary path may include information indicating the cell group ID and LCID of the primary RLC entity 130. Information about the secondary path may include the LCID indicating the segmented secondary RLC entity 132, and that this RLC entity belongs to a different cell group than the one used for the primary path.

[0083] In some implementations, a segmented bearer can be defined as follows: In dual connectivity, a bearer using resources from both the MgNB and SgNB is used, with its radio protocol residing in both the MgNB (or primary cell group (MCG)) and the SgNB (or secondary cell group (SCG)). For a segmented bearer, UE 104's PDCP entity 120 is associated with two RLC entities, namely, the primary RLC entity 130 and the segmented secondary RLC entity 132.

[0084] UE 104 receives 220 UL segmentation thresholds associated with the delay state for UL segmentation bearers from either the first base station 102-1 or the second base station 102-2.

[0085] Subsequently, UE 104 triggers UL segmentation 230 based on at least one UL segmentation threshold. In other words, based on at least one UL segmentation threshold, UE 104 performs UL segmentation-bearing UL data transmission using both the primary path associated with the primary RLC entity 130 and the secondary path associated with the segmentation secondary RLC entity 132.

[0086] Using process 200, UE 104 considers delay state information for PDCP routing, such as for selecting UL data transmission with split-bearing only the primary path or both the primary and secondary paths.

[0087] In some implementations, at least one UL segmentation threshold associated with the delay state may include a first UL segmentation threshold for the remaining time associated with the delay state.

[0088] In some implementations, the first UL segmentation threshold for the remaining time can be an enumerated value, such as 3ms.

[0089] In some implementations, the first UL segmentation threshold used for the remaining time may be the same as or different from the threshold used to trigger the DSR reporting.

[0090] In some implementations, if the minimum remaining time of the UL data is less than or equal to a first UL segmentation threshold for the remaining time, UE 104 uses both the primary path and the secondary path for UL segmentation bearer UL data transmission. Otherwise, UE 104 uses only the primary path for UL data transmission of the segmented bearer. For example, if the minimum remaining time of the UL data is less than or equal to the first UL segmentation threshold for the remaining time, PDCP entity 120 submits a PDCP PDU to either primary RLC entity 130 or segmentation secondary RLC entity 132. Otherwise, PDCP entity 120 submits a PDCP PDU to primary RLC entity 130.

[0091] In some implementations, UL data may include at least one of the following: • PDCP SDU, for which the PDCP PDU has not yet been built. • Lower-level PDCP PDUs that have not yet been submitted to the PDCP entity, or • The RLC SDU or RLC PDU to be sent.

[0092] In some implementations, the RLC SDU or RLC PDU to be sent may include at least one of the following: • RLC SDUs and RLC SDU segments that are not yet included in the RLC PDU, where an RLC SDU segment may be a fragment of an RLCSDU. • RLC PDU to be initially transmitted, or • RLC PDU to be retransmitted (RLC Acknowledgment Mode (AM)).

[0093] In some implementations, the remaining time for a packet is the value of the PDCP drop timer (configured by RRC) minus the PDCP drop timer's runtime. The PDCP drop timer is started after receiving a PDCPSDU associated with the packet from a higher layer of UE 104. Typically, the PDCP drop timer value is set based on either the packet delay budget (PDB) or the PDU set delay budget (PSDB). When the PDCP drop timer expires, UE 104 should discard the PDCP SDU.

[0094] Consider an example. In this example, the PDCP discard timer value is equal to 50ms. The first UL segmentation threshold for the remaining time is equal to 15ms.

[0095] In this example, the UL data includes group #1 (RT=12ms), group #2 (RT=13ms), group #3 (RT=20ms), and group #4 (RT=18ms). Since the remaining time for group #1 is the smallest among the remaining times for groups #1, #2, #3, and #4, the minimum remaining time of the UL data is equal to the remaining time for group #1. Because the minimum remaining time of the UL data is less than the first UL segmentation threshold used for the remaining time, UE 104 triggers UL segmentation.

[0096] Alternatively, in some implementations, at least one UL segmentation threshold may include a second UL segmentation threshold for the amount of data associated with the delay state. If the amount of data associated with the delay state is greater than or equal to the second UL segmentation threshold for the amount of data, UE 104 may use both the primary path and the secondary path for UL segmented UL data transmission.

[0097] Alternatively, in some implementations, at least one UL segmentation threshold may include a first UL segmentation threshold for the remaining time associated with a delay state and a second UL segmentation threshold for the amount of data associated with a delay state. If the minimum remaining time of the UL data is less than or equal to the first UL segmentation threshold for the remaining time, and the amount of data associated with the delay state is greater than or equal to the second UL segmentation threshold for the amount of data, then UE 104 may use both the primary path and the secondary path for UL segmented UL data transmission.

[0098] In some implementations, the amount of data associated with the delayed state may include one of the following: • The first data volume of the first packet set associated with the main path, wherein the remaining time of the first packet set is less than or equal to the threshold used to trigger the DSR reporting. • The second data volume of the second packet set associated with the secondary path, wherein the remaining time of the second packet set is less than or equal to the threshold used to trigger the DSR reporting, or • The sum of the first and second data volumes.

[0099] In some implementations, at least one UL segmentation threshold may include a third UL segmentation threshold. The third UL segmentation threshold may indicate the threshold used for UL data segmentation operations. If the total amount of the first data to be transmitted in PDCP entity 120 and the total amount of the second data to be initially transmitted in primary RLC entity 130 and segmented secondary RLC entity 132 is equal to or greater than the third UL segmentation threshold, then UE 104 may use both the primary path and the secondary path for UL segmentation-bearing UL data transmission.

[0100] In some implementations, the third UL segmentation threshold can be determined by... ul-DataSplitThreshold To configure it. For example, ul-DataSplitThreshold It can be configured as follows: UL-DataSplitThreshold::=ENUMERATED{ b0,b100,b200,b400,b800,b1600,b3200, b6400,b12800,b25600,b51200,b102400,b204800, b409600,b819200,b1228800,b1638400, b2457600,b3276800,b4096000,b4915200,b5734400, b6553600,infinity,spare8,spare7,spare6, spare5,spare4,spare3,spare2,spare1} The value b0 corresponds to 0 bytes, b100 corresponds to 100 bytes, b200 corresponds to 200 bytes, and so on. For those not supported... splitDRB-withUL-Both-MCG-SCG For the UE, and when the SCG is deactivated, base station 102 sets this field to infinity. If this field does not exist when the segmented bearer is first configured for radio bearer, the default value of infinity is applied.

[0101] In some implementations, the primary and secondary paths have different triggers for DSR reporting. The first base station 102-1 or the second base station 102-2 is configured with two independent or separate thresholds to trigger DSR reporting. This will refer to... Figure 3 To describe.

[0102] Figure 3 A signaling diagram is illustrated, illustrating an example procedure 300 for UL data segmentation triggered by a delayed state, supporting various aspects of this disclosure. Procedure 300 can be considered as an example implementation of procedure 200. Procedure 300 may involve... Figure 1A Or UE 104, first base station 102-1, and second base station 102-2 in 1B. For discussion purposes, process 200 will refer to Figure 1A , 1B Or it can be described as 1C.

[0103] In process 300, the first base station 102-1 can act as the MgNB, and the second base station 102-2 can act as the SgNB. Alternatively, the first base station 102-1 can act as the SgNB, and the second base station 102-2 can act as the MgNB.

[0104] Actions 210, 220, and 230 in process 300 are similar to those in process 200. For the sake of brevity, the details of these actions have been omitted.

[0105] Process 300 differs from process 200 in actions 310 and 320.

[0106] Specifically, UE 104 sends the first DSR of the UL segmented bearer to the first base station 102-1 via the main path. The first DSR is associated with the main path.

[0107] In some implementations, UE 104 triggers the reporting of the first DSR if the minimum remaining time of the UL data associated with the primary path is less than or equal to a first threshold used to trigger the reporting of the first DSR.

[0108] In some implementations, the UL data associated with the main path may include at least one of the following: • The PDCP SDU or PDCP PDU that will be routed to the primary RLC entity 130 or to both the primary RLC entity 130 and the secondary RLC entity 132, or • The RLC SDU or RLCP DU that will be sent in the main RLC entity 130.

[0109] In some implementations, the PDCP SDU that will be routed to the primary RLC entity 130 or to both the primary RLC entity 130 and the split secondary RLC entity 132 may include a PDCP SDU for which a PDCP PDU has not yet been constructed.

[0110] In some implementations, a PDCP PDU that will be routed to the main RLC entity 130 or to both the main RLC entity 130 and the split auxiliary RLC entity 132 may include a PDCP PDU that has not yet been submitted to the main RLC entity 130 or to both the main RLC entity 130 and the split auxiliary RLC entity 132.

[0111] In some implementations, the RLC SDU or RLC PDU to be sent in the main RLC entity 130 may include at least one of the following: • RLC SDUs and RLC SDU segments that are not yet included in the RLC PDU, where an RLC SDU segment may be a fragment of an RLCSDU. • RLC PDU to be initially transmitted, or • RLC PDU (RLC AM) awaiting retransmission.

[0112] In some implementations, the UL data associated with the primary path includes a first set of data packets associated with the primary path. The first DSR includes the amount of data in the first set of data packets, and the remaining time of the first set of data packets is less than or equal to a first threshold used to trigger the reporting of the first DSR.

[0113] Consider the first example. In the first example, the PDCP discard timer value is equal to 50ms. Each of the first and second thresholds is equal to 15ms.

[0114] In the first example, the PDCP SDU or PDCP PDU to be routed to both the primary RLC entity 130 and the secondary RLC entity 132 includes packet #1 (RT=12ms) and packet #2 (RT=13ms). The PDCP SDU or PDCP PDU to be routed to the primary RLC entity 130 includes packet #1 (RT=12ms). The RLC SDU or RLC PDU to be sent in the primary RLC entity 130 includes packet #3 (RT=20ms). The UL data associated with the primary path includes packet #1 (RT=12ms), packet #2 (RT=13ms), and packet #3 (RT=20ms). The first set of packets associated with the primary path includes packet #1 (RT=12ms) and packet #2 (RT=13ms). The first DSR includes the data volume of the first set of packets, i.e., the data volume of packet #1 (RT=12ms) and packet #2 (RT=13ms).

[0115] Consider the second example. In the second example, the PDCP discard timer value is equal to 50ms. Each of the first and second thresholds is equal to 15ms.

[0116] In the second example, the PDCP SDU or PDCP PDU to be routed to both the primary RLC entity 130 and the secondary RLC entity 132 includes packet #1 (RT=12ms) and packet #2 (RT=13ms). The PDCP SDU or PDCP PDU to be routed to the primary RLC entity 130 includes packet #1 (RT=12ms). The RLC SDU or RLC PDU to be sent in the primary RLC entity 130 includes packet #3 (RT=20ms). The UL data associated with the primary path includes packet #1 (RT=12ms). The first set of packets associated with the primary path includes packet #1 (RT=12ms). The first DSR includes the data volume of the first set of packets, i.e., the data volume of packet #1 (RT=12ms).

[0117] Continue to refer to Figure 3 UE 104 sends a second DSR of 320 UL segmented bearer to the second base station 102-2 via the secondary path. The second DSR is associated with the secondary path.

[0118] In some implementations, UE 104 triggers a second DSR report if the minimum remaining time of the UL data associated with the secondary path is less than or equal to a second threshold used to trigger the reporting of the second DSR. The second threshold used to trigger the reporting of the second DSR is independent of or separate from the first threshold used to trigger the reporting of the first DSR. The value of the second threshold may be the same as or different from the value of the first threshold.

[0119] In some implementations, the UL data associated with the secondary path may include at least one of the following: • The PDCP SDU or PDCP PDU will be routed to the split secondary RLC entity 132 or to both the primary RLC entity 130 and the split secondary RLC entity 132. • RLC SDU or RLC PDU to be sent in the segmented auxiliary RLC entity 132.

[0120] In some implementations, the PDCP SDU that will be routed to the split secondary RLC entity 132 or to both the primary RLC entity 130 and the split secondary RLC entity 132 may include a PDCP SDU for which a PDCP PDU has not yet been constructed.

[0121] In some implementations, a PDCP PDU that will be routed to the split secondary RLC entity 132 or to both the primary RLC entity 130 and the split secondary RLC entity 132 may include a PDCP PDU that has not yet been submitted to either the secondary RLC entity 132 or both the primary RLC entity 130 and the split secondary RLC entity 132.

[0122] In some implementations, the RLC SDU or RLCP DU to be sent in the segmented secondary RLC entity 132 may include at least one of the following: • RLC SDUs and RLC SDU segments that are not yet included in the RLC PDU, where an RLC SDU segment may be a fragment of an RLCSDU. • RLC PDU to be initially transmitted, or • RLC PDU (RLC AM) awaiting retransmission.

[0123] In some implementations, the UL data associated with the secondary path includes a second set of data packets associated with the secondary path. The second DSR includes the amount of data in the second set of data packets, and the remaining time of the second set of data packets is less than or equal to a second threshold used to trigger the reporting of the second DSR.

[0124] Consider the third example. In the third example, the PDCP discard timer value is equal to 50ms. Each of the first and second thresholds is equal to 15ms.

[0125] In the first example, the PDCP SDU or PDCP PDU to be routed to both the primary RLC entity 130 and the segmented secondary RLC entity 132 includes packet #1 (RT=12ms) and packet #2 (RT=13ms). The PDCPSDU or PDCP PDU to be routed to the segmented secondary RLC entity 132 includes packet #2 (RT=13ms). The RLC SDU or RLCPDU to be sent in the segmented secondary RLC entity 132 includes packet #4 (RT=18ms). The UL data associated with the segmented secondary path includes packet #1 (RT=12ms), packet #2 (RT=13ms), and packet #4 (RT=18ms). The second set of packets associated with the secondary path includes packet #1 (RT=12ms) and packet #2 (RT=13ms). The second DSR includes the data volume of the second set of packets, i.e., the data volume of packet #1 (RT=12ms) and packet #2 (RT=13ms).

[0126] Consider the fourth example. In the fourth example, the PDCP discard timer value is equal to 50ms. Each of the first and second thresholds is equal to 15ms.

[0127] In the fourth example, the PDCP SDU or PDCP PDU to be routed to both the primary RLC entity 130 and the segmented secondary RLC entity 132 includes packet #1 (RT=12ms) and packet #2 (RT=13ms). The PDCPSDU or PDCP PDU to be routed to the segmented secondary RLC entity 132 includes packet #2 (RT=13ms). The RLC SDU or RLCPDU to be sent in the segmented secondary RLC entity 132 includes packet #4 (RT=18ms). The UL data associated with the segmented secondary path includes packet #2 (RT=13ms) and packet #4 (RT=18ms). The second set of packets associated with the secondary path includes packet #2 (RT=13ms). The second DSR includes the amount of data in the second set of packets, i.e., the amount of data in packet #2 (RT=13ms).

[0128] Alternatively, in some implementations, a single DSR is used for both the primary and secondary paths. A single threshold is configured to trigger DSR reporting. This will refer to... Figure 4 To describe.

[0129] Figure 4 A signaling diagram is illustrated, illustrating an example process 400 supporting UL data segmentation triggered by a delayed state according to various aspects of this disclosure. Process 400 can be considered as an example implementation of process 200. Process 400 may involve... Figure 1AOr UE 104, first base station 102-1, and second base station 102-2 in 1B. For discussion purposes, process 200 will refer to Figure 1A , 1B Or it can be described as 1C.

[0130] In process 400, the first base station 102-1 can act as the MgNB, and the second base station 102-2 can act as the SgNB. Alternatively, the first base station 102-1 can act as the SgNB, and the second base station 102-2 can act as the MgNB.

[0131] Actions 210, 220, and 230 in process 400 are similar to those in process 200. For the sake of brevity, the details of these actions have been omitted.

[0132] Process 400 differs from process 300 in actions 410 and 420.

[0133] Specifically, UE 104 sends a 410 UL-segmented DSR to the first base station 102-1 via the primary path. This DSR is associated with both the primary and secondary paths. Additionally, UE 104 sends a 420 UL-segmented DSR to the second base station 102-2 via the secondary path. In other words, the common DSR is used for both the primary and secondary paths.

[0134] In some implementations, UE 104 triggers a DSR report if the minimum remaining time of the UL data associated with both the primary and secondary paths is less than or equal to a threshold used to trigger the DSR report. In other words, a single threshold is configured to trigger the DSR report.

[0135] In some implementations, the UL data associated with both the primary and secondary paths may include at least one of the following: • The PDCP SDU or PDCP PDU to be sent; and • RLC SDU or RLC PDU to be sent in the main RLC entity 130 and the segmented auxiliary RLC entity 132.

[0136] In some implementations, the UL data associated with both the primary and secondary paths may include a third set of data packets. The DSR may include the amount of data in the third set of data packets, and the remaining time of the third set of data packets is less than or equal to the threshold used to trigger the reporting of the DSR.

[0137] Consider the fifth example. In the fifth example, the PDCP discard timer value is equal to 50ms. The threshold used to trigger DSR reporting is equal to 15ms.

[0138] In the fifth example, the PDCP SDU or PDCP PDU to be transmitted includes packet #1 (RT=12ms) and packet #2 (RT=13ms). The RLC SDU or RLC PDU to be transmitted in the primary RLC entity 130 includes packet #3 (RT=20ms). The RLC SDU or RLC PDU to be transmitted in the segmented secondary RLC entity 132 includes packet #4 (RT=18ms). The UL data associated with both the primary and secondary paths includes packet #1 (RT=12ms), packet #2 (RT=13ms), packet #3 (RT=20ms), and packet #4 (RT=18ms). The third set of data packets associated with both the primary and secondary paths includes packet #1 (RT=12ms) and packet #2 (RT=13ms). The DSR includes the amount of data in the third set of data packets, namely, the amount of data in packet #1 (RT=12ms) and packet #2 (RT=13ms).

[0139] In some implementations, the third packet set may include a first packet subset in the primary RLC entity 130, a second packet subset in the segmented secondary RLC entity 132, and a third packet subset in the PDCP entity 120.

[0140] Consider the fifth example again. In the fifth example, the first subset of groups in the main RLC entity 130 includes group #3 (RT=20ms), the second subset of groups in the split secondary RLC entity 132 includes group #4 (RT=18ms), and the third subset of groups in the PDCP entity 120 includes group #1 (RT=12ms) and group #2 (RT=13ms).

[0141] In some implementations, to determine the amount of data to be included in the DSR at MAC entities 140 and 142, the primary RLC entity 130 may provide a first data amount of a first subset of packets to the MAC entity 142 associated with the secondary RLC entity 132. The secondary RLC entity 132 may provide a second data amount of a second subset of packets to the MAC entity 140 associated with the primary RLC entity 130. The PDCP entity 120 may provide a third data amount of a third subset of packets to both MAC entities 140 and 142.

[0142] Alternatively, in some implementations, in order to determine the amount of data to be included in the DSR at MAC entity 140 and MAC entity 142, MAC entity 140 may provide MAC entity 142 with a first data amount of a first subset of packets. MAC entity 142 may provide MAC entity 140 with a second data amount of a second subset of packets. PDCP entity 120 may provide MAC entity 140 and MAC entity 142 with a third data amount of a third subset of packets, respectively.

[0143] In some implementations, UL segmentation is only applied to specific PDU sets (e.g., PDU sets with low importance or low PDU set importance (PSI)). When UL segmentation is triggered, UE 104 only transmits the PDU set with specific importance via the secondary path. This will refer to... Figure 5 To describe.

[0144] Figure 5 A signaling diagram is illustrated, illustrating an example process 500 supporting UL data segmentation triggered by a delayed state according to various aspects of this disclosure. Process 500 can be considered as an example implementation of process 200. Process 500 may involve... Figure 1A Or UE 104, first base station 102-1, and second base station 102-2 in 1B. For discussion purposes, process 200 will refer to Figure 1A , 1B Or it can be described as 1C.

[0145] like Figure 5 As shown, UE 104 receives the configuration of 510 DRBs from the first base station 102-1. Alternatively, UE 104 may receive the configuration of the DRBs from the second base station 102-2. The configuration of the DRBs may indicate that the DRBs are configured as UL-segmented DRBs in NR-DC.

[0146] In process 500, the first base station 102-1 can act as the MgNB, and the second base station 102-2 can act as the SgNB. Alternatively, the first base station 102-1 can act as the SgNB, and the second base station 102-2 can act as the MgNB.

[0147] UE 104 receives a 515 indication from the first base station 102-1, which indicates that the secondary path is used for at least one set of PDUs with at least one value of PSI. Alternatively, UE 104 may receive an indication from the second base station 102-2.

[0148] In some implementations, the first base station 102-1 or the second base station 102-2 may indicate the primary and secondary paths of the UL-segmented DRB. Information about the primary path may include information indicating the cell group ID and LCID of the primary RLC entity 130. Information about the secondary path may indicate the LCID of the segmented secondary RLC entity 132, and that this RLC entity belongs to a different cell group than the one used for the primary path.

[0149] UE 104 receives 520 from the first base station 102-1 at least one UL segmentation threshold associated with the delay state for a UL segmented bearer. Alternatively, UE 104 may receive at least one UL segmentation threshold associated with the delay state for a UL segmented bearer from the second base station 102-2. Action 520 in procedure 500 is similar to action 220 in procedures 200, 300, and 400. For brevity, the details of this action are omitted.

[0150] Subsequently, UE 104 triggers 530 for UL segmentation of at least one PDU set based on at least one UL segmentation threshold. In other words, based on at least one UL segmentation threshold, UE 104 uses a secondary path for UL data transmission of at least one PDU set having at least one PSI value, and uses a primary path for UL data transmission of all PDU sets except for at least one PDU set having at least one PSI value.

[0151] For example, at least one PDU set with at least one value of PSI includes a first PDU set with a first value of PSI and a second PDU set with a second value of PSI. If the minimum remaining time of the UL data is less than or equal to a first UL segmentation threshold for the remaining time, then PDCP entity 120 submits PDCP PDUs from either the first or second PDU set to the segmentation auxiliary RLC entity 132. Otherwise, PDCP entity 120 submits PDCP PDUs from either the first or second PDU set to the main RLC entity 130.

[0152] UE 104 sends the first DSR of the 540 UL segmented bearer to the first base station 102-1 via the main path. The first DSR is associated with the main path.

[0153] In some implementations, UE 104 triggers the reporting of the first DSR if the minimum remaining time of the UL data associated with the primary path is less than or equal to a first threshold used to trigger the reporting of the first DSR.

[0154] Unlike process 300, in process 500, the UL data associated with the main path includes all PDU sets except for at least one PDU set with at least one PDU set having at least one PSI value. For example, the UL data associated with the main path includes all PDU sets except for the first PDU set and the second PDU set.

[0155] UE 104 sends a second DSR of 550 UL segmented bearer to the second base station 102-2 via the secondary path. The second DSR is associated with the secondary path.

[0156] In some implementations, UE 104 triggers a second DSR report if the minimum remaining time of the UL data associated with the secondary path is less than or equal to a second threshold used to trigger the reporting of the second DSR. The second threshold used to trigger the reporting of the second DSR is independent of or separate from the first threshold used to trigger the reporting of the first DSR. The value of the second threshold may be the same as or different from the value of the first threshold.

[0157] Unlike process 300, in process 500, the UL data associated with the secondary path includes at least one set of PDUs having at least one value of PSI. For example, the UL data associated with the secondary path includes a first set of PDUs and a second set of PDUs.

[0158] Referenced Figure 2 and Figure 3 Some of the implementations described also apply to procedure 500. For the sake of brevity, the details of these implementations have been omitted.

[0159] Figure 6 A signaling diagram is illustrated, which illustrates an example process 600 supporting PDCP replication triggered by a delayed state according to various aspects of this disclosure. Process 600 may involve... Figure 1A Or UE 104 in 1B and either the first base station 102-1 or the second base station 102-2. For discussion purposes, process 600 will refer to Figure 1A , 1B Or it can be described as 1C.

[0160] like Figure 6 As shown, UE 104 receives 610 from either the first base station 102-1 or the second base station 102-2 at least one threshold for triggering PDCP replication. PDCP replication is also referred to as replication at PDCP.

[0161] In some implementations, the first base station 102-1 can act as a MgNB, and the second base station 102-2 can act as a SgNB. Alternatively, the first base station 102-1 can act as an SgNB, and the second base station 102-2 can act as a MgNB.

[0162] Subsequently, UE 104 triggers 620 PDCP replication based on at least one threshold.

[0163] In some implementations, when PDCP replication is configured for radio bearers, at least one secondary RLC entity 132 is added to the radio bearer to process the replicated PDCP PDU. The logical channel corresponding to the primary RLC entity 130 is referred to as the primary logical channel, and the logical channel corresponding to the secondary RLC entity 132 is referred to as the secondary logical channel.

[0164] In some implementations, when PDCP replication is triggered, UE 104 replicates the PDCP PDU and uses the primary path associated with the primary RLC entity 130 for the UL transmission of the PDCP PDU, and uses the secondary path associated with the segmented secondary RLC entity 132 for the UL transmission of the replicated PDCP PDU. Therefore, replication at PDCP refers to submitting the same PDCP PDU multiple times: once to each active RLC entity used for radio bearers.

[0165] In some implementations, at least one threshold used to trigger PDCP replication may include a third threshold for the remaining time associated with the delay state. If the minimum remaining time of the UL data is less than or equal to the third threshold for the remaining time, UE 104 may use the primary path for UL transmission of the PDCP PDU and the secondary path for UL transmission of the replicated PDCPPDU.

[0166] In some implementations, at least one threshold used to trigger PDCP replication may include a fourth threshold for the amount of data associated with the delay state. If the amount of data associated with the delay state is greater than or equal to the fourth threshold for the amount of data, UE 104 may use the primary path for UL transmission of the PDCP PDU and the secondary path for UL transmission of the replicated PDCPPDU.

[0167] In some implementations, at least one threshold used to trigger PDCP replication may include a third threshold for the remaining time associated with the delay state and a fourth threshold for the amount of data associated with the delay state. If the remaining time of the UL data is less than or equal to the third threshold for the remaining time, and the amount of data associated with the delay state is greater than or equal to the fourth threshold for the amount of data, then UE 104 may use the primary path for UL transmission of the PDCP PDU and the secondary path for UL transmission of the replicated PDCP PDU.

[0168] In some implementations, process 600 can be executed in combination with any of processes 200 to 500. For example, actions 610 and 620 can be executed after actions in any of processes 200 to 500.

[0169] Already referenced Figures 2 to 5 Some of the implementations described also apply to process 600. For the sake of brevity, the details of these implementations have been omitted.

[0170] Figure 7An example of a device 700 supporting UL data segmentation triggered by a delayed state according to various aspects of this disclosure is illustrated. Device 700 may be an example of a base station 102 or UE 104 as described herein. Device 700 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 700 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 702, a memory 704, a transceiver 708, and optionally an I / O controller 708. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., a bus).

[0171] Processor 702, memory 704, transceiver 708, or various combinations thereof or various components thereof may be examples of components for performing aspects of the present disclosure as described herein. For example, processor 702, memory 704, transceiver 708, or various combinations thereof or components thereof may support methods for performing one or more of the operations described herein.

[0172] In some implementations, processor 702, memory 704, transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 702 and memory 704 coupled to processor 702 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 704 are executed by processor 702).

[0173] For example, according to the examples disclosed herein, processor 702 may support wireless communication at device 700. Processor 702 may be configured to operate to support components for: receiving at the UE at one of a first base station and a second base station, the at least one UL segmentation threshold being associated with a delay state for a UL segmented bearer; and, based on the at least one UL segmentation threshold, performing UL data transmission of the UL segmented bearer using both a primary path associated with the UE's primary RLC entity and a secondary path associated with the UE's segmented secondary RLC entity.

[0174] Processor 702 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 702 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 702. Processor 702 may be configured to execute computer-readable instructions stored in memory (e.g., memory 704) to cause device 700 to perform various functions of this disclosure.

[0175] Memory 704 may include random access memory (RAM) and read-only memory (ROM). Memory 704 may store computer-readable, computer-executable code, including instructions that, when executed by processor 702, cause device 700 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 702, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 704 may include a basic I / O system (BIOS) or similar system that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0176] I / O controller 708 can manage input and output signals for device 700. I / O controller 708 can also manage peripheral devices not integrated into device 700. In some implementations, I / O controller 708 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 708 can utilize an operating system such as iOS®, Android®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 708 can be implemented as part of a processor (such as processor 708). In some implementations, a user can interact with device 700 via I / O controller 708 or via hardware components controlled by I / O controller 708.

[0177] In some implementations, device 700 may include a single antenna 710. However, in other implementations, device 700 may have more than one antenna 710 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 708 may communicate bidirectionally via one or more antennas 710, wired or wireless links as described herein. For example, transceiver 708 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 708 may also include a modem for modulating packets to provide modulated packets to one or more antennas 710 for transmission, and for demodulating packets received from one or more antennas 710. Transceiver 708 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0178] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing it for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes (e.g., phase shift keying (PSK) or quadrature amplitude modulation (QAM)). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 710 for transmitting the amplified signal over the air or wireless medium.

[0179] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 710 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0180] Figure 8An example of a processor 800 supporting UL data segmentation triggered by a delayed state, according to various aspects of this disclosure, is illustrated. Processor 800 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 800 may include a controller 802 configured to perform various operations according to the examples described herein. Processor 800 may optionally include at least one memory 804, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 800 may optionally include one or more arithmetic logic units (ALUs) 806. One or more of these components may be electronically or otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0181] Processor 800 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., processor 800)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0182] Controller 802 can be configured to manage and coordinate various operations of processor 800 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 800 to support the various operations described herein. For example, controller 802 can operate as a control unit of processor 800, generating control signals that manage the operation of various components of processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating operation timing.

[0183] Controller 802 may be configured to fetch (e.g., retrieve, retrieve, receive) instructions from memory 804 and determine subsequent instructions(s) to be executed, enabling processor 800 to support various operations as described herein. Controller 802 may be configured to track memory addresses of instructions associated with memory 804. Controller 802 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 802 may be configured to interpret instructions and determine control signals to be output to other components of processor 800, enabling processor 800 to support various operations as described herein. Alternatively or additionally, controller 802 may also be configured to manage data flow within processor 800. Controller 802 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 800.

[0184] Memory 804 may include one or more caches (e.g., memory local to or included in processor 800) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 804 may be located inside or on the processor chipset (e.g., local to processor 800). In some other implementations, memory 804 may be located outside the processor chipset (e.g., remote from processor 800).

[0185] Memory 804 may store computer-readable, computer-executable code, including instructions that, when executed by processor 800, cause processor 800 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 802 and / or processor 800 may be configured to execute the computer-readable instructions stored in memory 804 to cause processor 800 to perform various functions. For example, processor 800 and / or controller 802 may be coupled to or coupled to memory 804, and processor 800, controller 802, and memory 804 may be configured to perform the various functions described herein. In some examples, processor 800 may include multiple processors, and memory 804 may include multiple memories. One or more processors may be coupled to one or more memories, which may be configured individually or collectively to perform the various functions described herein.

[0186] One or more ALU 806s can be configured to support various operations according to the examples described herein. In some implementations, one or more ALU 806s may reside within or on a processor chipset (e.g., processor 800). In some other implementations, one or more ALU 806s may reside outside the processor chipset (e.g., processor 800). One or more ALU 806s can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 806s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 806s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALU 806s may support logical operations such as AND, OR, XOR, NOR, and NAND, thereby enabling one or more ALU 806s to handle conditional operations, comparisons, and bitwise operations.

[0187] Processor 800 may support wireless communication according to the examples disclosed herein. Processor 800 may be configured to operate to support components for: receiving at the UE at one of a first base station and a second base station, the at least one UL segmentation threshold being associated with a delay state for a UL segmented bearer; and, based on the at least one UL segmentation threshold, performing UL data transmission of the UL segmented bearer using both a primary path associated with the UE's primary RLC entity and a secondary path associated with the UE's segmented secondary RLC entity.

[0188] Figure 9 A flowchart illustrating a method 900 for UL data segmentation triggered by a delayed state according to various aspects of this disclosure is provided. Operation of method 900 can be implemented by the device or components thereof described herein. For example, operation of method 900 can be performed by the UE 104 described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the described functions. Alternatively or concurrently, the device may also use dedicated hardware to perform aspects of the described functions.

[0189] At 910, the method may include: receiving at the UE at one of a first base station and a second base station at least one UL segmentation threshold, the at least one UL segmentation threshold being associated with a delay state for a UL segmentation bearer. The operation of 910 can be performed according to the examples described herein. In some implementations, aspects of the operation of 910 may be derived from references... Figure 1A Or the device described in 1B can be used for execution.

[0190] At 920, the method may include: performing UL segmentation-bearing UL data transmission using both the primary path associated with the UE's primary RLC entity and the secondary path associated with the UE's segmentation secondary RLC entity, based on at least one UL segmentation threshold. The operation at 920 can be performed according to the examples described herein. In some implementations, aspects of the operation at 920 may be derived from references... Figure 1A Or the device described in 1B can be used for execution.

[0191] It should be noted that reference has been made. Figures 2 to 6 The implementation of this disclosure described herein is also applicable to device 900, processor 800, and method 900.

[0192] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0193] The various illustrated boxes and components described in connection with this disclosure may be implemented or performed by the following: a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0194] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, these functions can be stored on a computer-readable medium or sent to that computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of the foregoing. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the function are implemented at different physical locations.

[0195] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose computer or a special-purpose computer. For example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and can be accessed by a general-purpose computer or a special-purpose computer, or a general-purpose processor or a special-purpose processor.

[0196] As used herein, including in the claims, the article “a” preceding an element is not limited and is understood to mean “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are used interchangeably. As used herein, including in the claims, the word “or” used as a list of items (e.g., a list of items prefixed with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Additionally, as used herein, the phrase “based on” should not be construed as referring to a closed set of conditions. For example, an example step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0197] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), comprising: processor; as well as The transceiver coupled to the processor, The processor is configured as follows: At least one uplink (UL) segmentation threshold is received from one of the first and second base stations via the transceiver, the at least one UL segmentation threshold being associated with a delay state for a UL segmented bearer; as well as Based on the at least one UL segmentation threshold, UL data transmission of the UL segmentation bearer is performed using both the primary path associated with the UE's primary radio link control (RLC) entity and the secondary path associated with the UE's segmentation secondary RLC entity.

2. The UE according to claim 1, wherein: The at least one UL segmentation threshold includes a first UL segmentation threshold for the remaining time associated with the delay state; and The processor is configured to perform UL data transmission of the UL segmented bearer using both the primary path and the secondary path as follows: Based on the determination that the minimum remaining time of the UL data is less than or equal to the first UL segmentation threshold used for the remaining time, the UL data transmission carried by the UL segmentation is performed using both the main path and the secondary path.

3. The UE according to claim 1, wherein: The at least one UL segmentation threshold includes a second UL segmentation threshold for the amount of data associated with the delay state; and The processor is configured to perform UL data transmission of the UL segmented bearer using both the primary path and the secondary path as follows: Based on the determination that the amount of data associated with the delay state is greater than or equal to the second UL segmentation threshold for the amount of data, the UL data transmission carried by the UL segmentation is performed using both the primary path and the secondary path.

4. The UE according to claim 1, wherein: The at least one UL segmentation threshold includes a first UL segmentation threshold for the remaining time associated with the delay state and a second UL segmentation threshold for the amount of data associated with the delay state; and The processor is configured to perform UL data transmission of the UL segmented bearer using both the primary path and the secondary path as follows: Based on the determination that the minimum remaining time of the UL data is less than or equal to the first UL segmentation threshold for the remaining time, and the amount of data associated with the delay state is greater than or equal to the second UL segmentation threshold for the amount of data, the UL data transmission carried by the UL segmentation is performed using both the primary path and the secondary path.

5. The UE of claim 3 or 4, wherein the amount of data associated with the delay state includes one of the following: The first data volume of a first set of packets associated with the primary path, wherein the remaining time of the first set of packets is less than or equal to a threshold for triggering a Delay Status Report (DSR) report. The second data volume of the second data packet set associated with the secondary path, wherein the remaining time of the second data packet set is less than or equal to the threshold for triggering the DSR report, or The sum of the first data volume and the second data volume.

6. The UE of claim 1, wherein the at least one UL segmentation threshold includes a third UL segmentation threshold; and The processor is configured to perform UL data transmission of the UL segmented bearer using both the primary path and the secondary path as follows: Based on the determination that the total amount of the first data volume to be transmitted in the Packet Data Convergence Protocol (PDCP) entity of the UE and the total amount of the second data volume to be initially transmitted in the primary RLC entity and the secondary RLC entity of the UE are equal to or greater than the third UL segmentation threshold, the UL data transmission carried by the UL segmentation is performed using both the primary path and the secondary path.

7. The UE according to claim 1, wherein the processor is further configured to: The transceiver transmits a first Delay Status Report (DSR) of the UL segmented bearer and a second DSR of the UL segmented bearer to the first base station and the second base station via the main path and the secondary path, respectively, wherein the first DSR is associated with the main path and the second DSR is associated with the secondary path.

8. The UE according to claim 7, wherein: The processor is also configured to: The reporting of the first DSR is triggered based on the determination that the minimum remaining time of the UL data associated with the main path is less than or equal to a first threshold for triggering the reporting of the first DSR. as well as The UL data associated with the main path includes at least one of the following: Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) or PDCP Protocol Data Unit (PDU) will be routed to the primary RLC entity or to both the primary RLC entity and the split secondary RLC entity. as well as The RLC SDU or RLC PDU will be sent in the main RLC entity.

9. The UE of claim 8, wherein the UL data associated with the primary path includes a first set of data packets associated with the primary path, the first DSR includes the amount of data in the first set of data packets, and the remaining time of the first set of data packets is less than or equal to the first threshold for triggering the reporting of the first DSR.

10. The UE according to claim 7, wherein: The processor is also configured to: The reporting of the second DSR is triggered based on the determination that the minimum remaining time of the UL data associated with the secondary path is less than or equal to a second threshold used to trigger the reporting of the second DSR; and The UL data associated with the secondary path includes at least one of the following: Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) or PDCP Protocol Data Unit (PDU) will be routed to the Segmented Secondary RLC Entity or to both the Primary RLC Entity and the Segmented Secondary RLC Entity. as well as The RLC SDU or RLC PDU will be sent in the segmented auxiliary RLC entity.

11. The UE of claim 1, wherein the processor is further configured to: The transceiver transmits the Delay Status Report (DSR) of the UL segmented bearer to the first base station and the second base station via the main path and the secondary path, respectively, wherein the DSR is associated with both the main path and the secondary path.

12. The UE according to claim 11, wherein: The processor is also configured to: The DSR reporting is triggered based on the fact that the minimum remaining time of the UL data associated with both the primary path and the secondary path is less than or equal to a threshold used to trigger the DSR reporting; and The UL data associated with both the primary path and the secondary path includes at least one of the following: The Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) or PDCP Protocol Data Unit (PDU) to be sent; and RLC SDU or RLC PDU to be sent in the main RLC entity and the segmented auxiliary RLC entity.

13. The UE of claim 12, wherein the UL data associated with both the primary path and the secondary path includes a third data packet set associated with both the primary path and the secondary path, the DSR includes the amount of data in the third data packet set, and the remaining time of the third data packet set is less than or equal to the threshold used to trigger the reporting of the DSR.

14. The UE according to claim 13, wherein the third data packet set includes a first data packet subset in the primary RLC entity, a second data packet subset in the segmented secondary RLC entity, and a third data packet subset in the UE's PDCP entity.

15. The UE of claim 14, wherein the processor is further configured to: Provide a first data volume of the first data packet subset from the primary RLC entity to the second media access control (MAC) entity of the UE associated with the segmented secondary RLC entity; Provide a second amount of data from the second subset of data packets from the segmented secondary RLC entity to the first MAC entity of the UE associated with the primary RLC entity; as well as The third data volume of the third data packet subset from the PDCP entity is provided to the first MAC entity and the second MAC entity respectively.

16. The UE of claim 14, wherein the processor is further configured to: Provide a first data volume of the first subset of data packets from the MAC entity of the UE associated with the primary RLC entity to the second media access control (MAC) entity of the UE associated with the secondary RLC entity; Provide the first MAC entity with a second data volume of the second subset of the second data packets from the second MAC entity; as well as The third data volume of the third data packet subset from the PDCP entity is provided to the first MAC entity and the second MAC entity respectively.

17. The UE according to claim 1, wherein: The processor is also configured to: The transceiver receives an indication from one of the first base station and the second base station, the indication indicating that the secondary path is used for at least one set of PDUs having at least one value of Protocol Data Unit (PDU) Set Importance (PSI); as well as The processor is configured to perform UL data transmission of the UL segmented bearer using both the primary path and the secondary path as follows: Based on the instruction, UL data transmission of the at least one PDU set having the at least one value of PSI is performed using the secondary path.

18. The UE of claim 17, wherein the processor is further configured to: The transceiver transmits a first Delay Status Report (DSR) of the UL segmented bearer and a second DSR of the UL segmented bearer to the first base station and the second base station via the main path and the secondary path, respectively, wherein the first DSR is associated with the main path and the second DSR is associated with the secondary path.

19. A processor for wireless communication, comprising: At least one memory; as well as A controller coupled to the at least one memory, and configured such that the controller: Receive at least one uplink (UL) segmentation threshold from one of the first base station and the second base station, the at least one UL segmentation threshold being associated with a delay state for a UL segmented bearer; as well as Based on the at least one UL segmentation threshold, UL data transmission of the UL segmentation bearer is performed using both the primary path associated with the UE's primary radio link control (RLC) entity and the secondary path associated with the UE's segmentation secondary RLC entity.

20. A method for wireless communication, comprising: At the user equipment (UE), at least one uplink (UL) segmentation threshold is received from one of the first and second base stations, the at least one UL segmentation threshold being associated with a delay state for a UL segmentation bearer; as well as Based on the at least one UL segmentation threshold, UL data transmission of the UL segmentation bearer is performed using both the primary path associated with the UE's primary radio link control (RLC) entity and the secondary path associated with the UE's segmentation secondary RLC entity.

Images